I think I'll just say from here that I can't be bothered responding to anything else in this thread, which tl;dr
- There is no evidence of a problem (There's plenty)
- There is evidence of a problem, but there's no evidence of the problem being Jagex side (The browser dev tools show it as being Jagex side because Jagex's own servers say it is)
- There's a problem but it only exists on this one API endpoint (it existed on basically all dynamically generated content on the forums)
- Hmm is basically a criminal for writing scripts to identify the problem and Jagex don't appreciate it (I definitely get the impression Jagex don't appreciate me! - but it still isn't breaking any of the TOS or rules so RIP, isn't criminal, nor does it stop there being a problem)
- The problem only exists when measured because measuring it triggers anti-ddos measures that cause the problem (Heisenberg Uncertainty principle aside, this problem exists and effects legitimate users who haven't done any testing, it's also effecting legitimate users when the actual testing is being done by Google, not the user, so its makes no sense that Jagex correlates the two).
I cannot imagine at all Jagex will care about an insignificant amount of automated testing. What I can imagine is that Jagex will read several pages of trash given the entire problem was reasonably assessed on the first post, and facepalm how it got this this far. So to the benefit of whom I presume will be Mod Lyon or Allstar, I'm gonna stop feeding this thread any further.
28-Mar-2020 15:26:48