![](https://lemmy.catasaur.xyz/pictrs/image/9a2f8a0c-0e7d-42eb-8912-d2dde20585de.jpeg)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
2·
1 year agoWe’ve got young adults entering the workforce that cannot comprehend what a filesystem and directory structure is due to 10+ years of these sandboxed, guard-railed tech products.
We’ve got young adults entering the workforce that cannot comprehend what a filesystem and directory structure is due to 10+ years of these sandboxed, guard-railed tech products.
This is why return to office is a joke.
Self hoster here, im nuking all of pictrs. People are sick. Luckily I did not see anything, however I was subscribed to the community.
sudo find /srv/lemmy/example.com/volumes/pictrs -type f -exec shred {} \;
Removed the pictrs config in lemmy.hjson
removed pictrs container from docker compose
Anything else I should to protect my instance, besides shutting down completely?