132

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.

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

all 33 comments
sorted by: hot top new old
[-] sevon@lemmy.kde.social 28 points 1 year ago

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.

[-] nutomic@lemmy.ml 22 points 1 year ago

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

[-] sevon@lemmy.kde.social 9 points 1 year ago
[-] fmstrat@lemmy.nowsci.com 8 points 1 year ago

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

[-] sevon@lemmy.kde.social 9 points 1 year ago

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

[-] dessalines@lemmy.ml 6 points 1 year ago

I elaborated on this here

[-] whimsy@lemmy.zip 20 points 1 year ago

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?

[-] dessalines@lemmy.ml 22 points 1 year ago

Yep, or the things you've downvoted.

[-] whimsy@lemmy.zip 9 points 1 year ago

Amazing, looking forward to this! :D

[-] unexposedhazard@discuss.tchncs.de 17 points 1 year ago

Lots of really useful sounding stuff in there. Good work :)

[-] geneva_convenience@lemmy.ml 14 points 1 year ago

Could you elaborate what multi communities is, maybe in the post?

[-] dessalines@lemmy.ml 9 points 1 year ago

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:

[-] geneva_convenience@lemmy.ml 6 points 1 year ago* (last edited 1 year ago)

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.

[-] avidamoeba@lemmy.ca 2 points 1 year ago

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

[-] nutomic@lemmy.ml 9 points 1 year ago

Its basically a collection of communities, so you can browse multiple related communities at the same time. Piefed already implements this under a different name:

https://piefed.social/feeds

https://piefed.social/f/cinema

[-] geneva_convenience@lemmy.ml 4 points 1 year ago

Ah got it thanks

[-] vermaterc@lemmy.ml 6 points 1 year ago

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

[-] OccasionallyFeralya@lemmy.ml 4 points 1 year ago

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

[-] nutomic@lemmy.ml 7 points 1 year ago
[-] OccasionallyFeralya@lemmy.ml 3 points 1 year ago

Excellent love to hear it thanks guys!!!!

[-] Die4Ever@retrolemmy.com 13 points 1 year ago

exciting stuff, can't wait to get v1.0

[-] sabreW4K3@lazysoci.al 5 points 1 year ago
[-] VoxAliorum@lemmy.ml 13 points 1 year ago

That's what I call a big update!

[-] OsrsNeedsF2P@lemmy.ml 10 points 1 year ago

Hail the victorious devs!

[-] jaybone@lemmy.zip 6 points 1 year ago

Will this break clients like voyager?

[-] dessalines@lemmy.ml 15 points 1 year ago

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

[-] Kirk@startrek.website 4 points 1 year ago* (last edited 1 year ago)

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.

[-] dessalines@lemmy.ml 6 points 1 year ago

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

[-] Kirk@startrek.website 5 points 1 year ago

twas a joke, but that's a nice feature!

[-] dessalines@lemmy.ml 7 points 1 year ago* (last edited 1 year ago)

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.

[-] avidamoeba@lemmy.ca 3 points 1 year ago* (last edited 1 year ago)

Good stuff. Donated.

[-] lazycouchpotato@lemmy.world 2 points 1 year ago

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

this post was submitted on 01 Jul 2025
132 points (98.5% liked)

Announcements

26248 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 7 years ago
MODERATORS