this post was submitted on 17 Jul 2023
3231 points (97.3% liked)

Technology

59314 readers
4719 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

With the number of people concerned about privacy, it is a wonder why chrome is even popular.

you are viewing a single comment's thread
view the rest of the comments
[–] 7heo@lemmy.ml 14 points 1 year ago (2 children)

With the number of people concerned about privacy, it is a wonder why chrome is even popular.

They aren't "concerned about privacy", they are "concerned about privacy for the same price". And they are real cheapskates.

Note: for those who lack the knowledge, the "price" of a free product comes as an overall bugs / features ratio, where "bugs" and "features" are respectively defined as any undesirable / desirable behavior in the use case for the software.

[–] Gremour@lemmy.world 31 points 1 year ago (3 children)

I wonder if you deem Firefox buggy or having not enough features?

Using Firefox since it came out and never experienced any troubles.

[–] dekatron@lemmy.fmhy.ml 8 points 1 year ago (5 children)

Google Meet's background blur and visual filters do not work on Firefox. MS Teams straight up says that Firefox is not a supported browser. These decisions might be intentional on the part of Google and Microsoft, but to the average user of these popular products, it looks like a Firefox problem.

These decisions might be intentional on the part of Google and Microsoft

Well, yes - it's profitable for these corporations to portray Firefox as buggy and their own browser as superior. Change your user agent to one of a Chromium-based browser and watch how your "unsupported" Firefox suddenly works correctly in most cases.

[–] redcalcium@c.calciumlabs.com 8 points 1 year ago* (last edited 1 year ago) (1 children)

Google products only supporting chromium is a tale as old as time. Try using this extension to enable background blur and see if it'll work: https://addons.mozilla.org/en-US/firefox/addon/mercator-studio/

Edit: Looks like background blur is working on the latest version of Firefox if you spoof your user agent to chrome. See my comment below.

[–] dekatron@lemmy.fmhy.ml 1 points 1 year ago (1 children)

This extension blurs the entire camera feed instead of only the background, so it's not really a solution unfortunately.

I've also tried a simple useragent change in Firefox, but the feature still didn't work. That leads me to think they're using browser features that are not available on Firefox.

Another thing I've noticed is that Google's background blur implementation has better edge detection than apps like Zoom, and it handles things like curly hairstyles more gracefully.

[–] redcalcium@c.calciumlabs.com 5 points 1 year ago* (last edited 1 year ago) (2 children)

I got curious and started looking into this. Looks like you can enable background blur in google meet if you're using the latest version of firefox, I just did myself to confirm.

All I need to do is by spoofing the user agent in about:config, by setting general.useragent.override to Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36.

If I remove the user agent spoofing, google meet refuses to show the background effect options.

So my conclusion is google deliberately gate this feature behind user agent sniffing. Firefox is perfectly capable of supporting this feature.

Some discussion about the issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1703668

[–] dekatron@lemmy.fmhy.ml 1 points 1 year ago

Awesome, I'll have a look again. Last time I tried changing the useragent (it was a while ago), the whole Google Meet website had some issues and it didn't work. Maybe the specific useragent you use also has an impact.

[–] dekatron@lemmy.fmhy.ml 1 points 1 year ago

You're right, I can confirm the feature does indeed work on Firefox by changing the useragent string. However, this introduces other issues such as input devices not being detected which makes normal use of Meet difficult. For now, there seems to be nothing else to do other than waiting for Google to enable this on Firefox.

[–] prole@sh.itjust.works 3 points 1 year ago

A lot of that stuff can be fixed by switching your user agent to Chrome

[–] MalReynolds@slrpnk.net 3 points 1 year ago

Teams works fine on ff / linux ...

[–] dan@lemm.ee 2 points 1 year ago (1 children)
[–] dekatron@lemmy.fmhy.ml 1 points 1 year ago (1 children)

Are you using a useragent changer?

I am still getting this:

Screenshot of Microsoft Teams on Firefox. The text says "Hmm. Your browser version isn't supported. Quickest solution? Download the desktop app." Below it, Microsoft Edge and Google Chrome are listed as supported broswers.

[–] dan@lemm.ee 2 points 1 year ago

Works fine: https://i.imgur.com/5dbLGNi.png

Might be cos I'm running on a mac?

[–] 7heo@lemmy.ml 3 points 1 year ago* (last edited 1 year ago) (2 children)

I deem Firefox a bit buggy, but that's because I use it on platforms that get very little use, And I ain't got time to hunt bugs down. I barely have the time to report them.

But it's not people like you and me I'm talking about. It's people who discovered internet after 2000, who think Firefox doesn't have enough features, and is "being unreasonable", because essentially every. single. browser is now chrome or chromium, with the exception of Firefox (and safari?); and because of companies like adobe blaming Firefox for "not playing nice with others" simply because it isn't chrome/chromium...

Edit: to those who downvoted, which I can only assume is because of my comment on bugs, please install NetBSD 9.3, ctwm, set pkgin up against 2023Q1, and install Firefox 110.0.1 with noscript, umatrix and ublock origin. Now witness how all your menus disappear immediatey as you mouseover upon them. Now please explain to me how this isn't a bug...

Edit 2: instead of attempting to "backseat debug" without any information on the actual problem, or even without trying to reproduce the bug (I gave all the info I would start with), please accept that Firefox can have bugs, and that people online can know what they are talking about. Thanks.

[–] prole@sh.itjust.works 2 points 1 year ago* (last edited 1 year ago) (1 children)

Sounds to me like some of the third party plugins/extensions you've installed are conflicting with one another. That's not Mozilla's fault. That can happen to Chrome too.

You're using several extensions that were all made by different people, and not necessarily designed to interact or be functional together. That's not a Firefox bug.

[–] 7heo@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

Yeah sure, the exact same set of extensions that worked with 102, and they also work with 110 on other OSes. Must be that...

[–] prole@sh.itjust.works 0 points 1 year ago

Extensions are third party apps and most, if not all, of them are not made by Mozilla. If an unofficial, third party plugin doesn't work, it's not up to Firefox to fix that. The issue is with the third party apps.

FF is allowed to change their software, and they're not at fault if those changes break existing plugins that they had no hand in creating. That's not how software works.

[–] Gremour@lemmy.world 1 points 1 year ago (1 children)

Look like a bug on the edge of WM/App

[–] 7heo@lemmy.ml 1 points 1 year ago (1 children)

Yeah well, Firefox is the only GUI software that shows this behavior, and it wasn't present with 102. The only thing that changed was Firefox.

[–] Gremour@lemmy.world 0 points 1 year ago

It works fine with my Cinnamon window manager. So the bug could be in Firefox, in your WM, in both, or more likely in the integration of two, as a side effect, which why I've said "on the edge". It's nearly impossible to test your software with every combination of a system. So the solution here to file an issue both for WM and Firefox and hope someone from either communities will solve it. Or just get another browser or WM.

[–] Captain_Patchy@lemmy.world 2 points 1 year ago (1 children)

They aren’t “concerned about privacy”, they are “concerned about privacy for the same price”. And they are real cheapskates.

Firefox is free. And respects your privacy.

[–] InFerNo@lemmy.ml 2 points 1 year ago (1 children)

You should look up what mozilla did with the mr robot extension.

[–] prole@sh.itjust.works 1 points 1 year ago

I just looked it up. Oh no. Anyways...