If you develop a Nostr SDK in any language or make a Go-based Nostr client, please drop a link below
Login to reply
Replies (2)
In the end it is all NAK anyway (which is in Go)
Building, slowly. The #PHP libraries are mature. The products I have built with them are in daily use. The release is the work still in front of me.
And released innis/nostr-demo today, which is probably not required but I wrote it anyway. Four scripts, under four hundred lines total, the whole protocol round trip from generating a keypair to publishing events to reading them back off a relay.
This is the last of the infrastructure releases for now. The core, the client, the relay, and now a demo that wires them together and lets anyone who still reads code see what the libraries actually look like in use. If the architecture is sound the demo should be boring, and it is. A keypair in one line, an event signed and published in three, a relay stood up in thirty odd lines including the imports. A short and obvious demo says more about what sits below it than any documentation I could write.
Built on innis/nostr-core, innis/nostr-client, and innis/nostr-relay. AI was involved on the same terms as the others.
https://github.com/johninnis/nostr-demo
nevent1qqs2fx8uglexndnx3ed9jx6awkms04u85t5fcatd5t6vy0x4ayzd8yqpp4mhxue69uhkummn9ekx7mqppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wsq3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdsq3vamnwvaz7tmzd96xxmmfdejhytnnda3kjctvqy2hwumn8ghj7un9d3shjtnfdehxjuew0puh5q3ql33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlqp75zx4
#nostr #php #opensource #nostrdev
View quoted note →