Because people. 

 Because they came to nostr for their kind of speech, and didn't realize that in order to keep it they have to let other people talk too. Many such cases. 

 again, say what you like on your feed, and in your life. but keep politics and religion out of the protocol. 

 ok snowflake. 

 projection, little boy 🙂 

 i’m not the person upset about what other people say.  

 i wish you the very best Rabble ❤️ 

 Don't conflate protocol spec with free speech. Anyone can add anything they want to profile metadata today, and nobody has a problem with it.

There are hundreds of fields we *could* add into the spec, pronouns are probably middle of the pack for demand, it doesn't exist in any clients, but you unilaterally merged it without any discussion and input from anyone. 

Anyway, nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhgprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqgcwaehxw309ahx7umywf5hvefwv9c8qtmjv4kxz7gpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7s3al0v made a very good PR that allows users to use any fields they want without standardizing them directly into the spec, we would love to get your input on it. 

 https://github.com/nostr-protocol/nips/pull/1593 

 I think if we do a flexible system with free form we should also define in the nip the conventions that a bunch of nostr apps are using in order to make it easier for those who want to support new fields to know the naming. 

Like for the ethereum folks is it eth.address or ethaddress or eth_address? @Alex Gleason 🐍 ’s proposed nip should be popular because it’ll allow support for linking to every kind of crypto wallet address. ;-D 

 You suck, and your fucking bots. This is freedom of speech!