Reflecting on the passed year, as one does around this time, i am looking back at a book that does not exist yet.
My original intention was to have finished written this ‘book about Nostr’ months ago. This was mostly due to the fact that the first part about the problems with the status quo and how we got into this mess was so easy to write. On the one hand because this year just kept handing out example after example where the problems lie, be it the Brazil X-ban or the myriad of other occurrences; but on the other hand more importantly because i already had that narrative down years ago. While digging through my hard-drive i found an interview i did in 2019 that was never published, where i laid out all the fundamental problems, and the story is basically the same (video down below, it is in Dutch). This part of the book has been mostly done for many many months now. The issue was describing Nostr itself.
I can’t pin point when I got aware of Nostr, and I mainly build my intuition around the protocol outside of the ‘community’ or use of the protocol itself; partly because I am not a developer nor much of a ‘social media’ user. It is only recently I actually started looking at NIPs due to my work with Nostr Special Forces, and for the longest time I never even read NIP-01. This way of going at it was facilitated by the fact I could just discuss Nostr matters with its creator, to the point where he rather have me stay blissfully unaware of the NIPs out there to keep my thinking uninfluenced by them.
But when it got to describing the Nostr phenomena for the book, I felt it was not enough. I started using the clients, turn NAK into a new best friend and engage with the broader (developer) community. The hardest part is that Nostr is still so actively evolving that describing it in its current state would make the book outdated by the time it comes out. Giving projections as to what it will become has its own problems because it might as well turn out to be completely wrong. It forces me to gain enough confidence in my perspective. Having enough confidence is one thing, but that still leaves me in finding the words to shape an accessible narrative in describing a new paradigm. This is ultimately the point of the book and I figured the only way through that problem is iteration.
I am passed the point of diminishing returns on my narrative iterations, so the only thing that is left to do is put is down on paper definitively. So there you have it, my new years resolution. Basically the same one I had last year, but it is what it is.
Merry Christmas Nostr.
https://cdn.satellite.earth/3d9fcab72c20ee6bb4c8a3e54e2490dc7e281b643f4ce24ba8954a60e40d4ebe.mp4
Amazing ✌️
GM Nostr! 🌞
🎁 Announcing Keycast 🔑
A remote signing platform for teams.
https://share.cleanshot.com/y4XbqKpT
Remote signing (NIP-46) has always had a lot of promise. Apps like Amber, nsec.app, and others have made it possible to manage your nostr keys in a way that is safer than browser extensions or pasting your nsec around the internet.
BUT, none of them catered to teams. Groups like nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l and nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk and many many companies out there are just sharing the main account nsec between different people and using it in different apps. A recipe for disaster.
Keycast aims to finally fix this. It allows you to:
- Manage teams of nostr users
- Manage multiple keys that you want to give others access to
- Create authorizations for those keys that grant specific permissions that can be changed, revoked, etc.
- Create your own custom permissions
- Run the signing infrastructure without any extra work
And do it all in a self-sovereign way. Keycast is meant to be run on your server, by you. I think it's tremendously important that this sort of tool doesn't exist as a hosted service (which would basically be a huge key honeypot over time).
The app is both a management web app AND a backend process that manages sub-processes that listen for remote signing requests, check permissions, and sign events.
There is a basic docker setup to start, but my goal is to have this easily deployable to StartOS, Umbrel, Podman, and others.
Code here: https://github.com/erskingardner/keycast
Ho ho ho 🧑🎄 that’s very cool 🫶
GM ✌️🎄
So far only NWC can bring some of this functionality I think.. Maybe just a monthly/yearly DM asking to pay is also less of a requesting model to implement without having to deal with the wallet interoperability stuff that NWC brings, but there should be some cashu ways to implement this with time lock & lock to key stuff right ?
Goedemiddag https://v.nostr.build/b9JomRmOAyzwvWzp.mp4
Desperate times 😅
Bedankt voor je bezoek https://v.nostr.build/Ic6rFZBtOhP0auGn.mp4
Boop 
Any future plans of implementing it with Bip353 ?
#nostr should be much weirder 
Heard some great talks today about simple component driven architecture within meta frameworks,.. reminder to post links here ✌️
Pitching #Nostr in about 24 min … don’t think there is a live stream but a video should be released soonish ✌️
Next time it’ll be a proper Zap ⚡️ nostr:note15wxs2p5xsvjt8dlcxqqe7etzf4taqzmv7ynwgw552fvll439apuscgr4hn
Worked great 🔥🫡


