Because of the nature of federation posts and comments on LemmyNSFW communities will live on basically forever. However the photos and videos will likely be lost. Some were links to external media and will stick around, some may be cached. But most photos and videos that were uploaded directly to the instance will break when the server fully goes down.

For example: [NSFW, OBVIOUSLY] !boobs@lemmynsfw.com - that link should load fine on your instance. It should look functional just with no new posts. (Note: it's actually possible to post and comment in these communities still, but only people in your instance will see it)

The images are served from links like these: (mild NSFW) https://lemmynsfw.com/pictrs/image/d50379d3-7d64-440c-bcf6-13dbf2b81c1b.webp?format=webp

The fact that the images still load is a somewhat hopeful sign. The server is still running, Lemmy just crashed. There's still time for the head admin to come back, the data still exists. This seems unlikely though as the other admin says they haven't heard from them since October.

So there's a small window to archive this stuff, if you're interested. Between now and whenever the media server crashes or gets shut off for non-payment.

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

[–] Warl0k3@lemmy.world 14 points 1 day ago* (last edited 1 day ago) (1 children)

If I remember right the images are all hosted on catbox not on lemmynsfw itself. I'm not sure why they're still accessible, I was never told how the backend was set up beyond that, but it does mean that the images are only available until catbox times them out.

[–] testauser1@lemmy.world 8 points 1 day ago (2 children)

I don't think so. These pict-rs links are standard Lemmy image hosting.

https://lemmynsfw.com/pictrs/image/d50379d3-7d64-440c-bcf6-13dbf2b81c1b.webp?format=webp

[–] Warl0k3@lemmy.world 4 points 1 day ago

Huh. This was from a conversation with said missing admin so I may just be misremembering.

[–] tofu@lemmy.nocturnal.garden 2 points 1 day ago

That likely means the server is still up and just the Lemmy containers/just the frontend container is down. The default setup has nginx proxying the /pictrs to pictrs I think.