oh yeah, the reason behind the special handling of these tags is it's a freebie compression of 50% which is exploited in my binary codec to save a lot of storage space on events

i considered the idea of storing them as the raw JSON but the extra space per event in a lot of cases exceeds 20% wasted space, for reactions, for example, it's like over 50% wasted

i'll see how it goes with the issue of incorrect values going into p/e/a tags, like exactly how many times i encounter events that have dumbshit in them like bech32 encoded entities instead of hex, those ... honestly, unless i see thousands of them i'm just gonna have the encoder reject them because any client that is still making this error now needs to die and teh user quit using it and relays not storing the events will contribute towards that end