Ignore obnoxious comment signatures, make dogwhistles more transparent, remind yourself not to interact with certain topics, uncensor common celf-censorship euphemisms, or just apply some good 'ol censorship of your own. What I am imagining is a system that allows the user to set custom regular expression rules that get applied to all comments. There could be both global rules (that apply to every single comment) and user rules (that apply to all comments from just that user, similar to custom user labels).

What are your thoughts on having a feature like this in whatever app you use? Would you even find it useful at all? If the change is only visible to the user, is there any abuse potential?

Pictured here is a proof of concept showing Thunder with a simple "Cloud To Butt" function applied.

you are viewing a single comment's thread
view the rest of the comments
[+] -2 points 1 year ago* (last edited 1 year ago) (7 children)
  • [–] 2 points 1 year ago

    Me and the Interstellar devs are collaborating on a shared filter spec. Would love to loop you into that discussion if you’re interested. With a shared spec, users could share popular filters between different clients.

  • source
  • parent
  • [–] [S] 1 point 1 year ago* (3 children)

    I jokingly thought about adding something like that already.

    Basically:

    (^Paywall(ed)?)$ -> I'm going to contribute nothing to the discussion except whine that you didn't cater to my laziness and make my laziness everyone else's problem until someone else replies with an archive link I could have easily gotten myself

    This is very close to what I had in mind when saying "remind yourself not to interact with certain topics". That any time a comment contains a certain keyword/phrase, it could replace the entire comment with "I am a person not worth talking to".

    What I have in mind would be a simple pair of textboxes for each filter policy: one for the regex pattern to search for, and one for the string to replace it with. Then a checkbox or something to toggle whether just the matched string gets replaced or the entire comment gets replaced when the pattern matches anywhere in the comment. Then, the user can add as many policies as they like.

  • source
  • parent
  • hideshow 3 child comments
  • [+] -1 points 1 year ago* (last edited 1 year ago) (2 children)
  • [–] [S] 1 point 1 year ago (1 child)

    As for indicator, I think what I would prefer as a user is a little icon next to the edited indicator, and then the ability to view comment source (which is already a feature on many clients). Though that is not really addressing the problem very well, as people viewing the screenshot need to understand what the icon means.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)