My point was those projects are still relevant this long after becoming defunct. That is kind of sad that there aren’t new projects that have arisen from the ashes, at least not ones that are talked about more than the corpses.
If it takes so much effort to make things compatible with Wayland such that fucking clipboard support is newsworthy, it’s no wonder Wayland has been such a shitshow.
While true, it can fill the drive replacement with data spread from way more number of drives than raid can, so the point I was trying to make is that a second failure due to resilvering cam be greatly mitigated by using a Ceph setup.
Just rebuilt onto Ceph and it’s a game changer. Drive fails? Who cares, replace it with a bigger drive and go about your day. If total drive count is large enough, and depends if using EC or replication, it could mean pulling data from tons of drives instead of a handful.
Yea that’s the whole trusting trust thing. You can theoretically set up hour browser to only trust your private CA and not trust any of the publicly trusted CAs. Depends on your threat model I suppose.
Because a private CA allows you to create a certificate and nobody else has the ability to create certificates unless you give them the keys or a signing CA. With Let’s Encrypt, you are trusting every major certificate authority to not create a cert on your domain; coupled with DNS poisoning means you would end up on a legit-looking but counterfeit website of yours.
They did not take money from anyone. Are ‘t we on the priacy community? What is with the double standards? It’s theft if it’s against the Little Guy(tm) but it’s civil copyright violation if it’s against the Corpos?
Services the only supported sqlite databases struggled (Jellyfin). Anything that worked with postgresql worked like a charm. So trick on the sqlite ones is a local PV then do a task to copy to NFS periodically.
I don’t disagree at all, I’m just noting this stuff isn’t easy.