Replying to Avatar powrespecter

I'm not saying tha REST is the right way to go. Just that it would be nice if a client to request POW (over a websocket is fine) without having to implement the auth nip.

And I can't imagine how a deep dependency graph could ever be a good thing. Modularity is one of the most important principles of design. You should be able to pick and chose which nips you implement without having to parse through a tree of interdependencies.
Avatar
Blake 2y ago

Sure. I’m not pro coupling code or dependencies.

If the only change is a pubkey added to the minimal request, we can do that.

However, keep in mind the request itself [“POW”, {}] is like other Nostr relay commands anyway. If you wanted different format for that too, then we start to diverge into really different approaches.

I’m not running a PoWSP, even using my codebase. I put this together mostly as protection if we need something urgently for spam or similar attacks. We have time to experiment - we need clients first anyway.

Reply to this note

Please Login to reply.

Discussion

Avatar
Blake 2y ago

Also, likely worth adding your thoughts here. On Nostr I’d had more positive support, but on GitHub it’s less encouraging. https://github.com/nostr-protocol/nips/issues/340