

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


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


They’re the same picture.jpg
Deleted the test suite since it was failing


Thanks for the hint! I didn’t know this setting existed and of course it was enabled by default… What happened to informed consent?


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 have no experience with inviting others to calendar events since I only use this setup for my personal calendar - sorry


Idk about E2EE, but I’m using self-hosted Nextcloud. Using CalDAV, you can integrate virtually any app. On Android I’m using DAVx5 and Fossify Calendar.
The advantage of Nextcloud is that it provides a lot of things in one package such as contacts, tasks, notes, files, etc. If you don’t need those, it might be better to look at some of the other suggestions that only provide calendars.


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.


See, they want you to believe that SQL stands for Structured Query Language. But I know from our lord and savior Elon that it actually means Socialist Queer Liberals!
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 ⚠️
So you’re saying we should create a programming language called “Welsh” with C-like function names?


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


currently being tested
They’ve been “testing” it for more than a decade at this point and even if Russia is able to actually bring the T-14 into service, they won’t be able to produce any significant number of them for the same reason their tank corps isn’t using many T-90M right now.
pure garbage
Go look up Operation Desert Storm and rethink what you wrote there.
If there’s anything here that’s garbage, it’s your notions about tank design.


more manoeuvrable
Ah yes, there’s nothing quite like a 4 km/h reverse speed. That’s a really tangible factor making the T-72 a better tank.


Who cares? They’re just pedestrians, it’s not like they’re honest car-driving citizens
~ 'murica
What’s the problem with that? In my previous team, we had a structure with four levels of nesting where we only ever needed to query the first two levels. At first we used Postgres with normalized tables, but it was just slow as hell. Switching to MongoDB actually made our performance issues vanish.
Of course it all depends on what kinds of queries you need to run, but I don’t think that large JSON documents are necessarily a problem.