cole @ cole @lemdro.id

I started lemdro.id. Pretty cool domain name, right?

---

Read more

Posts

5

Comments

362

Joined

2 yr. ago

I miss being able to search my screen that was so useful

I started an entire instance - https://lemdro.id - to provide a home to Reddit subreddits such as r/Android and r/Google Pixel (and other technical stuff)

animations are so pleasant. if you don't like them turn them off in dev mode, don't kill it for the rest of us

yes and you have to make them like 10 years before you actually want to eat them

and to note hasn't seen any progress or work in 3 years

cinnamon rolls

God of War. FYI, don't send keys over Lemmy private message. Anybody who runs an instance that federates with yours may be able to see your private messages. Just be careful is all!

!eternityapp@lemdro.id is the official community for it too!

support in desktop environments for managing dual backlights when provided by the kernel. I was working on this for a bit but got too busy

this is definitely not true. Computer Engineering is a relatively common major even

FINALLY! Hopefully this lets Google launch it's find network

lemdro.id doesn't disable editing so I'm not sure what you mean

fyi, I replied in this thread!

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.

test comment #3

test comment please ignore v4

another test comment please ignore

test comment please ignore

Test comment please ignore

this assumption is only correct if EVERYBODY is using as blockers. They aren't - so it makes sense to cut off the proverbial leeches