Skip to main content
SharePoint

Return to Answer

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

I just saw an issue like this over on the Travel site, so I'll steal my own explanation from there:

For what it's worth, spam flags are intended for use on only the most egregious cases, like "ChEaP GUCC1 BAGS HERE" or "STREEM LIVE 5PORT5 ||0VV!" They show up with priority in the mod queue and carry a hefty reputation penalty for post authors when enough accrue (just like offensive flags). The case you described is reaaaaaalllllly on the borderline... it's obvious why you considered it spam, but it's also at least intended to be relevant to the topic, so one could argue that it's not technically the intended target for spam flags. For more info, see the community FAQ on Meta SEthe community FAQ on Meta SE.

Ultimately, though, only the mod who handled the flag could say for sure what happened. Could be a difference of opinion about that borderline case, or something as simple as a misclick in the mod menu.

I just saw an issue like this over on the Travel site, so I'll steal my own explanation from there:

For what it's worth, spam flags are intended for use on only the most egregious cases, like "ChEaP GUCC1 BAGS HERE" or "STREEM LIVE 5PORT5 ||0VV!" They show up with priority in the mod queue and carry a hefty reputation penalty for post authors when enough accrue (just like offensive flags). The case you described is reaaaaaalllllly on the borderline... it's obvious why you considered it spam, but it's also at least intended to be relevant to the topic, so one could argue that it's not technically the intended target for spam flags. For more info, see the community FAQ on Meta SE.

Ultimately, though, only the mod who handled the flag could say for sure what happened. Could be a difference of opinion about that borderline case, or something as simple as a misclick in the mod menu.

I just saw an issue like this over on the Travel site, so I'll steal my own explanation from there:

For what it's worth, spam flags are intended for use on only the most egregious cases, like "ChEaP GUCC1 BAGS HERE" or "STREEM LIVE 5PORT5 ||0VV!" They show up with priority in the mod queue and carry a hefty reputation penalty for post authors when enough accrue (just like offensive flags). The case you described is reaaaaaalllllly on the borderline... it's obvious why you considered it spam, but it's also at least intended to be relevant to the topic, so one could argue that it's not technically the intended target for spam flags. For more info, see the community FAQ on Meta SE.

Ultimately, though, only the mod who handled the flag could say for sure what happened. Could be a difference of opinion about that borderline case, or something as simple as a misclick in the mod menu.

Source Link
Pops StaffMod
Pops StaffMod
  • 101
  • 3

I just saw an issue like this over on the Travel site, so I'll steal my own explanation from there:

For what it's worth, spam flags are intended for use on only the most egregious cases, like "ChEaP GUCC1 BAGS HERE" or "STREEM LIVE 5PORT5 ||0VV!" They show up with priority in the mod queue and carry a hefty reputation penalty for post authors when enough accrue (just like offensive flags). The case you described is reaaaaaalllllly on the borderline... it's obvious why you considered it spam, but it's also at least intended to be relevant to the topic, so one could argue that it's not technically the intended target for spam flags. For more info, see the community FAQ on Meta SE.

Ultimately, though, only the mod who handled the flag could say for sure what happened. Could be a difference of opinion about that borderline case, or something as simple as a misclick in the mod menu.