Last month we published the first beta for Lemmy 1.0. A lot of problems have already been reported and fixed. You can try the new features and visual updates in production by visiting the test server voyager.lemmy.ml. It is automatically updated to the latest development version every night. Please help by testing the new features and reporting any problems.

We also opened issues for the various open source Lemmy apps, to notify them of the upcoming API updates, and get ready for the 1.0 release. If there is any client that we missed, please let the developers know about the new version update.

You can follow our development progress with these milestone links:

• https://github.com/LemmyNet/lemmy/milestone/24
• https://github.com/LemmyNet/lemmy-ui/milestone/5

If you have any experience with web development or want to learn it, consider contributing to lemmy-ui. It is written in standard Typescript with Bootstrap. If you have experience with Kotlin or Android development, you can help contribute to Lemmy's open source Android app, Jerboa.

Here are all the changes from May:

Or see the full list of changes at the links below:

• Backend
• Frontend
• join-lemmy.org
• Jerboa

An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and Nutomic work full-time on these tasks and more. As there is no advertising or tracking, all of our work is funded through donations. Even so there is barely enough time in the day, and no time for a second job. The only available option are user donations.

To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached we can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

Donate

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.

Two years have already passed since we started working on some major new features for Lemmy. Back then we still planned to release them as version 0.20, but over time the scope expanded and it turned into version 1.0 instead. Besides many new features, we also took the opportunity to do a lot of cleanup work, so that 1.0 can remain stable for a very long time.

Below you can see the list of major new features. This is far from complete because there are simply too many changes to list. In general, any Github issue which was fixed over the last two years and didn't get into version 0.19, will be part of version 1.0.

For users:

• Redesigned UI: New card view, less clutter
• Post Tags: Categorize posts within a community.
• Multi-communities: Group 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 approved followers can view the content (plus other community visibilities).
• Notifications improvements including notifications for mod actions, and subscribing to community/post notifications.
• Combined Feeds: view your liked posts and comments together in a single list.
• User vote totals: There is a setting to view the vote totals you've given to any user.
• User notes: You can make and view notes for any user.
• GDPR style data exporting: You can now export your historical data as a JSON file.

Other changes:

• Comment Locking: Comments can now be locked, and it also locks any reply comments.
• Plugins: Can be written in JS, Python, Rust, and any other language that targets Webassembly. See the documentation for details.
• Cursor pagination: Don't lose your place in the feed when switching pages.
• OAuth: Login to Lemmy with existing account from another website.
• New API v4: Apps and frontends need to be updated to take advantage of new features. There is also a backwards compatible API v3 available.

The main work which still needs to be done before the official release is SQL optimizations. Some queries are still too slow, taking up to 300ms. And the database migrations from 0.19 to 1.0 take roughly 20 hours for lemmy.ml (smaller instances will be much faster). If you are an expert with PostgreSQL we need your help. Please have a look at the following issues which include all the relevant details:

• Slow SQL queries
• Reduce DB / table sizes

The other remaining task is testing and bug fixing. Now it is your turn as Lemmy users: on voyager.lemmy.ml try the new version and create an account. Signups are open, feel free to make posts, create communities and do everything else that can be done. Spamming test posts is absolutely encouraged. See how the new features work, and open an issue if you encounter any problem (backend, frontend).

If you run a test instance for Lemmy, we suggest that you upgrade it to 1.0.0-beta.0 by following the instructions. You can also try to run the 1.0 database migrations against a local copy of your production database. This will show how long the upgrade process will take, and help to reveal bugs in the migrations.

Be careful about upgrading production instances. In principle you can already use 1.0 in production. Be sure that you have working backups and that you can restore them. Expect to tolerate major bugs, or to revert back to the stable version for now. If you have any problems, join the admin chat on matrix or ask in /c/lemmy-support.

For developers of Lemmy apps and clients, now is the time to start updating your projects to use the new API v4. This will give you enough time to use the new API once Lemmy 1.0 is finally released. See the API v4 upgrade guide for instructions. If you develop any tools which integrate with Lemmy, have a look at the new plugin system.

Over the next months we will focus on testing and bug fixing. Afterwards, when when all major problems are fixed we will go to the release candidate phase. Then lemmy.ml will be upgraded to version 1.0.0-rc.0 to find remaining problems in production. When these are also resolved we will publish the final 1.0 release.

Thanks to everyone who contributed to the new release so far!

An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and Nutomic work full-time on these tasks and more. As there is no advertising or tracking, all of our work is funded through donations. Even so there is barely enough time in the day, and no time for a second job. The only available option are user donations.

To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached we can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

Donate

During the past month we finished the remaining, major tasks for 1.0 alpha. This means that we are ready to publish the first beta version in the next days! In particular we optimized database queries to have reasonable performance. While most are fairly efficient now, some are still too slow and would appreciate help from SQL experts.

@adrgs and @aisafe-bot found a few security vulnerabilities in the development version. Many thanks for doing this important work.

• Resend verification endpoint exposes registered email addresses
• Private Lemmy instances expose multi-community metadata without authentication
• Private community data exposed through community, saved, liked, and modlog API views

You can follow our development progress with these milestone links:

• https://github.com/LemmyNet/lemmy/milestone/24
• https://github.com/LemmyNet/lemmy-ui/milestone/5

To see the new features and visual updates in production, you can visit voyager.lemmy.ml which deploys new changes every night. Please help by testing the new features and reporting any problems.

If you have any experience with web development or want to learn it, consider contributing to lemmy-ui. It is written in standard Typescript with Bootstrap. If you have experience with Kotlin or Android development, you can help contribute to Lemmy's open source Android app, Jerboa.

