Firefox

21168 readers

24 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

144

PSA: Google Meet no longer works in hardened Firefox (lemmy.fish)

submitted 1 year ago* (last edited 1 year ago) by potentiallynotfelix@lemmy.fish to c/firefox@lemmy.ml

36 comments fedilink hide all child comments

EDIT

This issue may be due to WebRTC being disabled. WebRTC is required for google meet, but also used for fingerprinting.

Recently I tried to join a google meet meeting in my hardened config firefox browser, and google meet didn't let me in at all. I was confused as hell. I could join only on my phone, but not any of my three computers I tested it on. I then went into a virtual machine with regular firefox(also linux), and the meeting works. The only conclusion I can draw is that google is so desperate for my data that they refuse to service me unless I give them this.

This post intends to inform people that issues with google products may be related to their valid wish for security, and the actions they have taken in pursuit of that. The post also intends to inform people of a solution. The two apps that I recommend are:

Jitsi Meet: This is self hosted, but you can also make a meeting with jitsi's own servers. A excellent alternative to google meet, the only reason I didn't use it is that I had issues the day I needed to meet, and had to fall back to google meet instead.
Jami: This is a distributed-network chat and video calling app which is open source and a GNU package. It does require an app, but is free and open source and will serve your purpose.****_________

you are viewing a single comment's thread
view the rest of the comments

[–] Vincent@feddit.nl 1 points 1 year ago (1 children)

I don't know much about WebGL and WebRTC specifically, but sometimes it's just inherent to the feature, and it's literally impossible to implement it without allowing fingerprinting the user.

For example, your screen resolution/viewport size can also be used to fingerprint you. It is impossible to allow adjusting a website to different viewport sizes without leaking those viewport sizes - the only way to restrict fingerprinting is to not offer the feature of using arbitrary viewport sizes (which is what Tor browser does, for example).

[–] potentiallynotfelix@lemmy.fish 2 points 1 year ago

Yes, it's all a trade off of functionality for privacy.