RT @dret: great to see the #AS2 work now also covering the protocol side of things: hello #ActivityPub! #REST #IoT …

@nttp (#drs34ia) Hello there! 👋 I agree, #ActivityPub is an awfully complicated protocol that's not easy to build against. That's why we chose to use Twtxt for the underlying data interchance here with Yarn pods and basically HTTP for the protocol.

@eldersnake @movq (#376foda) > the 5 min syncing for example I assume is pretty conservative compared to a lot of services yeah well `If-Last-Modified` is used here, so I/O will be minimal depending on the extend of busy feeds you may or may not follow. All things considering this approach scales a lot better than #ActivityPub based stuff like #Mastodon -- Just read @jlj's experience with the #firehose he managed to get in to 🤣

👋 Question for Pod operators and even Twtxt users alike... Do we _really_ want to integrate with the so-called "Fediverse"? -- Even if the answer is a resounding "yes" from the community, the _only_ viable way I _think_ we would build this is via a separate 2-way bridge/service that anyone _could_ run -- I would probably run the first instance no doubt just like I run feeds.twtxt.net -- Thoughts? 🤔 #Yarn.social #Twtxt #Fediverse #ActivityPub

#twtxt vs #activitypub

#twtxt vs #activitypub

it is said #activitypub is too complex. I personnaly prefer #twtxt for simplicity, and even more #feeds like #atom or rss to follow someone

it is said #activitypub is too complex. I personnaly prefer #twtxt for simplicity, and even more #feeds like #atom or rss to follow someone

(#ixywgzq) Also #activitypub based "social platforms" tend to form a "distributed network", as opposed to a "decentralised" one like what we have here with Yarn.social / Twtxt 👌 (_even if things are a little slower, by design..._)

for possible #ActivityPub #yarn.social #twtxt integration @prologic #DecentSocial #fediverse