_-.
( (o)
" _ |_|"
- | | _ _
" - -" -.| | _ __ ___ _ _(_)___ __ ___ _ __ ___ __ _ _ __(_)
- " -| | | '_ \/ -_) '_| (_-</ _/ _ \ '_ \/ -_) / _` | '_ \ |
" _" -.|,!) | .__/\___|_| |_/__/\__\___/ .__/\___|_\__,_| .__/_|
"- `" -=' |_| |_| |___| |_|
This is a proof-of-concept Ruby client against the Periscope API. Use at your own risk.
The knowledge just came to me in a dream, and/or I reverse-engineered it by tinkering with the running iOS app and sniffing network traffic.
Yes, I just moved to New York and I am now available to help you make your computers compute.
Probably less time than you'd think.
This gem comes without batteries included, my friend. You can read a little about iOS reverse engineering on my site, and then forge your own path into the land of secret-pilfering.
I haven't tested this without signing up for Periscope in the iOS client first. YMMV.
$ export TWITTER_USERNAME=<your_twitter_username>
$ export TWITTER_PASSWORD=<your_twitter_password>
$ export IOS_CONSUMER_KEY=<twitter_consumer_key>
$ export IOS_CONSUMER_SECRET=<twitter_consumer_secret>
$ export PERISCOPE_CONSUMER_KEY=<periscope_consumer_key>
$ export PERISCOPE_CONSUMER_SECRET=<periscope_consumer_secret>
$ periscope-api-stream your-video.mp4
No.
Logging in and rudimentary stream publishing. ffmpeg is required for streaming.
Everything else. This code is terrible and was never intended for production use, so it's missing tests, and the heartbeat mechanism is kinda broken, so your stream is prone to just ending at some point. The full API isn't really implemented.
Kinda. See API.md.
Yes, with two caveats:
- I will not just give you the required OAuth credentials to work on this.
- I will definitely not just give you the required OAuth credentials to work on this.
- Fork it ( https://github.com/gabrielg/periscope_api/fork )
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create a new Pull Request