dessalines

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.

The last two weeks had these changes merged:

@Sleepless added a field so that users can see if they've been banned from a community. Has been refactoring Lemmy's exports to make them more easily used by 3rd party libraries, such as their lemmy-client-rs , and lemmy-ui-leptos. Added an animated avatar setting for users.

Has also been making improvements to lemmy-ui such as fixing a scroll bug, and hiding WYSIWYG buttons on preview. Has also been working a lot on lemmy-ui-leptos.

@Nutomic created an rfc for private communities, fixed an issue with the database logging connection URLs on an error. Added an optional site content warning and post-listing-mode. Also did a lot of code reviews.

@dullbananas fixed an issue with Comment Report reads, added better query plans, and is working on many DB improvements.

@dessalines added an instance-level default post sort. Added a maintenance task to clean up old denied users from the DB.. Made sure that blocking an instance also hides private messages from their users, to prevent harassment. He also added the ability to specify custom thumbnails for posts. Fixed an issue with auto-resolving reports when removing a post or comment.

Has also been making a lot of additions to Jerboa, such as admin registration applications, report queues, comment distinguishing, banning users from their profile page, privacy policies, and muted / smaller federated names.

@sunaurus created an rfc for separate report inboxes for mods and admins.

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)

Lemmy currently uses distinct tables like post_like: (post_id, person_id, score) and post_saved. Unfortunately this causes performance issues when we have to join many of these tables to create views.

One suggestion in this PR, is to combine these into a single post_action table, with a lot of optional columns depending on the action. This solution scares me a little, because I'm afraid we might lose data integrity, and many of our constraints with so many optional columns.

Is there a better way of doing this in SQL?

Sry about the last borked release. I added a CI task to prevent it from happening again.