Rate Limiting

Sort:
skelos

Thanks for the response @bcurtis, and also Jan.

Firstly, I'm glad my scripts are in scope. They make a number of admin tasks much less time consuming!

Re ping: Yeah, I noticed I was hitting the content distribution network. Ping is not a good test, however it is the absolute minimum (when ICMP ECHO is not disabled, at least) my connection might be able to handle if the data were already cached at the CDN.

 

The profile stuff ... I think I was saying why I needed (profile, stats, clubs, current games) even after I had an account name. Or was trying to say that at least. All that data is on the website profile, but it's four endpoints via api.chess.com.

I'm still sorting access to a (new) server in the USA. Once that's done, if some things are faster there I can probably run them there.

 

@Tricky_Dicky: I'm using a 1.4Ghz ARM CPU in a Rasperry Pi some of the time. Closer to a phone or a tablet in power than a PC; local processing time is unlikely to be the issue for almost anything I can think of. (Local access to gobs (GB) of cached data, maybe.)

Probably we're spoiled these days (but we deserve it!) as I think the Raspberry Pi would run rings around the VAX 11/780 I sometimes used at university. happy.png

Tricky_Dicky

VAX!

I used to manage a micro VAX engineering network.

 

 

 

skelos

Ah, but the VAX 11/780 I used ran BSD Unix. happy.png

When forced for one course to use VMS I started learning emacs. More value than the course, that's for sure. grin.png

Tricky_Dicky

But Alpha VMS was the first desktop 64 bit architecture. Way before any other.

 

 

skelos

Point, and the topic is drifting. happy.png

Difster

Instead of requiring a user agent, how about just issuing anyone that wants one, an API key that is tied to their account? Then, if you need to contact them, you have their info.

Furthermore, if each user has an API key, then maybe the user could pull more data than just what is public to everyone else.

bcurtis

Yes, you are describing the next generation of public API. It is not on the current roadmap, but it is mentioned as an "Interactive API" in the docs. We will get to it when we can.

For now, the API has no authentication layer, in order to improve its cache performance. Because of this, some people accidentally abuse the system and we want to help them avoid that. A user-agent is not required, but by adding one to your requests we can reach out and help you achieve your goals.

Difster
bcurtis wrote:

Yes, you are describing the next generation of public API. It is not on the current roadmap, but it is mentioned as an "Interactive API" in the docs. We will get to it when we can.

For now, the API has no authentication layer, in order to improve its cache performance. Because of this, some people accidentally abuse the system and we want to help them avoid that. A user-agent is not required, but by adding one to your requests we can reach out and help you achieve your goals.


Good to know. I've done quite a bit of API development myself. I look forward to the changese.

SirTooper

How does my friend get out of this?