beep beep - mylem.me checking in

I don’t really have an opinion right now 🤷‍♂️

I see where you’re coming from but to me anything related to programming goes.

If you don’t want that then point people to the right communities and delete unfitting posts. I guess that’s the only way to keep it clean. As a side effect, this may actually help other more specific communities in the long run.

I’ve limited the resources available to Lemmy and pictrs and will see if it helps.

Sounds more like it, yes. I’ll keep an eye on it.

Maybe we should create a post in the support community?

I’m having similar issues with my instance where I’m the only one on it. I allocated more RAM to it now to see if it does anything.

zombo.social because I just learned about zombo.com

Thanks. I didn’t realize that first but it’s been starting to become clear… now that I know I’ll have to adjust my setup accordingly.

Thanks a lot!

I see, thanks. What volume(s) are you persisting that way exactly? I mean the internal path that pictrs is using.

mylem.me

it’s intended to be a highly reliable little instance. For now it’s closed, though, until I figured out how to properly handle pictrs’ internal state.

how do you handle the sled state for pictrs with 2 nodes? I’ve been having some trouble with it.

My (short) take on this:

The whole fediverse lacks security right now compared to how email did in the 90s. This will only become a problem with mass adoption, again, like it did with email.

Good to start thinking about it early on, though.

I’ve got my pictrs backed by an S3, so that should scale well.

I had some issues with the image server, though, and I had multiple of them running at the same time at some point, so that may have been the cause.

That phrase makes perfect sense, though

I just set one up using docker. Went surprisingly smoothly.