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.
I think I could pretty easily shim that into the filter policies in Tesseract (that’s the big project for this upcoming release). I already have customizeable regex filter lists for keywords, but those only set the “filtered” flag if they’re detected and return the list of regex patterns that were matched.
Since the filter policies can be either global or per community group, you could get pretty granular with it. I’ll look into it and see if it’s feasible to shim in.
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 myselfI thought the feature was too absurd to flesh out, but if there’s interest, I’m open to adding it lol.
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.
The lengths you people want to go to roast instead of writing a bot that would provide archive links for paywalled articles.