505
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

cross-posted from: https://jamie.moe/post/113630

There have been users spamming CSAM content in [email protected] causing it to federate to other instances. If your instance is subscribed to this community, you should take action to rectify it immediately. I recommend performing a hard delete via command line on the server.

I deleted every image from the past 24 hours personally, using the following command: sudo find /srv/lemmy/example.com/volumes/pictrs/files -type f -ctime -1 -exec shred {} \;

Note: Your local jurisdiction may impose a duty to report or other obligations. Check with these, but always prioritize ensuring that the content does not continue to be served.

Update

Apparently the Lemmy Shitpost community is shut down as of now.

(page 2) 50 comments
sorted by: hot top new old
[-] [email protected] 14 points 2 years ago
load more comments (2 replies)
[-] [email protected] 11 points 2 years ago

I'm not subscribed to that community, but I guess I'm glad Pictrs doesn't work for me, since I am using the Yunohost version of Lemmy. The creators of the Yunohost package couldn't get it to work. I haven't really missed it honestly.

[-] [email protected] 8 points 2 years ago

Can you run lemmy without pictrs? What behavior is different?

load more comments (1 replies)
[-] [email protected] 9 points 2 years ago* (last edited 2 years ago)

Likely Spez’s personal jailbait collection

[-] [email protected] 8 points 2 years ago

I am using the Lemmy easy deploy would this command works?

[-] [email protected] 8 points 2 years ago

You'll need to find where the actual container files are being stored. I'm unfortunately not familiar with Lemmy Easy Deploy, but you should have a folder that has some files/folders like docker-compose.yml, volumes, lemmy.hjson.

The important one is the volumes/pictrs/files folder, take the full path of that folder and replace it with the /srv/lemmy/example.com... path from the original post, and then that command should work.

[-] [email protected] 7 points 2 years ago

There was a weird JSON error I was getting in the last few minutes. I'm not sure if this is at all related.

[-] [email protected] 7 points 2 years ago

As far as I know, images should not be federating to federated instances, right? Image proxying is supposed to be added to pictrs version 0.5.0 but it is still in alpha.

load more comments (4 replies)
load more comments
view more: ‹ prev next ›
this post was submitted on 28 Aug 2023
505 points (98.3% liked)

Selfhosted

46672 readers
332 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS