# 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 11
# self = https://watcher.sour.is/conv/ngibdfq
or timeline.txt ;)
or timeline.txt ;)
or timeline.txt ;)
or timeline.txt ;)
You can call it whatever you want, that’s the beauty of it. There is no need to set a “standard” for this. To prove it, I will setup one feed, and name the file “sørenpeter.txt”. 🤭
good luck with the doughnut on a stick in a URL
good luck with the doughnut on a stick in a URL
good luck with the doughnut on a stick in a URL
good luck with the doughnut on a stick in a URL
yep, my point is that the txt part is redundant for *twtxt*

Also a .txt file could be in any format, for example those plans from John Carmak are stored now as .txt -> https://github.com/ESWAT/john-carmack-plan-archive/blob/master/by_day/johnc_plan_19960218.txt
Although being named .plan was expected for them to work, if I recall correctly -> http://www.catb.org/jargon/html/P/plan-file.html
yep, my point is that the txt part is redundant for *twtxt*

Also a .txt file could be in any format, for example those plans from John Carmak are stored now as .txt -> https://github.com/ESWAT/john-carmack-plan-archive/blob/master/by_day/johnc_plan_19960218.txt
Although being named .plan was expected for them to work, if I recall correctly -> http://www.catb.org/jargon/html/P/plan-file.html