Gm,

Merging pronouns into our protocol spec as a joke is demonstrating that maybe we aren't serious people

Perhaps next we should add a field for number of abortions or favorite bible passages?

Keep politics and ideology out of the protocol spec, anyone is free to add any field to their bios already, it was designed like this on purpose

I'm gonna open a PR to remove this today, we should have a proper discussion about it on GitHub without nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spzfmhxue69uhhqatjwpkx2urpvuhx2ucpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxtnnda3kjctvll3q2p yolo merging things unilaterally


If it was a joke, why was it merged


Ah, the wonderful world of protocol spec debates! It seems like merging pronouns into the mix has sparked quite the discussion about what truly belongs in the hallowed halls of specifications. Adding fields for number of abortions or favorite Bible passages might just be taking things to a whole new level of...um, personalization?

You're absolutely right—keeping politics and ideology out of technical specs can help maintain a focus on functionality and interoperability. So, let that PR fly and open up those GitHub floodgates for a lively discussion. After all, it's all about finding that sweet spot between innovation and sanity in our digital realms! 💻🤖


+1 Let’s not ruin a good thing all by ourselves.


People already can add pronouns or whatever to their bio. Pronouns has nothing to do with the #nostr itself. On a client level, again, anyone is welcomed to do those changes.
On a different note, I am curious though how can this be merged on a protocol level so easily?


Zap zap ⚡


:purple-heart:


GM 🫂☕


My pronouns are npub/nsec


GM 🌞


Now just need to change the name to dumpstr and we are ready to go. 🤡


:amy:


Few..


Some people are jokes.


i don't really care if it's removed again, but i always love it when the right thing is accidentally done as a joke


I have had my preferred pronouns （and adjectives） in my profile since day one 😇


The right thing is 2 implementations before merge. At least that's what I was told.

We have zero


Good morning ✌🧡

There's already a bio. The pronouns were a joke and shouldn't be in the spec.

Least of all because they're a psyop.


:funkycat:


Link to PR please


Are the pronouns in the room with you now? Sheesh.


Well, it wouldn't be funny if people aren't triggered...

Look on the bright side: suddenly we have dozens more people interested in the protocol spec 😂


Sir/Ser


More serious people will likely fork the protocol repo, place it under a different governance, build serious solutions and render this community entirely moot. That’s the consequence.


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


Fuckin’ A


Not likely.


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


Good


how to trade
🚀🚀🚀

https://t.me/Nancy_Miller1


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.


Nah, I think we need to add cup/penis size next to pronouns too.


so, let me get this straight, not a communist or woke activist rabble tried to slam a change through to add pronouns to the user metadata stringified json... definitely not woke lol... definitely not interested in free love or non binary asexual man pregnancies and people getting tail implants to become proper kitties


he could just have added the idea of making a scheme for adding fields into the "about" field of the stringified json, then people can put what the fuck ever they want, including their penis size and preference in donuts


Wait…what? But there’s already Bluesky over there

GM Unspent! 🐸


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 was a great joke, but, cmon… 🤣


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


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.


or even saving space by informing people about the amount of your favorite donuts that can be held up by your own penis.


I’ve not even read the thread but:

👀


it still may not make sense even going back in the thread to be honest


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.


as u wish... here's one !!! 😀

https://github.com/laanwj/nostrudel/tree/2024-11-pronouns

https://media.x0f.org/0989f1685c46d46495837b95b41069526a6bbb349e44aa4d8cf1c0800ec8ea4e.png

.

https://media.x0f.org/84f6e310ef444c2b3561966d24c31ee49fbc047a621f16d6bae0101015304f08.png


If I use your pronouns, can you guarantee that I won't actually be chanting the ancient incantations that summon the slumbering lord of madness from the eldritch depths of R'lyeh?


but muh bluesky has more users dan us. we need user number go up so bad or we ashamed at infloooencer conference 😞
we have do pronoun for get angry blue hair. number!


I’ve worked for small companies that got bigger. When small, they’re like: Ooh we need a database. Then they make a field for every thought that pops into their head, not having the experience and vision for what being bigger will be like. Fast forward to being bigger. Database bloat, complex, convoluted, difficult to use, employees hate it, more staff to maintain it, can’t get rid of it bc…data. It’s not political, just about efficiency, scaling, and forethought.


no... no guarantees, u have to be really careful with pronouncing


That merge and PR was retarded. 100% agree.


well i can't disrespect your pronouns so i guess it's a risk we'll have to take 🤞


:Clap:


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.


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.


projection, little boy 🙂


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? nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p ’s proposed nip should be popular because it’ll allow support for linking to every kind of crypto wallet address. ;-D


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


i wish you the very best Rabble ❤


WTAF? Link to PR?


Gm,

Merging pronouns into our protocol spec as a joke is demonstrating that maybe we aren't serious people

Perhaps next we should add a field for number of abortions or favorite bible passages?

Keep politics and ideology out of the protocol spec, anyone is free to add any field to their bios already, it was designed like this on purpose

I'm gonna open a PR to remove this today, we should have a proper discussion about it on GitHub without nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spzfmhxue69uhhqatjwpkx2urpvuhx2ucpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxtnnda3kjctvll3q2p yolo merging things unilaterally


Lol, a pandemic & climate change denialist talking about "looking like serious people" on clown world's "decentralized protocol"


NO ADD THOSE THINGS IN THAT WOULD BE HILARIOUS


What a nice PR! 😂
https://github.com/nostr-protocol/nips/pull/1590


Let's go 🚀


Onward 🫡


We're gonna win 👊


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


believe or not, ban!