Agreed. @cypherpunks@lemmy.ml, I think this would be a great idea - making a weekly megathread for Linux questions, preferably also stickied for visibility.
Waydroid works, but there's three main things you need to get things going to replicate a typical Android device:
- OpenGapps: For GApps/Play Store. You'll also need to register your device to get an Android ID.
- Magisk: Mainly to pass SafetyNet / Play Integrity basic checks.
- libndk / libhoudini: For ARM > x86 translation. libndk works better on AMD.
- Widevine: (optional) L3 DRM for things that need it, eg Netflix
There are some automated scripts that can set this all up. I used this one in the past with some success.
Also, stay away from nVidia. From what I recall, it just doesn't work, or there are other issues like crashes. But if you're serious about Linux in general, then ditching nVidia is generally a good idea.
Finally, games that use anti-cheat can be a hit-or-miss (like Genshin Impact, which crashed when I last tried it). But that's something that you may face on any emulator, I mean, any decent anti-cheat system would detect the usage of emulators.
First of all, I'm not the author of the article, so you're barking up the wrong tree.
You're using the unstable channel.
That doesn't matter in the big scheme of things - it doesn't solve the fundamental issue of slow security updates.
You could literally build it on your own, or patch your own change without having to wait - all you have to do is update the SHA256 hash and the tag/commit hash.
Do you seriously expect people to do that every time there's a security update? Especially considering how large the ecosystem is? And what if someone wasn't aware of the issue, do you really expect people to be across every single vulnerability across the hundreds or thousands of OSS projects that may be tied to the packages you've got on your machine?
The rest of your points also assume that the older packages don't have a vulnerability. The point of this post isn't really about the xz backdoor, but to highlight the issue of slow security updates.
If you're not using Nix the way it is intended to be, it is on you. Your over-reliance on Hydra is not the fault of Nix in any way.
Citation needed. I've never seen the Nix developers state that in any official capacity.
I know it's not the same thing, but this kinda reminds me of the old GDI object limit in Windows which had an upper limit of 65,536. If you reached that limit your system would start exhibiting all sorts of weird glitches, including not being able to launch any apps even if you had plenty of free RAM.
No, you're right. There's no organisation options. It's pretty barebones overall, and doesn't look great on large foldables either. Guess there's no reason to switch from my current launcher.
You seem to know your stuff, so I have a question - growing up, we had a monochrome CRT monitor with a sepia tint to it, and I've been looking for such a monitor for a long time, with no luck. Most of the mono monitors I've come across online are either greyscale, amber or green. I can't find a sepia tinted one. I know my monitor wasn't unique since I clearly remember some of my friends having similar sepia tinted monitors, so I'm sure mine wasn't a glitchy or something.. but I can't seem to find any evidence such a monitor even existed. Any ideas if this was really a thing, or have I somehow mixed up the colors in my memories?!
There are lightweight GUI options for that too. For iwd, you can use iwgtk. For VPN, that would depend on your VPN protocol/service. Some providers like Proton have their own client, others can use something like Wireguard Client (as an example) or something similar depending on your VPN setup.
iwd is great. In fact I'd say take it a step further and get rid of the beast that is NetworkManager as well.
That's a shame. I hope someone continues a fork and calls it Shinyaku Toaru.
I was talking about the 1000 vs 1024 issue, do the dd test yourself and it's easy to verify that he was right.
As for the specific descrepancy that you're seeing, lots of things can throw off a file size calculation - symlinks, sparse files, reflinks, compression etc. Since you're the only one with access to your files, you'll need to investigate and come to a conclusion yourself (and file a bug report if necessary).
The general answer is to enable the RPM Fusion repos. But that won't automagically install the drivers for you, you'll need to manually identify what's needed and install them accordingly. This guide is a decent starting point: https://www.fosslinux.com/134505/how-to-install-key-drivers-on-your-fedora-system.htm
But also consider simply using a distro/spin that has all the drivers included (or automates the install), such as Nobara, or one of the Fedora Universal Blue distros.