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.

They specifically called it “child abuse content”, not “child abuse”. This seems perfectly valid, no?

By the way, just because these are digital renderings does not mean that there is no harm. Seeing such content can still be harmful to past victims. Just try to put yourself in this situation: imagine just playing some video game online, and suddenly being exposed to people recreating traumatic experiences from your past. Not only that - you also discover that the creators of the video game are involved & actively enabling such content. Seems completely messed up to me.

I think the OP is talking about Lemmy having both a content preview and a text area for link posts.

Some users tend to write their own summary in the text area, so when opening up a post, the result will be:

• Large title written by the OP
• Automatic preview of the page, generated by Lemmy
• Text summary of the page, written by the OP

I agree that this is a bit clunky in terms of UX

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.

This approach makes so much sense from a business perspective.

How many here have this experience: out of my entire friend group that I grew up playing video games with, I can’t think of a single person who kept pirating games after acquiring disposable income, even though we all exclusively played pirated games as teenagers. Without piracy, none of us would have had access to any games, and very likely none of us would still be into gaming today, spending probably thousands of euros every year on games, consoles, PC components, etc.

Damn, even $11.99 sounds like a lot - I only pay 12.99€ for a family plan in Europe.

Wow, both of those are among my all time favorite games. Good taste!

Nice work!

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

This doesn’t directly affect me, as I’ve exclusively bought digital games only for over a decade, but it still annoys me based on principle. It’s basically a bait and switch - it would be far more honest to just say “it’s digital only” than to sell a useless physical box.

Oh boy. I didn’t expect YoshiP to deliver a bad game by any means, but this is looking like it will exceed all my expectations anyway.

I would recommend reconsidering that solution - I’ve already seen some malicious image uploads which Cloudflare has caught. For example:

Maybe you can check which specific rule from the ruleset was being triggered? For me, legit uploads are still working with the default ruleset (as you can see by the screenshot I uploaded in this very comment), so maybe you enabled some extra rules?

Can you elaborate which functions are blocked by the managed rules? I haven’t noticed anything legit being blocked yet, just a bunch of obviously malicious things.

Reposting my comment from another thread to spread awareness:

There is a bug in 0.17.4 that stops front pages from updating shortly after the server is restarted, thus resulting in “hot” and “active” showing stale posts.

I have fixed this issue on https://lemm.ee already, you can check our front page to see fresh posts. The fix will soon land in the main Lemmy codebase as well so other instances can take advantage, you can track the issue here: https://github.com/LemmyNet/lemmy/issues/3076

I have also advised other instance admins that regularly restarting their Lemmy server will work as a band-aid workaround until the proper fix is released, so some admins have already implemented this in order to get their post rankings working again, but the proper fix will come in the next release of Lemmy.

I think people will eventually get used to the idea that the name of a community is not just the part before the “@”.

I mean, even regular people have no difficulty understanding that e-mail addresses like [email protected] and [email protected] are two different “identifiers” and, most likely, two completely different people. Given a bit of time, I think there will be a general understanding that “[email protected]” and “[email protected]” are different names.

The fragmentation is not inherent to how Lemmy works - the exact same fragmentation can and does happen on Reddit. Just a random example: https://imgur.com/inXBMMA

On Reddit, it usually works out in the end in one way or another. Either mods decide to team up and combine their communities, or the users just naturally pick one community as the “winner”.

I’m a huge fan of 1Password. Previously used pass for years, but there are many ways in which 1Password is more convenient, especially when it comes to sharing secrets with friends/family/colleagues.

Reddit admins are just protecting lemmy.ml from being further overloaded!

In all seriousness, it’s best to direct people to https://join-lemmy.org rather than any specific instance - the list of instances there is constantly being updated and can be used to spread out the load between different instances. Even so, your post would most likely still have been removed from Reddit, regardless of what specific Lemmy url you’re posting.

I just want to point out that you don’t need to use neither Docker nor nginx to run Lemmy.

At the end of the day, the really required pieces are:

1. lemmy_server binary
2. Lemmy-ui
3. pict-rs binary
4. PostgreSQL database

How you get those things to talk to each other is totally up to you. There’s nothing stopping you from just using Apache as a reverse proxy, for example.

One possible Dockerless setup is described here: https://join-lemmy.org/docs/en/administration/from_scratch.html. This should give you some idea of how it could be done.