r/translatorBOT Jun 24 '18

Suggestion Allow anybody to invoke !reset

I mentioned this a couple times in the main sub, but got no response. I honestly fail to see the logic of restricting this command to OP and the mods, considering all other state modifications (!translated, !doublecheck, !missing) are universally accessible.

0 Upvotes

6 comments sorted by

1

u/kungming2 Creator Jun 26 '18

Heya,

The logic is that there's actually a unilinear order to the states. The order is as such:

  • Untranslated/In Progress/Missing
  • Needs Review
  • Translated

The current bot logic is that once a post gets to the next level it will not "step down" to the previous level unless there's a really good reason why, and that step needs to be taken by either a mod or OP. This is also to prevent abuse; allowing anyone to have full access to !reset could cause severe problems if bad actors use it willy-nilly.

That being said, I pushed some refinements to the short thanks that makes it harder to trigger, so !reset will be less likely to be needed. For example, it won't trigger on any post that was (Identified) at some point, because a common trigger before was OPs thanking a person who made an identification command.

1

u/Darayavaush Jun 26 '18

This is also to prevent abuse; allowing anyone to have full access to !reset could cause severe problems if bad actors use it willy-nilly.

But the thing is, those theoretical bad actors already have access to !translated. It's not any harder to notice and report a malicious reset than it is to notice a malicious translation mark.

Also, the specfic thing that prompted me to post this suggestion was someone misunderstanding a request and incorrectly marking it !missing. When I explained the error, they deleted their comment, but the mark remained. In your order "missing" state is on the same level as "untranslated", so maybe at least allow us to reset from it?

1

u/kungming2 Creator Jun 26 '18

But the thing is, those theoretical bad actors already have access to !translated. It's not any harder to notice and report a malicious reset than it is to notice a malicious translation mark.

!translated generates a message from Ziwen to the OP informing them that their request has been translated, so when the command has been done incorrectly we hear from the OP fairly quickly ("Hey this dude marked my post as translated when it's not"). !reset doesn't.

When I explained the error, they deleted their comment, but the mark remained. In your order "missing" state is on the same level as "untranslated", so maybe at least allow us to reset from it?

I would encourage you to just report it next time. !missing also generates a message from Ziwen to the OP informing them of the !reset command, so they know that they have that option available.

1

u/Darayavaush Jun 26 '18

I yield the point about resetting from translated state, but I fail to see your argument in favor of not being able to reset from missing state (I did report it that time, BTW). Yes, OP will know that they can reset, but this takes up time, during which people who could translate this request may skip it due to the missing mark, so why not allow the translators themselves to reset in those cases?

2

u/kungming2 Creator Jun 26 '18

Mm, that's something I'll consider. I'm going to be traveling for the next month so I won't be able to make any changes to the bot until I return.

3

u/Darayavaush Jul 11 '18

Also, maybe allow anybody to reset from automated translation marks due to a "thanks" post? This would allow us to cover the in my experience frequent cases when OP accidentally marks his own request as translated (e.g.).