# 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 7
# self = https://watcher.sour.is/conv/nnr7z6a
Well, I'm surprised of the simple concept twtxt is, and the implications of it.
Perhaps I don't like that's too related with Twitter, but is a powerful reference point too, so... #dealWithIt
@eaplmx Twtxt is just the spec we use in conjunction with standard Web HTTP as the underlying "protocol". We extended small parts of the spec at dev.twtxt.net to support at a bare minimum things people expect to see of a "social media". Actually what you're on here twtxt.net is my pod, one of many, and a Yarn.social pod 😉
@eaplmx Twtxt is just the spec we use in conjunction with standard Web HTTP as the underlying "protocol". We extended small parts of the spec at dev.twtxt.net to support at a bare minimum things people expect to see of a "social media". Actually what you're on here twtxt.net is my pod, one of many, and a Yarn.social pod 😉
@prologic Cool! That's a nice distinction between the format, the extension, the pod and Yarn.social. Maybe the similar names are confusing to newcomers, but besides that, a really noble project. Thanks for all your effort!
I was reading a little bit more about it here: https://www.prologic.blog/2021/12/19/future-of-yarnsocial.html
As I was 'saying' on Twitter, this kind of extension and online services would be required for that 'social content generation', I'm glad dev.twtxt.net has those ideas covered, like pagination for instance.
@eaplmx Yeah so basically being a part of Yarn.social just means implement the extensions, at a bare minimum Metadata, Twt Hash and Twt Subject extensions. Or you _could_ just spin up a pod as it's a bit easier and less fuss 😅 Also uses minimal resources (_quite a few pods run on Raspberry Pis!_)
Also where is the "confusion"? The fact my own pod is called Twtxt.net? That's kind of legacy, as if you read more of my blogs you'll soon realize that this project came from a much simpler idea that then evolved into what is now Yarn.social 😎
@eaplmx Yeah so basically being a part of Yarn.social just means implement the extensions, at a bare minimum Metadata, Twt Hash and Twt Subject extensions. Or you _could_ just spin up a pod as it's a bit easier and less fuss 😅 Also uses minimal resources (_quite a few pods run on Raspberry Pis!_)
Also where is the "confusion"? The fact my own pod is called Twtxt.net? That's kind of legacy, as if you read more of my blogs you'll soon realize that this project came from a much simpler idea that then evolved into what is now Yarn.social 😎
@prologic well, honest confusion from my side...
I joined here because someone requested me to use the twtxt format, which took me to https://twtxt.readthedocs.io
I was thinking of using the base format for my site, but finding options for a simpler usage I came to https://yarn.social and lastly to https://twtxt.net
So... Yes, it could be confusing if 'twtxt' (spec) is exactly the same as 'twtxt.net' (service for the same spec) when it's a (great) extension.
Or on how to name that extension.... twtxt 2.0 to say something?