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

[–] mateomaui@reddthat.com 98 points 11 months ago (24 children)

The most reasonable solution I’ve seen so far, from the pixelfed and pixelfed.social creator

https://mastodon.social/@dansup/111617703110836835

[–] breakfastmtn@lemmy.ca 47 points 11 months ago (6 children)

Not the solution I was hoping for but it's an extremely reasonable compromise. I've never heard of selective authorized fetch. Pretty sure he just invented it.

[–] mateomaui@reddthat.com 27 points 11 months ago

FOSS ingenuity at work. All it needs is adaptation and adoption.

load more comments (5 replies)

load more comments (22 replies)