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.

    • breakfastmtn@lemmy.caEnglish
      451·
      11 months ago

      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.

      • Flaky@iusearchlinux.fyiEnglish
        8·
        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.

        • breakfastmtn@lemmy.caEnglish
          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.

        • Russ@bitforged.spaceEnglish
          5·
          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.

    • Alsephina@lemmy.mlEnglish
      211·
      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

    • Fizz@lemmy.nzEnglish
      14·
      11 months ago

      That’s a good solution. Keeps the all feed clear of threads content while allowing users to opt in

      • Flax@feddit.ukEnglish
        71·
        11 months ago

        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.

      • mateomaui@reddthat.comEnglish
        2·
        11 months ago

        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.

          • mateomaui@reddthat.comEnglish
            1·
            11 months 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.

          • Dame @lemmy.mlEnglish
            1·
            11 months 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