# 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 9
# self = https://watcher.sour.is/conv/yh3bdga
@bml Having read the spec I think it really was an April fools joke 🤣
@bml Having read the spec I think it really was an April fools joke 🤣
@bml Having read the spec I think it really was an April fools joke 🤣
@ It was totally an April Fools' joke; the IETF has a bunch of those. But! It has also been implemented. And 418 is my favorite error code.
@ It was totally an April Fools' joke; the IETF has a bunch of those. But! It has also been implemented. And 418 is my favorite error code.
@bml Yup, several. My favorite is RFC 1149, another that's since been implemented. https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments
@bml Yup, several. My favorite is RFC 1149, another that's since been implemented. https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments
@unknown thank you this. lol, there's an RFC for Hypertext Jeopardy Protocol (HTJP/1.0)