Creator of Deus Ex Randomizer and other mods: https://mods4ever.com/

https://lemmy.mods4ever.com/communities

  • 18 Posts
  • 52 Comments
Joined 3 years ago
cake
Cake day: May 6th, 2024

help-circle
  • I don’t think Zswap can be tuned like that.

    The idea is that the Linux kernel wants to get rid of this page of memory only because it has something better to use that memory for. So if it’s uncompressible then it should go to swapfile for optimal performance. Otherwise it means something else is getting kicked to swapfile, and it wasn’t the kernel’s first choice to be moved to swap so that’s even worse, and what happens if that is also uncompressible? Now you’ve got a cascading failure.














  • I would never say any distro is best lol, but Kubuntu is very underrated. It’s stable whether you choose LTS or the interim releases. The interim releases keep you up to date enough to not be annoyed, and be good for gaming or development, but slow enough to avoid most issues. It uses KDE Plasma. Discover makes it easy to add Flathub and avoid Snaps.






  • Die4Ever@retrolemmy.comtomemes@lemmy.world•Almost at 200k!
    link
    fedilink
    English
    arrow-up
    87
    ·
    edit-2
    1 month ago

    We are decentralized, according to FediDB, the Fediverse has 14.2 million accounts. Lemmy+Piefed+Mbin have 551k users. Obviously we could be better spread out, but the fact that there’s no instance at 50% share is already pretty nice.

    And if a big instance enshittified, it would be drastically easier for everyone to leave it compared to convincing people to leave Reddit or something. You just export/import your user settings and you get to keep the communities you’ve subscribed to and block, and the users you’ve blocked.







  • I wonder which way would give a better success rate.

    1. Write the patch for the latest LTS version and let the LLM forwardport it to master. (But don’t roll out the LTS update until after the rolling distros get the patch?)
    2. Or write the patch for master and let the LLM backport it to LTS.

    Especially if you’re having the LLM port to every active LTS version, maybe option 1 would work since it’s more like a midpoint? Kind of a more neutral zone, fewer commits to conflict in any direction. And that could theoretically prioritize the most recent LTS version as being the most reliable, which is probably what most critical deployments actually need.