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
Hello to you!
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.
Fox allowing him hours a day of direct speech…
Once Elon Musk returns him to Twitter, we will have the “bar and grill of all the world’s journalist” for the past 15 years become a black hole of old news story history. The symbolic tactics that are under play are massive. Reality has been rejected on a massive scale via electric media… Dans un sens, c’est le système entier qui, par sa fragilité interne, prête main-forte à l’action initiale. Plus le système se concentre mondialement, ne constituant à la limite qu’un seul réseau
Trump followers can’t even see how the former mayor of NYC has lost his mind. They meet at 4 seasons gardening.
It’s sort of like WiFi and 5G mobile drivers (especially the software driven radios), a lot of proprietary stuff is in the driver that reveals hardware secrets. GPU is also regulated now for export controls from USA-derived technology. With software-driven radios, you see a lot of effort to keep people from using bands outside their national laws.
Yes, I installed a Lemmy server my own self, there is no screening, approval, or even a “terms of use” on the signup page. This is the “wild west” of social media. And some of the claims on the GitHub project page such as “full delete” are an overreach, as it has no footnote that federated servers do not have to comply with the delete of your replicated votes/comments/posts/profile
the comment_like database table in Lemmy also has a timestamp on it, “published” field, that discloses what time you voted. This reveals patterns of your Lemmy usage to other federated servers.
When the browser loads that URL, hotlinked image, that server has to have your IP address to return the results. Just browsing posts those images are being loaded.
Your home instance will act as a proxy and only they have access to your email and IP address.
Your home image typically doesn’t proxy image loading, those are hotlinked to the Lemmy server that the image was uploaded to. So your IP address and browser string are going to other Lemmy servers.
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.
essentially that is what mythology has been for humanity. Too bad now we just let advertising borrow the techniques without education the population how it works.