I've actually built a fully non-KYC service before, and the ...

原始 JSON

{
  "kind": 1,
  "id": "8a6ca18064c25dcf2ba10dc5a0759d2f5a36edf2f2e864253c228bbad8b03f97",
  "pubkey": "0aea075b010fb595d6814f5633008e870d77a2c43d4dda1544e8730e00995144",
  "created_at": 1779236774,
  "tags": [
    [
      "e",
      "efafb852d21957cf72cbeee3c75f07550a9babfc489c2d89c8e8070ef2394009",
      "wss://nos.lol/",
      "root",
      "f8e6c64342f1e052480630e27e1016dce35fc3a614e60434fef4aa2503328ca9"
    ],
    [
      "p",
      "f8e6c64342f1e052480630e27e1016dce35fc3a614e60434fef4aa2503328ca9"
    ]
  ],
  "content": "I've actually built a fully non-KYC service before, and the thing is, it becomes extremely vulnerable to spam attacks. Then you end up piling on all this complexity just to mitigate it, and from the user's perspective the UX becomes genuinely awful. Anyone on Nostr probably feels this to some degree... and then what happens is maintenance becomes a nightmare, users go \"wtf is this, it sucks, I'm out.\" That's just how it goes.\nThe other classic solution is using reputation to filter spam — but then we basically just killed the whole point of anonymity",
  "sig": "0fa2e41890d38b29c8c7878b8cc221bea64c3fe62a8a700a8e516dcfbbac63d01ea7be04cff546d532cdd632b2388d8a35dfef539d0c4ea471735d78ced95337"
}