zlacker

[parent] [thread] 13 comments
1. dang+(OP)[view] [source] 2024-02-02 19:09:30
Absolutely. We review the list of stories that set off that software penalty and restore the ones that are clearly not flamewars. No doubt we miss a few, and also - not everyone interprets these things the same way. But if you (or anyone) notice a case of a good thread plummeting off the front page, you can always get us to take a look by emailing hn@ycombinator.com.
replies(3): >>Michae+S3 >>smcin+0c1 >>z_ack+Dn1
2. Michae+S3[view] [source] 2024-02-02 19:31:18
>>dang+(OP)
There should be some way of doing language detection to detect the relative quality of 'flaming' going on.

So the highest quality 'flame wars' can remain untouched, but downranking everything else below that bar probably makes sense.

replies(1): >>dang+Hc
◧◩
3. dang+Hc[view] [source] [discussion] 2024-02-02 20:11:18
>>Michae+S3
Yes, the carrot of automation would be so much easier than the stick of manual review. I haven't seen any system that works well enough yet though.

The nice thing is that the comments are all public so if someone wants to take a crack at building a state-of-the-art sentiment detector or what have you, they can have a go—and if anyone comes up with anything serious, we'd certainly like to see it. As would the entire community I'm sure!

replies(2): >>JimDab+Li1 >>fragme+3j1
4. smcin+0c1[view] [source] 2024-02-03 03:57:25
>>dang+(OP)
Here's one from last week:

"Ring will no longer allow police to request users' doorbell camera footage" (npr.org) >>39138423

I posted an on-topic supporting quote to explain why this item was newsworthy and got one unhelpful one-word response and my comment got inexplicably flagged (not the commenter) >>39138481

