# 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 3
# self = https://watcher.sour.is/conv/j3xacqa
eapl.me
eapl.me
View Thread
I'd like to know more about what andros and prologic are talking about, I feel lost.

"This will be managed by Registries." Are we talking about these registries?
https://twtxt.readthedocs.io/en/latest/user/registry.html
lyse
lyse.isobeef.org
View Thread
@eapl.me Yes, I believe so.
prologic
twtxt.net
View Thread
@eapl.me@eapl.me I _think_ the general idea that we're settling on here is that maybe we can build a simple solution to this whole "wtf is this hash?" problem. yarnd already forms a sort-of "distributed network" amongst its peers and whilsts uses Twtxt (_of course_) is both decentralised and distributed. Nothing wrong with that. -- I tried to build a search engine and crawler, but getting that resource efficient and useful is hard™.

So if we can have a small network of participating members of the community forming a "distributed network" of the Twtxt™ space, we can solve this problem quite easily. We could even put some GeoDNS routing in place and a single A record/domain to make things even easier. Let's call it s "Registry Service" if you will :)