nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h From a system engineering pespective, if we can all agree on the data structure of Nostr events, why do we have to have the same API? For example, a GraphQL API over a relay can be much more expressive than current filters API. Does it really make things more complex? Not necessarily. Mainstream web systems are request/response oriented and streaming API is added later. Nostr is the other way around. It does not have request/response model for its events.
Weird, I didn't get this in my notifications but did see it in my feed.. weird amethyst bug I dunno.
anyway, ya I just see nostr as the infinity protocol.. there's no reason you couldn't do anything. When you make UIs you either end up polling, or using a websocket anyway, so why not just start with the nostr socket? 乁༼☯‿☯✿༽ㄏ
The previous note is just my frastration of that "get event by id" is a stream. It makes no sense because events are immutable.
A relay either has or does not have an given event id.
It makes client's network code a bit longer. Not a big deal but still could be better.
Ah, ya ic
it is the connection protocol for everything, just that almost nobody realises this yet, except you, because you are awesome