How did that slip past detection? How do I get the abusive flag on my comment reversed? This behavior seems to have managed to push an important story off the frontpage quickly. (yes there was a badly-worded dupe headline, but that's a separate thing)

replies(1): >>dang+vg1
◧◩
5. dang+vg1[view] [source] [discussion] 2024-02-03 05:11:03
>>smcin+0c1
If I understand correctly, you have three concerns here: (1) the story was downranked off the front page; (2) your comment was flagged; (3) a comment that replied to you was not flagged. I'll try to respond to these in turn:

(1) the story was downranked off the front page because the topic had already been discussed a bunch—for example in these threads, two days earlier:

Amazon's Ring to stop letting police request doorbell video from users - >>39119387 - Jan 2024 (141 comments)

Ring steps back from sharing video with police – mostly - >>39120892 - Jan 2024 (15 comments)

Culling repetition from the front page is one of the most important things HN's systems need to do. Actually, it's probably the single most important thing. Certainly it's best if we can link to the previous discussions so people can know where to find them—but we can only do that some of the time. Users help out a ton by posting links to earlier threads. Ultimately we need better software support for dealing with this, but that's not done yet.

(2) Your comment >>39138481 was flagged by users. We can only guess why users flag things, but in this case I'm pretty sure I know why: comments that do nothing but quote from the article, or post a summary of it, are considered too formulaic by readers here. If you want to say what you think is important about an article, that's fine, but please do it in your own words and share your own thinking. To simply paste a quote from the article is too superficial. On HN the convention is to assume that readers are smart enough to evaluate an article for themselves.

Edit: I'm going to copy the above paragraph into a reply below, so I can link to it in the future when this comes up, without the rest of the post.

(3) The reply >>39138536 , which only said "and?", was definitely an unsubstantive comment that deserved to be flagged (and killed) even more than yours did. The reason it escaped detection was simple, albeit unsatisfying: pure randomness. We don't come close to reading everything that gets posted here—there's far too much. I've flagged it now.

replies(1): >>dang+Ftq1
◧◩◪
6. JimDab+Li1[view] [source] [discussion] 2024-02-03 05:41:59
>>dang+Hc
You don’t really need a state-of-the-art anything here. People get too distracted with building the perfect system when it comes to use cases like this because they are paralysed thinking about the avoidance of false positives and make a bunch of sub-optimal decisions on that basis. False positives are much less of a problem with a human in the loop, and putting a human in the loop doesn’t require moderator effort.

You can probably put a big dent in the number of low-quality comments by just showing a “hey, are you really sure you want to post this?” confirmation prompt and display the site guidelines when you detect a low-quality comment. That way you can have a much more relaxed threshold and stop worrying about false positives. Sure, some people will ignore the gentle reminder, but then you can be more decisive with flags and followup behaviour because anything low quality that has been posted will by definition already have had one warning.

replies(1): >>dang+kj1
◧◩◪
7. fragme+3j1[view] [source] [discussion] 2024-02-03 05:45:52
>>dang+Hc
I asked for a showdead feed to make it easier to train an LLM on for this purpose but got denied.
replies(1): >>dang+xj1
◧◩◪◨
8. dang+kj1[view] [source] [discussion] 2024-02-03 05:50:05
>>JimDab+Li1
You're right about one thing: I didn't need to say "state of the art". A system that works at all would be great!

I don't think a confirmation prompt will help because people tune such things out after they've seen them a few times.

replies(2): >>JimDab+Pm1 >>intend+Ap1
◧◩◪◨
9. dang+xj1[view] [source] [discussion] 2024-02-03 05:52:58
>>fragme+3j1
Not sure what you're referring to, but you don't need a showdead feed to train an LLM for this purpose. Only 2% of comments are dead, and the number of bad comments that aren't dead is certainly higher than 2%. That's the problem, in fact!
◧◩◪◨⬒
10. JimDab+Pm1[view] [source] [discussion] 2024-02-03 06:43:17
>>dang+kj1
Even a bad implementation isn’t going to be showing this warning to people often enough to desensitise them. And if they make a habit of ignoring the warning to post flamewar stuff… that’s solved with moderation by a human. The intent is to add friction for knee-jerk low-quality comments, not solve for people who persistently, intentionally post low-quality comments after a warning.
11. z_ack+Dn1[view] [source] 2024-02-03 06:57:45
>>dang+(OP)
I have a compliant : sometimes there a proliferation of anti-scientific posts, in example I can mention those related to the "50 years nuclear battery", I remember particularly one from techradar.com that was especially misleading and anti-scientific and more similar to a PR campaign then scientific information, they was stating che you can power a smartphone or a drone with a betavoltaic battery (millionth of Ampere ). This is only an example, I noticed similar article , often related to green energy with the same anti-scientific cut and sometimes anti-scientific is a euphemism. Could nice to have a way to report them , even for occasional readers like me. Often the same articles have approval posts that IMHO are bot made. we live in times where scientific fraud amplified by the media is becoming a serious problem and I think everyone should do more to stop the phenomenon.
replies(1): >>dang+Rn1
◧◩
12. dang+Rn1[view] [source] [discussion] 2024-02-03 07:00:52
>>z_ack+Dn1
Trying to assess what's scientific vs. anti-scientific is outside the scope of what mods can do. I have my opinions just like you do, but hashing these things out is a community process, not a moderation issue. We could put our fingers on the scale, I suppose, but nothing good would come of that, so we don't.
◧◩◪◨⬒
13. intend+Ap1[view] [source] [discussion] 2024-02-03 07:38:04
>>dang+kj1
I hate myself for saying it, because of all of the buzz/hype, but LLMs can assist here.

You get better intent assessment than with NLP/ regex/whatever.

Plus HN is entirely in English, so you never have to worry about lexical resource gaps.

There is no off the shelf solution - afaik. In addition I have no idea how expensive running costs will be.

But something serviceable can be built.

Source: mod /t&s person dealing with these things

◧◩◪
14. dang+Ftq1[view] [source] [discussion] 2024-03-02 14:55:19
>>dang+vg1
Your comment was flagged by users. We can only guess why users flag things, but in this case I think I know why: comments that do nothing but quote from the article, or try to summarize the article, are considered too formulaic by readers here. If you want to say what you think is important about an article, that's fine, but please do it in your own words and share your own thinking. To simply paste a quote from the article, or a summary, is too superficial. On HN the convention is to assume that readers are smart enough to evaluate an article for themselves.

(I copied this from the parent comment so I can link to it when this comes up in the future).

[go to top]