Skip Navigation

Lemmy v0.18.3 Release

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

This version brings major optimizations to the database queries, which significantly reduces CPU usage. There is also a change to the way federation activities are stored, which reduces database size by around 80%. Special thanks to @phiresky for their work on DB optimizations.

The federation code now includes a check for dead instances which is used when sending activities. This helps to reduce the amount of outgoing POST requests, and also reduce server load.

In terms of security, Lemmy now performs HTML sanitization on all messages which are submitted through the API or received via federation. Together with the tightened content-security-policy from 0.18.2, cross-site scripting attacks are now much more difficult.

Other than that, there are numerous bug fixes and minor enhancements.

Support development

@dessalines and @nutomic are working full-time on Lemmy to integrate community contributions, fix bugs, optimize performance and much more. This work is funded exclusively through donations.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. No one likes recurring donations, but they’ve proven to be the only way that open-source software like Lemmy can stay independent and alive.

Upgrade instructions

Follow the upgrade instructions for ansible or docker. There are no config or API changes with this release.

This upgrade takes ~5 minutes for the database migrations to complete.

You may need to run sudo chown 1000:1000 lemmy.hjson if you have any permissions errors.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

76 comments
  • 🙏 Thank you Devs.

    Kind People, please donate .

    • As a donor I had to spend some amount of time finding where to donate, that could be more explicit

  • well my Lemmy backups did exceed 10MB, but the 0.18.3 database optimizations brought me under 10MB again lol

     undefined
        
    11M Jul 28 22:35 bak-lemmy-2023-07-28_22.35.52.zip
    8.8M Jul 28 22:39 bak-lemmy-2023-07-28_22.38.59.zip
    
      

    (hosting an instance with communities but no users doesn't need much hardware at all btw)

  • Neat!

    If you can, please keep supporting the devs with some resources.

  • docker compose down && docker compose pull && docker compose up -d update was flawless. nice!

    • You can pull new images while the old ones continue running happily. That docker-compose down command is completely unnecessary.

      @ohai
      @dessalines

      • that's fair, just force of habit, i guess. thanks for the heads up! :)

    • docker compose down &&

      Looks like the & parsing in code blocks is another bug in 0.18.3 like the post title one. I'll add your comment to the GitHub issue.

  • Heads-up that a new issue on GitHub reporting this problem upgrading from 0.18.2 to 0.18.3:

    thread 'main' panicked at 'Couldn't run DB Migrations: Failed to run 2023-07-08-101154_fix_soft_delete_aggregates with: syntax error at or near "trigger"', crates/db_schema/src/utils.rs:221:25 note: run with 'RUST_BACKTRACE=1' environment variable to display a backtrace

    https://github.com/LemmyNet/lemmy/issues/3756

    If you use "Lemmy from scratch" install,

    you may be on an older PostgreSQL that Ubuntu distro provides, not the same as the Docker install method.

    • Yes, I had to upgrade from Postgres 13 to get this working. I’m not sure if there’s a minimum Postgres version specified anywhere in the docs, I took a quick look but couldn’t find it.

      For anyone else running Debian like me, you can add the official Postgres repo and use the pg_upgrade script to migrate to the new version.

      • I’m not sure if there’s a minimum Postgres version specified anywhere in the docs, I took a quick look but couldn’t find it.

        I do not find it in the "From Scratch Install" documentation. I will work to revise those documents this weekend to warn people that 0.18.3 and later is incompatible. Thank you again for sharing.

  • Thank you for all of your hard work devs! I'm a supporter with monthly payments.

  • Ran into this issue with database migrations:

    Failed to run 2023-07-08-101154_fix_soft_delete_aggregates with: syntax error at or near "trigger"', crates/db_schema/src/utils.rs:221:25

    Will open an issue on GitHub.

    • That has to do with you running a custom install with an older postgres that lemmy doesn't support.

      • I'll update to a newer Postgres version and report back. It would be nice to know what the minimum supported version is, maybe that should be added to the documentation.

        EDIT: Upgrading to Postgres 15 resolved my issue, but not without some pain since the migration scripts had already tried to run on my Postgres 13 database. So after dumping the 13 database, I had to make some modifications after the fact to satisfy the migration scripts. It was a pretty janky process but I seem to be in a good place now.

        I would highly advise communicating to people that they should upgrade past Postgres 13 before trying to upgrade Lemmy to 0.18.3 or higher, or you're gonna have a bad time.

    • Thank you for sharing.

  • Thank you for the continuing work! Just one bug report: when I click to load lemmy (either .world or .ml) from my homepage of various links, I'm logged out. If I refresh the page though, I'm logged in!

  • Super straightforward upgrade via docker compose, thanks for all the hard work ❤️

  • I wish clicking this link would actually show the context instead of just refreshing the page.

    • yeah, the comment thread navigation is broken. the same is true for following “More Reply” links deeper into a thread

  • Sunday, lemmy.ml is performing better than I have seen it in 60 days. I did get errors on Saturday and significant lag. Not sure if activity is just today or what, but it's really been fast in routine browsing.

  • I am sorry to all the never-joined, never-stayed users of Lemmy in May, June, July 2023 "Tweet is X", "Reddit is $API" ------ because I could not draw enough attention and developers to Github Issue #2910 avoidance. I failed entirely in my social effort I tried to do for 60+ days. I really failed, brain damaged fuck-up I am. The worst failure in my life, and it's the end of the line.

76 comments