Skip to content
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.

blacklist rooms. #283

Open
rlemon opened this issue Oct 14, 2016 · 5 comments
Open

blacklist rooms. #283

rlemon opened this issue Oct 14, 2016 · 5 comments

Comments

@rlemon
Copy link
Collaborator

rlemon commented Oct 14, 2016

certain rooms !!summon the bot and then spam/die/malicious use of it. I think we should implement a !!ban system for rooms.

@ssube
Copy link

ssube commented Oct 14, 2016

What if you use !!summon to rate-limit !!die and vice versa? If a room has killed the bot in the last N minutes, don't let them summon it.

@rlemon
Copy link
Collaborator Author

rlemon commented Oct 14, 2016

the problem isn't only with die, she is 'untethered' so to speak. anyone can summon her anywhere and then spam messages, echo shit, add new commands, etc. If a room has a history of doing this, why should they be able to summon the bot there?

Also with that idea in mind, people run !!die from the sandbox or from rooms she's been in for days (I don't often check which rooms she is in, only when I need to restart her).

@allquixotic
Copy link

+1

We just completely deleted summon.js over a year ago in the Root Access fork, so this has no impact on us. Do as you will.

@rlemon rlemon self-assigned this Aug 11, 2017
@rlemon
Copy link
Collaborator Author

rlemon commented Aug 11, 2017

I'm going to go ahead and implement this if there is no pushback.

There appears to be a set of rooms that just use the bot to spam their own room (they like gifs, who can blame them).

Due to the chat throttling this makes Cap very slow to respond to everyone else.. Said rooms can fork and run their own spambots if they like.

@Zirak
Copy link
Owner

Zirak commented Aug 11, 2017

This sounds like a fairly good idea, go ahead.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants