Post AoErWeFVX2ObGAsNQe by e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb@mostr.pub
 (DIR) More posts by e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb@mostr.pub
 (DIR) Post #AoErWboUaVb7hoDm2i by e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb@mostr.pub
       2024-11-20T14:50:13.000Z
       
       0 likes, 0 repeats
       
       @0461fcbe has the best suggestion to approach profile fields imo Make the spec allow users to define their own fields instead of attempting to standardize themhttps://github.com/nostr-protocol/nips/pull/1592#issuecomment-2488744571
       
 (DIR) Post #AoErWdHx6Sl0HT0obI by 460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c@mostr.pub
       2024-11-20T14:53:42.000Z
       
       0 likes, 0 repeats
       
       Standarization is required if you want clients to do something about the fields. If they are not doing anything (just displaying) then sure. PS: You can already write your list of labels and values on the About Me text. You can just add everything there.
       
 (DIR) Post #AoErWeFVX2ObGAsNQe by e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb@mostr.pub
       2024-11-20T15:02:05.000Z
       
       1 likes, 0 repeats
       
       We have the minimum amount of fields, like display name, image, lightning addr, bio, then just display things the user wants like pronouns or location or age or whatever This list would just get massive otherwise and likely have so much contention, and still have interoperability issues when some clients do something with a field and others don't
       
 (DIR) Post #AoEs4Dr2AnuJFBREKu by 460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c@mostr.pub
       2024-11-20T15:06:16.000Z
       
       0 likes, 0 repeats
       
       The issue is that if clients are doing something with a field, it should be listed and upgraded on the NIP. There are over 30 fields or so that I have seen on Kind 0s that are not listed there. And it is fine. I am not sure what the extra array does that the current field list wouldn't do.
       
 (DIR) Post #AoEs4EyW0TUAifwidU by 0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd@mostr.pub
       2024-11-20T15:59:06.000Z
       
       0 likes, 0 repeats
       
       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.
       
 (DIR) Post #AoEsEDVAL6o92tyWKO by 460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c@mostr.pub
       2024-11-20T16:00:15.000Z
       
       1 likes, 0 repeats
       
       Right, so if pronouns are just listed as a field when the user visits a profile, it works. But if they are added after each person's name in the feed, then it becomes something else.
       
 (DIR) Post #AoEsEGWh5soSQViHcu by 0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd@mostr.pub
       2024-11-20T16:01:20.000Z
       
       0 likes, 0 repeats
       
       Yep.