2025-12-24 - Lemmy Release v0.19.15 and Testing for 1.0
join-lemmy.org

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. Thanks to @flamingos-cant for contributing to resolve this.

Changes

We messed up the previous release and did not include the full list of changes. In fact there were a handful of other bug fixes, and notably a maximum page limit of 10 to prevent a DDoS attack. Some users were also hitting this limit, so with this version the limit is increased to 100. We apologize for these mistakes.

Here is the full changelog since 0.19.13:

  • Don’t allow accessing page numbers greater than 10 by @dessalines #6017
  • Update deps based on cargo audit by @Nutomic in #6258
  • Increase page limit to 100 by @Nutomic in #6252
  • Ban federation for deleted users by @Nutomic in #6207
  • Federate mod actions on deleted users by @Nutomic in #6199
  • Allow admins to view deleted user profiles by @Nutomic in #6194
  • Adding creator and community indexes for post_aggregates. by @dessalines in #6025
  • Ignore apub person banners which cannot be parsed by @Nutomic in #6015u

Now for the good news, the development version of Lemmy 1.0 is available for testing on voyager.lemmy.ml with lots of new features. Registration is open, you’re welcome to create an account. Feel free to post spam and try everything out. Here is only a short overview:

  • Multi-communities: Combine different communities together into a custom feed.
  • Post scheduling: Specify when your post should be published.
  • Keyword filter: Automatically hide posts about certain topics.
  • Private communities: Only followers can view the content, and need to be approved manually by mods. Other community visibilities are also available (unlisted, local only).
  • New notification system: Including notifications for mod actions, and subscribing to communities and posts to be notified about new comments.
  • OAuth: Login to Lemmy with existing account from another website. Use this link to signup with your Github account (the UI still needs to be improved).
  • Post Tags: Categorize posts within a community (UI part not implemented yet).
  • User vote totals: You can see the total number of upvotes and downvotes given to each user.
  • User notes: You can keep notes on other users.
  • Combined Feeds: View your saved, liked posts and comments together in a single list.
  • Comment Locking: Mods can now lock comments recursively.
  • GDPR style data exporting: You can now export your full posting history as a JSON file.
  • Plugins: Can be written in JS, Python, Rust, and any other language that targets Webassembly. The test server has a plugin for automatic language tagging of posts.
  • Cursor pagination: Don’t lose your place in the feed when switching pages.
  • API v3 compat: Lemmy 1.0 can be used by existing apps with no changes (but most new features are only available via the new API v4).
  • More: Countless smaller features, bug fixes and improvements, too much to list here.

All the above mentioned features are already implemented and fully working, but may need some polishing. If you encounter any problems, please open an issue (backend, frontend). voyager.lemmy.ml is automatically updated to the latest development version every night, so that changes can immediately be tested.

Keep in mind that Lemmy 1.0 is still in alpha state. There may be breaking changes and critical bugs, so do not attempt to upgrade your own instances yet. We intend to publish the first beta version in January, along with API docs and upgrade instructions for test servers.

We hope that you are as excited about these new features as we are. With all this said, happy testing and Merry Christmas!

Upgrade instructions

There are no breaking changes with this release.

Follow the upgrade instructions for ansible or docker.

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

Thanks to everyone

We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, donating and reporting bugs. We’re glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over five years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

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. A recurring donation is the best way to ensure that open-source software like Lemmy can stay independent and alive, and helps us grow our little developer co-op to support more full-time developers.

  • vermaterc@lemmy.mlEnglish
    8·
    1 day ago

    Is there a reason why you gathered so many features in a single update? It seems to be challenging to test all these features at once, why not just publish them step by step in smaller updates? For instance, Mastodon have even split quote posts into two separate versions (first backend, then frontend) to make this process smoother.

    • Dessalines@lemmy.mlMEnglish
      10·
      1 day ago

      It mainly has to do with trying to keep breaking changes releases as infrequent as possible. These make things difficult for app developers trying to keep up.

      • wiki_me@lemmy.mlEnglish
        1·
        1 day ago

        Not sure that is the correct approach. break frequently break often seems better (that’s what PHP and java seem to do as far as i can tell, unlike python 3 which caused a lot of drama).

        notify a API is deprecated. give some time for users to update to the new API (1 year?) and then remove it.

        Of course after version 1.0 there might be less breakage so it won’t be a be problem.

        • mondoman712@lemmy.mlEnglish
          3·
          1 day ago

          Frequent breaking changes in a programming language is crazy, I’m very happy I don’t have to work with one that does that.

        • Dessalines@lemmy.mlMEnglish
          1·
          1 day ago

          Breaking frequently is fine for libraries where all versions are available and usable.

          It’s not good for API’s, where every single change isn’t backwards compatible and available. We have lemmy apps that still aren’t supporting API changes added over a year ago. We even had one such case last week.

    • Nutomic@lemmy.mlOPMEnglish
      10·
      1 day ago

      The difference is that Mastodon already reached version 1.0 much earlier, but Lemmy did not. In the current development branch we made some large rewrites breaking changes early on. Over time more and more features were added, and we cleared much of the backlog of existing issues. Then instead of calling the new version 0.20 we decided to make it 1.0, which indicates that it will be stable for a very long time. After 1.0 is released we will definitely continue with smaller releases to get changes out faster, and there will be no need for breaking changes.

  • lazynooblet@lazysoci.alEnglish
    4·
    1 day ago
    • User vote totals: You can see the total number of upvotes and downvotes given to each user.

    Is this going to be like Reddit karma? I hope not.

    • Nutomic@lemmy.mlOPMEnglish
      5·
      1 day ago

      Technically it would be a breaking change to remove it, so in that sense it could only be removed in a version 2.0. But maybe after some time we could add a setting for admins to disable api v3, and later have it disabled by default.