Pull request to begin to add ActivityPub support to the bluesly PDS
PDS ActivityPub support 😉 by mikekasprzak · Pull Request #3943 · bluesky-social/atproto
This is really big imo.
This is big. Bluesky is getting lots of traction with normies who want off Twitter. Mastodon and pleroma and pixelfed all about to become much more discoverable
We pretty much had this when the first reliable Mastodon<->Bluesky bridge came online. The Fediverse side protested and made the entire system opt-in, making it practically unusable because people that don't have a favourite Linux distro don't know what a fedi is and why they should bridge to it.
When this goes live, I expect people to treat it the same as every other sizeable social media joining the Fediverse, with outrange and block lists.
Exactly. It is a huge, authoritarian, corporate platform that can absolutely ruin the fedi if it ever turns against us (think ads, bad moderation, nudging campaigns, etc).
Its not at all as black and white as threads is but it is still a huge problem.
Why would they protest and make it opt in? The whole point of the fediverse is that your posts are completely public. Literally anyone and anything can scrape it, your server would hand it to them on a silver platter. That's the point.
people that don't have a favourite Linux distro
Mere mortals
I dunno. I still posts from the Bluesky bridge getting boosts. This might not be as bad Threads.
Watch then deny it cos it will threaten their market capture lol
They'll say something like "can't handle the scale"
You shouldn't expect full interoperability with this alone! At most, you should expect that your public posts get shared with your followers on Mastodon (i.e. an outbox)
fart noises
Really cool honestly. How big it is is probably predicated on if Bluesky enabled it for PDS'es on bsky.social.
That's the benefit of Bluesky being totally centralized, not built with any capability for federation: When they decide to add some, they can hardly fail to see that it's best to go with ActivityPub.
Thats completely untrue :) .
app.wafrn.net is a separate app that connects to bluesky, atproto.africa is an alternate relay, deer.social is an alt appview.
You can use bluesky without relying on bluesky now.
Hmm, let's see if I remember the terminology correctly:
Client apps have nothing to do with it, obviously.
Alternate appviews have nothing to do with it, except in that they'd presumably need to work with whatever form of atproto federation exists, if any did.
Alternate relays aren't federated unless there's some protocol for routing messages between them — such as ActivityPub.