You shouldn't expect the next generate of Pixel phones to have GrapheneOS support out of the box. Google has stopped publishing device tree data, so custom ROMs for Pixels may not be a thing come the Pixel 10.

We're all hoping this is reversed.

yeah I'm worried about that. I like Pixel phones a lot because of their cameras. Everyone who ends up focusing on one thing ends up eschewing the camera much to my chagrin

yeah I don't think I will buy the Pixel 10 unless GrapheneOS supports it

ok so polarize the light in the fiber, gg no interference

oh no!

anyways...

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.

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™

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'm the backend guy at lemdro.id, I started the instance. I don't moderate the !android@lemdro.id community (or any of them... I purely do infrastructure), but I am quite aware of the drama around recent events involving the two android communities.

The intent behind banning all lemdro.id users from applying to be mods feels quite... retaliatory? I'm not sure there is anyone on lemdro.id who would apply, but depriving them the opportunity simply because they are associated with an instance that hosts a community which had another community merge into it?

It is your community, you can of course do what you want. I just wish we could drop the drama, act like adults, and move on. Tired of the vitriol.

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

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