fiatjaf on Nostr: Not really, you shouldn't try to force new stuff into old buckets. Well, honestly, I ...
Not really, you shouldn't try to force new stuff into old buckets.
Well, honestly, I really don't know what is the true and good way to do things, but the reason why I don't like that NIP is that it's proposing a top-down list kinds that only fits one specific app and one specific usage flow. Maybe that is ok in this specific case, maybe not, but it smells like you're trying to take a model conceived for a proprietary platform and translating it into event kinds, which doesn't benefit anyone.
There is nothing wrong with doing these things with just an HTTP API. The only reason why you should be doing it on Nostr would be if multiple clients could join and leave in every step of the process and deal with these events in slightly different ways. Otherwise this is probably better as a standardized HTTP API that many different providers could implement, for example.
Well, honestly, I really don't know what is the true and good way to do things, but the reason why I don't like that NIP is that it's proposing a top-down list kinds that only fits one specific app and one specific usage flow. Maybe that is ok in this specific case, maybe not, but it smells like you're trying to take a model conceived for a proprietary platform and translating it into event kinds, which doesn't benefit anyone.
There is nothing wrong with doing these things with just an HTTP API. The only reason why you should be doing it on Nostr would be if multiple clients could join and leave in every step of the process and deal with these events in slightly different ways. Otherwise this is probably better as a standardized HTTP API that many different providers could implement, for example.