Skip to content
This repository has been archived by the owner on Oct 28, 2018. It is now read-only.

Rate limit can be avoided using JS #30

Open
DeadPackets opened this issue Mar 4, 2017 · 4 comments
Open

Rate limit can be avoided using JS #30

DeadPackets opened this issue Mar 4, 2017 · 4 comments

Comments

@DeadPackets
Copy link

Anyone can pet with a ridiculous speed using the following JS:

window.setInterval(function(){ pet() }, 80)

@ineffyble
Copy link
Owner

Hey, yeah, it's not perfect, although there's some server-side limitations (in terms of max quantity of pets per POST (rejected if too large), and in terms of maximum number of requests per 5 minute window (throttled by rack-attack).

Definitely more to be done though.

@DeadPackets
Copy link
Author

Hmm, you could fix part of the issue by uglifying the client side JS or at least making it a bit hard to read.

@ineffyble
Copy link
Owner

Plan when I find time to improve things is switch to WebSockets and probably a ReactJS front-end. Which would definitely have an obfuscation advantage.

@Qwertie-
Copy link

How will you obfuscate the code when its open source anyway. Even if you couldn't work out which function to call you could just watch the network tab to see whats going on.

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

No branches or pull requests

3 participants