I'm not going to claim MCPs are sophisticated, but I'm not sure they're equivalent to DVMs
Nostr is Available and Partitionable, but not Consistent. I think it's a good tradeoff. If you want Consistency you can use open timestamps on the blockchain (which is Consistent and Available but not Partitionable)
The Tenzing-Hillary Airport in Lukla, Nepal, gained worldwide fame, both for its unusual location, but also because it was rated the most dangerous airport in the world for more than 20 years by a program titled Most Extreme Airports.
https://video.nostr.build/4e1db92e54709204621cfbde1bea3a6ddc15c8036f9416e451298bbd7cc0250a.mp4
Well now I don't feel so bad about my flight sim habits
We do what we must, because we can
nostr:note162ape339s0u42vjyma0pegsp7x5qc38z7vpeqa3l5y3p9pf5n0csguj5ut
Probably not too foreign in Spain either. Barcelona tended to stay out late, maybe siesta, maybe a nap before going out. Modern work hours don't align to this very well.
TIL my unhinged parental sleep schedule has a name
nostr:note1n3ytrqeuvvmvl3fmnrjsgmwqqd92dj3edc7nsn045u7a8h3cpeeq9640du
I'm big on goose. It's a bit spicy, but so am I
Whenever I vibecode UIs it feels like the agent is flying blind because it can't see what's being rendered.
Have any of you tried integrating a browser-automation MCP like this one? Seems like this could really help the agent QA its work.
https://github.com/modelcontextprotocol/servers/tree/main/src/puppeteer
I've done this, but I don't remember if I did it with goose or manual screenshots and the Claude chat interface. It worked pretty well
Nah, relays could certify the first time they've seen events
Yeah, seems the same. These kinds of things aren't surprising if you work at the protocol level, but people often make assumptions
That oath works better for a sexy new app than it does for core protocol improvements. Much less work to wait for some of ya'll to get pwned and then pitch my ideas
No, that was https://en.m.wikipedia.org/wiki/3dfx
Me proposing cool new NIPs to other devs.
https://cdn.nostrcheck.me/80df30f877d0afc07a542133c0f68d9d242ddab8463f9bb5c273bfeed149ebab.mp4
Yep. Seems like I'm going to have to write my own popular client just to get subkeys
Is this unexpected? You can trivially do the same thing on nostr. Some relays might not like it, but the protocol doesn't prevent it. It's actually a core issue with key rotation
nostr:note1hzxykshgfttmxffhk4nnp9dq3tq2frd5v8nl39hj9jw6mm3m9masg0pvyp
Don't tell me how LLMs work until you've nerd-sniped one
Can they steal some of nostr in return?