Skip to content
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.

Handling 'intelligent spam' #12

Open
sharky93 opened this issue Jul 12, 2014 · 1 comment
Open

Handling 'intelligent spam' #12

sharky93 opened this issue Jul 12, 2014 · 1 comment

Comments

@sharky93
Copy link
Member

We have a limited resource of execution at our hand so need to save it from spam.
By 'intelligent spam' i mean robots using legitimate Python code generating images etc.
Introducing a CAPTCHA might be overdoing things since it would make the process more tiresome.

I think rate limiting requests based on IP addresses etc might just work out fine. Can surely start out with a simple system.

Any other ideas?

@sharky93
Copy link
Member Author

sharky93 commented Aug 1, 2014

With the queue's in place, only a fixed number of containers are ever allowed to run at a time, so we're good for now. Might need an IP based filter in the future.

Refer - 5be1494 and b41e54f

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

1 participant