Saved Drafts on accidental swipe down please 🙏 I’ve lost so. many. posts. 🤣
OR
should I just keep the good stuff behind more useful dirs/ and have a stub at top?
OR skip the stub and top-level go.mod and spin up N individual dir/go.mod sub-projects rather than 1?
naming being one-of-two of the hardest problems, behind cache invalidation and off-by-one^H^H^H but throw in repo naming and package naming 😖
nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg when saved drafts? Risky UX 😬 have lost so many posts as fingers accidentally swiped
HELP i need a better name for this #golang repo for #nostr 😭 Any ideas? 🙏 🙇♂️
goNDK (no capitals sob)
gondk
gondo
gonzo
ndkgo
nostrgo
gonostr
gostr (already a client)
Yes, project’s goals are ambitious, so a suitable name to reflect this: cohesive, well tested, injectable, idiomatic low-level types and funcs, interfaces for rapidly prototyping and building out prod-ready solutions, at scale 👍A common base layer, other layers above. Smallish and focused first repo, intended as a solid foundation.
The problem is Go couples the repo name with the top-level package name, and package naming standard is lowercaseoneword, so I can’t use the ideal goNDK or goNOSTR as every symbol import you’d have to type that out …. 😬
Any ideas for a name? 🙏
WOW the long-term #nostr implications just hit me, after first-use of #nostrnests 🤯
holy crap, DROP EVERYTHING LOL
nostr:note16hdqufpzfqlrfjt6qlq0ssra9v0rdpuef8a20rdlzkcyf78fx0mq4p55yj
Focus & Finish…
Thank you nostr:npub15u3cqhx6vuj3rywg0ph5mfv009lxja6cyvqn2jagaydukq6zmjwqex05rq & nostr:npub1chakany8dcz93clv4xgcudcvhnfhdyqutprq2yh72daydevv8zasmuhf02 for embodying what building within the Nostr community is all about with the Zap.Cooking project.
nostr:npub1hqaz3dlyuhfqhktqchawke39l92jj9nt30dsgh2zvd9z7dv3j3gqpkt56s and I really enjoyed this show and we appreciate the #Plebchain who joined us live during the Nostr Nest.
For those that missed this episode…. as always, listen on Fountain and support V4V! 💜🧡
That blew my mind, even though I arrived late, and was so completely distracted (trying to get my own mic perms fixed so I could .. hear? 🤪 then couldn’t hear one speaker) that … I actually missed the content live 😭
#nostrnests is what blew me away - I had no idea what it was at first, I’ve only just enabled my keystore … 🤬 🤯 I wasn’t expecting that many event kinds, such a polished UX, let alone the core audio and recording features, chat, … ! Wow, this changes … holy crap, yep that final (architectural-implications) penny just dropped for me 🫨
Luckily the show has already queued itself up on nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 👍
🤯
wow how many patch-ssh
parties have we had now 🤪
#nostr can fix #distros
infra to help automate binary checksum verification at fork/exec sys/kernel, and help facilitate wider use of read-only filesystems 🎉
unified memory.. quantum optics.. execute-in-place.. huh computers might one day be capable, theoretically, of actually being made secure .. one day 🤞
yep that's the plan, several layers built out at once with first product exercising them, and open the foundation to encourage parallel and similar value-adds, work up the stack from there Cheers man
🎤 🚰 🚰
2…2….. Is this thing on?
Hi 🌊 nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 how would you describe or compare the goals of these repos?
https://github.com/fiatjaf/khatru
https://github.com/nbd-wtf/go-nostr
This weekend I will start something like ~gNDK~ a bunch of Go types, funcs just simple foundational building blocks to start but same aim as NDK to encourage and simplify adoption and development, then optimise and build on top of this some reference relays, outbox, clients, filters, tie in with any reference nip code…
Does it fit in with either of those repos, any other projects, or should I just start afresh with its own focus? 🤔
CITADEL DISPATCH 122: NOSTR DEVELOPMENT WITH FIATJAF, HODLBOD, PABLO, AND DILGER
- nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6, nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft, nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
Gold, thankyou gentlemen the path presents itself 🙇♂️ and I’m only halfway through the ep 🤣 nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
Strange investment strategy: buy up all of the banks ATMs and their cash business … step 2 … go out of business … step 3 cashless society 🎉
perhaps un-adopt first name in favour of “shared secret” as a safer way to think about this?
the #nostr “phone” …. modern client hardware, mic and speakers no 3G/4G/5G 👍👍 #takemymoney
good follow-up to #satslink hardware switches per radio, perm disable traces, LEDs for mic cam wifi disk … 😴 💭
nostr:note1d73sc3nrpcwpjkumhvupm6cfvrwwfrdtw6vkeact6u7dkw7cdn0smwqcmh
So who is making the modern ~iPod Touch~ a device with no 3G/4G/5G baseband??
just regular old 802.11xx non-beam forming 2.4GHz, full access to bootloader, a modern “Privacy Phone” with
**NO PHONE**
baseband / Broadcom chips?
💥 BitcoinMints.com 💥
We just launched the first place to list and review Cashu mints leveraging #nostr as the discoverability and identity layer.
Cashu is an ecash protocol that will enable https://makeprisms.com users to send millions of #bitcoin payments with one click.
BitcoinMints.com is a Nostr client that uses NIP-87 to publish and review mints.
$boost
nice one nostr:npub1cd0l3s6qgj0s6690rtkys39mgj5upwxpm4856nhmce0pyqu6xj9qh7xlvx , any plans or ETA for QR codes so we can easily scan into eNuts? 🌰 🙇♂️


