I think this warrants a fediverse wide boycott of all piefed/fedia instances until this is rectified.

  • Dessalines@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    13 hours ago

    There’s nothing we can do about server-to-server blocking, but I think over the long term, people will join servers that do less instance blocking, so that they can personally be in control of what they see.

    And of course everyone not on restricted servers will still see your replies / takedowns, so it really only harms them. In a big way, responses are just as important to onlookers, than the one you’re responding to.

    • Nakoichi [they/them]@hexbear.netOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      11 hours ago

      Oh yeah for sure I was just curious as to your thoughts on people taking this project and building in their own ideologically motivated blocking. I know that there is nothing to be done about it as its all open source I just find it scummy that they do this in the first place. I get not wanting to federate with specific instances but the way this works is to just automatically make it one way only unless the person using their fork manually changes it.

      I don’t want to force them to see our posts or comments or anything idgaf about that I just don’t want to have to guess which people I can see on my end can actually see my replies to them ya know?

      • Blaze (he/him)@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        2 hours ago

        unless the person using their fork manually changes it.

        Updating the defederation blocklist is done via the admin UI. A fork implies having to recreate the source code and modify it. This is different.

        Recent comment from another admin

        This is exactly how it works. I started a PieFed instance and made the decision (during setup) to trim the defederation list down to none. Users can block on the account level.

        https://wetshav.ing/comment/92409