It’s the first option in the dropdown:

Big thanks to all maintainers and contributors!

You can check the federated/defederated instances for any instance on the /instances page. For example:

https://sh.itjust.works/instances

https://beehaw.org/instances

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.

Good luck with the upgrade!

That particular instance was very recently the source of a lot of CSAM and spam, so that’d be why. A lot of instances recently upped their security to combat that.

Just to add some more context, there was an attacker recently who created accounts on several Lemmy instances and used those accounts to spread CSAM. On lemm.ee, this attacker created 4 accounts over a 24h period, but was not able to upload any CSAM to our servers due to our stricter upload rules (we require 4 week old accounts to upload any images at all), and all of the 4 accounts were removed very shortly after creation (most of them within an hour of signing up). The attacker gave up trying to use lemm.ee very quickly, and moved on to other instances.

I just wanted to share this context to illustrate that while indeed the different measures we implement to protect the instance can have a negative impact on legitimate users, I really believe that overall, they have a net positive effect. In addition to Cloudflare DDoS protection and image upload restrictions, we also have a separate content-based alerting layer on top of Lemmy, which allows our admins to quickly notice when something suspicious is going on. As another example, this alerting has allowed us to extremely efficiently deal with a current ongoing spam attack on the Fediverse, and I bet many lemm.ee users aren’t even aware of this attack due to the quick content removal. We will continue to improve our defenses, and hopefully try to limit the impact on real users as much as possible, but some trade-offs are necessary here in order to protect the overall userbase.

The nice thing about Lemmy is that you can always host your own instance, even if it’s only for your own individual use. You can basically use your own instance as a proxy - other instances will not see how or from where you are connecting to your instance.

Large instances are being attacked almost constantly at this point in smaller and bigger ways. Almost all measures we implement to combat these attacks come with some trade-offs for the rest of the userbase.

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.

Honestly… it’s not great. I would not recommend it unless you’re playing with somebody who is not put off by constant bugs and general jank.

In terms of bugs, I’ve had several occasions where one player can no longer open the map - it just starts opening the quest log instead of the map. I’ve also had a few occasions of the screen just going completely white. Also, I’ve had a player just become locked in a dialogue with no way of exiting.

For an example of jankiness, one key aspect of the whole game, dialogues, is just completely awful:

1. Both players can begin separate dialogues at the same time, one just gets muted
2. It’s impossible to automatically begin a dialogue with two players, one player has to start it, and the other has to “listen” to it as an additional step
3. It’s impossible to switch control of dialogues during a dialogue. This is constantly an issue, because sometimes, dialogues are triggered when you walk past some invisible checkpoint. Basically you’re forced to always have your high charisma player to walk in front and hope they end up triggering all the dialogues.
4. It’s impossible to contribute to dialogues in any way as the “listening” player. Even if you have some aspect to your character that might provide an interesting line, you are just locked out.
5. If both players speak to a character in succession, the exact same dialogue gets repeated. It’s jarring and completely breaks immersion.

There’s more, but I’m kind of getting more and more annoyed at the game as I write this, so I think I will just stop here, you probably get the picture 😅

I think the co-op is a complete afterthought in this game, and I will probably be replaying it in single player for a hopefully better experience at some point.

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.

Thanks for releasing it so quickly!

This “sunaruas” sounds like a cool guy 😛

Awesome work, big thanks to all who contributed!

This is already implemented in lemmy 0.18.1 for comments and posts!