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)
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.
Federating instance bans is a separate thing for far later on, but I recently added a “hack” that bans you from communities local to the instance you were banned on, and those should federate.
I just thought of an edge-case, what happens when someone gets instance-banned and then tries to interact with a commenter from that instance? Currently it will post the comment but nobody from that instance will see it. If this isn’t intentional, what would happen?
If they are banned from that community, they won’t be able to post.
This is a case where neither party is banned from the instance the post is on, however one user is instance banned from the instance that the other user is currently on. The way it currently works is that the banned user can see and interact with the other user and the rest of the federation can see this interaction, however the other user is completely oblivious to the existence of the banned user.
I am actually working on fixing this right now, so that in the future, users would be prevented from commenting in this situation