-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to prevent content that breaks the TOS? #75
Comments
So far that seems to have not happened. If it does though, I imagine the repository owner will have to step in. |
I think it happens by vote which (hopefully) is reasonably sane unless you get flooded by the likes of 4chan. I've proposed something in #82 to help at least with malicious code-related changes (wouldn't help with |
I think looking up each voter's account age would help. New accounts' votes shouldn't matter as much as someone who has been on the site a while (you could also look at activity, but some types of activity are easier to fake than others). I'm not sure there's a good way to do that, outside of taking a big hit up front and storing the API results inside the MySQL database that chaosbot ships with. Overall, it's an interesting problem and I think it'll sort itself out should the project become a target of online vandals. |
Currently the bot factors the voter's follower count. Granted, you could probably create an army of fake accounts all following each other, but that seems impractical. |
Not anymore! #42 made it so that all votes are equal (including people who create brand new accounts with no activity and no followers). |
This issue hasn't been active for a while.To keep it open, react with 👎 on the |
/vote close |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Command Ran |
⛔ The issue has been closed after a vote. |
Bad @chaosbot. Go to your corner and be quiet. 🤖 Mutes thread. |
I am pretty confident that the readme file (for starters) is going to get replaced with something pretty heinous by "certain internet communities".
Is there a way to prevent the chaosbot from merging blatant anti-TOS content here? Could it possibly get the project shut down? Who would ultimately be responsible for such an event?
The text was updated successfully, but these errors were encountered: