You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
6I do not like the idea of using fake / separate accounts for this. Philosophically, that breaks tradition: it allows whatever user controls the account(s) extra privilege over other users. Practically-speaking, it removes the cost of getting it wrong: everyone signing up for this does so with the understanding that they're still responsible for their actions, even if they allow those actions to be dictated to some extent by SD; they have their accounts to lose if they take that responsibility lightly.– Shog9Commented Mar 6, 2018 at 4:06
-
3@Shog9 - That's actually a very convincing point of view... A good thing about a special user is that if it goes haywire there is only one user to ban (and presumably it would make it relatively easy to find all the damage it caused). I also imagined that such a user would have little other privileges (ie, it can't vote/answer/comment/etc) so it wouldn't be a useful account excepting for spam flagging. But the potential loss of accountability is a very good counterargument...– ShadowCommented Mar 6, 2018 at 4:24
-
1@Shadow If the thing goes haywire, we have other ways of dealing with that. It'll get shut down very quickly by whoever notices, and if necessary we can revoke the API access tokens we have.– ArtOfCodeCommented Mar 6, 2018 at 5:36
-
2@Shog9 and Shadow, I continue to disagree; it would be cleaner with dedicated bots account, in the end the bot developers are always responsible (a random selection of 300 users is very hard to keep responsible), it's messy for moderators and it's gaming flags and badge (not that I care, but some do). Maybe yeah if instead the developers account were used but probably 1 bot account connected to a 1 single developers would be best, but I guess it is best we discuss this on another meta and concentrate on number on flags that SD should cast on this meta.– Petter FribergCommented Mar 6, 2018 at 20:37
-
1Ok, so you do want dedicated accounts, @Petter? I think that's something we'd have to be very, very careful with; the entire system is designed around individual responsibility, and a bot account separates that from any one individual. Try to focus on what problems such an arrangement would solve, and how we might reduce the risk of error or abuse.– Shog9Commented Mar 6, 2018 at 20:43
-
3@Shog9 Yes either developer accounts (like Andy, comment bot) or 1 single bot account connected to developer profile (like BR, natty), the developer can't flag when bot does, this makes it clear for moderator what is going on (they know why flagged), the flag goes either to developer (merit) or to bot account, but this rule is not directly related to SD more a general rule. This random picking a user from a +300 users base seems messy and without merit.– Petter FribergCommented Mar 6, 2018 at 20:48
-
3To flag 5 times you just would need 5 developers (hence probably not a problem for SD), but yeah the users connected to bot account can't flag themself If the bot does a messy you just follow the developer link in profile and you will find out who is to blame and can fix stuff– Petter FribergCommented Mar 6, 2018 at 20:49
-
2Just for sake of argue, immagine you have 300 users and miss flag 300 times, that however would be only 1 miss flag per user (how would you blame that user?). This is not the case for SD but just trying to explain how the logic of responsibility fails, also since badges are a thing for some, what merit did these 300 users have?, how can a moderator easily identify that it was auto-flagged if they see random users (they can't even get experience on who is who)– Petter FribergCommented Mar 6, 2018 at 21:09
-
1I think you should write an answer, @Petter; there's a lot to unpack in those last two comments. While you're writing that, consider this: one bot would be insufficient. Quite possibly 5 bots would be insufficient. A user with 15 rep starts out with 10 flags and that doesn't increase significantly until there are hundreds of past helpful flags - so on a site with a spam problem you'd need a lot of bots. If you wanted to raise 5 flags/post on 40 posts a day, that'd be 200 bots minimum. Nevermind the crazy optics of even creating 200 network-wide sockpuppets.– Shog9Commented Mar 6, 2018 at 22:29
-
1Naw, @FTP is right, I'm not thinking clearly here. 20 bots is still a problem, but less of one than 200.– Shog9Commented Mar 6, 2018 at 23:25
-
1@Shog9 Fundamentally, allowing a bot to act on my behalf separates responsibility (mine) from control (bot's). If its actions cause me to be banned, I have no recourse, except to deactivate it, and apologize. I can't see how this is better than having dedicated accounts, where responsibility is placed directly on the developer, rather than implicitly so.– jpaughCommented Mar 7, 2018 at 15:29
-
1That is recourse, @jpaugh. You're using a tool - that doesn't absolve you of responsibility. In practice, if something went horribly wrong we'd probably disable both the tool and the folks using it until the problem could be sorted out. But as with Petter's concerns, this probably should be a separate discussion if we're discussing hypothetical situations.– Shog9Commented Mar 7, 2018 at 16:03
-
1@Cerbrus Negative. Everyone who has SmokeDetector privileges. That's the list hardcoded into Smokey's config, available here on GH (plus all mods).– ArtOfCodeCommented Mar 7, 2018 at 16:29
-
1@Shog9 Yes, that is status quo; which is why I won't enable smoke detector, no matter how accurate it is.– jpaughCommented Mar 7, 2018 at 16:40
-
1I'm with @jpaugh on this. And if the SE interface asserts that user X has taken an action, other users should be able to trust this assertion. Currently, they can't. Something like en.wikipedia.org/wiki/Wikipedia:Bot_policy would be far more transparent & accountable. 3rd-party bots shouldn't masquerade as human users for the sake of any CRUD operation except maybe retrieval. I'm disappointed SE considers it acceptable, let alone on this scale. Spam-fighting is important, but hardly justifies such a serious abuse of accountability as this.– user136089Commented Mar 8, 2018 at 0:03
|
Show 24 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_`
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you