# 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 5
# self = https://watcher.sour.is/conv/tqapeoa
One of the things that attracts me about the "twtxt social network" is how radically decentralized it is. Not only each user is its own node (maintaining its own text file feed), there's no limits to the protocols used to access each feed. Sure, most of the feeds are probably being served over http or https, but there are feeds being served over gopher, and I bet some of them over ftp/ftps. But it doesn't have to be that way - feeds can be distributed in any modern equivalent to the sneakernet, you can save yours in a usb stick or a floppy disk, hand it over by hand or send it via postal mail; you can distributed them on a mailing list, on the usernet... The limit is your imagination.
This reflection made me realize that there's no reason to wait for secushare, twtxt feeds can already be used, shared, maintained and spread on GNUnet, taking this social media platform to the GNU Internet.
@marado I'm serving my twtxt in Spanish on Gemini as well, and perhaps we could serve Yarn/twtxt.net on a proxy.
I like that the 'protocol' goes beyond federalization and it's mostly decentralized, with some inherent disadvantages like discoverability, so you can federate it, have pods, instances, directories and such. I'm missing some interoperation like on ActivityPub but not having it is a kind of feature.
For me is like a self hosted blog with RSS.