now if only there was a universal definition and cut off point for CSAM world wide… but sadly the only valid option is indeed to disable images…
Lets hope https://github.com/LemmyNet/lemmy/issues/3920 gets a proper implementation or other fix so we can atleast vet before we allow an images.
the main issue is that 1 bad post, can poison a big pool of servers, currently. Lemmy needs a better way to deal with images, to combat this issue.
and I hope none here actively go look for CSAM material… that doesn’t mean its not in the network.
A trick to “learn” routes… put the GPS in your pocket, and only listen to it… this way you start to spot the landmarks we used to use to navigate by.
Saved you a click:
REJECTED CVE has been marked “REJECT” in the CVE List. These CVEs are stored in the NVD, but do not show up in search results.
Well, you aren’t the only one with “the skillz” on here…. So don’t feel to ignored. ;)
even when: @jerry and @shellSharks are working on the servers. and I have nothing but praise for them.
I also think there should be some (small) group of people able to help & assist with the task of maintenance and support of the backend.
(and i don’t mean getting root access to anyone’s hardware, especially not without vetting)
and I would also think it would be a good idea to have some (open) scenario / manual / strategies for different standard actions, preferably with a script to also fix the issue.
(just some ideas running through my brain)
ouch, you know its bad when a infosec Admin asks you to switch off 2fa…
even worse offenders are the ones with tick boxes for “Legitimate Interest”, since legitimate interest is another grounds for processing (just ads freely given consent is one), the fact you got a “tick” box for it makes it NOT legitimate interest within the confines of the GDPR.
it also doesn’t matter what technology you use whether its cookies / urls / images / local storage / spy satellites. its solely about how you use the data…