Interesting, when I tried a while back it broke all images (not visible on the website due to service worker caching but visible if you put any pictrs url into postman or something)
nick
joined 1 year ago
Wow another coup in francophone Africa. I wonder if the regional democratic powers not intervening in Niger encouraged this.
It's pretty popular with all the coffee youtubers, one (Sprometheus) even made a video just about this glass lol
I wrote a patch for Lemmy a week or so ago if you want to skip the caching: https://github.com/LemmyNet/lemmy/pull/3897
I think deleting images from the pictrs storage can corrupt the pictrs sled db so I would not advise it, you should go via the purge endpoint on the pictrs API.
Just a note that my PR there doesn't disable pictrs for your own instance's users. It just disables the caching of remote content.
Just near Startup, WA, USA
The Kruve Propel is dishwasher safe.
I don't know about lemmy.world but I assume they "purged" the user instead of banning them (or at least that's what I did for my instance). Purging wipes all of their data from your instance and exists as a feature basically for this reason. That means that the user wouldn't have a visible account to ban anymore because it literally removes them from the database.
Only way to be sure that your server doesn't have any of their content on it.
It was amazing! I wish I got to stay there longer.
The Lemmy instance I'm speaking from right now is running in my k8s cluster.
True, you're correct. I'm just not sure how you did it without corrupting the sled db. Maybe I'm just unlucky