{"type":"rich","version":"1.0","title":"Innis wrote","author_name":"Innis (npub1l3…5cxyz)","author_url":"https://yabu.me/npub1l33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlqk5cxyz","provider_name":"njump","provider_url":"https://yabu.me","html":"Released innis/nostr-core today. A PHP library for the Nostr protocol. Clean architecture, immutable domain objects, pure functions. The protocol layer separated from everything else, organised around domain concepts rather than NIP numbers, strict enough that a relay, a client, and a web application can share the same core without compromise.\n\nnostr:nprofile1qqsqvcu68pkfcyq5y9mz9n9u7sys33835rpnuglc6mtg7j4lv40c7ugpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqglwaehxw309aex2mrp0yhxummyv4e82mnwv4e8xtnwv468wmmjdvq3jamnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk64709kz and nostr:nprofile1qqsd8vn40hzezrfcespw5m23gx0t9hn5lvgfw9jsr4a2wuexxkulzxcpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakqzxrhwden5te0dehhxarj9eexj6mdv45k5etj9ehxcmp8v0y did the early work with nostr-php and nostriphant when there was nothing to build on and I am grateful for it.\n\nThe relay and the client and several things built on top of them are written and working. They are being reviewed and cleaned before release, though past lessons remind me not to let that become an excuse for delay. The core library went first because the architecture needed to be public before anything else.\n\nAI was involved. Not as a replacement for knowing what I was doing but as something closer to a second pair of hands. The architecture is mine. The decisions are mine. The machine was useful in the way a good tool is useful, which is that it did what I asked it to. At least most of the time.\n\nhttps://github.com/johninnis/nostr-core or composer install innis/nostr-core\n\n#nostr #php #opensource #nostrdev"}