shadowbert

My condolences :'(

I once lost a bunch of data because I accidently left a / at the end of a path… rsync can be dangerous lol

Unraid, mostly due to the flexible arrays.

which also includes their free services

Well… their free services remain free regardless of your registrar. Still, I don’t really mind supporting them given how useful they have been even in just the free tier.

like Google

Too soon. I mean, it was ages ago but…

3 billion of them. So, over a third of the population of earth does (at least according to this graphic).

It’s in the Arch TOS.

I’m using cloudflare as my DNS, and it’s literally just:

• Create an A record.
• Set the name to *
• Set the IP to the appropriate server
• You may want to untick the proxy, depending on what you’re hosting. If it’s web stuff only it’s fine, but if you’re doing anything else as well it’ll get in the way.

On the letsencrypt side, it’s pretty similar. Create a certificate with domain.name and *.domain.name (if you want them to share a cert) and you’re off.

I host some private stuff on mine, hidden behind an authentication service that is. But because I just use a wildcard no-one can really tell what I have hosted - the same login page occurs for every subdomain, regardless of whether it’s actually wired up to something.

That doesn’t help with services you wish to make semi-public (like a lemmy instance) though.

My mate’s home server.

I personally prefer bitwarden, using a self-hosted vaultwarden. It's free, it syncs, it's easy to use.

It's more like using the pill and a condom. Different ad blockers can block different sets of ads.

I don’t really understand what you’re suggesting. Having a seperate compose file for your database would “work”, but you’d lack any of the dependency handling.

Dependencies within unrelated projects (ie, sharing a single database container for a few unrelated apps) is something that would be pretty handy, and is missing from compose.

Auto-updates are cool - but also dangerous… I think there’s something in running watchtower manually like I have been - when something breaks straight after, I know the cause.

I haven’t had good experiences with it, but nor have I tried it for quite a while having switched to AMD.
My gut feeling is that it’s going to be even tougher than it already was, assuming nvidia’s continued lack of cooperation. With DLSS and other proprietary technologies becoming increasingly mandatory for nvidia card users, keeping up is going to one hell of a ride.

One thing I did miss about grocy was the ability to track equipment in the kitchen (and house) as well, including the storage of manuals and warranty information.

Do you have any intention (or interest) in adding that?

I was pretty annoyed when my grocy install broke ages ago, and I lost all of that information but it was very useful having all of that stuff centralised.

Why not?

Difficult, yes. Impractical? Absolutely not, at least with some planning ahead. It’s not trivial (and I never said it was) but it’s getting both easier and more important every year.

Of course - I get that. I’m a programmer myself.

But it does have to be said that there’s little excuse for not doing it anymore for heavy applications, especially games. The tools/frameworks/engines have vastly improved, and people know (at least roughly) ahead of time what work is going to slog the CPU, especially in the case of a AAA studio.

Note: I’m only referring to relatively modern games here - anything that’s older than when multithread really took off gets an automatic pass - it’s not reasonable to expect someone to cater for a situation that doesn’t exist yet.

Heh. Classic case of being able to market your product as being “multithreaded” because is uses 2 threads? :P

Surely there’s no way that’s just the ram… did you also double your workload or something?