I was going to comment on the Terence Eden excerpt quoted by the author about the woman researching housing benefits on an old PSP browser, when I noticed that you (the OP) are Terence himself. It's strikingly powerful, and a reminder of the duty we have in building our infrastructure.
> Of course, your javascript-based analytics package doesn’t see the users you are bouncing because of javascript failures.
It is frightening to think of how many people are alienated from critical systems every day because of this bias reinforcing the idea that they do not exist.
just use firefox with an adblocker like adnauseam and a fairly decent chunk of the internet stops working, including chase.com and several other massive corp sites.
I can't imagine trying to use links/lynx or a browser with less market share than FF that isn't based on chromium.
Chase works with ad blockers, though.
It doesn't work if you disable JavaScript...but it wasn't always this way!
They had a mobile version of their online banking service at https://m.chase.com that was EXTREMELY FAST and did 85% of what you need to do in an online banking portal (check balances, transfer funds). They scrapped it when they moved to their current bloated monstrosity of the portal that they have today.
It was a big reason why I moved to a credit union (who outsources their online banking services to Alkami, which maintains a very tight portal and supports 2FA AND passkeys!).
i am unclear on if it's because of the adblocker (specifically i use ad nauseam which does block some JS. some.) or because of firefox. I can load it on edge every time it fails on firefox. last week, chase.com worked fine on firefox. the previous 15 months where i needed to log in, it did not.
Someone at chase isn't checking their work on firefox.
FWIW I use Firefox with uBlock Origin and Enhanced Tracking Protection, and use Chase's website almost weekly. No issues that I've noticed on MacOS or Windows
When I have to log into Chase on my computer, I do via Firefox, and it works fine. Maybe you flipped something on in about:config that's breaking it?
i love that i'm holding it wrong. thanks, HN.
And that is what pixel tracking is for. :)