2nding @nutomic, that I’m really happy with the stack.

The one that seems really magical to me, is diesel. With it we get a compile-time-checked database, that’s tightly integrated to the rust objects / code.

Every single join, select, insert, etc is checked before lemmy is even run, and it eliminates a whole category of errors resulting from mismaps.

Its made adding columns, and changing our data structures so much less error-prone than when I lived in the java-world.

Whenever we find that we’d want to do things differently, we usually do a refactor ASAP so as not to keep rolling spaghetti code. We’ve had to do this many times for the federation and DB code, and even have 2 major refactors that also add features ongoing. But luckily we’ve been able to stay in the rust eco-system for that.

As for UI, leptos didn’t exist when I built lemmy-ui, so I went with a fast react-like alternative, inferno. Its showing its age now, so @sleepless1917 is working on lemmy-ui-leptos, which hopefully will supercede lemmy-ui.

The stack is great, I wouldnt want to change anything. Postgres is very mature and performant, with a high focus on correctness. It can sometimes be difficult to optimize queries, but there are wizards like @[email protected] who know how to do that. Anyway there is no better alternative that I know of. Rust is also great, just like Postgres it is very performant and has a focus on correctness. Unlike most programming languages it is almost impossible to get any runtime crashes, which is very valuable for a webservice.

The high performance means that less hardware is required to host a given number of users, compared to something like NodeJS or PHP. For example when kbin.social was popular, I remember it had to run on multiple beefy servers. Meanwhile lemmy.ml is still running on a single dedicated server, with much more active users. Or Mastodon having to handle incoming federation activities in background tasks which makes the code more complicated, while Lemmy can process them directly in the HTTP handler.

Nevertheless, scaling for more users always has its surprises. I remember very early in development, Lemmy wasnt able to handle more than a dozen requests per second. Turns out we only used a single database connection instead of a connection pool, so each db query was running after that last one was finished, which of course is very slow. It seems obvious in retrospect, but you never notice this problem until there are a dozen or so users active at the same time.

With the Reddit migration two years ago a lot of performance problems came up, as active users on Lemmy suddenly grew around 70 times. You can see some of that in the 0.18.x release announcements. One part of the solution was to add missing database indexes. Another was to remove websocket support, which was keeping a connection open for each user. That works fine with 100 users, but completely breaks down with 1000 or more.

After all there is nothing I would do different really. It would have been good to know about these scaling problems earlier, but thats impossible. In fact for my project Ibis (federated wiki) Im using the exact same architecture as Lemmy.

Being able to view “all” communities with the same name across all instances would be so nice.

This should be among the first priorities. It would really help kick things off. Not only niche communities, but bigger ones as well. They represent topics of interest. I think I’ve seen a thing like macro community in one of the clients?! Could that be it?

Having distinct communities is a feature, not a bug. If two cities set up their own lemmy instances, say lemmy.sao_luis.br, and lemmy.lagos.ng, they can each have a news community, without them overlapping.

Do a search for metroid, and subscribe to whichever ones you like.

Consolidation isn’t always a good thing, communities on different instances will have different styles and trends, and that’s a good thing. The benefit of federated social media is just as much in local instances as it is in federation, unique niches are going to have unique comments even if the post is the exact same.

this post provides a good overview of this issue and possible solution. https://popcar.bearblog.dev/lemmy-needs-to-fix-its-community-separation-problem/

What exactly is it you’re asking for, though? A change in user behaviour towards consolidation? Some new feature of the platform similar to multi-reddits? How exactly do you suggest that should work?

We have gone back and forth a few times on how deleted content is returned by the API, its very tricky to get right.

Yes this is a major benefit of an open network. Lemmy is a very large project already, so it takes a lot of effort to implement new features, because they have to meet high standards for quality and performance and also work together with all the existing features. A project like Piefed is much smaller and can implement new features more quickly. This allows for more experimentation, and successful features can later be added to Lemmy.

Also users who are not happy with Lemmy for any reason can switch to a different platform while still interacting with those on Lemmy. So if Piefed and Mbin grow that is also a benefit for Lemmy.

Yes I’m very excited about the growth of other fediverse software, and a lot of the cool new features they’re adding. Its a great eco-system where we can experiment, be creative, and learn from each other.

[email protected] started to ban people based on upvotes

[email protected] movement has motivated people to look around for European alternatives to Reddit

There’s some discussion of this here. It’s not something I care too much about, but anyone is free to add more detailed URLs to either lemmy-ui or other front-ends.

Its been years but no one has found it important enough to them to work on.

Another issue is that post links are instance-specific, since the post ID isn’t the same across instances.

ex: https://lemmy.ml/post/27659153 is https://lemmy.ca/post/41237641 on Lemmy.ca

There are external tools like https://lemmyverse.link/ and some browser addons to alleviate those issues, but it’d be nice if this could be addressed at the source if doable.

And I dream of a lemmy:\\ protocol handler one day.

Thx! Really appreciate it, and I’m glad someone thinks its worthwhile work we’re doing.

This is all a matter of dev resources. If we had maybe 6 full-time devs, we could handle things like backwards compatibility.

People forget that lemmy, like other open source hobby projects, don’t have the resources that large corporations do. People understandably get frustrated when there’s breaking changes, but they also need to not put enterprise-level expectations on a small number of people.

If someone wanted to work on that, of course we wouldn’t be opposed, but you should know how monumental a task that would be.

Its hard to say because these things always take longer than expected. Now we are finally getting to the point where all the breaking database and api changes are almost finished. After that it will take some months to update lemmy-ui for all the backend changes and new features, and the same for all other apps. Then a testing period to fix all the problems that come up. So maybe around autumn for the final release, although lemmy.ml and some other instances may upgrade some months before already.

With the rate ppl are adding issues (and we’re finding more), is sometimes feels like it keeps getting farther away than nearer, but we’ll get there in some months.

• Tags are work in progress
• Not exactly sure what you mean by “direct messages outside Lemmy”, but in version 1.0 they will be compatible with Mastodon and other platforms
• Its a known problem with Mastodon because it only renders Note objects properly, which are meant for short texts less than a paragraph. Lemmy uses Page which is meant for longer text. Some platforms like Wordpress (iirc) have an option to federate even long posts as Note so that it gets rendered fully in Mastodon, but that seems like a bad idea to me. In the end its up to Mastodon how to render different types of federated content on their frontend, so it needs to be fixed by them. Here is an entire discussion about this by developers of different Fediverse platforms (including a Mastodon dev).

I’d need more detail here. If registration emails aren’t being sent out correctly, we need to handle that.

Youre right, I also noticed some other problems while testing registrations:

• https://github.com/LemmyNet/lemmy/issues/5547
• https://github.com/LemmyNet/lemmy/issues/5548#issue-2949361836

For the email validation it could also make sense to send out another email saying “your email has been validated”, so its not only shown on the website.

This generally goes against security best practices as it can be used for attempted user enumeration. A better version would be “we’ll send you an email with your account status if this user exists” but obviously that results in a fair amount more complexity (and cost) to implement

Which tools specifically? I ask because this is a common complaint, but 99% of the time its something we already have, that most ppl are unaware of.

The key important one is being able to move posts to different communities.

Lemmy like all federated services, can’t rewrite history, but you can already cross-post (although it would be the mod cross-posting, as we don’t let mods alter user data except to remove it). It would just take someone adding that as an issue to lemmy-ui and working on it.