nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spzfmhxue69uhhqatjwpkx2urpvuhx2ucpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxtnnda3kjctvll3q2p wasn't wrong about it being a potentially neutral and totally optional feature. 

But neither was nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhhyetvv9ujuat50phjummwv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qg4waehxw309an8yetwwvh82arcduhx7mn99uuwx66a wrong that it's bloat - the profile field is flexible enough as is to support this already and it's unlikely any special computational privilege is needed for this field, especially considering it won't be normalized (if Rabble gets his way and it's a flexible field). 

nostr:nevent1qqstg0h37237pldcp4u2msa9k3wjjgpkpezcz6mv385u54sh3d2gldspz9mhxue69uhkummnw3ezuamfdejj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqzlz7kzl