I’m not sure that Proton can fix your problem. However, I feel like this project would love your help with capturing the USB traffic to get it supported and hopefully upstreamed in the kernel some day :)

Well, with NTFS, there isn’t. That’s why I said, BTRFS is definitely the better choice for games. Never had issues with two shared drives in over two years now with WinBTRFS.

I’ve been using WinBTRFS for quite some time without issues. It seems a lot of people recommend NTFS. But be aware, if you plan on using it for things like games, NTFS will absolutely break at some point. It is not compatible with Proton and will break things like updates for Steam. It always has for me up until very recently. Valve also says the same about using NTFS for games. I’m not sure this can be fixed with the NTFS driver unless they do workarounds like renaming things automatically because some things Proton does are not compatible with the filesystem spec.

What about Tauri? I don’t know what exactly your app is but since you mentioned Electron as an option I guess Tauri could run it. Offers more choice for frontend frameworks hence less „language lock-in“ than Qt.

!helldivers2@lemmy.ca just dropping this here to help growing smaller communities :)

Just know that sites like this are useless if you don’t understand the results. There are anti-fingerprinting techniques that add random noise to your fingerprint. This might result in these kind of tests claiming you have a completely unique fingerprint, even though the anti-fingerprinting mechanisms randomise the fingerprint for every site, browser session, etc. (depending on the config). This would mean that you are relatively „safe“ from fingerprinting because you never have the same print twice but tests think you are very vulnerable because it’s still a random “unique“ fingerprint.

Oh, interesting. In that case I misunderstood that part, I thought there were core devs of Atom involved in Pulsar, thanks :)

Oh, in that case you might like either. I think both are great in their own way!

I think Zed is quite different from Atom. But Pulsar might be your thing. A direct fork of the last release of Atom being developed by ex Atom developers :)

Yea but many of them were involved. The Audi CEO at the time was on the board making the decision and the first to be convicted.

Don’t worry, I don’t think you are. I just think there’s a reason they admitted so easily. Probably just another calculated fallout to save all their other brands from their own mini backlash which would ultimately cause more damage.

But yes, the whole industry is a dumpster fire when it comes to regulations and also lobbying.

I mean they also own like half the industry. So, I don’t feel particularly bad for them to be honest.

I mean they did also inject affiliate links without the users noticing which is really shady behaviour from a browser because it has one job, open the link I click and nothing else. But that’s just IMHO if that is acceptable for you personally then there is no issue with that.

Definitely, she has served me like the absolute beast she is. To this day the card actually deserves very admirable even in modern titles. The next destination might actually be my roommates PC who’se still running a 960 which is pretty lackluster these days with 2 GB of VRAM.

Absolutely it’s been mostly rock solid. I do however plan on switching to Wayland. Since that will now be doable with AMD graphics it might still be a pain with Gnome 42 so depending on my impatience I might not wait till Pop!_OS 24.04.

Pop!_OS atm but hopping in the future is not out of question since this was my first and only distro on this device for a few years now. I just was too lazy so far to try out new things.

Thanks, I think I’ve read something about LACT once but it wasn’t relevant back then. Certainly looks like the tool to use to tune my card :)

Just to clarify, I use Pop!_OS and not Fedora Ublue. I looked at their Wiki because they are the only ones who had documentation on how they made hw accel work with Flatpak and Nvidia specifically. More exaclty I was led there by this Reddit post.

AFAIK it should work fine with AMD since Firefox can use the VA-API FFmpeg Flatpak to provide hw accel which should work fine with AMD GPUs. This does however not support Nvidia GPUs, which is why you have to expose the driver in the sandbox and force Firefox to try to use it etc.

Mesa drivers for opengl, vulkan, etc. are likely already installed, what you need to install are the mesa-va and mesa-vdpau drivers for video acceleration. Other than that, you just need to make sure the GPU doesn’t stay in power saving mode when you play.

Thanks, I’ll make sure to install those for sure then.

Btw, video acceleration with Nvidia mostly works if you use this.

You know, I actually tried, and I couldn’t get hardware acceleration working in the Firefox Flatpak for the love of god. I tried everything, all the guides, looked at the Ublue documentation how they did it etc. and in the end I decided it’s just not worth it because playback worked fine without, just with a wee bit higher CPU usage.

From what he said in the video it’s a few things.

Firstly, they keep being disappointed with the performance. They somehow have to market devices that barely improve performance and battery wise at all. One of his sources called the new generation a waste of sand and said the writing is on the wall, it’s time for 50/50 Intel/AMD.

Secondly, apparently Intel has been very bad with communication leaving OEMs in the dark. That means sometimes they get information very late in the design process hindering their ability to get work done in time and other times they have get delays over and over again. I think that was a big issue with their discrete graphics.

This last one wasn’t mentioned in the video but look at the recent desktop fiasco. Intel gave MB manufacturers a spec, which they adhered to, that now causes stability issues. Their solution, changing the spec and saying motherboards pushed the power envelope to far. Hell I’d be pissed too.

On top of that as you mentioned Intel CPUs keep having new vulnerabilities because it seems Intel can’t improve performance anymore without trickery that causes problems down the line. I mean some CPU generations have lost over 50% performance since release because of exploit mitigations.