Hello to you!
I think timestamps of files would be one of the easier things, and try to track back to postings and comments that references the upload… ideally the logged-in account (which is the standard install of lemmy, only logged-in users can upload to pictrs)
Yes. odd how people think sharing CSAM is why people would post here, instead of actually tracking down and prosecuting those sharing CSAM. Details about the users who sharedl CSAM content, such as timestamps - would help identify the offenders for prosecution.
It sounds like you’re encouraging people to share CSAM images found, which is obviously not the intent of this tool.
Yes, that is in fact the context.
Context: "which is obviously not the intent of this tool. "
it is not my intent to share the images, nor is it the context of the tool… Sharing details about the users, timestamps - would be the obvious context.
I hope people share the positive hits of CSAM and see how widespread the problem is…
DRAMTIC EDIT: the records lemmy_safety_local_storage.py identifies, not the images! @[email protected] seems to think it “sounds like” I am ACTIVELY encouraging the spreading of child pornography images… NO! I mean audit files, such as timestamps, the account that uploaded, etc. Once you have the timestamp, the nginx logs from a lemmy server should help identify the IP address.
Some people seem to be interpreting this to mean 11 million comments per day. I think it means the numbers are updated daily.
The numbers also don’t make a lot of sense to me. Front page of lemmy.world says 620,000 (local origin) comments. And Lemmy sequentially numbers the comments for an instance, mixing both local and federated and the recent numbers look like 2,122,067. Lemmy.ml says 253,000 on the front page, and their index key is showing 2,321,959 for a comment made today. I have to imagine that these two servers are subscribed to a lot of stuff (including each other). I’d be surprised if there were more than 4 million unique comments in Lemmy. And there would be some kbin messages in the Lemmy.world index.
I don’t know why all of the other apps + web decided to break on me a week ago, but the only way I can reply to comments right now is because of Sync. Anyone else having this issue?
There is an open issue on GitHub. 0.18.3 seems to have changed the behavior of comment links. IN some cases, the comment specified isn’t even shown at all. https://github.com/LemmyNet/lemmy-ui/issues/1999
I saw you updated the repository right after you commented to me, but I was still getting the ‘500 internal error’ on /r/post/xxx route.
I tracked it down to:
/src/lib/components/Comment.svelte
Has a line:
import { comment } from 'svelte/internal';
Removing that line eliminated my page crash.
My main Lemmy.ml account comment isn’t properly federating over to lemmy.world, so I’m duplicating my reply on my alt-account:
Cool. SvelteKit is ideal for this.
Can you move the server name to an .env variable so I don’t have to run a sed? sharing my sed:
find src/ -type f | xargs sed -i 's/lemmy\.world/enterprise.lemmy.ml/g'
FYI, there is a double https:// on page https://github.com/ando818/lemmy-ui-svelte/blob/main/src/lib/lemmyclient.js
On desktop browser, I’m getting a ‘500 internal error’ on the /r/post/xxx route, but not sure why. The console isn’t showing anything. The page.server.js seems to get the JSON fine from the API, but the .svelte file in that route is failing.
It is not even a mistake, it’s some pretty mind-fucked up on part of @[email protected] to jump to such a conclusion. crap