yarn should define its own federation protocol that extends the basic twtxt in ways that twtxt doesn’t allow. it’s time. and i’ve got ideas!
@shreyan@twtxt.net What do you mean when you say federation protocol?
Either use webfinger for identity like mastodon etc. or use ATproto from Bluesky (or both?)
We can use webmentions or create our own twt-mentions for notifying someones feed (WIP code at: https://github.com/sorenpeter/timeline/tree/webmention/views)
I’m not sure we need much else. I would not even bother with encryption since other platforms does that better, and for me twtxt/yarn/timeline is for making things public
I agree with @sorenpeter@darch.dk. WebFinger and WebMentions are very much in the spirit of Twtxt and both of them are already in use. If we’re going to do much more than that, we should probably just use Nostr instead.
yarnd does not do auto discovery via webfinger though.. i cant put @username and have it fetch the feed url from webfinger. to fully make feeds portable. would also need to be able to use that for hashing.
@prologic@twtxt.net I know yarn is culturally a slower place than most mainstream social, but I would like to enable servers to somewhat “broadcast” new events on some subscribable endpoint. Since much of the network relies on indexers, this would help the indexers get new posts more immediately, rather than having to schedule their crawls. That’s just one idea to start with
@prologic@twtxt.net Cool! Now what might be useful is to take all the cool things Yarn does and spec them out into a full protocol. This is also where we might get into extending beyond what Twtxt can offer and into a yarn-specific spec.
So where do we start wring down the specs/protocol for twtxt2/yarn?