Hello, I started to experience a problem with Mull and Duolingo (and also bromite) that started about 1 month ago.
Basically Duolingo tells me that my browser is not supported but it worked perfectly fine before. Anyone experienced this issue? I can’t find an issue on mull repo apparently about this specific issue. Dunno if it is something about resisting fingerprint but I wonder why that happens…
what on gods sake are they doing so special that requires those browsers explicitly
I’m guessing they don’t want to test on any other browsers, so it’s easier just to say that those aren’t supported. Most likely it works on others, you just need to spoof the agent.
This is definitely the case, but I wonder why companies don’t add a button, such as “Access website without support”, that would get you to the site while clearly telling you that any technical problems (of which, in 99% of cases, there will be none, since all of this seems like supporting Google internet dominance) will be ignored by support.
Sir, this is the internet. Morons will still complain about broken things in public forums even if you make them click through multiple dialogue boxes and popups with warnings in flashing text.
Fair enough. But again, I seriously doubt that Duolingo uses something not supported in Firefox…
I have both Mull and vanilla Firefox on Android, they use all the same headers (including User-Agent) according to DuckDuckGo’s “what’s my user agent” tool.
My guess is that the same defaults that makes Mull more private also disables either cookies or scripts that Duolingo expects to be able to use.
That’s my guess as well. Their mobile app updates feel like they are only there to circumvent adblockers and stopped working all together months ago.
A few days ago I needed to download some transactions from a bank’s site. However, it kept giving “Something went wrong”. I called support and they told me I needed to use chrome. I did and surprisingly enough it actually worked. I did try Firefox less than a minute after that and it was still broken, so it wasn’t just a back-end issue that was resolved while logging on on Chrome. I still have no clue how it’s possible to create a download button that can break on Firefox.
They might not actually require them, but simply display this message if some features detection code fails