# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 35
# self = https://watcher.sour.is/conv/qvykv7a
changing the timezone encoding in #phpub2twtxt
changing the timezone encoding in #phpub2twtxt
changing the timezone encoding in #phpub2twtxt
@sorenpeter What did you change it to? You must use RFC 3339
@sorenpeter What did you change it to? You must use RFC 3339
@sorenpeter What did you change it to? You must use RFC 3339
@sorenpeter @prologic changed the suffix from +00:00 to Z
@sorenpeter @prologic changed the suffix from +00:00 to Z
@sorenpeter @darch Is that still RFC 3339 compliant? I’m not at my computer to check 🤔
@sorenpeter @darch Is that still RFC 3339 compliant? I’m not at my computer to check 🤔
@sorenpeter @darch Is that still RFC 3339 compliant? I’m not at my computer to check 🤔
@prologic it seem to work just fine for the most part. http://darch.dk/twtxt.txt for refernce
@prologic it seem to work just fine for the most part. http://darch.dk/twtxt.txt for refernce
@prologic it seem to work just fine for the most part. http://darch.dk/twtxt.txt for refernce
@prologic it seem to work just fine for the most part. http://darch.dk/twtxt.txt for refernce
@prologic @sorenpeter Z is for zero, so it just another way of saying +00:00. i makes thes txtxt.txt more readable in the raw
@prologic @sorenpeter Z is for zero, so it just another way of saying +00:00. i makes thes txtxt.txt more readable in the raw
👍
👍
👍
@darch The “Z” is fine, but date and time really have to be separated by a “T”, IIUC. 🙂 That one twt on http://darch.dk/twtxt.txt is broken, IMO.
@darch The “Z” is fine, but date and time really have to be separated by a “T”, IIUC. 🙂 That one twt on http://darch.dk/twtxt.txt is broken, IMO.
@darch The “Z” is fine, but date and time really have to be separated by a “T”, IIUC. 🙂 That one twt on http://darch.dk/twtxt.txt is broken, IMO.
@darch The “Z” is fine, but date and time really have to be separated by a “T”, IIUC. 🙂 That one twt on http://darch.dk/twtxt.txt is broken, IMO.
@vain I read somewhere that you could use a space instead of the "T" as still comply with RFC 3339. But I put the "T" back after testing it and found that it did not work with twtxt.net ;)
@vain I read somewhere that you could use a space instead of the "T" as still comply with RFC 3339. But I put the "T" back after testing it and found that it did not work with twtxt.net ;)
@sorenpeter @prologic @darch @vain The "Z" is even required over "+00:00" according to our Twt Hash Extension Specification. The ABNF for RFC 3339 states, that "T" has to be used. But the second note below can be interpreted such that RFC 3339 also permits a space. Up until now I always read this as they refer to ISO 8601 with the space rather than RFC 3339.
@sorenpeter @prologic @darch @vain Well, "Z" vs. "+00:00" only matters for the twt hash, not the timestamp of the twt.
@prologic test. Running new parser on txt.sour.is. :D
@prologic test. Running new parser on txt.sour.is. :D
@prologic test. Running new parser on txt.sour.is. :D
@prologic test. Running new parser on txt.sour.is. :D
yeah you need to follow the spec 🙃
yeah you need to follow the spec 🙃
yeah you need to follow the spec 🙃