#indieweb
2014-10-22
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
#indieweb
≡
←
→
2014-10-22
UTC
#
21:49
joskar
aaronpk: Are there any special parsing rules about p-* and nested h-* that I'm unaware of? The p-in-reply-to wont resolve to a URL when it's parsed (at least not the examples in
/reply-context)
joskar aaronpk: Are there any special parsing rules about p-* and nested h-* that I'm unaware of? The p-in-reply-to wont resolve to a URL when it's parsed (at least not the examples in /reply-context)