71–80 of 316 posts
Not just nightly. Stable is blocked as well. Seems we're in the next IE-era.
> the next IE-era the WebKit Wide Web
My organization (which uses Teams) forcibly migrated all Firefox users to Edge a couple of weeks ago and uninstalled FF. They were citing incompatibility with some software and I assumed that meant the new ERP system being adopted by one of the larger departments.
Looks like someone made a boo-boo it’s simply based on the user agent, w/e string matching they do is too strict they aren’t checking for actual JS/WebASM compatibility or anything like that. Chrome stable with a non standard user agent doesn’t work on via the windows live url but works through the O365 corporate one, same with Safari Mobile without any user agent modification. This to me looks like stupidity more th…
If you're not, you have no business running nightly, and you're probably going to generate a lot of "yOuR sITE is BRokEN!" support emails / forum posts / bug reports for other projects, and conspiratorial posts screeching on social media.
I see this all the time - people who run dev branches/nightlies/alphas and have the QA skills of a turnip who have no business doing so...and of course they're noisy as hell and waste a lot of people's times.
If you don't know the most basic points of QA and how to file a bug report that doesn't waste people's time, stop running anything beyond "stable" or betas marked specifically for public consumption. You're not "cooler" or more 133t running nightly releases.
We tried several things, update browsers, Firefox, Chromium, Flatpak...
In the end we just made a Jitsi meeting
https://www.microsoft.com/en-us/microsoft-teams/join-a-meeti...
Not just nightly. Stable is blocked as well. Seems we're in the next IE-era.
> Seems we're in the next IE-era Too bad there is no Register or Inquirer equivalent this time around.
Controversial opinion: I used to like Firefox but at some point you have to accept the reality: No developer likes to have 2 backlogs, one for Chrome and one for FF. IMO It's better to adopt Chromium-based browsers and put pressure on Google to avoid letting it become the sole decision-maker about the web.
Google doesn't care about us raging on HN, normal people are not going to 'put pressure on it' so all you're really doing is letting Google to become the sole decision-maker about the web, even more so than it already is.
Earlier quoted context omitted.
I think FF users need these sites more than the sites need them. There's little motivation to support a browser with relatively few users, and a big motivation to get users to switch to their platform.
I think you're right, but not supporting firefox leads more people to use chrome and suddenly we're living the exact definition of a vicious cycle. FWIW I'm not a firefox user myself, but I am not a fan of Google hegemony in browser tech.
This didn't happen the first time I clicked the link, by the way. It occurred on the second.
The first click, I was redirected through a bunch of pages until I landed on the sign-in form.
It took a few seconds to arrive there after navigating the redirects.
I thought the experience was so janky that I decided to try it again, then discovered the redirect loop.
Earlier quoted context omitted.
I can use Teams on the stable version without any issues. You might have cross-origin cookies disabled, which will stop Teams from working. PS. FF:v110.0.1 (64-bit), macOS: 13.2.1.
Those cookies are disabled by default in Firefox. Are you saying that to successfully use Teams one has to alter their browser configuration to make it _less secure_?