Edit about the 4chan image blocking, I asked Rimu directly:

I wrote a long message about how that checkbox only notifies about federated posts.

So the difference is for local posts it blocks the creation of the post entirely, but for federated posts it just notifies the admin.

https://chat.piefed.social/#narrow/channel/3-general/topic//near/10529

– Original message:

https://codeberg.org/rimu/pyfedi/src/commit/b168820a089ff6e835059f0d806f81b612987a79/app/models.py#L3513

A few people in the other thread assumed that it was required to fork the code to disable those filters. That’s not the case, the filters can be configured, and are off by default.

To hide the reputation system, here’s a line of CSS that admins can add in the admin area to hide it for every user

https://piefed.social/c/piefed_css/p/1722358/hide-red-triangle-warnings-on-accounts-with-bad-reputation

That CSS line can also be used by any user wanting to hide the score at the user level.

  • OpheliaAzure@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 day ago

    Honestly I don’t mind if it would be visible to the users. Like how long would this be secret if it wasn’t for the code audit.

    • anarchiddy@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 day ago

      I mean, I disagree, but that’s my own preference.

      Ranking/sorting/filtering systems should always be up-front and user-configurable, and their implementation should be instance-agnostic. Hiding it in the code is definitely the worst part of this, but far from the only problem.