Looks neat! In fact I never heard much about Quake having singleplayer.

Have a look here, they also did some free audits for Lemmy:

• https://nlnet.nl/NGI0/services/#security
• https://www.radicallyopensecurity.com/

Not sure what you mean by “advanced caching”. There is some basic caching for data which rarely or never changes, for example most things in /api/v3/site. But other data like post listings change a lot, so caching is not an option and instead its a matter of optimizing the sql queries (using the right indexes, reducing the number of joins, making benchmarks and looking at query plans).

Here is an issue on this topic: https://github.com/LemmyNet/lemmy/issues/5555

That is correct, and this happens to be another one of the issues which is already fixed for version 1.0. Basically for each ban we also store which instance it’s associated with, which is shown in the modlog and the new mod action notifications. If you’re interested I can link you the PR.

Notifications for mod actions are already implemented for Lemmy 1.0. Mod mail would take a lot of work to implement, and we have plenty of other things to work on. Being able to view your own removed posts makes sense, will note that down.

What’s wrong with instance bans on Lemmy?

Python is an interpreted language, which is fundamentally always slower than a compiled language like Rust. However the main performance bottleneck are actually sql queries, and I believe we make a lot more effort to optimize them compared to Piefed.

Afaik lemmy.world doesn’t have image proxying enabled, so your browser/app has to connect to other servers to load images. If you use an instance which has this enabled it’s probably faster.

At some point in the future I will also have time to implement community migration for Lemmy. In theory it’s not so complicated, but there are lots of other things to do.

We are close to releasing a first beta version for 1.0. Admins who are adventurous can already upgrade their instance to that. The final release will take longer though, with bug fixing, performance optimisations and general polishing.

Lemmy 1.0 is backwards compatible with the current API v3. You can try it here. This uses the API from our test instance at voyager.lemmy.ml which runs the latest alpha version.

It seems that the post is getting refetched over federation and marked as deleted again. So you will have to run that SQL query regularly (eg in a cronjob) to restore the post every time. Its also worth setting locked = true to prevent users from commenting.

By the way I opened an issue to fix this properly: https://github.com/LemmyNet/lemmy/issues/6044

You can run the SQL command update post where id = 53505862 set deleted = false. That way it will be visible on db0 again, although not on other instances.

This feature is already implemented for Lemmy and will be in version 1.0

Its the first time Im hearing about this problem. If no one reports it on the issue tracker we cant fix it.

Edit: You can block a community that banned you under /settings, but not directly on the community page. Issue link

Thats not possible because instances are completely independent from each other, and one one can force admins to do anything (except their local governments and hosting providers). So different instances will always have different standards, and at most other instances can defederate if they disagree.

The way I see it funding for Lemmy development is entirely separate from lemmy.ml moderation. That is something for the local admins and users to decide, and they are happy with the status quo.

Its definitely a problem. One way to fix it would be for admins to be more strict with the moderators of local communities, and replace them if they go too far. But it seems most admins are quite hands off and prefer to let things run their course.

Of the two us us Dessalines is the one who needs funding the least, he was fine with the previous donation amount of 1000 Euros per dev. Im the one who created the call for donations because I have two small children to feed. So whether you donate or not isnt going to change Dessalines’ mind at all.

Sorry I talked with many dozens of people about this topic and dont remember what you specifically said. In my head it all got mixed together into a single conversation.

The way I see it, funding for Lemmy development is an entirely separate issue from the moderation of lemmy.ml. The moderation for an instance should only be decided by its local admins and users. Imagine lemmy.ml users going around and saying that lemmy.zip must change this or that thing. You would tell them to mind their own business, and with good reason.

I found your reply now, here it is. You were asking for lemmy.ml donations to be separate from other donations. This was already addressed long ago, see here.