Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Teams is blocking Firefox Nightly

teams.live.com

Post reply on HN
Print view View original

101–110 of 316 posts

Re: Microsoft Teams is blocking Firefox Nightly

#101

Post by capableweb »

scarface74 wrote: post #94
nerdponx wrote: post #66

Earlier quoted context omitted.

> 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. Microsoft has repeatedly engaged in malicious anticompetitive behavior. Without any additional information, I therefore think it's rational to place a high prior probability on this being malicious anticompetitive behavior. Th…

[flagged]

This is what I see on Windows 11 + Firefox: https://imgur.com/a/aqzU2jr

Seems to be recommending Edge to me, or Chrome.

Re: Microsoft Teams is blocking Firefox Nightly

#102

Post by CamperBob2 »

jzombie wrote: post #93
wkat4242 wrote: post #72

Earlier quoted context omitted.

Microsoft is very heavily lobbying organizations to use edge as a standard browser right now. They're doing the same to us. It's really annoying. They're hell-bent on increasing marketshare no matter what.

It would be interesting if Google tweaked their Chromium licensing so that Edge couldn't use it. Then Microsoft wouldn't have a browser at all.

[flagged]

Re: Microsoft Teams is blocking Firefox Nightly

#103

Post by worksonmine »

This is not just nightly, even Firefox-esr on Debian didn't support screen-sharing at least a few months ago. Had issues during client meetings last year and since then I always propose google meet instead if I see a teams link in the invitation, explaining why.

It's not technical it's lazy devs. The button is disabled claiming my browser doesn't support it. Bullshit.

Re: Microsoft Teams is blocking Firefox Nightly

#104

Post by tuwtuwtuwtuw »

WirelessGigabit wrote: post #62

It's 2023. Why are we still doing user agent detection? We're supposed to do feature detection. userAgent is deprecated. https://developer.mozilla.org/en-US/docs/Web/API/Navigator/u...

Not always that simple. Where I work I need to provide a list of browsers customers can use, list those in the documentation and make sure QA test all of them and block any others.

Bugs in the app can lead to big issues and telling the customers to use whatever browser suits them and "if it works it works" is not good enough. There are still large differences between browsers that feature existence is not same as feature conptivinility.

Of course customers can tweak user agent and "lie" about their browser but then responsibility of issues is shifted to them.

Re: Microsoft Teams is blocking Firefox Nightly

#105

Post by capableweb »

l_theanine wrote: post #100
capableweb wrote: post #95

Earlier quoted context omitted.

Imagine being a malicious actor in this world of ours, where as long as you could make it look like a potential mistake, you can get away with whatever, and people on the internet will simply say "Sounds like Hanlon's Razor" and you're basically in the clear :shrug:

Imagine being someone who made a simple mistake, and people on some weird internet forum with no identity verification said "Oh, that guy must be malicious!" and you lose your job. How would you feel? It's justified, if I understand the point you're trying to make, right? Which is worse? Edit: Not that I expect much from here, but since there are a number of child(ish) replies, I might as well clarify this for the re…

I don't think anyone is assigning blame to a specific individual here, but to the corporation as a whole. A corporation that has time and time again been proven and acknowledged themselves to engage in anti-competitive behavior.

Re: Microsoft Teams is blocking Firefox Nightly

#107

Post by Dispatch1902 »

WirelessGigabit wrote: post #62

It's 2023. Why are we still doing user agent detection? We're supposed to do feature detection. userAgent is deprecated. https://developer.mozilla.org/en-US/docs/Web/API/Navigator/u...

I use the same userAgents in all of my web-scraper code, I just copy and paste my user-agent string after all these years.

It is still an old FireFox user agent I got somewhere. I should test my code and see if it still works after all these years. At the time, it was the only userAgent string which didn't lead to being limited. It was almost like an invisibility cloak for my bots.

Re: Microsoft Teams is blocking Firefox Nightly

#108

Post by hinkley »

scarface74 wrote: post #94
nerdponx wrote: post #66

Earlier quoted context omitted.

> 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. Microsoft has repeatedly engaged in malicious anticompetitive behavior. Without any additional information, I therefore think it's rational to place a high prior probability on this being malicious anticompetitive behavior. Th…

[flagged]

You’re comparing the behavior of a 10 year old with the behavior of grown adults.

The guy who bullied your friend in college is probably still a monster today. And here you have a company full of people who were older than that (including grad and doctorate students).

If he says the sky is blue you look up. It’s probably cloudy.

Re: Microsoft Teams is blocking Firefox Nightly

#109

Post by scarface74 »

palata wrote: post #85
behnamoh wrote: post #19

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.

A good way to put pressure on Google is actually to use Firefox.

Yes, because using Firefox doesn’t put money in Google’s coffers.

Oh wait…

Re: Microsoft Teams is blocking Firefox Nightly

#110

Post by nabilhat »

plorg wrote: post #56

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.

This sounds remarkably familiar. A certain ERP I've been dealing with sent out dire warnings about installing and updating Edge, else something nebulously defined would break. This understandably caused a lot of confusion and frustration with users (the ERP spammed so many with this warning...) and pissed off IT teams. It turns out that the Edge they were talking about was the ERP's own software named Edge (amusingly named and released long after Edge the browser showed up), which they leave for the end user to optionally install, and actively refused to clearly document why, where, and how to install it.

The fun part is all of this was to update an expired certificate.

Post reply on HN