Conversation

Notices

1. Embed this notice
   Melvin Carvalho (de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645@mostr.pub)'s status on Monday, 25-Sep-2023 05:41:47 JST Melvin Carvalho
   Isnt displayName in much wider use?
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 25-Sep-2023 05:41:47 JST Alex Gleason

     in reply to
     @de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645 @460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c NIP-01 only defines `name`. The other properties aren't in NIPs at all.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 25-Sep-2023 06:10:33 JST Alex Gleason

     in reply to
     @de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645 I'm planning to support custom profile fields on Nostr, but it will be a `fields` array within the metadata content. It wouldn't be additional arbitrary keys.
   • Embed this notice
     Melvin Carvalho (de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645@mostr.pub)'s status on Monday, 25-Sep-2023 06:10:34 JST Melvin Carvalho

     in reply to

     • Alex Gleason
     No strong opinion here, but isnt it up to the user what they put in their profile?
     
     In Solid we had open ended profiles. That's an aspect of decentralization that I loved.
     
     Linked data in general allows lots of fields.
     
     Mastodon lets you add 4 fields in a quite restrictive way.
     
     Referring to a nip for descriptions and guidance could be useful (all be it quite centralized) another way would be to make an LD type vocab that could be extended, similar to:
     
     https://w3id.org/nostr
     
     Ultimately first generation apps, goverrned by the NIP process will move fast and break things. 2nd generation might learn from that approach and build in a more long-term way.