That's too bad. :\

Have you contacted a blue about it?

Weeeeeeeeeeeell, no, not yet... I'm going to wait for another day to see if that helps, if not, I'll try to contact a blue and brace for the imminence of being ignored :).

Good luck! ;)

I like that the associated game forum for this is the Die by the Sword forum. =D

Some good news and some bad news...

The good news is that I'm getting a response from the APIs again, but that has more to do with some changes my ISP has done today rather that GOG lifting the block, as far as I'm aware. Of course, now I have no way of checking how long a block lasts unless I get blocked again :|.

The bad news is that there is indeed a throttling/blocking mechanism now in place on the products API at least. With some help from a friend that has some AWS instances and doesn't care if his IPs are blocked by GOG or not, I've determined that the throttling is global, his IPs also being banned after various time intervals in which the scanning script worked fine.

The conditions triggering a block seem to be erratic... perhaps there's a schizophrenic machine learning algorithm that controls things without a discernible pattern, or perhaps GOG has trained monkeys for this task as well.

I'm still trying to figure out how to avoid triggering a block, either by lowering the scan rate and distributing the load across a number of IPs or by offering the monkeys responsible for blocking some tasty bananas.

All things considered, I'm getting closer to ending a full mapping run, now a little above 2 billion ids mapped. Nothing spectacular or worthy of mention in the latest batch.

Sublime Text - I approve :)

Now that is what I call a sweet GOGBear cave!

However, bears should really be hibernating in their caves this time of the year, not writing service throttling algorithms. Overlooking this deviation from standard bear behavior, I promise to send honey jars to appease the furry overlord!

Seriously now, can you at least tell us how long an IP block lasts (and when we can expect it to be lifted)? 48 hours, a month, forever? Forever and ever? :)

Forever-and-a-half.

With an abrupt ending to the second half.

I knew it.

But why used signed for IDs instead of unsigned? Same amount of space, double the possible IDs.

Because it makes things more complicated with no benefit. If 2 billion isn't big enough, 4 billion most likely won't be either. Nobody wants to take the big risk of hitting a limit for the tiny benefit of saving a few bytes. Databases don't grow linearly, otherwise Google would probably be running on a single Raspberry Pi now. In short: If you're worried about space, just go with the bigger type instead of messing with unsigned.

Beautiful XD