ByteWelder
If a messaging service is non-compliant, the government could theoretically take action with court orders against domain owners, server owners or pursue anyone hosting a node in case of a distributed setup. In a worse case scenario, they might instruct ISPs via court orders to block these services (e.g. The Pirate Bay in some countries)
It’s literally in the article: They want to use client-side scanning. The client already has the data decrypted. This is much like what Apple wanted to introduce with CSAM scanning a while back. It’s a backdoor in each client and it’s a matter of time until it will be abused by malicious entities.
Have an upvote. I’d pay double what Affinity is currently asking to have their products on Linux. Gimp is the opposite of intuitive.
Regarding gaslighting: See Apple’s response on the CSAM backdoor shit show. All the critics were wrong, including the various advocacy groups.
Not all of it though. Like JST plugs, barrel connectors, breadboard pin spacing, etc.
If a driver doesn't behave properly, the things that are built on top of it won't work properly either. When that misbehaving driver is not open source, you're at the mercy of the vendor.. It's common knowledge for over a decade that nVidia drivers are problematic with Linux - especially on laptops. Bad drivers are entirely nVidia's fault.
I've been running Wayland with Intel graphics on my laptop and my desktop runs a Radeon. I've had 0 Wayland issues in the past years.
A trigger warning on this post for Android devs would’ve been nice.
I think it’s roughly 2 hours at 60fps, but I don’t know for sure because I have mainly been playing with power connected.
“Deep Rock Galactic: Survivor” has been a blast so far. I’m about 12 hours in.
I’m running DualSense on Arch without issues. It even uses the touch pad for mouse movements when not in-game (Steam).
Make sure to check the docs if you aren’t using Gnome: https://wiki.archlinux.org/title/Gamepad.
My only complaint is the atrocious battery life, but that’s not a Linux issue.
The existence of ArchWiki and the Arch User Respository (AUR). And rolling releases, if that’s your thing.