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. View quoted note →

@Vertex is suggesting a way to get follower counts, filter out spams or even get suggestions to follow or see. If we get an standard interface to it, clients can behave it like a Blossom server or a relay. You can just use a public/private (self-host) / paid Vertex server and then your client will use it to filter spams, show follower counts (don't need heavy queries, and you can self host if you don't trust), and get content and profile suggestions. I think that standard interface is its DVM now. HTTP/WebSocket interfaces can help too. If people are going to finish DVMs (I don't know the current state).

https://npub1hu47u55pzjw8cdg0t5f2uvh4znrcvnl3pqz3st6p0pfcctzzzqrsplc46u.nsite.lol Just published latest version of @Raxva 🪽 website on Nostr. URL is too long. Soon I'll do some stuff to make a shorter one. 🥶 #nsite