fonix232

If you want a NAS specific case, check on AliExpress - a bunch of $200-300 options with SATA backplanes, EATX support, and your typical 8-16 front-loaded disk bay with disk caddies.

I think this topic is actually ripe for debate.

On one hand we know that Majel specifically recorded phonemes so her voice can be used for Star Trek purposes after her passing. While not a direct consent of "do whatever you want with my voice", the intent of similar purposes as OP's has been clearly present.

There's also Paramount's refusal to use her voice in new Trek, aside from a few snippets here and there (mostly Picard for the throwback value). Which kinda goes against the spirit of Trek.

On the other hand, the entire area of voice cloning is gray as fuck. It can very easily be used for nefarious purposes, yes - let that be corporate greed or fraud or propaganda. But if I make my own voice system, do I really hurt anyone by using their voice? I am not profiting off of it, I am not sharing the end result, it lives on my computer and that's it.

But, let's say I want to do the same. There's this TV show from some 20 years ago called Eureka. In it is one of the earliest representations of a smart house with an AI governor, called SARAH. SARAH is voiced by one of the recurring cast members, in fact it's an ongoing joke that the house is voiced by this guy "talking like a girl", and that he's trying to get Sarah Michelle Gellar to do the proper, final voice...

Now, the voice itself is pretty unique, but it isn't the voice of the actor, it's been heavily digitally edited. It's also a pretty unique voice but not something 99.9% of people would recognise. I make my clone from my own BR disk collection, with a set of automated and AI tools to get the right audio, clean it up, split by talker, and process all 77 episodes, manually selecting the right samples, manually tagging and labelling each; and finally, fine-tuning my own model for my own use. It will never leave my home, I won't sell or share it, and technically, with me owning the BR collection, this would fall under fair use.

Which is still quite different than, say, a corporate entity trying to sell more product by using your voice.

"The best" depends on what you really need.

Authentik and Authelia are two of the top most quoted solutions, but they aim to be an "everything in one" package, with tons of features a simple homelab will rarely need. They're aimed more at enterprise-like setups.

On the other end of the spectrum you have e.g. Pocket-ID, which only does OIDC by itself (you can hook up an LDAP server as user database though); but that tradeoff means it uses little to no CPU time, and, in my experience, around 130MB RAM. Given RAM is getting more expensive than gold, one needs to consider memory footprint, especially for older homelab setups. We can't all be running 256GB nodes after all.

So instead of hunting the mythical "best" solution, decide what features you really need, grab a list of providers that cover those features, and compare them to see what fits your needs best.

The recommendations so far are quite solid.

I'd also add that crowdsec with the right collections as a primary filter within your reverse proxy setup can be extremely useful, potentially even better than fail2ban, as CS delivers a literal "scan every packet and put them against these rules" approach - where the rules are crowd sourced, thus are more up to date than any manual blocklists, filter list etc. can be, and can spot even 0day intrusion approaches.

It depends on the app. You can use Authentik as an OIDC provider and allow apps that offer OIDC to log in through that - and that usually works for TV sticks and such.

Uhm, no.

Only if the licence allows. I personally go for A/GPLv3 wherever I can because I don't want corporations to just take and not contribute back. But that means I can't just copy MIT/Apache software, need to do my own implementation from scratch. Which I prefer anyway.

why would I try a book REQUESTING system when I'm working on my own AIO solution?

I'm actually working on an all in one solution that sort of fills the roles of Readarr AND Calibre - without all the baggage of the latter.

Oh, and of course a KOReader library plugin that foregoes OPDS and works like the Kindle interface ("available books" synced from this backend, one tap downloads them, plus potentially adding series handling too in the future).

But right now it's mostly manual downloads + CWA ingest + OPDS via KOReader.

Before you carbonate the whole batch, separate a cup/pint glass worth, and nitrous it. Just to check the difference.

An mSATA or small NVMe in a USB enclosure is the best way to go. No wasting a precious internal slot, and they can be super tiny (2230/2242 enclosures are dime a dozen).

Windows Server exists.

It really shouldn't, but it does.

You can buy ESP32 boards with built in DACs, just FYI.

Also there's a handful of Pi Zero shaped ESP3 boards as well, which you could use with the existing DACs.

But again my point was that Sendspin requires even less hardware than Snapcast (and while technically you can indeed run Snapcast on an ESP32, last I checked it uses up a lot of resources, making the ESPHome given extras like BT proxy and usage in real time BT based location, unusable).

I am using it on a handful of devices (mainly voice interfaces), and it's quite seamless, even in the beta stage.

Not up to Sonos level controls yet, but it's getting there slowly. Music Assistant is gaining a lot of UX improvements recently, so it will be soon a viable alternative to not just SnapCast but Sonos too.

And you did it all in time just to have it be upended by SendSpin - which can even run on an ESP32 level MCU so you don't even need a Pi Zero.

To be perfectly fair, a proper wheel of Parmigianino Reggiano IS quite hard...