I like the idea of removing it from the spec
Sure, but if something is agreed upon to be a bad idea and the few implementations that exist implement the bad idea, removing it from both could help prevent a bad idea from spreading.
I’m sure nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy added the L tag without looking at it too much: “it’s in the spec, the only implementation uses it, I’ll copy it”
Discussion
LFG! 🙌
I'll draft a PR. It won't be backwards compatible but the json has little enough adoption I think
ACK
Ok, so maybe this won't work, I was fixing my explore page this morning, and it searches by namespace. If we had prefix searches on tags still we could bake the namespace into the tag and use prefix search, but I think that's gone? Anyway, reviewing the design I now remember why it ended up the way it did.