This is how we did it with the user galleries at nostrcheck, nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w I'm here for whatever you need 🙂
I gotta find time for that, and it’s a rare commodity for me. PHP doesn’t have good libs, so I have to rely on nginx and njs module to write that layer and pass npub to the PHP fcgi. I wish the whole thing was written in TS, then it would have been done yesterday. I have the skeleton written some time ago: https://github.com/nostrbuild/nostr.build/blob/main/libs/NostrAuthHandler.class.php
🐶🐾🫡🫂💜
I don't know if it's a bit crazy, but what about installing an instance of nostrcheckme server and implement this part for nostr.buid? There are several endpoints, and you could use only the NIP98 part (or whatever you want of course). In fact my idea is that the software can be used for any backend in nostr, reaching the final goal that any user can install it in umbrel for example.
Then the clients should only have a section to specify the URL of the backend server (multimedia, etc).
I totally discarded PHP to advance (a little) to the rhythm of nostr, because otherwise it is impossible 😅
Another advantage, Amethyst already has it implemented for nostrcheckme server, changing it for nostr.build will be very easy for them.
That seems like having an extra dependency that needs servicing. Idea is not very crazy but completely will grow exponentially, and I’d like to avoid that. I already want to migrate to Laravel which should make things much easier, plus diversify of languages and technologies is good, so we all don’t hit the same bug or roadblock at the same time. Thought? 🐶🐾🫡
