I think that social networks are not meant to be moderated at scale. We are meant to have what I call 'overlay networks': we occupy the same infrastructure but see content filtered to the style that befits us. Most social networks have the notion of friend symmetry, but I think that read-time filtering needn't be like that.

To that end, I made a trivial Chrome extension and an equivalent CRUD backend that just helps me store lists of users I like and dislike. The former are highlighted, and the latter are simply removed from comments.

As an example, the user I'm responding to is someone whose comments I like so I have had them in my highlight list for two months now and not regretted it https://overmod.org/lists/view?pk=ELpqNsanTYP9_wZXNjdF-FcEOc...

My personal tool is particularly idiosyncratic but I think information sieving is particularly important these days, so I recommend everyone build something like this for themselves. One thing I've found it particularly helpful with is the usual outrage bait. But I also killfile users who I think particularly misunderstand the comments they respond to, and I also killfile users who express what I think are low-information views.

▲

GaryBluto 44 minutes ago | parent | next [-]

I designed an extension with a roughly similar aim that filters based upon various phrases and characteristics rather than the poster of the comments themselves. It collapses comments (via automatic triggering of HN's built-in collapsing feature) and adds a "reason" tag to the comment information, so I can choose whether or not to read it anyways. I feel the features with the most positive differences are the capitalization detector (hides all caps or all lowercase) and the character requirement.

	▲	arjie 25 minutes ago \| parent [-]
		That is very cool. It would be cool to see what you decided to filter on (other than the same-case filter and the char limit). I had a similar idea where I would run comments through a fast cheap LLM to evaluate whether they could be tagged in a certain way. I originally tried just pure word-stemming and phrase-based blocking and found that I couldn't tune it well for my uses. I also found that collapsing comments lead to my opening them out of curiosity. Thank you for sharing what works for you. I think it's great other people have been doing this style of read-side filtering. It's a pity that there's no way to inject code into mobile apps safely (i.e. this is an easy path to app-store rejection). Perhaps there's no option there but to push `shouldFilter` out to a server where you can run the logic. My use of my phone is the weakest link in my filtering strategy.

▲

esseph an hour ago | parent | prev [-]

Beware of trapping yourself in a manufactured social bubble of emotional comfortable

	▲	bentcorner 2 minutes ago \| parent \| next [-]
		Is that bad? I black-hole plenty of sites via pihole above and beyond the typical adblock lists. On a very few rare occasions I have turned off the pihole to unblock a site because I was curious after following a link that was blocked by said pihole. Every single time I quickly learned why that site was blocked, and visiting that site gained me nothing.
	▲	arjie an hour ago \| parent \| prev [-]
		If it happens it happens. I can only hope that the result is boredom rather than increased engagement.