You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2022. It is now read-only.
TBH, I am pretty disappointed HOW bad blizzard site is. It uses crazy cache that can show you literally three different profiles just by clicking "refresh" button in browser. Refresh -- profile is private. Refresh -- profile SUDDENLY NOT private. Refresh -- profile not private, but dozen of info not loaded. It's f...in crazy.
I am thinking about abandoning my project until API will be released (so sort of never, I guess).
I see what you're saying. It's pretty sad that it would load this way via blizzards frontend. The most I could recommend is hitting the endpoint several times (perhaps concurrently) and hope one of the payloads is larger than the rest and has real data. Since this app is a basic passthrough I don't think there's much I can do on my end besides performing the same concurrent logic.
Web scraping is never fun. This project and my anime ripper are both projects I don't keep up with very often for this particular reason. It's almost not worth the trouble.
I tried to make stats-function recursive with attempts counter. Even with 100 attempts it not loads some profiles. Because their caching is NIGHTMARE. It started only after december, their forums have tons of reports, but nobody cares, "api is not a priority"...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like this:
We should somehow mitigate it, current answer in such cases:
It happens pretty often (40% of page loads).
Related to #22
The text was updated successfully, but these errors were encountered: