I’ve got a i3-10100, 16gb ram, and an unused gtx 960. It’s terrible but its amazing at the same time. I built it as a gaming pc then quit gaming.

Having this bug right now too.

I remember my graduation used wireless(presumably bluetooth) speakers, and they were constantly cutting out almost the whole time. Not quite to the scale you’re talking about but the graduation hall was packed and I’m sure it was full of phones and smartwatches.

I don’t think cell tower networks would be because they are probably on wifi when calling(at home) and likely use something like facetime or your choice of free open source messenger which uses the internet.

3 times a day is normal? that sounds torturous!

Here’s the solution for you

yeah its not google chrome level which i’m thankful about.

I only saw it now, maybe it happened before on a different version.

But it’s gonna be very difficult when you’ve got Google and OpenAI up there.

There’s a whole lot of different smart TVs. If you want help, it would be useful to provide the brand of smart TVs as well as the operating system that it’s running.

Jellyfin is under the GPLv2 Github

Theoretically could that cause an issue? I’m a computer guy and I think that if one bit on a computer is flipped, that could cause a major issue with the computer, but is that the same with a human?

deleted by creator

It would motivate more low quality post spam like we see on reddit.

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

If you need meet, then try enabling webrtc(media.peerconnection.enabled). BE WARNED THAT THIS MAY MAKE YOU SUSCEPTIBLE TO FINGERPRINTING. If already enabled and you’re still facing issues, then my issue might lay elsewhere.

No. However, the issue was ultimately my fault. Google meet relies on webrtc, and I disabled it to prevent fingerprinting.

The issue was likely WebRTC being disabled. The thing is, WebGL and WebRTC should be more secure. They shouldn’t be implemented in ways that make it easy to fingerprint the user. Unfortunately, for now I can’t change that, but I can use alternative methods like Jami or temporarily enabling rtc again to use a locally hosted instance of Jitsi.

The webrtc setting is probably it. IMO it’s still google’s fault for not providing a meaningful error message. It just stuck on the loading screen, assuring me that I would enter the meeting but I just didn’t. I don’t like webrtc because it can be used for fingerprinting, so I will probably use jami in the future. Thank you very much for diagnosing my problem!

This was not a work meeting, though I appreciate your concern.