• 1 Post
  • 37 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle
  • When I joined, it was the only instance, but it was also useful that it was aggressively left-wing.

    Before Lemmy, all the Reddit alternatives were Nazi bars, because everyone that got banned from Reddit congealed there. The Lemmy devs/admins banned anyone on sight who hinted at Nazi apologia and I don’t think Lemmy would exist today, if they didn’t.

    But yeah, folks also assign way too much meaning to the instance. I don’t have to hold hands with my admins when I log onto lemmy.ml. I don’t have to agree with them. I barely interact with lemmy.ml users, because I just browse /all. And that generally looks the same as on other instances.
    It’s just a way to access the wider threadiverse. If the lemmy.ml server is down, I log into my alt account on another instance and the experience is virtually indistinguishable, I just don’t have my block lists there…



  • Yeah, I always wonder, if it’s a matter of having multiple knives in rotation, so they don’t dull as quickly and so you can keep some in the sink until you do the dishes.
    Because if you’ve got the space and the money to spare, then using the slightly more optimal knife isn’t extra effort anymore.

    But yeah, I’m also of the opinion that if you keep your knife sharp, then it can split those atoms, and that’s ultimately what we’re here for.
    So, personally, I’d rather not spare the space for having multiple tools with the same purpose. ¯\_(⊙ʖ⊙)/¯



  • From what I just read about pacstrap, I think so, yeah, but you can control many more things, like for example you can configure KDE to use wobbly windows¹.

    But it’s also declarative, rather than just a script.
    If you do configure wobbly windows this way, it doesn’t just do a find & replace on the respective KWin config file, but rather it generates the entire KWin config file anew, with all the values you defined in your NixOS config + whatever defaults may be needed.

    This has the big advantage that it doesn’t depend on whatever is currently on disk. It will just make your system match your NixOS configuration in any case.
    Disadvantage is that any other KWin settings need to live in your NixOS config from now on, too, i.e. you can’t use the graphical settings anymore or they will be overridden on the next nixos-rebuild switch.

    Well, and there’s other disadvantages to NixOS, like it not using the standard Unix folder structure (FHS), so some programs have problems with that, and that there’s at least two different ways to do anything, so it’s difficult to find straightforward documentation.

    But yeah, if you can push past the pain of learning it and configuring everything initially, it does then work quite nicely.


    ¹) Requires Home-Manager and Plasma-Manager, and then this line in your Home-Manager config:

    programs.plasma.kwin.effects.wobblyWindows.enable = true;
    


  • A colleague was gushing about NixOS and so I gave it a shot, too. Eventually, I was wondering how to best configure something and he just told me I can look in his Git repo.

    This happened two more times until half a year later, I saw that he was now also using Starship for the terminal prompt. So, I asked what made him switch and his response was basically “Star-what?”.

    That’s how I found out that he just copied someone else’s configuration and pretty much left it at that. He was pointing me to his repo, because he genuinely had no idea where to even start configuring these things.

    Like, yeah, technically it’s documented somewhere in that repo how to configure that. But I assumed, it would be obvious, if I see the code, because why else would he tell me to look there…? 🫠








  • I guess, it can select the wrong song, if:

    • the correct song doesn’t have its acoustic fingerprint in the MusicBrainz database (otherwise it would be the closest match), and
    • another song has a similar enough acoustic fingerprint, above a threshold that you can configure in the Picard settings.

    I assume, it has to be a threshold, because you might have slight variations for the same song/recording, like silence at the end trimmed or volume normalized or whatever.

    And yeah, Picard’s UI is certainly a bit of a hurdle. Conveying information for so many changes is definitely not easy, so I don’t want to complain.
    But you know, if it would have detected that some of my songs will get renamed not just with a few capitalization fixes, but rather completely different words, and it would have prompted me for those, then I wouldn’t have misnamed songs now…




  • Yeah, at some point, I told Picard to just re-sort everything and that was not a good idea. Some songs got renamed or put under a different artist, because I guess, the actual song is not in the MusicBrainz database.
    I do have a backup that I should restore actually, but yeah, difficult to notice such changes and especially to know how much damage was done.

    I did also figure, I should just add the unknown songs into MusicBrainz, but boy, I added one album and that took more than half an hour…

    Definitely leaning more and more towards that unsorted life…



  • I mean, increasing that timeout doesn’t really sound like it resumes the download, but rather that it never properly cancels it. I don’t think, Firefox would want to implement that, as it’s somewhat bad etiquette for a client to keep a connection open for a long time.

    My understanding is that actually resuming partial downloads is generally badly supported by server software and that’s why support for it is not implemented in Firefox.