Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTMP third party client API will be banned #30

Open
Divi opened this issue Aug 23, 2014 · 9 comments
Open

RTMP third party client API will be banned #30

Divi opened this issue Aug 23, 2014 · 9 comments

Comments

@Divi
Copy link
Member

Divi commented Aug 23, 2014

See : https://developer.riotgames.com/discussion/riot-games-api/show/oklxAP21

TL;DR: Riot will block all RTMP third party API. The only way to retrieve game data will be with their official API, which is very poor at this time. Retrieve the spectating encryption key will be impossible. Maybe they will release an API with this data, I don't know.

@jaagupkymmel
Copy link
Contributor

http://www.reddit.com/r/leagueoflegends/comments/2easbn/riot_wants_any_3rd_party_applications_like/cjxpb3r

Apparently Riot will allow to continue downloading spectator data, so if they are using the same method that they are, we should be in the safe. Should confirm with a rioter tho.

@Divi
Copy link
Member Author

Divi commented Aug 23, 2014

You're right, but the encryption key is not in the meta, it's in the RTMP API. And we won't be able to know the live game id.

@lukegb
Copy link
Contributor

lukegb commented Aug 23, 2014

From my reading: They're not blocking it, they're just going to start enforcing the don't-use-APIs-we-haven't-provided rule. They then went on (in edit 2) to explicitly spell out that exclusively for spectating stuff you can retain this functionality and continue to use, for the time being, the RTMP API, since that's the only way to actually get the data you need to do that.

@avborhanian
Copy link

Yeah, I thought it was okay because of this comment. "I meant, they are welcome to keep using it as they have been, as a solution until some future point where we can potentially bring this functionality into the API. This is less of an exception for a particular use case, and more of the point that what they are doing does not affect our platform in the way the more common scraping methods do and is therefore not a concern at this time." Seems to imply RTMP is okay, but they will eventually move it to the Riot API.

@Divi
Copy link
Member Author

Divi commented Aug 23, 2014

I don't think so, they say OP.GG and lolking have exclusive API (private API), which has the spectator API.

@jaagupkymmel
Copy link
Contributor

@Divi source? Should I message a rioter about this (possibly RiotSargonas)?

@Divi
Copy link
Member Author

Divi commented Aug 24, 2014

It was in the Reddit thread. Sargonas said big webites has moved on an "exclusive" API. I already send a message to Riot Sargonas, but no answer atm.

@frostycpu
Copy link
Member

@Divi @jaagupkymmel this: https://www.reddit.com/r/leagueoflegends/comments/2easbn/riot_wants_any_3rd_party_applications_like/cjxp2d3

I don't think he meant LoLKing uses an exclusive API, but rather use the official API for everything possible (meaning they only use RTMP Calls for current games).

@Divi
Copy link
Member Author

Divi commented Sep 18, 2014

Update: RiotShmick said :


If your site is using RTMP, specator data, or other alternative sources than the API to power it, then yes, it will be in violation of the Terms of Service starting 10/1/14. The only exception is using spectator data to generate replay files. The data gathered from spectator data can not be used in other way.

So parsing the spectator files will be prohibed.

Source : https://developer.riotgames.com/discussion/riot-games-api/show/LQEpmLEX

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

No branches or pull requests

5 participants