Damus
dankswoops profile picture
dankswoops
@dankswoops

Nostr Dev, client releasing in July.

7 world first stunts, 2 harness innovations.
Created the 13th discipline in skydiving, Mixed Vertical Piloting.

Relays (12)
  • wss://bitcoiner.social/ – read & write
  • wss://btc.klendazu.com/ – read & write
  • wss://nos.lol/ – read & write
  • wss://nostr.jcloud.es/ – read & write
  • wss://nostr.land/ – read & write
  • wss://nostr.wine/ – read & write
  • wss://purplepag.es – read & write
  • wss://relay.damus.io/ – read & write
  • wss://relay.mostr.pub/ – read & write
  • wss://relay.primal.net – read & write
  • wss://relay.snort.social/ – read & write
  • wss://welcome.nostr.wine/ – read & write

Recent Notes

dankswoops profile picture
Proposal: New Nostr Kind-0 Metadata Fields

Please share this note for more peer review.

I've drafted a proposal to add three new optional fields to kind-0 user metadata: status, partner, and kin.

— status (integer 0-7): relationship status, from single to married to open relationship. Integer-based for localization across all languages.
— partner (hex pubkey array): link your partner(s) to your profile. First entry is primary.
— kin (tuple array): family connections with optional relationship types — parent, sibling, child, cousin, in-law, and more.

All fields are optional, public, and use hex pubkeys natively. Clients that don't support them simply ignore them. The spec includes relay size analysis, a privacy section, and a comparison to NIP-81 (Contact Cards).

Full proposal: https://github.com/dankswoops/proposals/tree/main/nostr-kind0-metadata

GitHub Discussion: https://github.com/nostr-protocol/nips/issues/2202

Feedback welcome. Looking for input from client devs and protocol contributors before drafting a formal NIP.
dankswoops profile picture
its one of those low hanging fruits that go giga viral but the expert ninja stuff doesn't get much traction with the outside world.