Some of the comments you've been taking action on have had some foul language but this one is just an opinion.
There are some that argue the monarchy constitutes a human rights abuse both against the people she took tax money from and against her own family which was forced to participate in the pageantry.
Calling those opinions "flamewar tangents" is incredibly dismissive.
If by foul language you mean profanity, we don't care about that.
The GP comment was definitely a flamewar tangent: 'flamewar' because it's a classic political battle, and 'tangent' because it touches the original topic at one point and then veers away from it.
Tangents can be fine if they're unpredictable, but generic tangents are predictable and those are the worst sort of thread on HN. They're so predictable that they're the opposite of the curious conversation we want here.
I think in the future it might be better to say "This comment is not up to HN's editorial standards to produce curious conversation" rather than asserting that it is "flamebait tangent". Using such strong language is a type of flamebait in itself (and the number of comments criticizing the moderation of this thread should be evidence that others agree).
I take your point but I think it's more important to avoid bureaucratese.
The number of comments criticizing moderation in this thread is not because I used the word flamebait. I've used that word thousands of times on HN. Rather, it's a function of my screwing up with https://news.ycombinator.com/item?id=32769925. That happens sometimes—usually when I mis-pre-assess people's feelings.
The GP comment is certainly not a top quality comment but there are many "positively disposed" comments of much worse "quality" that have not motivated a specific moderator response warning.
As for it being "flamebait", within this context anything that motivates this classical political battle will be a comment on the opposite side of a topic to one's own opinion. Moderation would need to be balanced in restricting such comments to effectively restrict "flamebait" - yet only comments on one side are being killed.
"Foul language" is a very rough measure. The parent's thought could have been communicated with less sarcasm ("Sad that ... ?") and bitterness ("doesn't deserve").
Edit: Further, some topics, no matter how carefully broached, are just a bad value proposition. They may have a bad ratio between their intrinsic value (importance, relevance, etc) and how likely they are to spawn a low-quality thread (and how low that quality is likely to be).
Indeed - the implication that a statement merely containing anything factual or backed by evidence makes the whole thing uncriticizable ("but it's true") is maybe the most common fallacy made in defense of provocative statements.
"Delete the whole" is not how threads work on HN. The way that threads work on HN, assuming that they're on topic, is that people should post intellectually curious comments and avoid posting unsubstantive or predictable ones.
Dang, does this post 'gratifies one's intellectual curiosity.'? Should it be on HN? I don't believe so. The only intellectually interesting thing about the monarchy is how we let them persist now all the fake divinity is gone. Which is what my comment is intended to spur conversation about. So claim what you like, it's your site, but I believe you're wrong.
I genuinely believe the interesting aspect of Elizabeth's death is the focus it can (if we allow it) put on the inherent injustice of monarchies. But OK, you don't. Fine, its your site. The temp ban/rate limit was kinda low key uncalled for. I was civil.
We rate limit accounts when they post too many low-quality comments and/or get involved in flamewars. You've posted quite a few low-quality comments lately, not just in this thread. I'm sorry if it came across the wrong way, but this is standard HN moderation, and one of the few software tools we have to try to dampen the decline of this place.
If you want to build up a track record of posting better-quality comments for a while and then ping us at [email protected], we'll be happy to take a look and hopefully remove the rate limit; we do that all the time.
And no, I'm not going to debase myself and beg you to remove something you implemented out of pettiness. It's your error, and it's unfortunate (for me) that you wield your power like this.
https://news.ycombinator.com/newsguidelines.html
We detached this subthread from https://news.ycombinator.com/item?id=32769091.