If I want to add a unique feature/API to a Nostr relay is it better to create a new Kind and pass in the contents as a new event and the relay can process it, thereby being compatible with all relays? OR should I just create a new http path based API endpoint in the relay that is unique to just my app? nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcpz4mhxue69uhkzet8d9ejuat50phjummwv5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5zgwjy3 nostr:nprofile1qyw8wumn8ghj7un9d3shjtnzd96xxmmfdecxzunt9e3k7mf0qy2hwumn8ghj7un9d3shjtn4w3ux7tn0dejj7qpqutx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4sau8ykj

Reply to this note

Please Login to reply.

Discussion

Depends on the feature.

But as rule of thumb if you don't think there are gains from it being made an interoperable standard then a new HTTP path is ok.

In any case it's always ok to start with an HTTP standard and change later.

“HTTP _path_“ (not "standard" in that last line, right?)

Yes.

whatchu buildin over der, bobby?

Just starting playing around with my first nostr UI so trying to get a feel for the conventions etc. Nothing too exciting yet unfortunately.