this post was submitted on 29 Mar 2024
5 points (100.0% liked)

Announcements

22742 readers
1 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
 

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.

top 8 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 5 months ago (1 children)

Awesome work!

Do you have an idea yet for the timeline of the 0.19.4 release?

[–] [email protected] 1 points 5 months ago (1 children)

Hopefully within the next few weeks. I'm forcing myself to stop making API changes / additions so sleepless and I can get caught up on adding them to lemmy-ui, then we should be ready.

[–] [email protected] 1 points 5 months ago (1 children)

but every API change brings it closer to perfection! cant stop, wont stop!

the API change high is such a rough addiction to break.

[–] [email protected] 1 points 5 months ago

Haha for sure. Kinda miss the days when we didn't have to worry about that as much.

[–] [email protected] 1 points 5 months ago

This is great, really happy that so many people are contributing these days and so much stuff is going on! Keep it up 💪

[–] [email protected] 1 points 5 months ago

The Listmedia endpoint and deleting user uploaded images on deletion of account were longtime requested features and I'm glad it's coming!

[–] [email protected] 0 points 5 months ago (1 children)

Worked on notifying users when they’re banned from a community.

Does this also include when you get banned from an instance? Obviously being instance-banned won't prevent you from commenting on their posts, it just won't get federated to that instance, but I would still like to know when it happens so it's not a surprise later on.

[–] [email protected] 1 points 5 months ago

Obviously being instance-banned won’t prevent you from commenting on their posts, it just won’t get federated to that instance

I am actually working on fixing this right now, so that in the future, users would be prevented from commenting in this situation