#dev
2020-10-03
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/Sao_Paulo
America/Toronto
America/Vancouver
Asia/Bangkok
Asia/Calcutta
Asia/Kolkata
Asia/Kuala_Lumpur
Asia/Manila
Asia/Seoul
Asia/Tehran
Asia/Tokyo
Atlantic/Faroe
Atlantic/Reykjavik
Australia/Adelaide
Australia/Brisbane
Australia/Melbourne
Australia/Perth
Australia/Sydney
CET
Canada/Eastern
Europe/Amsterdam
Europe/Athens
Europe/Belfast
Europe/Belgrade
Europe/Berlin
Europe/Brussels
Europe/Copenhagen
Europe/Dublin
Europe/Helsinki
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
≡
←
→
2020-10-03
UTC
#
22:03
GWG
aaronpk: If you look at the W3C version of the spec, it says to verify an authorization code, which is the previous post option to the authorization endpoint, section 5.4 of the W3C edition, you only needed code, client_id, and redirect_uri