Comment on Programming.Dev Feature Requests

popcar2@programming.dev ⁨1⁩ ⁨year⁩ ago

• mark@programming.dev ⁨1⁩ ⁨year⁩ ago

  I’ve always felt like the blocking should happen at the user level and muting should be at the instance-level. Feels odd for admins be able to prevent users from seeing content.

  source

  • Reader9@programming.dev ⁨1⁩ ⁨year⁩ ago

    Feels odd for admins be able to prevent users from seeing content

    My understanding is those admins aren’t just allowing users to view it but also allowing copies of the federated data to be stored on the server those admins are responsible for, so for certain types of content it seems really important to be implemented in this way.

    source

    • mark@programming.dev ⁨1⁩ ⁨year⁩ ago

      We’re talking about blocking all content on an instance though–not necessarily a few nasty communities or posts or users. Blocking an instance blocks all content, including non-offensive content that may be posted by legimimate users.

      For an admin to make the assumption to block everyone on an instance from all of their users just because of a few bad actors still seems weird to me. Makes more sense for this to be a user choice.

      source

      • Reader9@programming.dev ⁨1⁩ ⁨year⁩ ago

        Good point and I agree with the downsides. Giving admins more granular ways of hiding content sounds healthy.

        There’s also the important distinction between admins finding opinions on the other instance “disagreeable” and muting vs. illegal content in the instance server’s jurisdiction and those of the admins. Defederating the whole instance does seem harsh if the problem is within specific communities only and doesn’t deal with illegal content.

        Difficult problem!

        source