lichess.org
Donate

Local analysis problems? Please read this.

#11
@DanMoller said in #8:
> I'm using chrome on Android and this workaround "alone" didn't work. I had to clear the browser's cache for it to work again in version 14 (didn't try v16, though)
>
> Is there anything an Android user could do to help? I can't seem to find a developer console here.

Not really, except let us know once you get around to checking v16
#15
@beginnerdev said in #14:
> I mean, is there an alternativ to cloudflare for lichess.

Not sure. Perhaps this discussion deserves its own thread. See also the warning about off-topic comments being deleted. I would argue this is not off-topic, because it still regards my question, which is on-topic.

It depends on what LiChess needs, which is how I phrased the question. Lichess can still buy their own rackspace to host content, but it would require several locations around the world. And simple rackspace does not offer resilience against DDoS attacks, so yeah.

It's worth it if you consider CloudFlare to be a degradation of the privacy Lichess users can now expect. The "we protect your privacy, but our contractors don't" is a euphemism for "we don't protect your privacy", especially if those contractors can price their services more affordably by selling user data.
#16
Engine is only working on and off. It has been down the previous 24 hours. Following the steps posted above it reads:

lichess.min.js:2 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. goo.gl/7K7WLu
rn @ lichess.min.js:2
(anonymous) @ lichess.min.js:2
(anonymous) @ lichess.min.js:2
lichess.min.js:2 Lichess is open source! lichess.org/source
lichess.min.js:2 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. goo.gl/7K7WLu
(anonymous) @ lichess.min.js:2
resumeWithTest @ lichess.min.js:2
play @ lichess.min.js:2
await in play (async)
(anonymous) @ lichess.min.js:2
(anonymous) @ lichess.min.js:2
r @ lichess.min.js:2
(anonymous) @ lichess.min.js:2
move @ lichess.min.js:2
ht @ puzzle.min.js:1
(anonymous) @ puzzle.min.js:1
setTimeout (async)
q @ puzzle.min.js:1
Gi @ puzzle.min.js:1
wg @ puzzle.min.js:1
Q @ lichess.min.js:2
await in Q (async)
(anonymous) @ P9hAi:9
Promise.then (async)
(anonymous) @ P9hAi:9
stockfish.js:22 Stockfish SF_classical 64 POPCNT by T. Romstad, M. Costalba, J. Kiiski, G. Linscott
P9hAi:1 [Deprecation] The keyword 'slider-vertical' specified to an 'appearance' property is not standardized. It will be removed in the future and replaced by vertical writing-mode (currently experimental).

Chrome. UK.
#17
Watching today's tournament the engine worked well for me and was again quickly updated while leafing through the turns, perhaps faster than ever.
#18
@s2numbuq35i
This is not the thread to discuss CloudFlare alternatives. And just so noone gets the wrong idea, popular websites lacking the resources of an Amazon or Comcast actually need CDNs like Cloudflare and Akamai for a good user experience. Their business model is not based on sharing your data like Facebook or Google. They just cache javascript and large files. They've historically released transparency reports detailing government requests for data and their responses to these requests. You can read more on their website.

This thread is for posts that say "yo, fix my shit".
#19
Just a quick note on where we are, there is no hard evidence in this thread that the CloudFlare caching issue is still occurring. Some failures posted here could well be errors in lichess code or mangled local data that usually can be fixed by clearing site settings. Noone @ lichess has reported engine load failures due to cached 404s in about 3 days.

But this thread will remain sticky until we are sure.
#20
It got resolved for me by disabling my ad blocker, maybe this is part of the issue

This topic has been archived and can no longer be replied to.