Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 1
Generated: 14:16:20
Any kind of Service Provider thing over Nostr is a waste of kinds that can be reserved for better stuff. At least, when providing such ideas, use one kind and make them different with a tag to show the type of request. Not just reserve another kind that probably only you need until the end of world. If you want to make a new HTTP API, you don't update the HTTP RFC spec, you define your own routes and stuff by changing parameters that you have access. So if you have a new service over Nostr (Using a DVM or anything similar) just use the same kind with a different tag, maybe called the type or function. nostr:nevent1qqs2fptqrvu2ah27rlkuj00un8ns27cpq3jy6yu7ttg7mzcw905c7rspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyrjjwt0fzj7nq964csum3rnftxjre8fxvjp37zfu285u0xdpdggz7qcyqqqqqqg4yj0wu
2025-11-17 11:19:47 from 1 relay(s) 1 replies ↓
Login to reply

Replies (1)

Two of our newly proposed WoT NIPs, Trusted Assertions and Decentralized Lists, both of which you can find at NostrHub.io, are each frugal when it comes to event kinds. Some people would have used a new kind for each trust metric, but Trusted Assertions uses a different tag for each metric, which I think is exactly what you’re suggesting. Decentralized Lists uses the z tag to point to the list header and doesn’t use up nearly as many kinds as NIP-51. So I think I agree with your basic philosophy.
2025-11-17 12:25:27 from 1 relay(s) ↑ Parent Reply