- cross-posted to:
- fediverse@lemmy.ml
- cross-posted to:
- fediverse@lemmy.ml
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.
You must log in or register to comment.
This insane isolationism from the vocal minority will kill ActivityPub. The fact that the author is now backing down and switching to an opt-in system is infuriating. Makes want to fork the project and host a copy of the bridge that’s opt-out.
deleted by creator
“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
I understand blocking this bridge, but if admins do that, they should block other bridges too, like bird.makeup
bird.makeup is not a bridge in the proper sense, it only brings content from Twitter to the Fediverse, not the other way around.
