What do you think would be better? (Serious question)
Discussion
Depending on how we judge it.
1. I understand that supporting browsers is necessary to bootstrap the ecosystem
2. Even with WebSocket itself, the browser API does not implement the full websocket spec defined in its RFC
3. WebTransport looks more secure and flexible but I haven’t used it.
I don’t know the answer but I have some important questions to consider:
1. If the legacy browser API is designed poorly, do we really need to design Nostr in a way that makes legacy API happy?
2. If we want to be innovative, shouldn’t we be brave enough to throw away the legacy infrastructure all together?
Bold statement:
Native clients, desktop and mobile, will be where we win and they are overlooked.
If Nostr is really the next gen protocol, it needs solid implementations in system languages such as Rust and Zig in both SDK and applications.
Love your way of thinking! Great questions. I agree that we will win met good native clients👌