# 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 6
# self = https://watcher.sour.is/conv/ke37fpq
@prologic why is yarn not in the github.com/buckket/twtxt readme?
@lukas Long story. :-) Felix is... not entirely happy with this project. :-)
@lukas I think this might shed some light on the background. Bottomline, @prologic used (and registered the domain for) twtxt originally---his *yarnd* pod still runs at twtxt.net---which was the name chosen by buckket for his client, and format specification.
I would had probably gotten annoyed, perhaps mad for a while, too. But that's about it. It comes to show everyone is, and acts, differently.
@lukas Because we have little to nothing to do with Felix’s original Twtxt project he started back in 2016 which subsequently died as quickly as it began 😢
Yes Yarn.social uses Twtxt as it’s underlying spec + regular Web HTTP as it’s protocol and we extended the specs which we publish at https://dev.twtxt.net 👌
@lukas Because we have little to nothing to do with Felix’s original Twtxt project he started back in 2016 which subsequently died as quickly as it began 😢
Yes Yarn.social uses Twtxt as it’s underlying spec + regular Web HTTP as it’s protocol and we extended the specs which we publish at https://dev.twtxt.net 👌
@lukas Because we have little to nothing to do with Felix’s original Twtxt project he started back in 2016 which subsequently died as quickly as it began 😢
Yes Yarn.social uses Twtxt as it’s underlyi