fwiw, I used Kopia for around a year, but eventually the backup got corrupted with a BLOB not found error and there was no way to fix it.

similar to this issue, except that nothing would fix or improve the situation https://github.com/kopia/kopia/issues/1087

and because it seemed to be an issue with the repo (not just with a snapshot), the remote copy was also borked. I couldn’t even list the snapshots.

I’ve since migrated to Rustic (though Restic might be more reliable today).

This seems to be the a similar issue too, but I was nowhere near the scale of this user. There are other similar reports that may or may not be linked to the same root cause, so it’s hard to say how rare this problem is.

It’s private as opposed to the public internet; there’s no “personal” in VPN.

I think Tor is too slow for most people / everyday browsing

I’m having problems opening the image, is it just me?

deleted by creator

You were given a list of scenarios above that list where vpns are useful. It seems you’re the one who don’t know what you’re talking about.

alright then, keep your secrets

Isn’t that creating hardlinks between source and dest? Hard links only work on the same drive. And I’m not sure how that gives you “time travel”, as in, browsing snapshots or file states at the different times you ran rsync.

Edit: ah the hard link is between dest and the link-dest argument, makes more sense.

I wouldn’t bundle fs and backup compression in the same bucket, because they have vastly different reqs. Backup compression doesn’t need to be optimized for fast decompression.

yeah, more often than not I notice the bottleneck being the storage drive itself, not rsync.

yeah, it doesn’t, it’s just for file transfer. It’s only useful if transferring files somewhere else counts as a backup for you.

To me, the file transfer is just a small component of a backup tool.

It works fine if all you need is transfer, my issue with it it’s just not efficient. If you want a “time travel” feature, your only option is to duplicate data. Differential backups, compression, and encryption for off-site ones is where other tools shine.

I tried portainer for a while, but it was almost useless to me, as I’d always end up in the command line anyway. So I dropped that and any other dashboard idea.

Yeah, I have everything as compose.yaml stacks and those stacks + their config files are in a git repo.

it might be worth watching this PR for memos, which adds encryption at rest. I can’t vouch for it, as I didn’t read the code but I do use memos and might consider this if it’s merged.

https://github.com/usememos/memos/pull/5130

This is not E2EE, but I don’t think E2EE is that important if you’re hosting your own data. And clients can use TLS for encryption in transit.

it’s a lot of code, not a lot of data. If any repo has binary files you’ll most likely need to store it somewhere else as there’s not even an option to pay that used storage.

they also have a limit of 100 repos, so I can’t even migrate everything I have on github

context, for the unaware

https://en.wikipedia.org/wiki/1995_Greater_Pittsburgh_bank_robberies

That’s my point, checking a few boxes in the settings is the bare minimum if you care about it, so idk what’s the value in comparing defaults.

And privacy is often a tradeoff, if a browser doesn’t have the strictest by default, it’s probably because the ones who forked it didn’t consider it a good tradeoff.

That only seems relevant if one uses the defaults, and if you care about privacy you probably don’t, so idk what’s the goal of this little experiment other than just curiosity.

It’d be a whole lot more useful if it was “here’s the connections these browsers made after enabling all privacy-preserving settings they offer”.

who would have thunk