[–] 2 points 1 month ago (2 children)

Thanks, I might give this a shot. My whole family is on Spotify though so it'll be a tough sell. We use it in order to play certain tabletop games as well, with printed links that open songs on Spotify. 😅

But this could be a fun experiment for just me.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (3 children)

    Sure, just download Nicotine+ or another Soulseek client and search for the artists you're most interested in. You won't be able to "import library" or probe 2000 artists at once, but still, it will give you an idea. Since Soulseek is a P2P network, ideally you should keep port 2234 (or whatever you set in the client) open to see all content it has to offer. But if you can't, no worries, you'll still see plenty!

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (4 children)

    it doesn't even have to take as much time or drive space as you imagine.

    I follow almost 2,000 artists on Spotify 😅

    Is there a way I can probe this library you speak of so I can make sure it has all my shit before I devote all this effort and drive space?

  • source
  • parent
  • context
  • [–] 2 points 1 month ago* (last edited 1 month ago) (5 children)

    Might be a time to build your own music collection.

    It takes some work, yes, but the result is very satisfying, and it doesn't even have to take as much time or drive space as you imagine.

    Pretty much everything else is handled already. You can:

    • Have brilliant personalized music recommendations (thanks, ListenBrainz and last.fm!)
    • Download dozens of millions of tracks, including very obscure ones, in two clicks (thanks, Soulseek and its amazing clients like Nicotine+, also, support indie music producers on Bandcamp and take their music from there - your money there will go much longer way!)
    • Automatically add all metadata to a song, even if you have none, not even its name, in which case the sound itself will be matched against the database (thanks, Picard!)
    • Host your music somewhere to build your streaming service for a lower price than your Spotify subscription (thanks, Navidrome/Subsonic/Jellyfin/Koel/...!)...
    • ...or just dump it into your device's memory and choose one of the million players out there, some of them laid out in a way very familiar to streaming service users.

    All of the tools (well, maybe not hosting a music server, but it's not too hard either) are absolutely grandma-level, and you can easily install and operate them seamlessly.

    And on top of it all, of course, is that no one will take your music or the ways to play it away from you. No item will ever be removed from your library (unless you yourself do it). No player will stop working with it. It's all yours, and it's just a bunch of .mp3/.flac files that will outlive us all.

    Give it a few evenings, and you'll never need to worry about enshittification of streaming services again. Genuinely recommending it as someone who didn't pay a dime to streaming services in 4 years now.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (1 child)

    Hmm, that's just the initial configuration, though, right? If you want to roll out updates to the config, you would presumably use Salt or similar (like they have a config field in that generator).

    That's also an improvement for this use-case over your average Linux distro, especially because MicroOS is immutable as well, but NixOS is still a big step further into this direction.

    I guess, what I really wanted to say in my previous comment is that NixOS isn't just immutable, but rather also declarative.
    You define your system config and then it makes it so the system matches that configuration, whether it's a new system or a previously installed system.
    So, it's not just a script where you need to describe how to apply or unapply a change, but rather the entire OS declared in a config file (and a ton of defaults).

    The big difference is that you know the state of a system, when you apply a configuration. It is written into your configuration file.
    Whereas with a distro which is merely immutable, even if you completely prohibit users from making changes, you still have the problem that someone might've been on vacation while your script contained a line to e.g. modify some config file.
    If you update that line before they return, then you better hope your new modification logic can deal with whatever is on their system.

    With a declarative system, this cannot happen, because the contents of that specific config file would be defined in your NixOS configuration file. No matter when you do the sync, the up-to-date contents will be put in there correctly.

    (And yes, I know, if you get your scripts right, you can achieve similar results. The point is that you don't need to.)

  • source
  • parent
  • context
  • [–] 14 points 1 month ago (1 child)

    Great news! Increasing independence from American tech seems like a great idea to me. Hopefully they also invest in the open source side of things so everyone gets to benefit from this move.

  • source
  • [–] 5 points 1 month ago

    I just know that the macOS thingamabob is called nix-darwin. A colleague, who presumably also just watched a video about it, said that it does work, but it needs a bit of extra setup.
    Well, and presumably, the ecosystem is smaller, so you probably won't find as many pre-made modules as for Linux programs.

  • source
  • parent
  • context
  • [–] 42 points 1 month ago (6 children)

    I have been thinking that NixOS might be a cool base for governments or whatever to build their 'distro' on top. Because you just need a config file, where it says you want 1 KDE, please, with wobblyWindows.enable = true and then you're golden.

    It's immutable as well, which you typically want in such organizations...

  • source
  • view more: ‹ prev next ›