Here are the major changes from April:

Or see the full list of changes at the links below:

• Backend
• Frontend
• join-lemmy.org
• Jerboa

An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and Nutomic work full-time on these tasks and more. As there is no advertising or tracking, all of our work is funded through donations. Even so there is barely enough time in the day, and no time for a second job. The only available option are user donations.

To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached we can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

Donate

Ibis is a federated encyclopedia with numerous features. If you want to start a wiki for a TV series, a videogame, or an open source project then Ibis is for you! You can register on an existing instance or install it on your own server. Then you can start editing on the topic of your choice, and connect to other Ibis instances for different topics. Federation ensures that articles get mirrored across many servers, and can be read even if the original instance goes down. Ibis is written in Rust and Webassembly, fully open source to make enshittification impossible.

After a long hiatus here is finally a new release of Ibis. The user interface received some polishing, and can now be translated to different languages. You can help with translations via Weblate.

If you already have an account and want to fill it with more articles, use the new Wikipedia import! You can import individual articles by Url on the "Create Post" page. Or write a bulk import script with curl https://ibis.example/api/v1/article/import -d 'url=https://en.wikipedia.org/wiki/Pet' -H 'Cookie: auth=my_auth_cookie'.

Full changelog

If you are interested what a federated wiki can do, join and give it a try. You can register on ibis.wiki, open.ibis.wiki or other instances. You can also install Ibis on your own server. It is very lightweight and can easily run on an existing server alongside other software. This release includes an additional installation method using Docker. To discuss the project, report problems or get support use the following links:

Lemmy | Matrix | Github

Ibis is a federated encyclopedia with numerous features. If you want to start a wiki for a TV series, a videogame, or an open source project then Ibis is for you! You can register on an existing instance or install it on your own server. Then you can start editing on the topic of your choice, and connect to other Ibis instances for different topics. Federation ensures that articles get mirrored across many servers, and can be read even if the original instance goes down. Ibis is written in Rust and Webassembly, fully open source to make enshittification impossible.

After a long hiatus here is finally a new release of Ibis. The user interface received some polishing, and can now be translated to different languages. You can help with translations via Weblate.

If you already have an account and want to fill it with more articles, use the new Wikipedia import! You can import individual articles by Url on the "Create Post" page. Or write a bulk import script with curl https://ibis.example/api/v1/article/import -d 'url=https://en.wikipedia.org/wiki/Pet' -H 'Cookie: auth=my_auth_cookie'.

Full changelog

If you are interested what a federated wiki can do, join and give it a try. You can register on ibis.wiki, open.ibis.wiki or other instances. You can also install Ibis on your own server. It is very lightweight and can easily run on an existing server alongside other software. This release includes an additional installation method using Docker. To discuss the project, report problems or get support use the following links:

Lemmy | Matrix | Github

This last month we worked on optimizing database queries for Lemmy 1.0. This was one of the major remaining tasks. We were also busy improving lemmy-ui with new lints and type checks to make it more reliable. Now that this is completed, you can expect the first 1.0-beta version to be published very soon!

On the stable branch we published two smaller bugfix releases which include security fixes. If you didn't upgrade your instance yet, now is the time.

You can follow our development progress with these milestone links:

• https://github.com/LemmyNet/lemmy/milestone/24
• https://github.com/LemmyNet/lemmy-ui/milestone/5

If you'd like to see the new features and visual updates in production, you can visit voyager.lemmy.ml which deploys updates every night. Please help by testing the new features and reporting any problems.

If you have any experience with web development or want to learn it, consider contributing to lemmy-ui. It is written in standard Typescript with Bootstrap. If you have experience with Kotlin or Android development, you can help contribute to Lemmy's open source Android app, Jerboa.

Thank you to everyone who has helped out with finding bugs, testing, development, spreading the word about lemmy, and building communities. Your help has brought lemmy from an idea to one of the most vital pieces of software in the fediverse.

Here are the major changes from March:

Or see the full list of changes at the links below:

• Backend
• Frontend
• join-lemmy.org
• Jerboa

An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and Nutomic work full-time on these tasks and more. As there is no advertising or tracking, all of our work is funded through donations. Even so there is barely enough time in the day, and no time for a second job. The only available option are user donations.

To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached we can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

Donate

This release fixes federation with Lemmy.

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

This release mitigates a potential security issue with the image endpoint. In short, an attacker can inject query parameters and make proxied requests to arbitrary URLs. See the security advisory for details.

Also there are fixes for the database connection pool. The pool size is now at least two, as a lower size can result in deadlocks. Additionally there are now connection timeouts added. If your server logs show pool timeout errors, you should increase database.pool_size in the Lemmy config.

• Fix for image proxy filetypes by @dessalines in #6357
• Enable DB connection timeout by @Nutomic in #6355
• Use min database pool size of 2. by @dessalines in #6345

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, and helping find and fix 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.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency

If you want to develop a plugin and have any questions, feel free to comment here or in the dev chat.

join-lemmy.org regularly crawls all active Lemmy instances to keep the instance list updated. Additionally it also collects data from all Lemmy communities. The data is now publicly available in the following git repository:

https://github.com/LemmyNet/lemmy-statistics

Check the readme for details about the available data. Interestingly the numbers are quite different from other websites:

Here are some ideas what to do with the data:

• Recreate the Lemmymap, graphically showing the connections or defederations between instances.
• Render graphs, which could be added directly to join-lemmy.org (#532).
• Investigate what is causing the different numbers shown above.
• Run various types of analysis, like this one done by @malsadev.
• Build a tool to help users discover interesting and relevant communities.