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.

  • Flaky@iusearchlinux.fyiEnglish
    9·
    11 months ago

    Authorised fetch has been a thing on Mastodon and I believe Akkoma too. I don’t know if Pleroma, Soapbox or Misskey have it though.

    • Russ@bitforged.spaceEnglish
      6·
      11 months ago

      Authorized Fetch has been a thing for a bit on Mastodon at least - but as far as I can see it’s a global toggle rather than saying “If you present as a domain on the blocklist then you must be authorized to fetch this resource” (the selective authorized fetch I assume they’re talking about).

      Never used Akkoma though, so I can’t speak for it.

    • breakfastmtnEnglish
      6·
      11 months ago

      Unless I’m wrong, the unique thing here is that auth fetch is always off for the server. It’s on only at the user level and it’s only on at that level if a user has an active domain block.

      That could actually solve a lot of problems for people. Admins are reluctant to enable it server-wide because it causes a bunch of problems. The biggest being that it breaks federation with servers running older software (Mastodon v <3.0 I think) and with other services (Pleroma, maybe others). It also uses more server resources. But there are always people who think it’s worth it.