Replying to Avatar Melvin Carvalho

Nostr is better as an API than as a protocol. It might end up as either. If it's an API it doesnt need to scale, because it inherits scale from http. So you use the API and are happy. I think that's where it will end up, but it could go either way. Both are good outcomes.
d5
bloblob 1y ago

What do you mean as an API?

Can you give a small example?

Reply to this note

Please Login to reply.

Discussion

Avatar
Melvin Carvalho 1y ago

The analogy is that you have a working system and add an API, ie add nostr. Rather than using nostr as a starting point. So, say, activitypub could use nostr for realtime updates. Git could use it for single sign on. Twitter could use it for micro payments. And so on.

d5
bloblob 1y ago

Ok I see.

Do you think for streaming audio nostr could be useful for infrastructure?

I am not sure if it match with the notes thing, so I am not sure it's relevant for this use case.

Avatar
Melvin Carvalho 1y ago

I think nostr could help do the handshake, then you figure out where the audio files are. Then stream it client server, or through an audio relay. So if nostr is just an API you can figure out what tool to use, it might be nostr, it might not be. As a developer you have freedom to choose.