fuck

It is my opinion that there is only “tension” because you say there is. I do not believe that most people feel that way; it isn’t exactly an active war zone. Nevertheless, I respect your decision as moderator of this community, and I’ll leave you be in the future. Best of luck!

I’ve gotten an email like this before for lemdro.id. I think it’s a generic phishing email since the community links look like email addresses (and actually often are)

Freesync yes, HDR soon™

sure! take a look at this issue: https://github.com/LemmyNet/lemmy-ansible/issues/106

It is likely yours is fixed if you deployed recently

I feel like Dune was a good outlier to this. It’s the only movie I’ve seen in theater in the last few years and I really enjoyed not having everything explained to me

If you support changing the default frontend to Photon, upvote this comment! If you don’t support it, downvote this comment!

this might be an improvement

Basically, the lemmy backend service for some reason marked every instance we federated with as inactive, which caused it to stop outbound federation with basically everyone. I have a few working theories on why, but not fully sure yet.

TL;DR lemmy bug, required manual database intervention to fix

This was a stressful start to a vacation!

For a more detailed working theory…

I’ve been doing a lot of infrastructure upgrades lately. Lemdro.id runs on a ton of containerized services that scale horizontally for each part of the stack globally and according to load. It’s pretty cool. But my theory is that since the backend schedules inactive checking for 24 hours from when it starts that it simply was being restarted (upgraded) before it had a chance to check activity until it was too late.

theory:

• scheduled task checks instances every 24 hours

• I updated (restarted it) more than every 24 hours

• it never had a chance to run the check

• ???

• failure

This isn’t really a great design for inactivity checking and I’ll be submitting a pull request to fix it.

Edit: A fix has been deployed, and federation should work now. Unfortunately, kbin.social is taking its sweet time federating with us, it is probably overloaded. Lemdro.id is already accessible from other kbin instances such as fedia.io (https://fedia.io/m/android@lemdro.id)

Hello! Admin here at lemdro.id. This is the result of several problems in the lemmy default reference nginx config. I am working on resolving this right now and should have it fixed within the next 30 minutes!