Thank you, the part about the database is important.

Of course that depends on the apps in question and if you are even able to install additional apps in a managed environment.

But not all apps are so limited. The cookbook app for instance saves all recipes as markdown files you can easily share with others, download or backup.

Managed Nextcloud is definitely easier than hosting it your own. I bet they also have the hardware to guarantee good performance. With any luck Hetzner also offers AI features like face recognition and automated tagging.

But don’t go in there expecting a fully fledged Google Photos alternative. Even when Memories is much better than Nextcloud’s own Photos, it lacks many essential features like easy filtering of your collection. You basically have to sort your photos yourself.

Unless Hetzner offer something on top of Nextcloud file sync is done via Webdav, not sftp or rsync. But basically every OS has Webdav clients.

Calendar and Contacts are also synced via DAV. CalDAV and CardDAV. Works well for me on Android with DAVx⁵.

You probably think that systemd-boot is tied in any way to the rest of systemd. It is not. Systemd-boot is just a very simple EFI boot loader that is hosted by the systemd project. It does not require any part of systemd to work. It has no problems booting a distro without any systemd components.

I just googled something. Don’t remember what I ended up on. Probably some blog post combined with rspamd’s website. It depends on your mailserver anyways.

rspamd is used nowadays. Add sieve filtering to automatically move mails with a 7.0 or higher to a spam-folder. Manually move mails there that haven’t been detected and move mails out of the spam folder that have been falsely detected (personally don’t have any false positives with rspamd).

Then set up bayes learning with rspamd, either when mails are moved between folders or every few hours.

Thanks, setting up the runner and actions works great! Permissions are a bit wonky but not unsolvable.

I use Nextcloud. Of course that only makes sense when you use the other Nextcloud stuff as well.

Huh, TIL.

Honestly, that’s what most web API’s are. You are just pushing data around. The “hard” part is that everyone has their own opinions on how it should be formatted.

And of course the minor inconvenience of having to give the user a way to make data entry easy, convenient and consistent.

But deep down it’s all spreadsheets. The faster you can wrap your head around that the easier programming is for you.

Probably easier to hook those panels up to your balcony. You’d charge at home anyways, right?

Are those 15 km under ideal conditions? With static panels you can control those easier. On the car the panels will usually have the wrong angle. Plus the added weight and wind resistance further decreases the effective range they provide.

I’ve got a really obscure one.

Anyone here heard about FLI4L? Floppy ISDN for Linux? Built from the ground up to be usable on your really old PC as a router. Originally it fit on a single floppy disc and was able to turn a 386 into a modem or ISDN router. Later they added the ability to route between LANs and DSL.

By now the requirements have been raised to super beefy 586 PCs. It probably doesn’t fit on a floppy disc anymore.

Sure, but having /boot on BTRFS won’t save you if the bitrot fucked up your ESP.

Good luck, when EFI has to live on FAT32.

For anyone reaching for the downvote button:

Systemd-boot is completely independent from systemd init. You don’t have to be running systemd to use it. It’s a really really simple EFI bootloader. You just give it the location of your kernel and initrd and boot options and it does the rest.

Switch and Click had a video about that recently: https://youtu.be/M9qJI2u_be0

I was and still am on HDD. The CPU was upgraded as well. I migrated to a new server.

The main culprit was the database. As far as I’m aware Lemmy is missing some indexes and due to the ORM they used didn’t always have optimised queries. Now with 64 GB RAM the whole database (almost 30 GB) fits in there fixing most of those issues.

The real fix will probably come with Lemmy 1.0. They radically changed the database layout and queries.

Image proxying wasn’t bad for performance. Just storage space. It was growing really really fast. Now that only I am using it to host the pictures I uploaded it is still much too large (24 GB). But its directory structure is so convoluted that I can’t really debug it. My stuff really shouldn’t be taking up more than a few hundred MBs.

I am the only one using this instance. I am subscribed to a hundred communities or so. I am always pretty up to date with my Lemmy versions.

RAM. Maybe 32 would have been enough but 64 cost as much as 32 so that decision was easy.

Same stuff you do on any other instance. Looking at stuff, upvoting, downvoting, posting and commenting.

Control. I’m not beholden to anyone. My server is federating exactly those communities that interest me.

I run an instance just for myself and it was a nightmare on HDD and 16 GB RAM. It was slow as molasses. Supposedly the database layout will be fixed with the 1.0 release that is just around the corner.

Since I upgraded to 64 GB it’s been pretty smooth. Still wild that that is necessary for a single user.

Also, disable image proxying. I have no idea what pict-rs does but it seems to be too much.

You should consider running Piefed instead. It’s not as resource hungry as Lemmy.