The feddit.de admin disappeared on a work trip to Japan. At least that is the official story.

This is something that even larger corps struggle with. My old company would buy some other company, lay off a bunch of people, others would quit, and then it was shocked Pikachu faces all around when That One Thing stopped working in an office they turned into a ghost town and, well, no, nobody was going to be there until Monday morning to power cycle etc. True lights out/OOB reachability is WORK. And there’s always going to be a SPOF somewhere that requires hands on-site.

Do what you can, when you can. And thank you for all that y’all have done so far.

For that, I’d highly recommend a power conditioner with outlet controls (and preferably sequencing).

Most are pretty expensive, but you can get something like a surgex squid or a gude expert power control for a few hundred here and there, which will give you great data on power usage as well. You can also grab an older model with serial and/or relay controls, and use a pi or whatever is handy to trigger it. Actually have a setup like that in a few racks for clients (mostly orange pis and a couple of Asus tinker boards).

Hope your trip goes well!

They have stepped in when a lot of people complained, it took their whole instance complaining to do so while a Nazi troll spammed hate across the local feed.

you can still have it with NodeBB!

Lemmy has a lot of individual parts that don’t interact very well with each other, especially the image host part. Futhermore the main UI is quite a mess and we were thinking of switching to an alternative already, but this would further increase the “too many moving parts” issue. Piefed on the otherhand has an integrated and very lightweight UI, which also has some nice additional filtering and moderation features Lemmy currently lacks.

And I personally feel more at home with the Python codebase, as it allows better troubleshooting and more standartized (Flask) tooling. The Rust codebase of Lemmy has a lot of obscure custom stuff and the error messages are extremely obstruse from a sysadmin perspective.

And looking at the performance metrics of Lemmy, the main limiting factor seems to be the Postgres database anyways, so the theoretically slower Python codebase of Piefed should not have much impact.

Not necessarily, no. We aim to preserve users, communities and posts/comments. Image uploads might get lost though.

Such an in-place migration will need extensive database operations and likely some support by the Piefed developer (to add support for bcrypt hashed passwords), but we are hopeful to make it happen and maybe this will result in a database migration script other Lemmy instances could also use.

If this turns out to be infeasible, we will stay with Lemmy rather than reset everything.