Here is our regular update that explains what we have been working on for the past two weeks. This should allow average users to keep up with development, without reading Github comments or knowing how to program.

We’re readying the release of Lemmy v0.19.4 in the upcoming weeks, but still have a few performance and front-end issues to address. If you’d like to help us test betas to help find issues, you can go to for the newest beta, or run your own test ones locally from our beta docker tags.

Please do not run unreleased builds in production, as these could cause issues which require some manual intervention to fix.

@snan fixed parent comment context links.

@matc-pub added mixins to simplify tippy popups and scroll-restoration, and conditional rendering to lemmy-ui. Also fixed deselecting community / creator filter for the search form. Added blur server-side-rendering by default for content-warning sites.

@sleepless added an adult consent popup to lemmy-ui, to account for the new site.content_warning field. Fixed an issue with fallback images. Prevent video embeds from displaying, for content-warning sites. Added a way to view historical mod actions done on a single post or comment.

@dullbananas moved the SQL triggers out of migrations, and into a reusable SQL file. This will really help with fixing / tweaking database triggers.

@dessalines fixed extra modlog entries when filtering by post or comment id, removed the scheme from URL blocks to prevent duplicate http / https regex matches, made all single-row database fetches return an Option so as to catch the missing case more explicitly, created a LocalImageView so that front ends can better handle listing media. Also added the image upload views for users and admins to lemmy-ui. Full federated usernames are also always shown now for non-local users. Added vote display mode preferences to lemmy-ui, with upvotes / downvotes as the default. Added a banned indicator to the view votes popup.

@nutomic and @kroese have been fixing / tweaking thumbnail generation.

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. Recurring donations are ideal because they allow for long-term planning. But also one-time donations of any amount help us.