Ironically, probably on Twitter, @eth_limo.

Limo don't yet support this directly - you need to ping them and ask them to add the record for you. They're working on an automated solution!

We're redoing our kitchen in an older home. It's navy blue shaker cabinets with a white quartz bench top. What sort of pendant lights should we consider over the breakfast bar that have a more modern look while still fitting in?

By special request to the Limo team, but they're working on making it self-serve.

It's going to be really important that all nodes agree on the namespace mapping, though. If different nodes have different views on who nick.crypto is, that seems Bad.

Defaults! Similar to the DNS root, the default could be a service maintained by a set of trusted parties.

That's a good idea. How do you know the gateway they provide is authoritative, though?

Alternatively, maybe the node owner can specify a gateway?

Ah true, I hadn't thought about the federation angle. Using one of the gateways like eth.limo would be an option, but it's not maximally decentralized.

@jay.bsky.team Any interest in working together to add ENS support?

I've been harassing the bluesky devs about it. Is there some kind of standard?