Radicale. I just finished setting it up and with that, I can now finally shut down Nextcloud.

I don’t think they want to bother with the administration, they were forced to to stop anyone from spamming from random SMTP servers.

Because of dmarc and DKIM, we don’t really need this anymore, but there were good reasons for it.

This list is terrible. These are all “Ai-powered” apps that have mostly better and established alternatives.

Plex isn’t perfect, but jellyfin X Y Z

Really, my guy? You forget that Plex takes things away after saying they wouldn’t? You’re happy with your paid Plex pass… Until Plex decides one day that your pass isn’t lifetime anymore. Or that it doesn’t cover the features it used to. And yes, Plex has lied about this before. That’s why so many ppl are pissed at Plex.

And please give an example of “jellyfin being held back”, whatever that means.

Ethan Sholly, if you don’t know anything about how FOSS works, just listen and stop talking.

I went the other way; I had a Dell r430 and downsized to two hp elitedesk g4 mini. Together, they use less than half of the power of the 1u server.

But I am never satisfied, I’m sure I’ll want to iterate again next year.

On what platform?

Sure, I can accept that.

I don’t particularly have an opinion on artist compensation vs listener freedom when it comes to this. Obviously, I would prefer artists were paid what they deserve, but I don’t like participating in the fallacy that the end user is ethically responsible for the bullshit music industry infrastructure not paying artists properly.

I give where I can, but I’m just some person.

I think like this solution the best.

Not if you’re buying them 2nd hand on eBay, which would represent the bulk of building a collection.

To be clear, im not trying to detract from the effort, it’s just op mentioned artists not getting paid what they deserve.

Legal, yes. Supports the artist? No.

That thing about docker being so badly behaved in unprivileged containers seems to be a proxmox problem, not an LXC problem, as I’ve discovered running LXC in a non-proxmox environment.

Same here. I used proxmox for 8 years and have recently dumped it in favour of a couple of incus machines running OCI and LXC containers.

Much lighter, much faster, and to be honest, more straightforward when it comes to storage abstraction, which I think proxmox does in a very… convoluted way.

You can create a canonical name (CNAME) record to point to your old domain, you don’t need to recreate the LE if you don’t want to.

Assuming I understood your scenario, Canonical name record pointing one DNS name to another domain, then recreate your letsencrypt on the host.

“18% of car owners don’t know their brake fluid DOT rating.”

Makes sense, thank you.

Looks great, and I’m fully supportive of this.

However, I can’t understand the use case, and the part I can’t wrap my head around is why the server part is required… What differentiates pinepods from, say, antennapod from a functional standpoint?

I thought I was being clear that I have audited some of the scripts. They are built referencing other scripts instead of functions, and these rely on URLs. It’s difficult to follow.

Don’t ask chatgpt to audit code.

Have you ever looked at what was once ttek scripts? They’re a spaghetti of calls to other scripts. It’s not pretty. And not intuitive to audit.

An apipa address is a sign that networking is not working as intended. This should be resolved first before assigning a class C private addr manually.