They are not keys, they're names. It's completely free-form and they have no semantic meaning. See: https://github.com/nostr-protocol/nips/pull/1593
To directly answer: the user can capitalize if they want it to appear capitalized. It's up to you.
They are not keys, they're names. It's completely free-form and they have no semantic meaning. See: https://github.com/nostr-protocol/nips/pull/1593
Here you go: https://github.com/nostr-protocol/nips/pull/1593
Custom fields have been added to #Ditto! Merged, deployed, etc. Try it out on ditto.pub.
Code: https://gitlab.com/soapbox-pub/ditto/-/merge_requests/591
Yep.
It creates a clear distinction between user-defined fields and protocol fields. User-defined fields are only for display (and only for display in a confined region of the profile), while protocol fields can actually influence the behavior of the account, like set your Lightning address or avatar.
User-defined fields are an amorphous blob the user can do whatever they want with but should not be relied upon in any way, kind of like pronouns.
Because it's impossible
No
He actually merged it 😠😂
That's crazy. I found this: https://www.abuseipdb.com/check/159.203.73.253
I think the IP was flagged before I was using it.
What the fuck?! 😂
Can you please tell me what OS/browser this is? I thought it was Windows. So I spun up a Windows VM. It's not a problem in WIndows 11 like I thought. What even is that emoji set in your screenshot? I can't find a match of it on Emojipedia: https://emojipedia.org/grinning-face#designs
This is a problem unique to Windows. On Android and iOS it looks great, and I think people prefer to see their native emojis there.
I didn't realize the situation was so bad on Windows. I'll think about what to do.
Is this happening on Windows?
No idea.
Academics will explain something simple using the most abstract language possible, then on the next page explain something obvious like you're a baby who doesn't understand anything.