26 / chaotic neutral / autist / fedi: @flaky@furry.engineer

Avatar by Orc_Enk on Twitter

  • 0 Posts
  • 28 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle
  • Before I hopped onto Bluesky, I was one of those fediverse evangelists trying to get my friends onto it. Except, I couldn’t give a solid answer to the fediblock problem, and my friends definitely saw right through it or were confused about it. And I can’t blame them. They don’t want to worry about federation, or whether one instance will be blocked by the other over some drama. Meanwhile since Bluesky has been opening up more, I’ve only seen the fediverse grow more toxic towards Bluesky, to the point where it’s exhausting to be part of.



  • AFAIK, Bluesky started on ActivityPub at first, but then it was decided to make a new protocol which resulted in Atproto. It also started as an internal project at Twitter, was funded by Jack, but then as it got popular amongst a more regular audience, he left when he kept getting pestered with @ mentions and anti-crypto stuff. He hangs out at Nostr now and from what I’ve been told, isn’t really involved in Bluesky’s meetings.

    There was an effort to bridge Bluesky/Atproto, ActivityPub and also Nostr together - Bridgy Fed - for when Bluesky started getting their protocol federating outside its own network. The issue was, the creator made it opt-out rather than opt-in. The AP fediverse collectively shat themselves, spreading their delusions about Bluesky, one guy called the creator a rapist for using public data and another threatened to sue/fine the creator. It was absolutely bonkers and that incident exemplifies a good part of why people find the fediverse to be toxic, moreso than anything involving Threads.














  • Essentially, Facebook’s Twitter competitor Threads is gearing up to join the fediverse by integrating ActivityPub into their platform. Don’t take my word too much on this but I believe this is due to the European Commission’s Digital Markets Act which requires interoperability (similar to how iOS now requires sideloading in the EU). This is essentially their cheap way of complying.

    The fediverse has a strong hatred of Facebook, for various reasons (from petty things like “embrace, extend, extinguish” to much more serious things like Facebook’s compliance in the Myanmar genocide) and a “pact” was enacted of fediverse instances that are simply outright blocking Threads. Part of it is the fear that Facebook will federate its moderation problem and cause a headache (which, in my opinion, would be better dealt with by limiting Threads to followers only - Mastodon and Pleroma allow this).

    Opponents of the Fedipact are optimistic this will help a more mainstream audience warm up to the fediverse. The fediverse has a reputation of being unwieldy and complicated to newcomers, and having a major platform like Threads integrating ActivityPub might help bring them in and see what it’s like. Toxicity is cited as a reason for defederating Threads, but IMO I see more toxicity towards newcomers and outsiders coming from the people already on the fediverse, so I’ve been quite apathetic to the Threads thing.


  • On Lemmy, it’s shown. On Mastodon, instances are given the ability to hide their blocked instances which IMO hinders people’s ability to join. A lot of the drama on the fediverse with regards to blocking is from Mastodon and similar instances.

    People claim the instance you join doesn’t matter because “everything is federated!” but it kind of does. It strongly affects the people who will see your posts and even who you can follow, and if you don’t know what an instance is blocking it creates an air of uncertainty. I’ve seen instances get blocked for stupid at best and downright malicious at worst reasons, so the 4chan post isn’t inherently wrong.