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 :)
That’s why Tenacity is here to save the day!
Great, that sounds amazing. Let’s hope it’s also used even if it means less excises for tracking.
Could the new CHIPS functionality help websites like Microsoft Teams working without you having to enable third-party cookies for their websites? If I understood it correctly this might be exactly the kinda use case but I couldn’t find anything specific online.
I looked at some info for reporting this to the kernel developers but the process is too complicated at the time. I’m currently a bit short on time but I did report it to libinput, maybe they can give pointers where exactly to report this.
On Mastodon they said there will be a blog post outlining the changes. That will probably be out tomorrow because that’s when alpha 2 officially launches.
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 :)
I’d definitely recommend Anki over Quizlet. Among many things it is very versatile, doesn’t cost a subscription, and has a better retention algorithm in my experience. Can’t comment on the rest although Photomath definitely helped me a few times :)
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.
I really liked Typewise. However, third party keyboards seem so broken on iOS that I went back to stock. I regularly had issues with the keyboard not opening properly, bugging out, etc. :/
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.
My understanding is, that the 1.0 spec for the extension was basically finalized in 2021 and CPUs using it are already available. Now it’s just fully ratified. Also, while it might seem like RISC-V is “behind” compared to AVX-512 for x86_64 or SVE for ARM, this fundamentally differs from these SIMD Instructions. They talk more about it in this article SIMD Instructions Considered Harmful. So, this is not merely RISC-V playing catch-up, but also trying a “new” (the idea is actually old and how things used to be done) ways to make a more sustainable ISA.