Hey thanks for the tips. I've been unable to login for at least a week from this system - I tried in private mode too (no password extension) and the same thing happened. I have also tried chromium (no plugins).
Explicitly not allowing logins from megacorp browsers is at least a deliberate choice. What's worse are all the websites out there that do not allow login or use because they paid web devs who chose to use features which only exist in megacorp browsers. This is so common it's almost the status quo now. At least a website just refusing intentionally is a nice change of pace and you know where you stand.
What features/browsers are you talking about specifically?
On one hand, you cannot expect any developer to support a browser that is completely unheard of to them, or expect codebases to freeze because something doesn't work on some certain ancient Opera Mini version. Developers serve business goals, which are tied to user goals. If a single user is using some super niche browser with a custom home-brewed rendering engine, then I don't feel bad about not supporting it - not at all.
On the other hand, if you're talking about something like WebNotifications on IE11 or a certain browser API on a B-list browser, then there should certainly be some graceful fallback instead of the entire site being unusable.
The point is you really don’t need to anymore. The IE6 days are long gone, thankfully. It’s very rare that something non-essential breaks if you just follow the standards. At worst you tend to get a semi-broken layout issues, but still functional.
> if you're talking about something like WebNotifications on IE11 or a certain browser API on a B-list browser, then there should certainly be some graceful fallback
These sites need to have fallbacks for those types of specializations anyway, since there’s enough variation even among the popular platforms/browsers/last few versions.
Anyway, I don’t think we’re disagreeing at all. Just wanted to mention for those that aren’t doing frontend today that this kind of browser support issues is almost always a result of blatant disregard for best practices – like user agent gating – or user hostile behavior like ad-tech fingerprinting.
There are standards and then there are de facto standards. Sadly, it looks like Chromium is well on its way to being the latter. As soon as Apple is forced to allow alternate browsers on iOS it’s only a matter of time before the takeover is complete.
I've had the same issue with Twitch. I think something in some kind of bot detection framework changed, or some Firefox update broke the weird assumptions bot detection frameworks make. Either way, these websites need to fix their login system.
It's likely intentional as I am sure Google will try again to change manifest v4 to disallow the functionality that makes adblockers work, in the way they tried with v3 before massive pushback.
Twitch wasn't allowing me to login using Firefox in windows either. The site was totally fine not logged in, so who the f knows what the screw up is there. I'll add to the pile of WTF seems to be happening with twitch these days. It's a service ripe for disruption, so please someone make a compelling alt.
Last week (week before?) I had a few days I couldn't login from firefox. They said to update your browser, and that firefox was a supported browser, but I was on the latest firefox. Works now though.
Another datapoint: I'm streaming and watching on Twitch multiple times a week, all from Linux and using Firefox. Never had any problems with login.
(Though, somewhat related, I have a funny bug for nearly a year now where Ctrl-V does not work in the Twitch chatbox. I have a workaround in place with a script bound to a global hotkey that sends the clipboard contents as individual keyevents via the Wayland virtual keyboard extension protocol. [1])
Like all broken bot detection, detection breaks and unbreaks at random. Maybe it dislikes my timezone, maybe it's my exact GPU driver, maybe it's the weather.
My laptop's Firefox works, my desktop's doesn't. Same IP, same browser, same addons, same account. I can't explain it and the error message "verification failed" doesn't exactly give me much to go on.
I've just logged into my corp Godaddy account using Firefox on Arch (actually). I'm not hiding my user agent. I haven't used Windows for over 15 years.
I suspect that a lack of Javascript is the culprit, as mentioned in the error report.
Javascript is not disabled on any of my browsers. I am not using a vpn or proxy. I have tried multiple browsers. I have tried with and without extensions.
I suspect their stupid popup wouldn’t have even shown if JS was disabled.
Add zalando to the list, for well over a month now throwing error in FF on Linux. Experienced folks got priced out, Angular/React devs use only chrome.
31 comments
[ 3.6 ms ] story [ 71.7 ms ] threadEdit: The same thing is happening with chromium.
If it’s deliberate it’s a very new issue, or at least something I haven’t encountered.
Maybe it’s an extension or something?
On one hand, you cannot expect any developer to support a browser that is completely unheard of to them, or expect codebases to freeze because something doesn't work on some certain ancient Opera Mini version. Developers serve business goals, which are tied to user goals. If a single user is using some super niche browser with a custom home-brewed rendering engine, then I don't feel bad about not supporting it - not at all.
On the other hand, if you're talking about something like WebNotifications on IE11 or a certain browser API on a B-list browser, then there should certainly be some graceful fallback instead of the entire site being unusable.
The point is you really don’t need to anymore. The IE6 days are long gone, thankfully. It’s very rare that something non-essential breaks if you just follow the standards. At worst you tend to get a semi-broken layout issues, but still functional.
> if you're talking about something like WebNotifications on IE11 or a certain browser API on a B-list browser, then there should certainly be some graceful fallback
These sites need to have fallbacks for those types of specializations anyway, since there’s enough variation even among the popular platforms/browsers/last few versions.
Anyway, I don’t think we’re disagreeing at all. Just wanted to mention for those that aren’t doing frontend today that this kind of browser support issues is almost always a result of blatant disregard for best practices – like user agent gating – or user hostile behavior like ad-tech fingerprinting.
There are standards and then there are de facto standards. Sadly, it looks like Chromium is well on its way to being the latter. As soon as Apple is forced to allow alternate browsers on iOS it’s only a matter of time before the takeover is complete.
Or maybe the cost to test on alternative browsers and operating systems is greater than the revenue lost by not properly supporting Firefox & Linux?
Can you elaborate?
(Though, somewhat related, I have a funny bug for nearly a year now where Ctrl-V does not work in the Twitch chatbox. I have a workaround in place with a script bound to a global hotkey that sends the clipboard contents as individual keyevents via the Wayland virtual keyboard extension protocol. [1])
[1] https://github.com/majewsky/devenv/blob/4a3b36daafbcb93d8b43...
My laptop's Firefox works, my desktop's doesn't. Same IP, same browser, same addons, same account. I can't explain it and the error message "verification failed" doesn't exactly give me much to go on.
Strange.
I did just check it using multiple browsers and different IPs and the prices are the same. So they are probably not getting away with this...
I suspect that a lack of Javascript is the culprit, as mentioned in the error report.
I suspect their stupid popup wouldn’t have even shown if JS was disabled.