A diversity of implementations solves Hyrum's law, in which implementation details are transformed implicitly into interface guarantees. Nostr has some gross conventions (like error: prefixes on OK messages), but the compensation is that every implementation chooses different wording, and so clients have to be pretty ambivalent about relying on how messages are parsed. This reduces reliability, but improves compatibility.
https://lawsofsoftwareengineering.com/laws/hyrums-law/
hodlbod
npub1jl…jynqn
2026-05-06 16:18:48 UTC
Author Public Key
npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqnSeen on
wss://nostr.momPublished at
2026-05-06 16:18:48 UTCEvent JSON
{
"id": "c20677aaad8c5a16c81d690625b2aa73050bdf39131e80bbb50cdf425c94137b",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1778084328,
"kind": 1,
"tags": [],
"content": "A diversity of implementations solves Hyrum's law, in which implementation details are transformed implicitly into interface guarantees. Nostr has some gross conventions (like error: prefixes on OK messages), but the compensation is that every implementation chooses different wording, and so clients have to be pretty ambivalent about relying on how messages are parsed. This reduces reliability, but improves compatibility.\n\nhttps://lawsofsoftwareengineering.com/laws/hyrums-law/",
"sig": "574e787ef40a9a64ed6ba226e81986cc0794a4a9d3e60c23a94bcd37f5e76338cdafe87bff1d7c77e317f8f0b127c081dcc747d1f432bdee7d0a02b2a7df9f03"
}