Nope, only workaround i have found is to instantly press the back button as soon as i see cloudflare
As of now i suppose an android browser is the only real alternative…
Nope, only workaround i have found is to instantly press the back button as soon as i see cloudflare
As of now i suppose an android browser is the only real alternative…
Let’s not? Must understand the threat model out there. CF is in front of all my businesses by default, because it’s so much less expensive than dealing with a single cyber-attack of any kind.
This site does not work in Sailfish browser:
https://jouw.postnl.nl/track-and-trace/
Sorry for your businesses , cheap services are a common problem that only can be tackled by paying a fair price. By offering free and cheap services Google and the like could grow into superpowers.
Finally, i can confirm that with the new .67 update youtube works, and also much much better than before
Now anyway, i suppose it’s time to fix instagram, as so much time has passed but it’s still not loading videos…
We can try to figure out a user-agent override for instagram as well.
On tagesschau.de and sportschau.de the menu doesn’t work anymore.
Sites that are protected by cloudflare show this annoying cloudflare-spinning-wheel and then crash the browser somehow. Not immediately, but closing the tab leaves the cloudflare-site visible even in the other tab and the browser becomes unusable. 5.0.0.62.
You are saying this like the user agent is the culprit,
I don’t know if it’s true but if it’s just that, i suppose it’s demostrating us how evil they are…
The user agent itself is not the culprit. The culprit is the sites which use the user agent to detect browser features. Instead of doing something sensible, like actually detecting browser features.
That’s what i meant, but you explained better
And this would mean they are just bad, cause yes they should do something better then…
Meta decided to train its AI with European user data on all Meta products. Better not use them.
It looks like after more than a month of hard work by several dedicated teams, clownflare have finally managed to “fix” their “compatibility problem” with “older browsers”:
Youre lucky it only happens for cloudflare;
imagine having to ack every single time you search from the browser (best feature ever btw, honestly)
I guess some headers are missing in the outgoing request…
I found a way to reliably crash the browser. It’s rather unusual.
It is a bit annoying to reproduce though since it requires a marktplaats account and perhaps several conversations with sellers.
The page in question is Login Mijn Marktplaats. The interesting thing is that this page itself works fine. But any atempt to navigate away from the page (refreshing, navigating forwards or backwards, clicking an external link, entering something else in the address bar on the same tab) causes the browser crash ~90% of the time with the following output:
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PMessagePor
t::Msg_PostMessages Processing error: message was deseri
alized, but the handler returned false (indicating failu
re)
Segmentation fault (core dumped)
They seem to roll out important features like that in waves or so, maybe they want to test if it really works well… I’ve been seeing this for some days now, maybe two weeks or so.
Again asking stupid questions as non tech person… now that Jolla will update to ESR102 with 5.1 update, will it solve problems seen with for example websites using cloudflare?
Probably not, and if Cloudflare is really doing their best trying to cripple the Internet for old browsers, I don’t believe even ESR 115 (next ESR after 102) is going to work much longer (if it hasn’t been blocked already).
Edit: I checked, that ESR 115 is already EOL, except for Windows 7 and some old macOS versions, which will go EOL with ESR 128 in September 2025.
Thank you for the answer!