russjr08

I posted about this on the KDE community a couple of weeks ago, but Dolphin (their file manager) has a nice trick for archives (zips, tar's, etc) - in the extract menu, there's an "Extract, Autodetect Subfolder" button which will:

• If the archive has an inner subfolder (and just that), it will extract this as expected
• If the archive doesn't have an inner subfolder, and all the files are at the root level, it will create a new folder for you and extract the files there

This way, you don't end up with files splattered all over say, your downloads folder. Easily one of my favorite features, and is something I wish every File Manager had. It feels like someone had the same pain that I do (and I'm sure plenty others) of extracting something, and regretting it - but then they went as far as to fix the problem for everyone and implemented a feature for it (I'd love to have the knowledge to contribute to KDE someday)!

Oh this is a fantastic show! While I do re-watch it, I would give anything to re-watch it from "scratch" again.

Oh that's awesome! Although I can't say I'm surprised, the last I heard Nixpkgs had more packages than the AUR, which is certainly no small feat.

Continuing on what Rolling Resistance said (sorry for the delay, had to step away for a while), I know plenty of people who do use a password manager and still use a static password in some places (hell, I've been guilty of that in a few places - but generally on network-isolated systems). Some people also don't use 2FA because they find it inconvenient.

Passkeys are more or less very similar to how SSH keys work if you're familiar with those, your device (or password manager) generates a secret key that it only has access to, and then gives the public key to the website (and a new keypair is generated for every single website). When you login to a website, the website sends you a challenge which you sign with your private key, that the website can then verify using the public key that you used when enrolling the passkey. This way, a website never has any form of secret - making say password hash leaks less relevant, whereas in theory you could give your public key(s) and post it on Google's homepage without any repercussions... but don't quote me on that one.

So even if you use a password manager, if you still have a few websites that share the same password, and one of those gets compromised - those other websites may still be vulnerable which wouldn't be possible with a passkey.

I see, that's plenty fair enough, although I don't think they meant it quite so literally (but rather as a method of lightening their support requests - I don't have any fwupd capable hardware AFAIK however I get the feeling fwupd is pretty popular).

I find it really cool what Nix/Guix are doing and I give major props to their communities for what they've pulled off, for what its worth.

Oh, nice! Doesn't look like it's hit the Firefox Addons repo yet, but I'll be looking forward to it when it does.

I'm not sure I see the problem here? It does say most cases and I'd definitely consider Nix/GUIX users to be in the minority for this (on top of users who would even compile software themselves in the first place).

Also from what I experienced during my (not so long) time with NixOS, usually things in Nixpkgs were contributed there by community members who ported applications over to be compatible with Nix. Sure, it's a nice extra thing when the application developer does so out the gate, but given how special Nix and GUIX's environment is, the onus has never really been on the app dev.

I made some significant progress on a project I have been working on yesterday, so I'm excited to get back to it today if I can!

I take it you're on Wayland? The fonts issue is a bug that's being fixed IIRC in KDE's portal, but as a workaround for now you can install the GTK desktop portal, which should make the fonts render correctly.

(That is, if you end up needing to use other Flatpaks that have an OBS-like situation)

Pretty much, unfortunately. It sucks, because in order for Nix to accomplish its vision, things have to be like this - I don't really see a way around it.

I am amazed by what the Nix[OS] community has accomplished and give high respect to them for it, but I can't do it. If the documentation (and procedures, eg Flakes) were a bit more structured I'd probably be a bit more willing to put more time into trying to figure it out but... that's just not the case currently.

I have similar feelings about immutable distros, it is a very intriguing concept but every single time I've tried one out, I run into some issue that requires hacks to get around it. If I did end up using one long-term, it'd probably be something from Universal Blue because it seems fairly easy to just modify the image. However, it's still a massive paradigm shift of getting used to making changes at build-time (of the image), rather than making changes to your system at runtime.

For now, I just do pretty much the same thing you do, important dotfiles go into git, and btrfs snapshots for "Uh oh, something broke and I need things to work right now" moments (which is thankfully quite rare).

Huh, I wasn't even aware that the Switch had a Twitch app available. I was still under the impression the only video apps were YouTube and Hulu... Guess I am out of date then.

I wonder if the question is in reference to unlocking the root account and setting a password for it. I don't know of any distros that actually have an unlocked root account and leave its password as empty, but I suppose its not completely impossible.

That being said, if an attacker gets physical access to your PC, its game over anyways. If your drive isn't encrypted with something like LUKS, then they can just boot up a live USB of whatever distro they want, mount the drive, and have easy access to its contents.

Ideally if you want to protect your PC against physical attacks, you'll at the minimum want some sort of drive encryption enabled, and preferably with Secure Boot enabled with your own keys enrolled if your machine supports it.