Interesting that the Under Attack Mode wasn’t used at all here. I understand not wanting to break APIs but I feel temporarily challenging non-API usage could have at least helped without impacting users too much?
I talked about that directly in the post. We didn't want to just challenge everyone. We use JS challenges but we try to use them sparingly. The rest of the ops team and I were fighting to stay up but it never got so bad that it was a choice between complete outage and using the Under Attack mode.
Such an interesting showcase of history.
RCT was a masterpiece written in Assembly from hand. Looking at code from OpenRCT2 you can really see the thought behind it.
Now ISO Coaster really is a badly slipped together adaptation. A lot of details don’t make sense, graphics often look weird and performance is terrible - all while using tons of compute resources.
Nothing to do with politics and everything to do with crappy AI slop.
There was some list somewhere of some of those reports and it was painful to look at
Visited for the first time and it said I already visited 800+ times with a 99.5% accurancy - not very promising.
From the code this also looks like very simple client-side fingerprinting + IP information?
We’ve just deployed a fix to the core matching logic that should significantly improve accuracy and reduce false positives. Feel free to retry at https://deviceprint.io
and share your results!
reply