# 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 1
# self = https://watcher.sour.is/conv/tvfc4xq
{@https://lyse.isobeef.org/twtxt.txt>#q3uhika} @vain @prologic (#yjtzdka) The "+00:00 to Z" thing comes from Go's internal time handling. time.RFC3339 will always produce Z rather than +00:00. I doubt that it is possible to keep the original information in the time.Time object itself, whether +00:00 or Z was parsed from the _twtxt.txt_, so I took the lazy route of just defining Go's behavior in the spec. That's also why UTC must be used, if the original date does not specify a timezone at all. For a quick and easy hash calculation it would be ideal to hash the exact twt line without the twter URL, but that would have been a tiny bit bigger change I didn't have the courage to suggest.