I use it almost every day. I'm thinking The user is using a weird user agent/browser and misdiagnosed the problem.
It looks like Firefox but there's just so many small browsers these days. Honestly I'd need to see the offending code. If it's user agent testing, those strings should still be readable even in a compressed js unless they run it through an obfuscator
> should be readable even in a compressed js unless they run it through an obfuscator
User-Agent may be determined on a webserver/proxy level and request redirected silently to a page with JS just showing the banner. It does not have to be based on JS checking anything.
The small browsers thing sounds about right. Check the link he posted about the email someone received on Reddit. It's posted like it's a screenshot from Mutt or some other terminal mail editor. Looks more like they are flexing their email terminal usage not just copy/pasting the message (png for text? come'on!).
Probably using qutebrowser or something else like that.
Just from the Reddit post as well - doesn't feel overly user-hostile or deserving of the 'JP Morgan Chase Bank admitting to me they hate Linux and BSD desktops and actively block them' title anyway.
If there's active blocking based on OS (from replies in this thread, evidence seems to be slim) then that's not great, but this seems to be pretty one-sided so far.
Well that kind of matches the message he received from the website. It looks like they are just trying to notify you that there is a Chase Mobile App available (which for the average phone user, would be 99.9999% better than using a browser). Personally I wouldn't use a phone for banking but some people don't have laptops/desktops.
The article is 100% correct, I've experienced the exact same thing. For a while I thought it was blocking me due to uBlock or something, took me a while to figure out it was just the user agent.
It looks like Firefox but there's just so many small browsers these days. Honestly I'd need to see the offending code. If it's user agent testing, those strings should still be readable even in a compressed js unless they run it through an obfuscator