Restic doesn’t write your files 1:1 to B2, but instead chunks their content into files according to a configurable pack size (16MiB by default). If you have a very large amount of data, you could look into increasing the pack size, although that comes with its own risks (see the docs above).

I never claimed it would make security better. I said it would reduce noise, and it does.

Good luck getting e.g. Ansible to work with that. At that point I’d just switch to a hosting provider with an actual firewall.

If you have a public IPv4 address and use port 22, you’ll see lots of login attempts. I wouldn’t worry about it, given that you’ve disabled password login. The only thing I would advise is to disable root login as well (if not done already). Edit: Just saw you’ve already disabled root login.

If you’d like to reduce the noise somewhat, consider changing to a randomly chosen high port. I’ve done this with my VPS and hardly get any login attempts.

The docs on DNS challenge are here, and a bit further down you can find the ones on wildcard certificates

Why is this post in the privacy community of all places?

I think you should read the article before heading to the comment section.

This is not about saying “something slightly wrong decades ago”, this is about giving a platform to a self-proclaimed fascist and being unrepentant about it to this day.

Regardless of how you feel about the definition of open source, that should really make you think.

+1 for Podman. I’ve found rootful Podman Quadlets to be a very nice alternative to Docker Compose, especially if you’re using systemd anyway for timers, services, etc.

If you also use FreshRSS, you can configure filters to automatically mark new articles as read (e.g. !intitle:'beta'). Since I only view unread articles, that effectively deletes them and I never have to see them!

While I agree with your sentiment, no interoperability obviously hasn’t made people switch to better platforms either. The only difference is that without interoperability, I’m forced to still use WhatsApp to communicate with those unwilling / unable to switch.

While I agree, it seems a little ironic given your username

Definitely, that’s what I’m doing as well. I’ve found some to be lacking for my needs (e.g. music), but most of them are good enough for most use cases.

I’m using Nextcloud as well, but I’ll admit that it’s probably a bit heavy if all one needs is a calendar.

Simple Mobile Tools was sold a while back, IIRC to an ad company. As a consequence, the Fossify forks were created.

As much as I agree, I think we’re past the point of preventing normalization.

OP said to mind the clunkiness, so fair point. Though by far the worst part of this are the slightly skewed lines going to KeePassXC, KeePassDX, and Proton Pass…

You mean

question vs not question

You still have 63% RAM available in that screenshot, there are zero problems with Java using 13% RAM. It’s the same as the tired old trope of “ChRoMe Is EaTiNg My MeMoRy”. Unused memory is wasted memory if it can be used for caching instead, so unless you’re running out of available memory, there is no problem.

Also, the JVM has a lot of options for configuring its various caches as well as when it allocates or releases memory. Maybe take a look at that first.

Edit: Apparently people don’t want to hear this but don’t have any actual arguments to reply with. Sorry to ruin your “JaVa BaD” party.

I use Backblaze B2 for one offsite backup in “the cloud” and have two local HDDs. Using restic with rclone as storage interface, the whole thing is pretty easy.

A cronjob makes daily backups to B2, and once per month I copy the most current snapshot from B2 to my two local HDDs.

I have one planned improvement: Since my server needs programmatic access to B2, malware on it could wipe both the server and B2, leaving me with the potentially one-month old local backups. Therefore I want to run a Raspberry Pi at my parents’ place that mirrors the B2 repository daily but is basically air-gapped from the server. Should the B2 repository be wiped, the Raspberry Pi would still retain its snapshots.

What am I supposed to do with those informations?