# 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/gwuwxmq
prologic-twtxt-atom-feed
feeds.twtxt.net
View Thread
(#zbsrabq) In other words, choosing to follow an actor does not follow the same model as Yarn/Twtxt does, where we then decide to "fetch" their ...
In other words, choosing to follow an actor does not follow the same model as Yarn/Twtxt does, where we then decide to “fetch” their feed. In fact it’s the other way around, you end up telling server X that you’re interested in actor Y, and servers X will then “push” stuff back to you. You can see how this can lead to some of the infamous DoS behaviours that can occur in the wild 🤣 ⌘ Read more