Gzuuus on Nostr: We need to address this and work towards building consensus. The ecosystem feels ...
We need to address this and work towards building consensus. The ecosystem feels somewhat fragmented and unclear, largely because the specification being implemented is frozen and resides in a pull request, making it difficult for everyone to fully understand. This often leads to custom implementations. However, this is a broader issue with the NIPs themselves tho. Dvmdash calls can be a good opportunity to discuss these challenges and make the specification evolve. Wdyt?
Published at
2025-04-14 19:11:32Event JSON
{
"id": "a64a0263a8164d4e2ab8300757ffdb609a1174f4d1e3e9902a4f495de66bd5c2",
"pubkey": "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451",
"created_at": 1744657892,
"kind": 1,
"tags": [
[
"e",
"57fe893b0b458b03b34b4ecd3e8b35505699bb043aec9ab7280d4ff283be6aa1",
"",
"root"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
],
[
"p",
"99bb5591c9116600f845107d31f9b59e2f7c7e09a1ff802e84f1d43da557ca64"
]
],
"content": "We need to address this and work towards building consensus. The ecosystem feels somewhat fragmented and unclear, largely because the specification being implemented is frozen and resides in a pull request, making it difficult for everyone to fully understand. This often leads to custom implementations. However, this is a broader issue with the NIPs themselves tho. Dvmdash calls can be a good opportunity to discuss these challenges and make the specification evolve. Wdyt? ",
"sig": "054b36cd16242a4ef5cc152b11626d5e618fad8934dbbb2a4db307f65d126aaba641e3715e8424aa19f476a10253082b296f577e312bca53faf0d0d1d7b07355"
}
