mplorentz on Nostr: Yeah as a client dev I can’t even begin to keep up with all the NIPs. Fragmentation ...
Yeah as a client dev I can’t even begin to keep up with all the NIPs. Fragmentation is going to be a big challenge for Nostr. But as long as we can keep deprecating or fixing mistakes (like how NIP-27 replaces 8) then I don’t think we need to slow down. At some point things will shift and maintaining backwards compatibility will be a serious concern. At that point I think more formalized standards bodies will be needed. Not necessarily a single standards body, but coalitions of apps that want to work together will need to agree on things.
Published at
2023-04-25 22:59:55Event JSON
{
"id": "9fcb368aec7b3f73a3885db6f71a8e82c3a3445762af2517a4b0b6b06021bd0c",
"pubkey": "d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e",
"created_at": 1682463595,
"kind": 1,
"tags": [
[
"p",
"b2dd40097e4d04b1a56fb3b65fc1d1aaf2929ad30fd842c74d68b9908744495b"
],
[
"e",
"5501edc34d960d9c06bed71f0cb73dd999e4dfb87ffed8cc96a18037e2b6435b",
"",
"root"
]
],
"content": "Yeah as a client dev I can’t even begin to keep up with all the NIPs. Fragmentation is going to be a big challenge for Nostr. But as long as we can keep deprecating or fixing mistakes (like how NIP-27 replaces 8) then I don’t think we need to slow down. At some point things will shift and maintaining backwards compatibility will be a serious concern. At that point I think more formalized standards bodies will be needed. Not necessarily a single standards body, but coalitions of apps that want to work together will need to agree on things.",
"sig": "098f346e0311fe279a9dc3720b745991f91c0adf5daf4bb3d4a4708eb32bd8bbdb8d60f2c4791c664e7f929acae5fd16ca93d5a889fc2a22eee52ed4f1f47adb"
}
