2 ms·
USENET had this (per-account killfile); ended up with a hack to do "global cancels" to try to contain spam, though. There's probably a role for both. The prob
by rdl 13y ago
USENET had this (per-account killfile); ended up with a hack to do "global cancels" to try to contain spam, though. There's probably a role for both.
The problem with individual user killfiles is you then end up with weird conversations where some people can't see some of the responses, leading to duplication and confusion.
Being able to "killfile" certain submitters or certain sources of articles or certain tags/topics/etc. might work better, and would be a lot simpler.
- foobarbazqux 13y agoYeah, I saw the tail end of all that. One difference is that newsgroups don't have the same precise threading that HN does. I would be okay with not only killing comments on a per user basis but also killing all replies to those comments. So don't show me any submissions that SparrowOS makes, don't show me any of his comments, and don't show me any replies to those comments. Conceptually easy, but perhaps expensive in some cases such as looking through another user's comment history.
- deleted 13y ago[deleted]