You are trying to solve the problem that spam exists on rela...

Raw JSON

{
  "kind": 1,
  "id": "f4654c846e9575cbdc66c2e8b2ba61b9d3d8263d9344552ee629f6db6afc99da",
  "pubkey": "52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
  "created_at": 1780858480,
  "tags": [
    [
      "e",
      "00003b57d9c7575fadd4eebd01ceeccf89c3885edbc34b06282bd88ec06ed4ba",
      "",
      "root"
    ],
    [
      "e",
      "00000351c7a90c5eaab14f754991784916e6ba6312ef9c9e1845fa3367698c54",
      "wss://nostr.land",
      "reply",
      "00000000827ffaa94bfea288c3dfce4422c794fbb96625b6b31e9049f729d700"
    ],
    [
      "p",
      "00000000827ffaa94bfea288c3dfce4422c794fbb96625b6b31e9049f729d700"
    ]
  ],
  "content": "You are trying to solve the problem that spam exists on relays.\n\nTo do this, you need to distinguish what is likely spam and what is likely ham.\n\n“Adaptive” PoW only works if you know if the content is spam or ham.\n\nBut the entire point is that we don’t know this and want to find it out. And PoW provides no information about spam/ham.\n\nSo, why bother? Instead of disproportionately disadvantaging your average user with PoW, you can work on methods that can reliably identify spam/ham and implement ratelimits instead of adaptive PoW. (which don’t make the UX suffer for the average person)",
  "sig": "d08c0fa41b852fca90cd8f8b349fc01526c63e6b93f9d27a4d2e867b103f7398954433b515dc444006057c28435950523fe28e672c81105c530f0ce75f1b64b8"
}