russjr08 @ russjr08 @outpost.zeuslink.net

Posts

2

Comments

525

Joined

2 yr. ago

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.

Ah very nice, a 7800 XT should be a fantastic upgrade (assuming my understanding of AMD's GPU lineup is correct, I can hardly keep up with Nvidia's as a "software" guy)! I'll be keeping my fingers crossed that it gets there quickly for you, and that the swap goes smoothly.

Yeah it's absolutely ridiculous. The "stable" release is out in the extra-testing repo for Arch, and I just had an absolute nightmare trying to get it to work. Installed it, added the suggested nvidia-drm.modeset=1 nvidia-drm.fbdev=1 kernel parameters to systemd-boot, ensured all of the Nvidia kernel modules were present in initrd to do early KMS loading - tried to start a KDE Wayland session and the desktop ran no more than maybe 5 FPS and I wish I were exaggerating that. A very similar issue was reported on their forums but the error I'm getting from kwin_wayland_drm is slightly different.

Tried install GNOME, but its Wayland session wouldn't even launch at all. Loaded into its X11 session and it seemed to not be using accelerated graphics whatsoever.

Now of course, part of the blame goes to me for opting into the testing repo... but at the same time, I shouldn't have to go through those hoops just to potentially get a working Wayland desktop (and I suspect even if I had succeeded, the same issues will have still been present). As far as I understand, AMD/Intel's drivers are just part of mesa and are included in the kernel - no modifying your initrd, no worrying about DKMS, no trying to mess with .run files...

I have a Windows partition on one of my SSDs for the few occasions that I need to do something that can only be done from Windows, and I think I'm just going to use that till my GPU comes in. Funnily enough, Nvidia's drivers aren't even that great on Windows either - I still get a screen flicker issue whenever (I believe) the power state of the GPU changes, so for example playing a YouTube video, or even Steam popping a toast notification saying that a friend has launched some game. And plenty of my friends have tales of nightmares with trying to install and manage the Nvidia driver on Windows.

I would've never bought an Nvidia GPU in the first place if I had known how bad it was on Linux, and my current Nvidia GPU (a 2080) wasn't actually purchased by me, but handed down by a very gracious friend at the beginning of the year since times have been really tough for me. Thankfully this last month I was able to put in some extra hours to be able to set aside some money for a used 6700xt because if I have to deal with this any longer I'm going to lose my sanity.

I appreciate the heads up either way, thank you!

If you don't use any XWayland apps, yeah - this is still a major blocker unfortunately assuming they didn't make any significant changes between the beta from a couple of weeks ago and now.

No, thankfully that was resolved with this update.

I tried out the beta version of 545 last week, I swear it made the render issue with XWayland apps worse. Even if it's back to the 535 state, it still makes using Wayland on Nvidia very difficult unless every application you plan to use is Wayland native. It'll be a while before that's the case for me.

I plan to just pick up a 6700 XT next week. I'm tired of being a second class citizen in Nvidia's eyes.

That being said, I appreciate the devs themselves who've been working on improving what they can (there's a couple that I've even seen participating in the Freedesktop GitLab). I assume the lackluster Linux support comes from the management side of things. I may not like the company, but I obviously don't have disdain for every single person there.

Ah, there-in lies the good ole chicken & egg problem. The majority of people won't sign up until bigger people are on the platform, but bigger people won't sign up for the platform until the majority of people are on there.

I do wonder why billion dollar companies (or in the case of NASA, an organization that AFAIK is still funded directly by the government) can afford to do this.

I'd also argue that extremely rigorous testing is a bit more important in terms of life-or-death scenarios for the companies that you mentioned, rather than Mozilla - but hey, that could just be me.

I mean come on, your comparison might work for a company that can hold a candle to the ones you mentioned (ie, Google or Apple) but how large do you think Mozilla (who still has to take handouts from Google essentially) is? Even then, I'd still say it's probably a bad comparison given my second point.

I find the concept of NixOS to be incredibly cool, and in terms of immutable operating systems it would in theory be one that I'm really interested in!

But the last time I tried it, I found that I was constantly fighting the system, and the documentation is all over the place and confusing. There's things like "Oh hey use Flakes!" but then most of the documentation doesn't really cover Flakes because it's still considered experimental, yet it feels like the majority of the community uses it.

I also had software that would just randomly break, and when trying to track down the changes from Nixpkgs I couldn't find anything that would prompt why it broke. Which... seems counterproductive to one of the strong points of Nix.

One example I ran into, is OpenRazer - the service is no longer being exposed and was reported 7 months ago. I did my best to try to track down the changes that broke it, but I suspect it's possibly a lower level change outside of the OpenRazer package/module that caused it to break.

I get the impression that if I wanted to try to fix it, I'd have to take on the massive gauntlet of understanding how all of NixOS' internals work, and while yes someday I'd love to have a better understanding, right now I'm more focused on just making sure the things I'd like (or even need in some cases, like software for my job) just works.