Closed vitorpamplona closed 2 days ago
Looks good to me. It's entirely optional and users can put what ever text they want. Super flexible able to handle they/them, ze/zer, and Elon Musk's confusing prefered pronouns of Prosecute/Fauci.
š¤”š¤”š¤”š¤”
Nice! I am happy @rabble cares enough to move this forward for real. Let's go! š
Ps.. I am going to start sending all my or as jokes since the rate of approval seems to be better. š
Super flexible able to handle they/them, ze/zer, and Elon Musk's confusing prefered pronouns of Prosecute/Fauci.
yes... perfect
Genuinely what the hell is this.
@vitorpamplona, using a clown icon to mock people can come across as unprofessional. Nostr is a protocol, not a cult, and it's important that we avoid reinforcing any negative far right reputations or misunderstandings around it.
I wasn't aware that @rabble had merge access, but itās good to see.
User should control profiles not devs; in Mastodon, for instance, users can add four custom fields, while Solid allows unlimited customization. We need this in nostr.
After five years, it would be great to expand Nostr profiles with features like pubky and other fields. I've been documenting profile field extensibility here for reference:
Agree with @melvincarvalho.
People who are triggered by pronouns should review other NIPs, pull requests to see the real stuff that affects nostr and wasn't required.
@vitorpamplona is completely justified in using a clown emoji to describe this change lol.
If you want to do custom fields, do custom fields. I donāt see how bloating the protocol with pronouns when it can be very easily and correctly assumed by anyone who is capable of thinking and breathing at the same time is a useful or necessary change. Nor is this anything to do with politics/far right..?? What
You people need to go outside and touch some grass.
Bring back bullying, jeez. Yāall are embarrassments
Hi @Zk2u,
These kind of issues and comments pose a risk to the entire project, especially in the protocol area, where we are bound by GitHub's Terms of Service. Specifically:
Hostile Tone: Statements like "You people need to go outside and touch some grass" and "Bring back bullying, jeez. Yāall are embarrassments" are dismissive and insulting. This type of language fosters a hostile environment, discourages collaboration, and is not aligned with GitHubās requirement to maintain a welcoming and respectful space for contributors.
Mocking of Inclusivity: The use of a clown emoji to mock the addition of pronouns undermines efforts to make the project more inclusive. Such behavior alienates contributors, particularly those who value inclusivity, and creates unnecessary division within the community.
As this project operates within GitHub's ecosystem (at least for now until we move to ngit), we have to adhere to its guidelines or it creates unnecessary problems for contributors and the project area.
Consider a more constructive effort such as here: https://github.com/nostr-protocol/nips/pull/1593
Lol
Anyone can add this field if they want, but NIP-24 is meant to keep track of these extra fields that have already become de facto standards.
A more reasonable approach would be to open a serious pull request (one that isn't a ill-intentioned bad joke meant to trigger leftists or right-wingers) as a way to notify clients of the possibility, then if many of them like it and implement it we proceed to add the field to NIP-24.
:fire:
Boo.. the dictator doesn't like fun when it is against his ideology.
The place to have fun is in the clients. I would suggest adding pronouns to amethyst to show your support instead of playing games in the protocol repo.
revert improperly
Would you consider letting the community decide on changes like this instead of one person taking control? I think a more open process would be better for Nostr and for you as well, helping the project grow stronger.
trigger leftists
Could I also suggest avoiding terms like this in protocol discussions? People outside the project notice and comment on these things, which can hurt Nostrās image. For example, on the ActivityPub forum, someone said:
Looking more broadly, Nostrās a tricky situation in that their pseudonymous founder has āleftism is a virusā on his profile
This might be unfair, but as a leader, your words set the tone. Keeping the protocol area neutral and focused on technology would help Nostr grow and attract more people. Also pronouns, love them or hate them, are a de-facto standard across the entire open social web. Hopefully we can get a good solution with Alex's compromise. Thanks for considering!
The place to have fun is in the clients. I would suggest adding pronouns to amethyst to show your support instead of playing games in the protocol repo.
I was waiting for resolution on #1593, but sure: https://github.com/vitorpamplona/amethyst/commit/4a80a16473f6a0357a367e40836089c16ff463f3
The rule we decided on was that 2+ implementations need to exist before merging. This is a reasonable criteria that I think everyone should agree with.
I think fiatjaf's response was balanced.
trigger leftists or right-wingers
And then he left an open door:
if many of them like it and implement it we proceed to add the field to NIP-24
It was actually Rabble who broke the rules. But only because he called Vitor's bluff. :smiley: It was good entertainment, but not actually something worth fighting about.
I think fiatjaf's response was balanced.
Agreed.
rprounouns cannot be removed
you believe in freedom and i will show what is freedom
This was legit just
Here's the second implimentation of this change to the nip.
https://github.com/planetary-social/nos/pull/1695
I think the custom fields option that @alexgleason proposed #1593 could work but i'd like to see something there which defines conventions so folks know that it's "pronouns" vs "Pronouns" vs 'pronoun'. Basically make it clear what the conventions are for suggesting commonly used labels.
š¤”