Oddbean new post about login | logout I support this message, if only because NIPs should have 2+ implementations before merge.
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
It misses the point. Users should control their profiles, not a centralized committee. Nostr is a protocol, not a cult. Let users choose. Have some defaults, and then users can select a number of extra fields. For example mastodon has 4, which people like alot. We can then start to add new things to nostr such as #pubky decentralized dns and true censorship-resistant. We are far too centralized right now.
Users can still add whatever they want to their profiles. I don't know why you are saying that a centralized committee is blocking it. Right now we already have 30 or so different fields on Kind 0 events. Just five of them are defined on the NIP. There are hundreds of kinds that were never defined as NIPs. This centralization idea you make of Nostr is so strange. I don't know if you are just saying things in bad faith or if you truly don't know how Nostr works. The NIP is just an interoperability point so clients can understand each other and bounce ideas off each other. It is not a W3C spec.
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.
again, say what you like on your feed, and in your life. but keep politics and religion out of the protocol.
ok snowflake.
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.
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