App looks very nice and good to see active subsonic clients. I'll stick to DSub until random album support (#289) and download starred albums/artists (#197) is implemented, but I'll be keeping a close eye on this one.
I also like to grab a bunch of content all at once and then watch at my leisure.
If you're tech-inclined you might like pinchflat or Tube Archivist, which can archive channels/playlists in the background with video metadata automatically, which you can then use with JellyFin.
Not something so complex that it requires docker. Not something that requires you to install a separate database. Not something that depends on redis and other external services.
This comment is a bit silly. Databases just make sense for many services, although many could just use sqlite which would be fine (and many do). Redis etc is usually optional and might increase performance in some cases.
I wouldn't be a fan of something requiring docker, but it's often just the easiest way to deploy these types of services (and the easiest way to install it as a user).
Anyway, I'll echo that clear, up-to-date documentation is nice. I shouldn't have to search through actual code or the bug/issues section to find current information (but I get this is very challenging). And I'd rather projects didn't make Discord a source of documentation (especially not the primary one).
I'll add that having a NixOS module is a big plus for me, but I don't expect the developers themselves to maintain this.
Beyond the other comments is your public IP on ipinfo.io etc something like 100.64.X.X or 10.X.X.X?
If so, you're behind a CG-NAT and raw wireguard will not work. I say this so you don't waste time configuring something that will never work. Ignore the below if you have a real public IP.
Some ISPs will allow you to get a real dynamic ipv4 address for free, or you can configure ipv6 but any clients that you connect will also need public ipv6 support.
Otherwise, consider tailscale/headscale/netbird (SaaS or on a VPS) which have NAT traversal support.
The whole NYSE thing though is blatantly sucking up to Trump. And since Times already gave it to him once, maybe don't feed his overinflated ego even more? Because there is no way he is going to take it as a negative, as his desperate desire to be on the cover has shown.
I have some lisp knowledge, so the scheme version doesn’t look frightening to me, but I guess for sysadmins, who should write these kind of files frequently systemd’s TOML like language is much more easier to understand.
People who only know C-style languages tend to struggle with anything that deviates from that too (which is a lot of developers). The Shepard example looks readable to me, but then I'm a Emacs user and have learned a few languages with "weird" syntax so something that looks a bit different is fine.
Why this kind of files should be written in a programming language at all? I guess it’s a remnant from the old times, but I like when tools abstract away the programming parts, and users shouldn’t have to deal with that
It's user base is akin to the NixOS audience. It's more aimed at advanced users and sysadmins (with some programming ability) that want to configure their whole system declaratively.
Using a real programming language gives a lot of power and flexibility to achieve this that you'd effectively have to create a new language to replicate that (I.e. Nix or Guile).
On the other hand, something like Shepard is potentially overkill for even Nix and Guix. Nix works quite well as a layer on top of systemd to declare a NixOS system, and still gives you enough power to do most things.
Seems fine. I have an affordable NAS that mostly serves files and has a few containers, and a second server using one the Lenovo Tiny machines that has many more services and a lot more RAM. And it works well.
It may since have been fixed, but the Android client didn't handle IP changes well in my experience. From my understanding, it only checks DNS when it initially connects, and so if the public IP changes the connection just stops working. This might be fine if the public ip changes infrequently or if you frequently connect and disconnect rather than leave the client always on, but not so much otherwise.
Tailscale (and headscale) handles this gracefully, and you also get the nice NAT traversal features so no need to worry about CGNATs which are becoming more common.
There's also the phenomenon where you make a forum post and then immediately solve it after (or even before) you submit it. Although that is more because it forces you to think through the problem systematically.
once you know how to use linux, you can stop fixing everyone elses problems for them.
I know you meant being able to claim "I don't use Windows" but just installing Linux has massively lowered the tech support requests I get from my parents.
App looks very nice and good to see active subsonic clients. I'll stick to DSub until random album support (#289) and download starred albums/artists (#197) is implemented, but I'll be keeping a close eye on this one.