I disagree. GNOME is a bit buggy, but plasma is not designed for touch, and I think that matters a lot. Steam deck also has touchpads that most users use when mousing about their regular de, the steam decks touch support is mainly meant for the steam bigscreen ui.

A correction they are using PHOSH, which is a variant of GNOME.

Ubuntu touch uses unity

It has a few bugs. It’s not the smoothest, but it works pretty well

GNOME is the only one I use on my tablet

I’ve just used wine or wine ge. Some games don’t work as well as others. If you want better compatibility adding games to steam or lutris might help if you can use proton

Manjaro is already less stable than arch, now it collects your data involuntarily? Fucking wild how anyone can use it.

Assuming you are finnish and google translate did my right, olet huono

The guy made 3+ pages of posts shitting on linux, all while nobody else posted and 95% of the posts were downvoted to shit. Nobody was laughing, the guy made real arguments, and genuinely seemed to have an issue with linux. I never detected any satire presonally.

Interesting concept, if it gets good enough I hope ubuntu touch adopts this because I’m not a big fan of waydroid.

I set to hot or new, depending on the quality I want

Denuvo and every employee there can suck my hairy, unshaven, sweaty, salty, moist, oily ball sack.

Kevin Gates?

Planned on saying this. I am a very judgemental person, but I try not to let it impact my actions.

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!