Been a while, because life happened. In the meantime the relay and client components have been extracted from #transpher and can be included into your own project as a composer dependency.
It does not entail much as of yet, but ideas are:
- nostr login
- notifications
- talk integration
- data/compute vending
What would you like to see?
Starting a new project: nostrifying #nextcloud https://apps.nextcloud.com/apps/noxtr
I already knew that #PHP is
+ a dentist in The Hague,
+ a Banana plantation in Cameroon,
+ an airport in North Dakota,
+ a French Rear-admiral,
+ a Highway patrol in Pakistan,
but TIL it is also a hairdresser in slovakia.
And you? What is your own special #PHP meaning?
https://www.exakat.io/en/what-does-php-mean/
It is also a currency
Still plenty to do, but after building whitelisted storage I feel confident on releasing v0.1.0. Only events authored by the relay owner or a pubkey on their follow list is being stored. Preventing unwanted notes to clutter up your relay. https://github.com/nostriphant/transpher
https://github.com/nostriphant/transpher switched to a sqlite backend, performance improvements and working on whitelist whose notes are being stored (currently only the owner and agent). Others notes ARE relayed to subscribed users.
Extended nostriphant/nip-19 with support for #nprofile, #nevent, #naddr and #note #bech32. Documentation is still lacking, but tests can help you get underway. https://github.com/nostriphant/nip-19
Releasing my #php nip libraries with #composer. Come and use them!
Split off the php implementation of nip44 and nip01 in separate libraries, while listening to #nostr-nl #meet-up with nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe and nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw, nice to hear people discuss their vision on #nostr. Still needs some polishing, but the basis is there...
Hi, I'm the author of secp256k1_nostr.
We also stumbled upon the invalid signature errors while working on the nostrver-se/nostr-php library and figured out the fix: https://github.com/public-square/phpecc/pull/1
However the fix never got merged, so I did yet another fork of phpecc that includes it in case someone really needs a working PHP implementation of Schnorr signatures (uma/phpecc v0.1.3).
Besides the poor speed the problem with phpecc and all its forks is that they are not maintained at all (including mine!). Relying on libsecp256k1 is way better.
That's the next step then, thanks for your heads up!
Split off #nip-19 in library repo https://github.com/nostriphant/nip19
switched over to ext-secp256k1_nostr
phpecc implementation of SchnorrSignature gave many invalid signature errors, so switching over (for transpher) to ext-secp256k1_nostr (https://github.com/1ma/secp256k1-nostr-php). For future libraries support for phpecc is desirable, because extensions can (most likely) not be deployed to shared hosting environments
https://github.com/nostriphant/transpher/commit/a8ac4d4aedcf60f0cb6ac0e0c35cca38e9905dee
#transpher #nostrifying-php
Woop woop, basic #nip-92, #nip-94 and #blossom support for pre fetching and serving referenced external files in notes. 😎
https://github.com/nostriphant/transpher/issues/25
#transpher can limit incoming events based on minimal PoW constraints. 🎉 Event id is working, pubkeys are untested. We need proper vectors for that and there are possibly some problems in underlying libraries with the pubkeys I generated...
Just added nip-45 event counts support to [transpher](https://github.com/nostriphant/transpher] 🔢🔥
Transpher now supports several event (https://github.com/nostriphant/transpher/issues/21) and subscription (https://github.com/nostriphant/transpher/issues/22) limits. 🔥
#transpher relay now has support for NIP9, event deletion requests. 🔥 https://github.com/nostriphant/transpher/issues/9
Here we go #rest2nostr proxy proposal https://github.com/nostr-protocol/nips/issues/1549
Still a lot to be done, but the presence is there, let's #nostrify the #elePHPants!