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.

I want those cars on the used market so that I can actually afford one.

Can’t you just make the Local feed your default?

Personally I just subscribe to everything I want to see and browse that.

More or less.

• Zswap is better than zram because it’s integrated with the kernel. Swap in zram is more of a hack.
• zram can kill your file cache unnecessarily, which leads to more disk reads.
• Don’t use zram without an oom killer.
• They’re working on zswap to not require any disk swap at all, basically killing the last reason why one might want to use zram over zswap.

He addresses that later under the title “zram on Fedora”.

Basically because Fedora wants to eliminate disk swap entirely. They have systemd-oomd configured to mitigate the downsides.

That’s the way it goes with the scale from simple to “something that fits our needs”. Either something is too simple or it is so complex that you can’t let your more challenged users at it. So you end up rolling your own solution.

That’s how many companies end up with monstrous Excel or Access applications.

The upside of having your own app that uses common open source components is that integration with other tools is easier later down the line. Make it web based and it can run on basically every computer on the planet. Use PostgreSQL or MySQL in the backend and you can easily add other frontends if needed.