Give NixOS a shot. It’s got a learning curve that may be difficult if you’ve never read code, but it’s my preferred immutable setup.

It even has more packages than Arch.

Here’s the video that got me onto it:

https://youtu.be/CwfKlX3rA6E

I’m really enjoying Otterwiki. Everything is saved as markdown, attachments are next to the markdown files in a folder, and version control is integrated with a git repo. Everything lives in a directory and the application runs from a docker container.

It’s the perfect amount of simplicity and is really just a UI on top of fully portable standard tech.

I completely gave up torrents for Usenet, also using the -arr’s to get content for Plex. I completely saturate my bandwidth with Usenet downloads and I’ve never once received an ISP letter, and I’ve been entirely without a VPN.

As someone who completely gave up torrenting for usenet, what made you decide against usenet?

To elaborate further from the other comment, it’s a person running a copy of the Lemmy software on their server. I for example am running mine (and seeing this thread) from https://zemmy.cc. Thanks to Federation all of our different servers are able to talk to each other so we can have a shared experience rather than everyone being on one centralized instance managed by one set of administrators (like reddit is).

This provides resilience to the network. If reddit goes down, reddit is down. If lemmy.world goes down, you can still access the content of every community that isn’t on lemmy.world, and if other servers were subscribed to the content on a community from lemmy.world you could still see the content from before the server went offline (and it will resync once it’s back up).

If we put all of our eggs into a single basket, we have a single point of failure. If all of the major communities go to lemmy.world then lemmy.world is that single point of failure. Doing that is effectively just recreating the same issues we had with reddit but with extra steps. By spreading larger communities across servers we ensure that the outage (or permanent closure) of a single instance doesn’t take down half the active communities with it.

My friends instance, crystals.rest, is hosted on a $5/mo Linode with 1GB of RAM

Putting all of the large communities on a single instance is just reddit with more steps. It’s good that one of the larger Lemmy communities is not also on the largest Lemmy instance. Lemmy.world suffers a lot of outages (in part because it’s so centralized), meanwhile this community remains available.

Static pages with hyperlinks have evolved into a certain horror we all know.

Why couldn’t this just be a webring of sites following a specific design philosophy?

This is a neat idea, but the requirement of installing a whole new piece of software just to decide if it’s worth exploring is already a non-starter.

Sure you could make the argument that HTML has too much going on, but you don’t have to use all of that. It is still at its core just as capable of rendering plaintext and hyperlinks as it was the day it was originally conceived.

Why couldn’t this just be a webring of sites that are following a specific design philosophy. I don’t understand the requirement of an entirely new language, protocol, and client. You’re not executing the goal in any way than what is already possible, and you’re cutting yourself off from being accessible by the vast majority of people by requiring them to install a whole new piece of software just to see if this idea is worth exploring.

How is this website so wrong?

I don’t have a static IP. I’m not in the United States. I’m not even in North America…

I’m literally on another continent which can be very easily verified using nothing more than a geoIP lookup, but they somehow place me somewhere 3,000+ miles away. And no, I’m not using a VPN.

This is neat, but this decidedly a niche product with very limited application. I’m an old hat and I can’t see the inherent value proposition in this, why is this better than static pages with hyperlinks? That doesn’t and frankly shouldn’t require a whole new protocol and client. That’s what HTTP and HTML were originally built for.

I never have been able to, even while wearing wired studio monitors

They keep updating the list every week even if you’re not listening. Also I’ve used their service for years so they have me pretty well figured out.

I’ve honestly never been able to discern a difference in quality between 96kbps and 320, even while wearing my ATHM50’s, maybe my hearing just sucks. 🤷‍♂️

Azuracast let’s me stream up to 320, but I choose to use 96 to save bandwidth.

Unfortunately no, but any client that supports the subsonic api will work

It’s good enough for my purposes, which mostly involve streaming it over 96kbps for playback on wireless headphones. It’s a small price to pay for the convenience of the automation.

Navidrome natively supports scrobbling. I also scrobble from Clementine on my desktop.

I’m downloading individual tracks much more than I’m downloading entire albums.

That was my mistake, and I’ll edit the post. I just verified that you are correct by checking a random subset of the MP3’s I have. I clearly got wrong information from somewhere.

I’m a dev of nearly 20 years, but all of this was written by ChatGPT as described in the repo readme 😅

https://github.com/Zetaphor/personal-auto-radio#created-by-chatgpt

Spotify pretty much has them down from my years of use. Even if you’re not coming back and listening regularly it will still update that playlist every week.

LastFM is getting my actual up to date listening habits as I use their scrobbling service with my music clients, including Navidrome.