This story is horrific.

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 (currently on 0.19.4-rc.2), in the upcoming weeks, but still have a few more issues to address, and testing that needs to be done. If you'd like to help us test betas to help find issues, you can go to https://voyager.lemmy.ml or ds9.lemmy.ml for the newest RC, 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.

We've also added a few github milestones for our upcoming releases, to keep track of what we'll be working on, but you can also look at our pending pull requests.

@flamingo-cant-draw increased the character limit for alt-text fields.

@dullbananas just graduated from high school and will have a lot more time to work on Lemmy for a few months. Has been working on a custom database migration runner.

@matc-pub cleaned up and added a lot of asynchronous loading for various components in lemmy-ui.

@sleepless and matc-pub fixed an issue with leap years in lemmy-ui.

@sleepless fixed a bug with admin settings in lemmy-ui, fixed an issue with language not allowed, fixed an issue with video thumbnails, and upgraded to a non-deprecated QR library. Has also been adding a lot of the backbone for lemmy-ui-leptos.

@nutomic fixed some issues with importing partial settings backups, 2, made NodeInfo standard compliant, and upgraded to 2.1, added some test cases for user reports, removed unused federation code, added a stricter rate limit for logins, made password reset tokens non-reusable, marked DB fields as sensitive so they don't show up in logs, allowed passing of command-line params via environment vars. Also prevented removal of comments which are already deleted, and configured a max comment width in clippy.

@dessalines fixed some issues with image proxying, 2, made some fixes to our woodpecker CI jobs. Replies and mentions are now correctly hidden for blocked users.

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.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency (scroll to bottom of page)

archive.is link

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 more issues to address, and testing that needs to be done. If you'd like to help us test betas to help find issues, you can go to https://voyager.lemmy.ml 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.

We've also added a few github milestones for our upcoming releases, to keep track of what we'll be working on, but you can also look at our pending pull requests.

@ticoombs converted our docker upgrade script to the newer version, and has been readying lemmy-ansible for the next release.

@dullbananas optimized the actor language inserts, and fixed an issue with triggers locking the tables.

@sleepless Removed an unecessary login step from our crates.io publish, fixed a deprecated reliance on encoding.rs, fixed an issue with onBlur in lemmy-ui, and added a dependency on lemmy-rs-client for lemmy-ui-leptos, which included a lot of structural changes. Fixed an issue with broken direct messages in lemmy-ui, and a bug with newly-created communities.

@nutomic added setting the show_nsfw site setting based on content_warning, fixed an issue with Discourse federation, added NodeBB federation, fixed an issue with crashes for missing domains, added wordpress federation, fixed an issue with early exits when only running scheduled tasks, added a timeout on incoming activities, and made instance.preferred_username optional.

@dessalines fixed an issue with broken community outboxes, fixed an issue with search returning deleted / removed posts. The liked_only for GetPosts now doesn't return your own items, making this more usable to show a history of your likes.

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.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency (scroll to bottom of page)

"Order must prevail"

Hopefully shouldn't take more than an hour.

Time converter link.

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 https://voyager.lemmy.ml 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.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency (scroll to bottom of page)

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.

@snan fixed parent comment linking when not showing context in lemmy-ui in #2417.

@matc-pub fixed deselecting community/creator filter for search form in #2416.

@aeharding fixed incorrectly escaped user data export JSON in lemmy-ui.

@kroese added a fix for the pictrs image mode setting.

@richardj added a comment margin to lemmy-ui.

@tracyspace fixed unecessarily duped notifications.

@jim-taylor-business added ignoring lemmy config based on an ENV var. Has also been working on lemmy-ui-leptos.

@dullbananas optimized set featured posts, added more test coverage.

@SleeplessOne1917 added url blocking and post hiding to lemmy-ui and has, more generally, been preparing lemmy-ui to support the 0.19.4 features added to the backend. He has also been working on lemmy-ui-leptos.

@dessalines added alt text and custom thumbnail to lemmy-ui. Fixed private message sort order. Fixed the docker release.. Partially fixed custom thumbnail updates.. Fixed a bug where comment notifs wouldn't be sent to blocked instances.. Changed defaults on user vote display mode to upvotes + downvotes. Converted many Result<..., LemmyError> into LemmyResult. #4614.

@nutomic added metadata and thumbnail fetching in the background. Added caching of LocalSite::read. Added ignoring of old federated post edits.. Changed exponential backoff for federation sends.. Added a test for fetching from a local url. Fixed a wrongly merged breaking change related to public_key, and reduced api cache duration.

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.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency (scroll to bottom of page)