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.
Waterdan /
npub1dww…pdnf
2024-06-06 18:38:45
in reply to nevent1q…wwm8
Author Public Key
npub1dww6jgxykmkt7tqjqx985tg58dxlm7v83sa743578xa4j7zpe3hql6pdnfPublished at
2024-06-06 18:38:45Event JSON
{
"id": "6beb90fe35b8b60bc0241042fca71b006c147d138a0e7a997a206e38f8e1db85",
"pubkey": "6b9da920c4b6ecbf2c12018a7a2d143b4dfdf9878c3beac69e39bb597841cc6e",
"created_at": 1717691925,
"kind": 1,
"tags": [
[
"e",
"6d108d939dbcbf51f19156e3ec44a08f92f5eb73ba8329d983b6dcb4bfdd8268",
"wss://blowater.nostr1.com",
"root"
],
[
"e",
"55df2d0db6d1683a4096ddc6462094b26cce68fac81f95556aa69a4c950a5b95",
"",
"reply"
],
[
"p",
"7abbf3067536c6b70fbc8ac1965e485dce6ebb3d5c125aac248bc0fe906c6818"
]
],
"content": "I don’t know the answer but I have some important questions to consider:\n\n1. If the legacy browser API is designed poorly, do we really need to design Nostr in a way that makes legacy API happy? \n2. If we want to be innovative, shouldn’t we be brave enough to throw away the legacy infrastructure all together?\n\nBold statement:\nNative clients, desktop and mobile, will be where we win and they are overlooked.\n\nIf Nostr is really the next gen protocol, it needs solid implementations in system languages such as Rust and Zig in both SDK and applications.",
"sig": "0b6985c4a3a86f2cb91859964eab47d9adf78b0342270d960452e6984b370c4a41e72cce2224e0dbe1951e9eb21ca8aa92eaa8b00777bc02a681f58c52cbe072"
}