• 11 Posts
  • 645 Comments
Joined 3 years ago
cake
Cake day: July 8th, 2023

help-circle

  • 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.



  • I’ve been gaming since C64 days. We had the problem of too many games already back then. Hundreds of pirated games on disks and most of them weren’t even good.

    The other day I felt the urge to play a new game from the “dead” point & click adventure genre. Filtered my Steam games and even found a relatively recent one with full Steam Deck support that was given away for free.

    And I think I can do that with basically any genre.

    Great indy titles get released all the time. Emulation gives me the ability to play almost everything from the entire history of gaming. Or just play one of my favourites. I just have to reach out and play. 2023 was an amazing year for gaming. 2025 wasn’t bad either.

    Sure, bad games get made as well. But when I feel down I can just stop playing those and play Diarrhea 4 instead.




  • 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.





  • 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.




  • The kernels (and accompanying modules/drivers) are more or less freely interchangeable.

    Bugs in the kernel are pretty rare in my experience. I think it’s more likely that the bug was somewhere in KDE Plasma. Kubuntu’s version should be older than the one on Cachy. On top of that Kubuntu has their own patches for KDE, so even if the version numbers are the same they are not the exact same programs. And on top of that the way they compiled KDE will be slightly different.


  • 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.




  • We had that issue at work with email account passwords that could be entered into a browser in UTF-8 but would be sent by email clients on Windows in whatever the default encoding there was, usually not UTF-8.

    The server just blindly pushed the bytes it received into the hashing algorithm. It didn’t have any means of identifying the encoding used either way. We “solved” it by showing a warning about the bug when people logged in and entered a password with non-ASCII characters. Many people used a web-based email client anyways so it wasn’t such a huge issue anyways. We didn’t want to force customers to only use ASCII symbols.