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

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 @dullbananas@lemmy.ca 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.

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.

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.

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

Communities that go against hegemonic capitalist/imperialist discourse will always get marginalised. Not being able to take down those communities easily like on Reddit is a huge win by itself for Lemmy. The software offers a valuable savehaven for e.g ex r/chapotraphouse, r/genzedong etc.

It seems some people simply need some target to hate on. Hopefully they will learn to accept different opinions when they arent being manipulated by for-profit social media anymore.

The anti-communist witch-hunters are extremely peeved that they can’t remove our communities like they can on reddit. Overall it doesn’t bother me because I don’t work for them, and they can always go back to reddit where their views are already dominant.

Anyone trying to make the world a better place, will always be hated and hunted by some people; it’s a fact of life, and the sooner we accept it, the better.

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.

You can export your settings, community follows etc and import them in another instance. Moving your existing posts and comments doesnt work well with federation.

!reddit@lemmy.world started to ban people based on upvotes

!buyeuropean@feddit.uk movement has motivated people to look around for European alternatives to Reddit

• 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).

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.

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