Work on the backend changes for 1.0 is mostly finished now. What’s missing is optimizing the migrations as they currently take about 9 hours for lemmy.ml. Now we are starting to work on updating lemmy-ui for the API changes and new features.

In the last days we did a big cleanup of the lemmy-ui issue tracker, closing 450 mostly outdated issues. Many of these were over a year old describing problems that have long been fixed. From 570 issues only 120 remain. Most of these are very minor, changing a single UI element here or there. It should be possible to implement 90% of them within a month or two.

Here are some of the major changes made over the past month:

• Add ability to block all users of an instance (#5784)
• Notifications rewrite, users can be notified about new posts or comments (#5604)
• Post tags (#5869)
• Site and user setting for items per page (#5887)
• Don’t show edit mark if comment was edited in less than 5 minutes (#3197)
• Speedup of 1.0 migrations (#5873)

Full list of changes by user

jfaustino

• Change textarea placeholder for locked posts
• Don’t show edit mark if comment was edited in less than 5 minutes

SleeplessOne1917

• Re-export UpdateCommunityNotifications
• Re-export some types from lemmy-api-common
• Add missing TS derives that were causing errors when generating Typescript bindings
• Add creator_banned to VoteView

dessalines

• Adding a local_site and local_user setting for default fetch limit
• Add ability to block all users of an instance.
• Fast history no background
• Fixing username-instance duplicate migration.
• Don’t export inbox combined view internal.
• [Main] remove all caches

dullbananas

• Add update_schema_file.sh
• Refactor pagination cursor parsing
• Speed up init in start_dev_db.sh using no-sync option
• Fix comment depth test
• Prevent stack overflow when fetching nested comment
• Require indexes for all foreign keys
• Use a new separate crate for uplete
• Allow running all migrations with minimal dependencies

Nutomic

• Use case insensitive sort for followed communities (fixes #5903)
• Merge different AlreadyExists errors (fixes #5897)
• Properly parse icons federated from Peertube (fixes #5894)
• Rename modlog items
• Refactor email
• Only use MiMalloc on x86_64 target arch (fixes #5695)
• Purge user images in background task (fixes #4642)
• Finish adding post tags
• Allow remote groups to follow Lemmy communities (fixes #5354)
• Fix foreign key indexes migration
• Remove unused items
• Notifications rewrite and post following (fixes #3069)
• Add unique constraint for person(name, instance) (fixes #5045)
• Extism release version
• Delete report views, add missing report fields
• Update extism
• Federation refactoring
• Fix comment depth off by one
• Move local site user count updates to scheduled task
• Revert " Add post_actions.disable_notifications (fixes #3042) (#5826)"
• Add missing comment depth check
• Dont call resolveObject for search
• Change icon for save action (fixes #1564)
• Use anchor for comment permalinks (fixes #2908)
• Only cache success responses (fixes #3129)
• Redirect away from /setup page if already created (fixes #897)
• Update regex for validating matrix id (fixes #1726)
• Fix host splitting for IPv6 (fixes #2374)
• Increase bio max length to 1000 chars (fixes #2657)
• Change link from element.io to matrix.org (fixes #2293)
• Search changes
• Change display format for community name in search

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

• Backend
• Frontend

---

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