It’s the first option in the dropdown:

Big thanks to all maintainers and contributors!

The sad fact is that some people keep constantly spreading false rumors about Lemmy devs not working on mod tools. Anybody can just take a few minutes and go through the past Lemmy updates in this community to see that moderation improvements are basically worked on constantly (and this is not some recent change either). But there are plenty of users who never bother to actually check this, and so the rumors keep spreading.

Obviously being instance-banned won’t prevent you from commenting on their posts, it just won’t get federated to that instance

I am actually working on fixing this right now, so that in the future, users would be prevented from commenting in this situation

Awesome work!

Do you have an idea yet for the timeline of the 0.19.4 release?

If I have several backends that more or less depend on each other anyway (for example: Lemmy + pict-rs), then I will create separate databases for them within a single postgres - reason being, if something bad happens to the database for one of them, then it affects the other one as well anyway, so there isn’t much to gain from isolating the databases.

Conversely, for completely unrelated services, I will always set up separate postgres instances, for full isolation.

I kind of get where you’re coming from, but to me it sounds like you’re looking for a different experience than what Lemmy is designed for. It seems you are more interested in aggergating all posts about specific topics (like “books”), and strongly limiting the effect of moderation (as nobody would have final say about how to moderate an entire topic). If I correctly understood the experience you’re interested in, then for sure the design of Lemmy will not match that.

I don’t think it’s fair to describe this as a fatal flaw, though. Lemmy is not built around the idea of generic, “ownerless” topics, instead, it’s built around communities with clear owners. We have decentralization at the admin and infrastructure level (as in, a single admin does not control the entire network), but this does not really mean we also need to have it at individual community level.

IMO it’s totally fine that different people create different communities with extremely similar purposes. The entire internet as a whole also works like this - the internet itself is decentralized, but at the same time people can create different websites with very similar purposes (and even domains!), and it works out fine. For example, it’s totally possible for there to exist a news.com, news.co.uk, news.ee, news.fi, etc. Imagine if whenever you navigated to news.fi with your browser, it would also automatically insert content from all the other news websites of all possible domains - it doesn’t really seem like a useful feature, but that’s kind of analogous to what you’re suggesting for Lemmy at the moment.

It’s OK to post questions here:

Feel free to post and upvote questions beforehand in this post, as it will turn into the AMA tomorrow.

Do you think Lemmy is decentralized enough right now, or are you worried about some of the bigger instances growing too much?

What exactly is the issue with our admins? If you feel you’ve received some unjustified moderation, feel free to contact me and I can have a look.

As a test, I ran this on a very early backup of lemm.ee images from when we had very little federation and very little uploads, and unfortunately it is finding a whole bunch of false positives. Just some examples it flagged as CSAM:

• Calvin and Hobbes comic
• The default Lemmy logo
• Some random user’s avatar, which is just a digital drawing of a person’s face
• a Pikachu image

Do you think the parameters of the script should be tuned? I’m happy to test it further on my backup, as I am reasonably certain that it doesn’t contain any actual CSAM

Any thoughts about using this as a middleware between nginx and Lemmy for all image uploads?

Edit: I guess that wouldn’t work for external images - unless it also ran for all outgoing requests from pict-rs… I think the easiest way to integrate this with pict-rs would be through some upstream changes that would allow pict-rs itself to call this code on every image.