this post was submitted on 28 Jul 2023
81 points (100.0% liked)
Technology
37730 readers
271 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Things change over time.
For example - I want to see the broadest possible choice of content in my feed. I want to be able to interact with anywhere that's not outright hateful and/or malicious. So when I was choosing an instance, finding a permissive (but not too permissive!) admin was important to me.
But when Threads started making waves and the fedipact started becoming a thing that people were discussing, things changed out of left field.
I still wanted to federate with Threads. I think fears of EEE are overblown; Facebook has to comply with the Digital Markets Act and guarantee third-party interoperability. EEE on the fediverse runs counter to EU law. Additionally, most of my friends are folks who don't "get" the fediverse; I tried coaxing my fiance onto Mastodon and she lasted 1 day before going back to birdsite. She uses Threads actively now, and I'd love to be able to see her posts and interact with her without needing to sign up for Threads myself.
I had hoped that the semi-permissive admins I've found would tolerate it, but a lot of them decided to draw the line and join the fedipact (including my Mastodon admin).
Which now sucks - it feels like a bunch of bullies are trying to use intimidation to tell me where I can and can't post. By threatening to defederate everywhere that's not in the fedipact, there's this feeling where now I can't join a server that curates the way I want because if I do, I'll be cut off from the rest of the fediverse. If I run my own server, there's a good chance these other instances will use bots to catch that my server federates with Threads and pre-emptively defederate me.
Defederation is used as a weapon and a way to bully other instances, which I really don't like. I understand the need for defederation as a tool but it sucks seeing how easily it's abused, and how you really can't trust that admins of a server you join won't be intimidated into compliance by these fedipact bullies.
So now, if I want to like my fiance's posts... I basically have to join Threads and help Zuck directly, or have an account elsewhere that basically can only federate with Threads. Thanks, fedipact.
Well, on the plus side, one of the admins of firefish.social (not the one at the center of this art drama) has been very public about his belief that there need to be lobby servers that do federate with Threads to help provide a path for Threads users to escape the Facebook ecosystem and transition over to the fediverse. He thinks some Threads users will find other servers more appealing in the end. He picked up a second domain, notmeta.social, to eventually set up as a separate fedipact option, but that hasn't even been upgraded from Calckey to Firefish yet so I don't know how seriously they take it.
You won't have access to mastodon.art from firefish.social, but you can access the threads-welcoming side of the fediverse.
Honestly, I was hoping to find a fedipact firefish server that doesn't have meta in the name (why would I want to advertise for them in my server name?), but the information on which servers are in the fedipact is so poorly organized that I gave up on that entirely for now.