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

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

What’s the problem with the Digital Services Act?

But “Congenital Venereal Edema” is better?

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.

That doesn’t work in all cases. I’ve recently come across two examples where we had a hard time explaining our costs even though we extensively tag and even have fine-grained AWS accounts:

• Some costs can’t be tagged or at least not easily, e.g. custom CloudWatch metrics.
• For some resources it makes a lot more sense to provide them centrally for multiple services at once, e.g. NAT gateways or load balancers.

For anyone as confused as me about what a “Forth” is: Forth is a rather old stack-oriented programming language.

✅ but I can’t give the competitors too many ✅ so let’s go with ⚠️

syncthing also relies on a web server for device discovery, it’s just that you’re probably using someone else’s server instead of hosting your own.

Correct me if I’m wrong, but I also think that Vaultwarden itself doesn’t have access to the unencrypted password database. In that sense it’s E2EE similar to KeePass, the only difference being that KeePass is a desktop app and Vaultwarden a web app.

Nothing, this is not about that.

This change gives you the guarantee that .internal domains will never be registered officially, so you can use them without the risk of your stuff breaking should ICANN ever decide to make whatever TLD you’re using an official TLD.

That scenario has happened in the past, for example for users of FR!TZBox routers which use fritz.box. .box became available for purchase and someone bought fritz.box, which broke browser UIs. This could’ve even been used maliciously, but thankfully it wasn’t.

Being in alpha and having breaking changes is fine, the question is how many. My impression is that Immich seems to introduce breaking changes far more frequently than what people might be used to from other projects.

And that does go back to professionalism: The better you plan ahead, the fewer breaking changes you have to impose on your users.

Minio now describes itself as “S3 & Kubernetes Native Object Storage for AI” - lol

Guess it’s time to look for alternatives if you’re not doing ML stuff

Wouldn’t (30px)² be 30*30*px*px and thus 900px²?

cataas - not to be confused with catass

Wait till you find out what Russia and China are doing on Facebook

…what? SpaceX is years behind schedule for delivering crewed space flight to NASA. US tax payers have had to cough up billions of dollars for seats on Russian Soyuz spacecraft to at least be able to get to space somehow in the meantime.

Iterating and failing is okay, but SpaceX has neither been faster nor cheaper in doing so than NASA’s original moon landing program.

I wouldn’t call criticism of their strategic focus “shitting on” Nextcloud. It obviously still does a lot of things right or at least right enough to be useful and relevant to many people, or else we wouldn’t be discussing it. But it has its issues and many of them have been unadressed for a long time, so why shouldn’t people voice their displeasure with that?

investment gamble

FTFY

There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver

Depending on how one defines the “initial development” phase, those projects are actually conforming to semver spec:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.