11–16 of 16 posts
https://www.npmjs.org/package/tinderbot
Edit: My tinder bot: https://github.com/deftx/loltinder
You can combine with an Android emulator (to spoof GPS location), and a fake facebook to be literally anybody, anywhere, and see who likes you. While it's certainly not the intended use of the app, A/B testing your appearance to different regions is not out of the question.
Or just use this handy node package. I used it to auto like 22,000 people in LA, and went on dates for 9 days in a row. Let's just say I'm a bit exhausted. https://www.npmjs.org/package/tinderbot Edit: My tinder bot: https://github.com/deftx/loltinder
Or just use this handy node package. I used it to auto like 22,000 people in LA, and went on dates for 9 days in a row. Let's just say I'm a bit exhausted. https://www.npmjs.org/package/tinderbot Edit: My tinder bot: https://github.com/deftx/loltinder
Is it possible to mitigate this kind of thing by using certificate pinning?
How would that help? The client doesn't need to trust anything from the server, just firehose likes back at it. Even if you were for some reason using client certificates, you'd just have to rip apart the Tinder APK to get the cert and you're done.
Earlier quoted context omitted.
How would that help? The client doesn't need to trust anything from the server, just firehose likes back at it. Even if you were for some reason using client certificates, you'd just have to rip apart the Tinder APK to get the cert and you're done.
By pinning the cert, the inspection of the protocol wouldn't have been possible the first place, since the app would reject fiddler's SSL cert. The tinder APK would only contain the information needed to verify the cert, not generate a valid one. If this wasn't the case, SSL would be useless.