great chat @jb55 with Odell, agree with you wrt relays, outbox/inbox, re-balancing 👍👍
I’m catching up on the relay side, new Go sdk encapsulating and polishing existing solutions => goal is to enable and produce many experimental, performant relays in Go - personal, public, group, local, …
I’ve been thinking a relay could do ~something vaguely like~ publish its own kind0 .. / negotiate with clients to expose via standard format it’s capabilities, policies, NIPs, read/write/other perms that clients could parse, and inform focus/alternate view mode/context? 🤔
a nostr Identity (user or agent) has an nsec (or just npub, if non-signing)
npub gives us (via relays) lists of events of various kinds, so profile and all .. 🤔
What else is there, at the core of #NOSTR Identity, or is it just 🔑 all the way down? 🐢🐢
would a global geomagnetic induction event, along the lines of Carrington but more of a quadrupole-dipole “jump start” … travelling through every inductor on Earth …
would that effectively produce localised EMP, or at least some sort of sympathetic-harmonic field resonance ~Schulman..? 🤔
⚡️ 🦠
gosh I could spend another month / half-dozen point releases just on a single type: Event{} 🧐 #golang #nostr
simplify/reduce dependencies, inject pluggable .With() opts… then all the lightweight ingress/egress types and helpers, example this or that, docs comments, more tests, some
khatru/go-nostr compatibility shim tests, final polish..
itching to get to Client and Relay but yeahnah we doing this 🙏 gonna be worth the time spent for sure later on 😁
obviously this is very, very early
but once I hit 95+ coverage and polish
I'll call this Event{} release ~v0.0.1 of goNDK
appreciate any #golang 👀 #nostr reviews 🙏
just what is an Event?
* what does it do?
* how could we do that safely, more predictably, faster, ..?
* what does the spec say?
just what is a Client?
* …
I’m having fun, because it’s #nostr and because it’s #golang