- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Bridgy Fed made a splash earlier this week by announcing its latest progress in connecting the Fediverse to Bluesky and Nostr. Sadly, not everyone was welcoming.
Bridgy Fed made a splash earlier this week by announcing its latest progress in connecting the Fediverse to Bluesky and Nostr. Sadly, not everyone was welcoming.
“Foam mouthed Threads opponents”
Threads is quite blatantly just going to throw it’s weight around. It’s not in good faith. They’re already not going to properly implement ActivityPub (which they apparently would do, according to pro-Threads federation people), and so certain content will appear different on Threads and AP. And of course threads is massive already as if you have an Instagram account you have a Threads account.
Smaller services and services which aren’t megacorps are fine. Honestly, BlueSky federation seems like a good thing to me. But we’ll have to see about that.
My point is there’s a line between “federate to get more exposure and connections” and “federate to get EEE’d”. Threads crosses that line. BlueSky I don’t know about. They’re very different scenarios.
Mastodon and many others do not “properly” implement ActivityPub and have a ton of their own extensions and implementations
But do they ignore existing implementations of a feature when they want to add that feature? And make it crappier when federated?
Threads has implemented both ActivityPub implementations of quote posting: it uses the Misskey quote posting system, and also implemented fep-e232 (which is a better version of quote posting, but not implemented by any major platform), so that they are already immediately compatible with platforms that use the FEP version.
Mastodon ignores the current implementations of quote posting, and wants to do their own new implementation so that they can add granular control.