You are right to be afraid. I had a similar story, and am still recovering and sorting what data is recoverable. Nearly lost age 0.5-1.5 years of media of my daughters life this way.

As others have said, don’t replicate your existing backup. Do two backups. Preferably on different mediums, spinning disk/ssd eg.

If one backup is corrupted or something nasty is introduced, you will lose both. This is one of the times it is appropriate to do the work twice.

I’ve built two backup mini PCs, and I replicate to them pretty continuously. Otherwise, look at something like Borg base/alternatives.

Remember, 3-2-1 and restore testing. It’s not a backup unless you can restore it.

I have never understood this fork argument. All it takes to make it work is a clear division for the project.

If you want to make something, and it requires modification of the source for a GPL project you want to include, why not contribute that back to the source? Then keep anything that isn’t a modification of that piece of your project separately, and license it appropriately. It’s practically as simple as maintaining a submodule.

I’d like to believe this is purely a communication issue, but I suspect it’s more likely conflated with being a USP and argued as a potential liability.

These wasteful practices of ‘re-writing and not-cloning’ are facilitated by a total lack of accountability for security on closed source commercialised project. I know I wouldn’t be maintaining an analogue of a project if there were available security updates from upstream.

Everything’s a trade off, as you already know. I still use lets encrypt, despite the fact that I know attackers watch CT logs, and they’ll know as soon as I mint a cert.

Also, according to the propaganda model, in developed democratic societies, the propaganda is assumed to be true, and if you’re not on board with that, you’re not part of the debate.

Fair enough, I did assume the target audience was selfhosters based on the question.

As for provider backups - well, you’d hope. But M$ doesn’t do user available backups, so I’d be surprised if that was bundled by the average SaaS provider.

And if you don’t know what database you’re running, how are you backing it up?

If you don’t know what database you’re running, are you bothering to do a full shutdown before backups? Are you doing backups at all…

I haven’t tested the spouse approval factor, but once Radicale is setup, you don’t have to do anything other than create new calendars through a caldav app, or through the web front end.

Android can use DavX to sync if you’re in to foss stuff

I pretty much only use it for tasks and a maintenance calendar, but I’ve had zero problems with it so far

All I need is for them to fix the public collection RSS feed bug where they embed “https,http” in the feed xml if you’re behind a reverse proxy - which breaks parsing

Muppet Treasure Island, and “Spider-Man and his Amazing Friends Ep.16 - A Fire Star is Born!”

On VHS, of course!

and has integration for Oxidized, smokeping, greylog and more

And bleaching the reefs

Yes. But also, despite having done it literally thousands of times, I still can’t tell you which way round to put the target and the link name for a softlink on the first go.

My first guess is always

ln -s $NAME $TARGET

No amount of repetition will fix this.

Sounds like you have reason to bump it up the list now - two birds with one stone.

I need to do this too. I know I have stuff deployed that has plaintext secrets in .env or even the compose. I’ll never get time to audit everything. So the more I make the baseline deployment safe, the better.

That’s fair, there’s other angles of observation made available already.

Seeing as you like speculating about cyberpunk, how about if observation is just the initial way to way to sell the drone cloud? Depending on how cheap you can make them, there’s an argument to made for reducing time-to-intercept for low-speed aerial objects.

If you’ve got a bunch of drones overhead already, you could run one in to the path of a kamikaze drone, or if your swarm is even lightly armed, you can extend engagement range and reduce required accuracy with a single buckshot shell to shoot an offending drone down.

If you’re content to prioritize executive safety over public saftey, there’s a lot that can be done.

Drone displays terrify me.

Not to mention, the minute it happens, the government will carpet the skies with observation drones in the name of safety

Just a little piece

Quad9. Swiss based, dnssec available, has beaten blocking orders by Sony before.

They’re about as open as resolvers get, and they pretty much released everything they could when courts tried to interfere with them.

This article is basically referencing the same event as OPs article, but after Canal+ expanded the scope of their legal challenge.

And a dnssec policy will solve that for you

You’re a monster. My scps would go nowhere

It’s the right move.

I tell you, the first time you’re sat in front of a CEO and an auditor and you have to explain why the big list of servers has a highlighted one called C-NT-PRIK-5 is when the fun stops.

Explaining that it’s short for ‘customer network tester Mr. Prickles 5’, and is actually a cacti server never really seems to help the situation.

At least a few of the customers got a laugh out of it being on the reports!