Spyke
announcements·AnnouncementsbyDessalines

Lemmy Development Update June 2025

This was a busy month, with ~80 pull requests merged, as we're trying to get all the breaking changes we can added before the 1.0 release.

The release is still several months away, as even after finishing up the rest of the 1.0 milestone issues, we still have to add this new functionality to Lemmy-UI and Jerboa, and do extensive testing.

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

  • Added multi-communities (One of the most requested features).
  • Added a new rate limiting library.
  • Refactored the API structs and library for better usage in Rust projects.
  • Improved the migration diff checker.
  • Using an external library for checking invisible characters.
  • Votes are now removed when banning + removing data.
  • Added a GDPR style data export.
  • Storing upvote / downvote totals you gave to each user, and a setting to display that history next to their name.
  • Added ability to make a note for a user.
  • Added an RSS feed for modlogs.
  • Added an API action to get liked / disliked content.

::: spoiler Full list of changes by user

Lemmy:

Lemmy-ui:

:::

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

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

View original on lemmy.ml
133
Comments34
svn
lemmy.kde.social

I've been keeping an eye on the multicommunity issue and that getting merged was a nice notification.

Thinking of further use cases, maybe a multicommunity could be used as an "Instance curated" option in addition to All/Local/etc. Because frontpages of topic-specific and regional instances seem to all be dominated by us politics.

28
Nutomicreply
lemmy.ml

This is already implemented, admins can specify a "suggested" multi-community which will be shown next to Subscribed/Local/All just like you say.

22
fmstratreply
lemmy.nowsci.com

What exactly is multi-community? It's not defined above and the PR has no description.

8
svnreply
lemmy.kde.social

A multi-community groups outputs of multiple communities into one entity that you can subscribe to and browse.

9
whimsy
lemmy.zip

Added an API action to get liked / disliked content.

Oooh! Does this mean clients/apps can then show me all the stuff that I've upvoted?

20
Dessalinesreply
lemmy.ml

Here is the issue and the pull request.

Essentially multi-communities are a federated item very similar to communities, that federated users can subscribe to. They have an id, a creator, name, description, and a list of communities. If you subscribe to it, your instance will pick up any changes to it. You can then get a list of posts filtered by that multi-community.

Here are the new endpoints:

9
geneva_conveniencereply
lemmy.ml

Thanks.

Are "shared communities" between instances in the pipeline or would that cause too much headache?

For example having a shared WorldNews community between lemmy.ml and lemmy.zip, maybe with a possibility to seperate them if mods have beef in the future. Or seperate moderator teams.

Currently there are many duplicate communities between instances. Now this is important for defederation, but causes a lot of fragmentation. Maybe having admins opt in to share a community with other instances could help this while possibly keeping control over moderation of what their own instance can see.

6
Blaze (he/him)reply
lemmy.dbzer0.com

Feeds don't really completely solve fragmentation, as comments are still attached to a single community, and you don't see them in a single view.

To completely solve fragmentation, you need a consolidated view of comments as well

https://piefed.zip/post/100161

All comments from 5 crossposts in a single view

4
Avid Amoebareply
lemmy.ca

This sounds somewhat similar to what circles used to be in Google+. A collection of users that can be created and followed.

2
vermatercreply
lemmy.ml

I support this request, even issue on GitHub does not contain any (even short) description

6
OccasionallyFeralyareply
lemmy.ml

I’m hoping it’ll be like multireddits (groups of subreddits that could be shared) because I’ve been wishing for that for a while

4
Dessalinesreply
lemmy.ml

The 1.0 release is many months away yet, and we'll give ample time to app devs to update.

15
James R Kirk
startrek.website

Storing upvote / downvote totals you gave to each user, and a setting to display that history next to their name.

Where is the instance that autobans any account that users have downvoted X times? I want to join it.

4
Dessalinesreply
lemmy.ml

This has nothing to do with that. But we have expanded the site settings to reject federated votes (or downvotes only)

5
Dessalinesreply
lemmy.ml

Ah my bad.

Ya we have to deal with so many vote bots, dead account voters, and vote spying tools now from some instances, that it's genuinely going to be one of the biggest challenges on the fediverse in the future.

If some special interests set up shop on the fediverse, and upvote their content with a lot of fake accounts, or downvote others views they don't want popularized, without a way to combat it while still preserving overall vote privacy, we'll be in bad shape.

7
LCP
lemmy.world

Whoa lots of good stuff in this update. Thank you for all the work!

2

You reached the end