nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyt8wumn8ghj7mn0wd68ytnxd9kx6am9vgh8qmqqyz4cewqwtep2t3zleu9xc2t7wk93zw58m2js9zcskg4c4h6njh2syetct3f invited me to give a brief demo of Nostrly on the nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0s0pfy4z community call today.

Here's a quick summary of the technology behind it:

🟣 The site is built on WordPress, with webpacked Javascript doing the lifting on the front end with the help of Nostr tools and NDK.

https://github.com/nbd-wtf/nostr-tools

https://github.com/nostr-dev-kit/ndk

🟣 It uses NIP-98 authentication to login to WordPress, with backend Nostr authentication handled by the Nostr-PHP SDK

https://github.com/nostrver-se/nostr-php/

🟣 Registration payments are proxied through the Alby Bitcoin and Lightning Publisher plugin to my nostr:nprofile1qyxhwumn8ghj7cnjvghxjme0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyzjnd2cl0u7qzva64k7lgu4343adfdm5a4pjcxvf9pqex4e83z72qngxhfg .

https://wordpress.org/plugins/bitcoin-lightning-publisher/

I chose to proxy registration payments through Alby BLP because it implements BTCPay Greenfield API out of the box, provides flexibility for the future (eg: switching to NWC) and records payments in WordPress for ease of administration.

🟣 Web Zap, NIP-19 decoder and Public Key Converter are all front-end only tools build using Nostr Tools SDK. The confetti effect after payment uses canvas=confetti.

https://github.com/catdad/canvas-confetti

Happy to answer any questions