[ ](image ) [WALL·E]( ) Lately I’ve been thinking about orphaned code. Code that’s still running, live, with no remaining developers or users. Forgotten hardware devices. Deserted VMs on cloud free tiers. Smart contracts whose DAOs disbanded years ago. Old school internet worms. Abandoned, starving Tamagotchi. Can you think of other examples? There are obvious conclusions here about maintainability, ecosystem security, etc, but I’m not here to lecture, I have no particular conclusions. Just a vibe. It’s a very, very…mad world. image
We had some downtime bridging to Bluesky last night, roughly 10:30-15:30 UTC. Back up and running as of a couple hours ago. Bridging from Bluesky, and between web and fediverse, were unaffected. Apologies for the outage! Will investigate, feel free to follow for details.
[*Art of Manga*]( ), [de Young Museum]( ), Oct 2025
standards bodies: “bureaucracy for good”
A glimpse into the [Bridgy Fed]( ) monitoring dashboards. Pretty conventional mix of infra, OS, and app level metrics. Note the delay numbers. When you do something in one network, how quickly do we bridge it across? We pay a lot of attention to that, we try hard to keep it as fast as possible! [](image ) [](image ) [](image ) [](image ) I wish we could [make these dashboards public]( )! Google Cloud Monitoring doesn’t support that right now; [hopefully they will eventually]( ).
office [](image ) image
[](image ) image