#dev
2021-06-05
Prev
Next
#indieweb
#dev
#wordpress
#meta
#stream
#microformats
#known
#events
search
-5 GMT
Africa/Accra
Africa/Tunis
America/Boise
America/Chicago
America/Denver
America/Detroit
America/Edmonton
America/Halifax
America/Los_Angeles
America/Los_angeles
America/Mexico_City
America/Monterrey
America/Montreal
America/New_York
America/Phoenix
America/Santiago
America/Sao_Paulo
America/Toronto
America/Vancouver
Asia/Bangkok
Asia/Calcutta
Asia/Kolkata
Asia/Kuala_Lumpur
Asia/Kuching
Asia/Manila
Asia/Seoul
Asia/Tehran
Asia/Tokyo
Atlantic/Faroe
Atlantic/Reykjavik
Australia/Adelaide
Australia/Brisbane
Australia/Melbourne
Australia/Perth
Australia/Queensland
Australia/Sydney
CET
Canada/Eastern
Europe/Amsterdam
Europe/Athens
Europe/Belfast
Europe/Belgrade
Europe/Berlin
Europe/Brussels
Europe/Budapest
Europe/Copenhagen
Europe/Dublin
Europe/Helsinki
Europe/Istanbul
Europe/Lisbon
Europe/London
Europe/Luxembourg
Europe/Madrid
Europe/Moscow
Europe/Paris
Europe/Prague
Europe/Rome
Europe/Stockholm
Europe/Zurich
GMT
Pacific/Auckland
US/Central
US/Eastern
US/Pacific
UTC
#dev
≡
←
→
2021-06-05
UTC
#
19:23
barnaby
it would mean that server implementations can broadly apply CSRF protection to the authorization endpoint, where it’s important, and leave it off the token endpoint, where it shouldn’t be used
