So if we want to stop this infighting, should we push everybody to use #wafrn and help develop it instead and automatically support both protocols?

[wjmaggos@liberal.city]

So if we want to stop this infighting, should we push everybody to use #wafrn and help develop it instead and automatically support both protocols? how does it work differently vs the normal #ATproto infrastructure or an #ActivityPub instance? no more need to bridge etc? would this be similar to what happened with IMAP, SMTP and POP3 for email?

cc @j12t @quillmatiq @mackuba @mastodonmigration @gabboman

[gabboman@gabboman.xyz]

@wjmaggos@liberal.city @quillmatiq@mastodon.social @mastodonmigration@mastodon.online @j12t@j12t.social @mackuba@martianbase.net

Wafrn does not use the bsky infra for obtaining bluesky posts, we get them directly from the PDS.

We use A jetstream (one of many available, a thing very easy to self host. Mini firehose. Also easy to host) to get the events, when we get one event we check if we need to store it (post by followed user, post in reply…). If so, we directly call the pds and ask for the post.

Wafrn servers were not affected by the event of a few days ago

[gabboman@gabboman.xyz]

@wjmaggos@liberal.city @quillmatiq@mastodon.social @mastodonmigration@mastodon.online @j12t@j12t.social @mackuba@martianbase.net

I will also say: wafrn is janky as hell. Im working to make it even worse. People should hosts more wafrns and someone should make a fork at some point