It’s very different from NIPs.

577de06dce160a03...

npub12a77qmwwzc9qx7gk8f9m0d5qhclq5rsudr0xu6agcqgnfdzqvnwsfrrdyd

hex

4cd88963283cb3c2b4ac57cdd0c9ab7f65900a542bbc434dc42d0aa8b51f06a6

nevent

nevent1qqsyekyfvv5rev7zkjk90nwsex4h7evspf2zh0zrfhzz6z4gk50sdfsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs9wl0qdh8pvzsr0ytr5jahk6qtu0s2pcwx3hnwdw5vqyf5k3qxfhgc0ak6q

Kind-1 (TextNote)

2026-07-27T18:00:27Z

↳ 回复 semisol (npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj)

It doesn’t. This is no different than the current hell, except instead of kind numbers it uses strings.

It’s very different from NIPs.

For one, lexicons have no pretense that there is or will be interoperability. They assume that there isn’t, in fact. But lexicons do assume that at least one developer is using them (it’s under their namespace).

NIPs are the opposite. They assume interoperability, but in reality zero apps are using them.

There is only hell if we impose it upon ourselves. Basically, it’s all about expectations and ownership. Nostr does both terribly.

原始 JSON

{
  "kind": 1,
  "id": "4cd88963283cb3c2b4ac57cdd0c9ab7f65900a542bbc434dc42d0aa8b51f06a6",
  "pubkey": "577de06dce160a0379163a4bb7b680be3e0a0e1c68de6e6ba8c01134b44064dd",
  "created_at": 1785175227,
  "tags": [
    [
      "e",
      "db3b178ee4f98bc9fcd5cf425cb208eda3a960b29b2984693922c0f3c1898267",
      "",
      "root"
    ],
    [
      "e",
      "e9f093e772335238ee53e8d76d41366f56ca6d8561c11a3e680bd9e24ad5ee82",
      "",
      "reply"
    ],
    [
      "p",
      "52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
    ],
    [
      "p",
      "577de06dce160a0379163a4bb7b680be3e0a0e1c68de6e6ba8c01134b44064dd"
    ],
    [
      "client",
      "Nostur",
      "31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
    ]
  ],
  "content": "It’s very different from NIPs. \n\nFor one, lexicons have no pretense that there is or will be interoperability. They assume that there isn’t, in fact. But lexicons do assume that at least one developer is using them (it’s under their namespace). \n\nNIPs are the opposite. They assume interoperability, but in reality zero apps are using them. \n\nThere is only hell if we impose it upon ourselves. Basically, it’s all about expectations and ownership. Nostr does both terribly. ",
  "sig": "de2ab76bf9ce13b792cdbfb1ccfad88e4545fef8cf948560d99633ba9b9fc23ded7bd39a7f3c34b9ae3ea6ad6c26d9bcb1ee9d28941c323ffd019503384a74e6"
}