133
34

Lemmy Development Update June 2025

11mon 21d ago by lemmy.ml/u/dessalines in announcements@lemmy.ml

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:

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.

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

Nice.

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

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

I elaborated on this here

Added an RSS feed for modlogs.

You're so thoughtful omg

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?

Yep, or the things you've downvoted.

Amazing, looking forward to this! :D

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

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

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:

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.

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

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

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

Ah got it thanks

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

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

Yes exactly.

Excellent love to hear it thanks guys!!!!

That's what I call a big update!

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

Innit!

Hail the victorious devs!

Will this break clients like voyager?

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

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.

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

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

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.

Good stuff. Donated.

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