Nathan Gathright on Nostr: npub10fp3e…4qqev npub1ln5q8…5xyw6 npub1jtm4d…rrxtn A spec shouldn’t imply the ...

npub10fp3ehl8utp98zgk6lx87uwkfxm9zq6z9varapeuluz9cdf3zfvs94qqev (npub10fp…qqev) npub1ln5q8np5aezhtt7ztv6tah86xk4t3smjuchdvxp0u6uta056204q45xyw6 (npub1ln5…xyw6) npub1jtm4dxvu3ccgk60wvvt0uw9j9vz7nuc80f7agrv0vgkkushxk5zq0rrxtn (npub1jtm…rxtn) A spec shouldn’t imply the existence of guardrails where none exist. I think it’s important for our tags to be resilient to misuse or at least provide a clear way for developers to handle misuse. (e.g. if there’s two `podcast:guid` tags, only respect the first one)

If misuse isn’t accounted for, then each developer will handle edge cases differently (usually with no documentation.)