I support this message, if only because NIPs should have 2+ implementations before merge.

Reply to this note

Please Login to reply.

Discussion

Implementations don't make something better. NIPs already have lot of things that were not required.

Eh, nips are for documenting common practices. If clients want to let users virtue signal, it's good to agree on how to do it

I don't have any issues with pronouns. I care about things that really affect nostr.

I have issues with pronouns πŸ˜‚. But do you mean that defining fields in kind 0 affects nostr negatively?

IMO the standard has been fixed in place for over a year and mechanisms for extension without breaking many existing implementations is more the issue

most apps will have no problem adapting or ignoring these extra fields, probably, because they are not making any assumptions about the key names in the object in the content field

my main issue is just that you don't put things in the nips without having two working implementations. period.

Working on that…

https://github.com/planetary-social/nos/pull/1695

Seriously though, why do folks think free speech is only a thing for the kind of speech they like?

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.

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