I used to think that there would be 1, main 'Fediverse' with all of the 'big instances' connected to each other. The recent Threads debacle has shown me otherwise.

The point of the Fediverse is that there is no one single entity, or group of entities, dominating it all.

Right now it feels like whatever the big instances do, we kind of have to go along with to be a part of anything. As the Fediverse grows, there will be more options to suit different types of users.

I think it's fine if big instances federate with Threads and it's fine if they don't. People can just join instances that align with what they want. It's not like defederating means being cut out of the Fediverse, that's not possible.

Great design. I'm eager to see how it plays out.

you are viewing a single comment's thread
view the rest of the comments

[+] [email protected] 12 points 1 year ago* (last edited 1 year ago) (2 children)

[deleted]

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

I'm pro federate, but honestly, this seems fair. However Lemmy wouldn't need it, as to see a threads post on lemmy, the person would have to @ the lemmy community in their post.

[–] [email protected] 2 points 1 year ago (1 children)

All true, and making this a feature would simply be implementing the inverse of the new capability… overriding an instance level block instead of imposing one not already at the server level.

[+] [email protected] 1 points 1 year ago* (last edited 1 year ago) (2 children)

[deleted]

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

I think you only made a case for having two or more levels of instance block, that already exist. One due to objectionable/illegal material that cannot be overridden, and another for something like threads where a significant number of users may not want to be opted in automatically, or want to block it due to purely ideological, non-illegal reasons, which would effectively be put in place by automatically adding the instance block to user accounts that can be removed at any time, which arguably can already be done with minor changes. That’s essentially what dansup is doing, complete with including a command for Pixelfed instance admins to apply the optional block to all user accounts.

[–] [email protected] 1 points 1 year ago

That’s not how Bluesky does it. Sure it empowers users which is great but if there is a PDS for example with lolicon, one I don’t see it making past the content filters but if it did the BGS/Relay would blacklist that PDS