I use Kopia to perform incremental encrypted backups (with some retention policy of up to two years) and store them on Backblaze B2, which is reasonably cheap.

That, on the other hand, is only viable, if you are sure, data never needs to expire. Dedicated backup solutions work with retention policies.

Where I could see an LLM being useful is categorizing entries and maybe proposing sanitization (for example when the payment provider uppercases or abbreviates stuff)

From maybe to definitely not.

Just to clarify: OwnCloud or OwnCloud Infinite Scale (OCIS)?

Probably some fastboot shit. I like the idea of fastboot… if only it wasn’t so tied to Windows.

The ONLY thing I don’t like about it is having to finish the install of windows before you can wipe the ssd.

Why? Can’t you get to the bios, change to usb boot loader, boot linux and wipe the disk?

If your client(s) accept irregularly changing remote certs (i.e. they don’t do cert pinning), it should work. If both cloudflare and you use the same CA, it would likely work even with cert pinning. Certainly possible, but increases the complexity of the overall setup.

Possible, true. But then the setup also becomes more complicated. In addition you end up with different certs for local and remote access, which could cause issues with clients if they try to enforce cert pinning for example.

Cloudflare tunnel likely terminates TLS on the edge. So if you bypass it, you don’t have HTTPS. Not a problem locally, but then destroys the portability of the URL (because at home you need http and outside you need https). Might as well use different hosts then.

it doesn’t matter

Hehe.

Anyway, I am also completely on Zigbee. While I like the concept of Matter over Thread, I wouldn’t want to switch, because it will start with a too small network to cover a good distance and if I start replacing Zigbee devices, I effectively sabotage that network as well. So my only move would be to replace all Zigbee with Matter/Thread devices. And that seems insane. So I hope I keep getting new Zigbee devices for a while.

That’s the “pedantic” part that also gets me, but realistically it doesn’t really work out anyway, because the “servings” are individual sizes. I can’t really calculate exactly how much everyone is going to eat. So even if the recipe turns out the exact amount it intended, it could still be too much or not enough, simple because someone is more or less hungry than usual / expected.

I like having reproducible results, but practically with food it just doesn’t happen perfectly, even if I actually measure everything perfectly (amounts, time, etc.)

I am probably too pedantic for that. If the recipe says 500g of this with 250g of that, it’s typically a good 2:1 mix and the packaging sizes often aligned. Now you have shit like 400g and 220g and you can’t easily align them anymore. Realistically it probably won’t matter even if it’s not a nearly perfect 2:1 mix either. But … I can’t help myself :D

I also like that they no longer align with typically required measurements for recipes. Nothing gets me off more than having to calculate fractions for amounts of ingredients.

Does it make a difference, if that setting uses a trailing slash? Might be it redirects you to the path without, which triggers caddy to redirect you again, and so on and so forth.

You could also, instead of redirecting, rewrite it. Then it is handled serverside without sending the client somewhere else.

Are all the *arr services aware that they are expected to have a certain basepath?

LOL, ok, fair 😁

You should in any case consider your backup strategy. If you have reliable backups, your fuckups can’t be as bad anymore. If you don’t have reliable backups, a “raw” storage doesn’t help you either. Maybe even the contrary: you won’t notice, if individual files get corrupted or even lost until it’s too late. (Not talking about disk corruption, against which the right filesystem can guard you… but I am not sure you trust filesystems either 😛)

Why does the storage layer of seafile scare you? Are you also scared of databases and prefer storing things in raw txt files? The difference is the same. You get certain features in return:

• Versioning is possible (so each file can have a history you can roll back)
• Sync is very fast
• It can sync incremental changes even of big files

You still have access via:

• Web
• Synced locally using Seafile Client
• WebDAV
• Mounted as network filesystem anywhere using SeaDrive.

I don’t like the syntax, the runtime environment (which runs interpreted) and for PHP more than many other languages (aside from JS), a lot of code out there is hacked together horribly which makes me completely distrust the community.

Personally I stay away from anything that doesn’t have a compiler.

I was in the same boat and therefore my nextcloud instance was mostly running for backwards compatibility with a few setups I have, while I mostly use seafile, immich and sogo. But a few days ago I updated to nextcloud hub 10 (I think that’s with nextcloud 31 under the hood) and damn does that run smooth. I was so impressed I got motivated to finally setup the high performance backend for nc talk.

I still dislike PHP, but nextcloud just won back my heart a little.