You are viewing a single comment's thread.

view the rest of the comments →

TwoTailedFox ago

The problem wasn't you being controversial, the problem was you spamming.

j_ ago

If the problem is spamming — in this case taken to mean posting at a high rate — then shouldn’t the solution be to throttle based on this rate? i.e. a user is posting too often, so limit his submissions for a short while.

How do you justify a throttle based on controversiality (downvotes), if controversiality is not the problem?

TwoTailedFox ago

Downvotes do not indicate controversy; they indicate that a discussion point is disruptive, or unproductive.

Here, users have correctly indicated that the user is a problem, and that his spamming is detrimental.

j_ ago

Downvotes do not indicate controversy

I’d like this to be true but we know it isn’t. People downvote things they disagree with.

Here, users have correctly indicated that the user is a problem, and that his spamming is detrimental.

So again, shouldn’t the countermeasure be targeting his spamming behaviour, regardless of the content? i.e. if a user only posted cute kitten photos, but then started posting them not only to /v/aww but to random subs multiple times a day, they should be penalised equally to someone who spammed whatever content CSW did.

TwoTailedFox ago

The issue was spamming the same content (in this case, an inaccurate copypasta). The scenario outlined above should be taken care of by the mods of those subverses; one of the issues here is that the spammer was the mod of his own subverse.

j_ ago

The scenario outlined above should be taken care of by the mods of those subverses

Same for what happened; mods should ban CSW.

one of the issues here is that the spammer was the mod of his own subverse.

And that’s why we can block subverses we don’t want to see. Perhaps subverses should be unlisted from /v/all temporarily if there are enough spam reports (or spam reports are verified by an admin).