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.

@sunaurus fixed our rate-limiter and is working on federation of local site bans.

@SleeplessOne1917 added banned_from_community to post and comment views. Added a matrix account link to the create private message form. User emails are now shown for registration applications, to stop spam emails. Worked on notifying users when they're banned from a community.

@matc-pub reworked and cleaned up lemmy-ui's query parsing.

@rodrigo-fm added a loading skeleton for posts / comments to lemmy-ui.

@phiresky and @dullbananas have been doing a lot of work reviewing PRs, and finishing up current ones.

@nutomic worked on generating post thumbnail/metadata in background, deleting old avatar/banner/icon's when uploading a new one. On registration, automatically set content languages from accept-language headers. Migrated apub block activity to standard endTime property and deprecate expires. Added delete user field removeData to apub assets. Fixed handling of apub downvotes.

@dessalines has worked on fixing some issues with Woodpecker, our CI, deleting a person's local images on account deletion., adding a listMedia endpoint for users and admins to view local image uploads. Also added a creator_banned_from_community to vote views, and fixed an issue with comment replies being wrongly marked as read.. Also made jerboa use a new preference library.

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.

We failed to publish the update last Friday as scheduled, so this update contains more changes than usual. We also added @dullbananas as maintainer for the Lemmy backend repo.

@matc-pub reduced the amount of data that needs to be fetched by the browser for rendering lemmy-ui, by loading only translations which are actually used.

@flamingo-cant-draw added a URL Blocklist, to prevent link spamming.

@SleeplessOne exposed Lemmy errors in the Rust API. In lemmy-ui he added a badge for number of local subscribers to a community and added a UI to see and edit community visibility. In the leptos UI, he made the UI use the lemmy-client crate for API requests.

@Nutomic fixed synchronization of featured posts. He added a 'delete content' checkbox for account deletion which was missing from previous releases. He also fixed various bugs related to password reset, signed fetch from Mastodon, search listing type, password reset and 2FA. He updated the federation library with security improvements. Added dont require leading ! or @ for webfinger resolve. Fixed video thumbnail generation.. Added including an apub hashtag with a post.

@Dessalines added a new API endpoint for users to hide posts. He made various moderation improvements, such as removing content from local communities when a remote user is banned or purged, viewing mod action history and report history for specific posts and comments. Additionally he added an alt_text field for posts, and a new user setting for vote display mode. Also added extra fields to PostReport and CommentReport views. Has also, along with @MV-GH, been making many improvements to Jerboa.

In personal news, @nutomic's daugher will be born next month. Afterwards he will take a break from Lemmy to take care of her for some months.

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.

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.