But how are you doing

👀

Taking my kids on a trip to the Olympic Penninsula to look at anemones next week, don't break the protocol while I'm gone

Not only is it ugly, it's gay too

What makes you think so?

Remember how I was writing a book? Well, I gave up on it. But then I wrote a different one: https://building-nostr.coracle.social/ This book is both practical and philosophical. It ellides a lot of the details you can otherwise get by reading Nostr NIPs, focusing instead on all the things I've learned over three years working on nostr. It includes a number of contrarian opinions which may be partially or completely wrong. Feel free to disagree, or even tell me where I'm wrong. I'll be releasing updates to the book as I have time and inclination to repent of my mistakes and omissions. The book is free, with epub and pdf versions available for your reading pleasure. If you like the book, you can send me bitcoin via nostr or at https://geyser.fund/project/buildingnostr, and if people like it enough I may publish a version that you can touch with your fingers.

Is someone linking directly to coracle for somewhere? I'm seeing a ton of traffic the last week or two for the profile page. I'm flattered, but loading up Coracle just for a profile page is very inefficient and it's costing a lot of bandwidth.

Icing after every run, but doing well so far!

14 years ago I ran my longest distance, 15 miles. Today, I just finished my first 18 mile run.

It was all my wife

You're clearly not listening to what I'm saying

If you haven't already, give flotilla.social a try

Join us

@me

Awesome

Thanks, I was messing with DNS so I could get better logging on a different deployment to figure some stuff out. Just pointed it back to the old deployment, so it should work once DNS propagates. I'm not sure why it was broken, since nginx is set up right and working for me, but cest la vie

A portent of things to come on nostr: https://daniel.haxx.se/blog/2025/08/08/http-is-not-simple/

This is actually a great analogy for the "bitcoin uses too much energy" argument

bro get your own kind

Derp, was thinking about NIP 13. That's what I get for memorizing all the numbers. Not a bad idea, although like someone said you would lose the attestation when you update your profile.

In order to be meaningful, pow should take some time (how much do you need to deter spam? 30 seconds?). So unless you're super clever with the implementation your user would have to wait for it to finish. Maybe if you collect profile information and generate the user's key at the beginning of the onboarding process you might be able to generate the work in the background while the user is occupied with something else. You could also publish first a low-pow version (to avoid failing to publish one if the user leaves the page), then a high-pow version later. So I guess it's possible, just complex in terms of implementation.

This is awesome, I love the server-published ui components

No, it adds an `expiration` tag, which is less well supported than deletes, but part of the event itself

I have some ideas about that, but haven't implemented any of them. One approach I had considered a while back was this: https://github.com/coracle-social/nips/blob/60179dfba2a51479c569c9192290bb4cefc660a8/xx.md#federation Basically, a relay could declare that it federates or mirrors another relay, which would allow clients to rely on either or both for redundancy/backup.

💯

Yep, you can also add handlers to the socket class (via pool or makeSocket if you want to do it for all sockets)

Because it introduces pretty significant friction to onboarding. An ok compromise that I have in coracle is to nip 03 the user's first post, which could be used to discover new users (although it probably isn't really)

I've definitely felt that too, I want to integrate bookmarks at some point