Thumb rule: whichever I feel comfortable with in a given situation, I use.

At workplace, use whatever OS and tools allowed by company policy.

At home, use whatever OS and tools you like.

At least that is how I’m managing it.

Ubuntu 25.10 + Wayland + Gnome 49 + Nvidia driver v580.95 (RTX 3070 Ti) works flawlessly for both gaming and normal apps.

Sorry, I just noticed that now.

You may create a bootable/live USB with Mint [1] installed on it, and try it out to see if its works perfectly for you - from functional and performance POV.

With Linux, at least you will continue to get security patches. For Win 7 and 10 are out of support now.

[1]https://linuxmint-installation-guide.readthedocs.io/en/latest/burn.html

The good news is Nvidia consumer grade GPUs don’t even support vGPU and can’t be passed though if Host OS is using it.

My 3070Ti also doing just fine - both for Gaming and for running Llama.

Now, to be honest, I never had a chance to use AMD GPU on Linux, so I can’t really say if it is at par with AMD GPU performance or not.

When it comes to Nvidia driver for Linux, my suggestion is - always stick to the version you find stable enough.

In my case, Last Nvidia 580 driver version works smoothly on my Desktop. Earlier I was on 550.

On a side note, faulty RAM often cause system freeze/crash. You might want to run memtest from boot menu as well.

Do you know if a similar report exists for Intel based CPUs?

However, these were not “journalists” in the traditional sense, but hacktivists who were involved in a number of hacking incidents, which is a violation of Proton’s ToS, and therefore subject to suspension of all accounts. In this case, I made the decision to exceptionally restore two accounts because hacktivism cases are not always black and white.

So, either your original judgement to suspend the account (and to reject subsequent appeal) was correct, or you latter judgement to reinstate the account was correct.

I fail to see how you can claim with a straight face that both of your actions were correct, while every other facts about the owner of that account remain the same during the whole drama.

Nate’s side of this story:

https://pointieststick.com/2025/09/16/a-few-corrections-about-the-transition-from-blue-systems-to-techpaladin

While Proton does have an obligation to stop spread of SPAM mail, this incident is a bit different. Let’s see -

1. Proton was not approached by other Email providers (Gmail/Outlook) about suspected email SPAM campaign originating from their network.
2. This matter is NOT even related to SPAM mails.
3. krCERT - a Govt agency approached Proton and asked them to disable the account.
4. Proton simply complied to that without verification.
5. Appeal made by Owner of that email id was rejected.
6. Subsequently follow ups were also ghosted.
7. Until the tweet from the journalist went viral, Proton was not in mood to reinstate the account.

Note that while Proton Mail (server) is E2E encrypted, but once email exits their network it no longer remains as such. So, whoever (other email provider or incident reporter) reported the incident, should have a copy of unencrypted email to prove abuse of Proton Mail service.

Given that proton now reinstated the account, that proves Proton initially froze that account based on “Trust me, Bro” proof only from krCERT.

In ideal world, any service provider should require a court order to comply with Govt request to remain unbiased in such situation.

UX is a subjective topic.

This is the most likely reason why all of sudden there is an uptick in attempt to embed malware in AUR build scripts.

But, if you are lazy like me then https://distrosea.com/

Flatpak does have a concept of Verified Publisher. Many distros ship flatpak app store with default filter set to Verified Publisher only.

Personally I’m waiting for the day it comes out of “under active development” state so that I can migrate from NextCloud to it.

While that’s true, but the main issue here is the unavailability of frequent security patches that Fedora now appears to be attempting to solve with X11Libre.

Stick to Production version of Nvidia Linux driver - v550, v570. I’m using v570 on Ubuntu 25.04, no issue in either day to day work or in gaming.

I guess it takes time to built a DE from scratch.