| #!/bin/sh | |
| command -v apktool >/dev/null 2>&1 || { echo >&2 "I require apktool but it's not installed. Aborting."; exit 1; } | |
| command -v keytool >/dev/null 2>&1 || { echo >&2 "I require keytool but it's not installed. Aborting."; exit 1; } | |
| command -v jarsigner >/dev/null 2>&1 || { echo >&2 "I require jarsigner but it's not installed. Aborting."; exit 1; } | |
| TMPDIR=`mktemp -d 2>/dev/null || mktemp -d -t 'apkdebug'` | |
| APK=$1 | |
| DEBUG_APK="${APK%.*}.debug.apk" | |
| if [ -f $APK ]; then |
I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)
Note: this was written in April/May 2014 and the API may have changed since. I have nothing to do with Tinder, nor their API, and I do not offer any support for anything you may build on top of this
| use POE qw(Component::Client::HTTP Component::Server::HTTP ); | |
| use HTTP::Request; | |
| POE::Component::Client::HTTP->spawn(Alias => 'ua'); | |
| POE::Component::Server::HTTP->new( | |
| Port => 8000, | |
| ContentHandler => { | |
| '/' => sub { | |
| doHttp("FINDME:".time()); |