👋 To all our Twtxt users and friends (regardless of what client you use, or how you choose to host your feed): Anyone interested in a Twtxt <-> Activity Pub bridge or even a CLI client/tool for interacting with AP actors as Twtxt feeds? 🤔

(#2wuyiea) @prologic While I think this is a cool idea, I don't think it is a replacement for what you have been trying to achieve on yarn.social.

(#2wuyiea) Also, how would you go about it? I mean, I can start using a txt on my client that is actually coming from a proxy service generating it from an AP account (like we already have on feeds), but how do I announce that your service should "follow back" my own feed so you can see replies and translate them into AP replies?

(#2wuyiea) @marado See it would work a lot like this. Ther eare two ways we can do this, either a full-bridge service where you registry your Twtxt feed + forward WKD requests for your domain to the service. AP actors would then follow you at the bridge service (transparent to them really) and you would in turn follow them as regular Twtxt feeds. There'd be the same amount of work doing translations on both sides. The other way to do this (or in addition to) would be to build a Twtxt client (of sort, or maybe a new multi-protocol client) that supports fetching AP actor's outboxes (the only requirement really being that you need to have a defined Actor with an RSA key pair, which is easy to do on a static site)

(#2wuyiea) @prologic I see. Well, as I said, I see value in such a bridge, but I don't think it replaces yarn.social's AP integration. It could, however, be used as a backend in yarn.social: a pod would delegate the AP bridging, and all of that would be transparent to the user.

(#2wuyiea) @marado That's right. This was the original plan, to basically build an AP bridging service and integrated that with `yarnd` -- but at the time it was a lot more work/harder to do this as I had no idea what I was doing then 🤣 Now I do, but the effort/work is still a lot either way 😅