It is not even a mistake, it’s some pretty mind-fucked up on part of @bamboo@lemmy.blahaj.zone to jump to such a conclusion. crap

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! @bamboo@lemmy.blahaj.zone 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.

and avoiding link rot

Lemmy seems built to destroy information, rot links. Unlike Reddit has been for 15 years, when a person deletes their account Lemmy removes all posts and comments, creating a black hole.

Not only are the comments disappeared from the person who deleted their account, all the comments made by other users disappear on those posts and comments.

Right now, a single user just deleting one comment results in the entire branch of comment replies to just disappear.

Installing an instance was done pretty quickly… over 1000 new instances went online in June because of the Reddit API change. But once that instance goes offline, all the communities hosted there are orphaned and no cleanup code really exists to salvage any of it - because the whole system was built around deleting comments and posts - and deleting an instance is pretty much a purging of everything they ever created in the minds of the designers.

There is a pattern of retries built into the code, but syncing has no ability to repair failures, and there have been hand-documented cases where even with retries, there is significant data loss: https://github.com/LemmyNet/lemmy/issues/3101

I am starting to see some partial page loads, broken pages - bug with actual data content of posting/comments on them. I expect other federation servers are swarming to the site to try and replicate - and it’s causing a mess given how many communities lemmy.ml is center of.

Still down as of time of this comment, 45 minutes since I first observed it.

I saw you updated the repository right after you commented to me, but I was still getting the ‘500 internal error’ on /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.