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.

  • Alsephina@lemmy.mlEnglish
    3·
    11 months ago

    For the lazy:

    After some careful consideration, I have decided to block threads.net on pixelfed.social and .art by default

    However, users will have the ability to unblock the domain

    Soon we will be selectively enforcing authorized fetch for accounts with domain blocks so as to provide the best of both worlds.

    (I’m also shipping a command for :pixelfed: admins to easily add user domain blocks for all local users)

    I’m eager to hear your feedback!

    PR: https://github.com/pixelfed/pixelfed/pull/4834