![](https://lemm.ee/pictrs/image/b5644329-1d41-47b7-a17a-fb055c071b5a.webp)
![](https://sh.itjust.works/pictrs/image/045a2049-eb61-4960-88ba-97e7f1ffbf31.jpeg)
We finally have a release date for Microsoft Flight Simulator 2024!
We finally have a release date for Microsoft Flight Simulator 2024!
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.
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:
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!
Awesome news, good luck with the work!
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.
Only way the current situation makes sense to me:
If this had really been about Shoigu or a coup or anything other than just a suicide mission, then the current result makes 0 sense. (But in that case, maybe the situation isn’t really over at all)
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 and prevented. 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.
There has been some very loud opposition to this, but thankfully it’s a minority. Great to see that our constitutional right of not being discriminated against based on sex finally also applies to marriage as well.
By the way, shameless plug, we have a small Estonian community going at !eesti@lemm.ee - if anybody wants to chat about Estonia or with Estonians, then English posts are more than welcome as well 😃
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 difficutly understanding that bob@google.com and bob@microsoft.com are two different “identifiers” and, most likely, two completely different people. Given a bit of time, I think the understanding that “foo@lemmy.ml” and “foo@beehaw.org” are different names
It’s a full new game that you need to purchase separately, but all the marketplace stuff you’ve bought for 2020 will also come with you to 2024