Selfhosted

60451 readers

974 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

455

WARNING: Lemmy Self-Hosters, There Have Been CSAM Attacks taking place against !lemmyshitpost@lemmy.world (jamie.moe)

submitted 2 years ago* (last edited 2 years ago) by Jamie@jamie.moe to c/selfhosted@lemmy.world

146 comments fedilink hide all child comments

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

There have been users spamming CSAM content in !lemmyshitpost@lemmy.world 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.

you are viewing a single comment's thread
view the rest of the comments

[–] ludrol@bookwormstory.social 4 points 2 years ago (1 children)

There is a possibility that my instance is buggy and it isn't caching images even though it should.

[–] hitagi@ani.social 4 points 2 years ago* (last edited 2 years ago) (1 children)

It's pretty inconsistent from my experience. Sometimes images do cache and sometimes they don't.

edit:

Here's an example from my instance:

https://ani.social/post/284147 - JPEG image that isn't copied/cached by my server.

https://ani.social/post/285861 - WEBP image copied/cached by my server.

[–] Rentlar@lemmy.ca 2 points 2 years ago (1 children)

Let me try to figure this out. The first is a photo uploaded to lemmy.world, the second is a photo originally uploaded to lemmy.nz, both posts are in a federated version of lemmy.world's shitpost community.

This is just a theory, but perhaps images hosted on the same server as the federated community will directly link, whereas images uploaded somewhere other than the federated community will be copied into cache, presumably in case the original host shuts down unexpectedly? See if this is the case?

[–] hitagi@ani.social 2 points 2 years ago

images hosted on the same server as the federated community will directly link

https://ani.social/post/288601 - This image is uploaded from a user on the same instance as the federated community (lemmy.world) but the image is cached.

images uploaded somewhere other than the federated community will be copied into cache

https://ani.social/post/285354 - This image is uploaded from a user on a different instance (lemm.ee) from the federated community (lemmy.world) but the image is not cached.

The behaviour is pretty weird. Hopefully we can disable image caching/copying-over-locally so we don't have to deal with problematic images hosted by other instances.