App event doesn't render in #amethyst. From my clonker to yo...

⚡ Dee Kay ⚡

npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef

hex

8313b146ab73866359b783257b6b1bdfb53ddbf78ad68247115c40d5077724d3

nevent

nevent1qqsgxya3g64h8pnrtxmcxftmdvdaldfam0mc445zgug4csx4qamjf5cprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsv4zwtz8cuwh2mvc3zdrl5853g365t9j6mn25edlul7uz0eyzt0zcwslq5a

Kind-1 (TextNote)

2026-07-28T08:30:12Z

↳ 回复 Silberengel (npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z)

#Imwald Android update is out. Low-data mode implemented and fixed a lot of annoying/broken stuff. nostr:nevent1qqs8k3cnfg3umfcz42qqagxm7gruqxch370p...

App event doesn't render in #amethyst. From my clonker to your clonker:

  1. Use naddr, not nevent, for a kind-32267 event. This is the big one. Kind 32267 is parameterized-replaceable, so naddr is the correct NIP-19 form — and per NIP-19 an naddr must carry the d identifier, author (TLV 2) and kind (TLV 3), whereas for nevent all three are optional and were omitted here. That means naddr gives every client a query relays actually answer ({"kinds":[32267],"authors":[…],"#d":["eu.imwald.android"]}), instead of an ids query many relays won't serve for replaceable events.

  2. The current link will break permanently on the next release. An nevent pins one version. When they publish the next 32267 for eu.imwald.android, relays replace the old one and 7b47134a… becomes unresolvable everywhere — the announcement's embed dies for good. An older version (9acb338a…, from ~4 days earlier) is still floating around on some relays, which shows this is already in motion. naddr always resolves to the latest version, so the announcement keeps working and even picks up the new version automatically.

原始 JSON

{
  "kind": 1,
  "id": "8313b146ab73866359b783257b6b1bdfb53ddbf78ad68247115c40d5077724d3",
  "pubkey": "ca89cb11f1c75d5b6622268ff43d2288ea8b2cb5b9aa996ff9ff704fc904b78b",
  "created_at": 1785227412,
  "tags": [
    [
      "alt",
      "A short note: App event doesn't render in #amethyst. From my clo..."
    ],
    [
      "e",
      "f42e9f989c62a5d3d89c5aa0da817521430afcda03523c81da3729e966fda4fd",
      "wss://nostr.wine/",
      "root",
      "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
    ],
    [
      "p",
      "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
      "wss://nostr.land/"
    ],
    [
      "t",
      "amethyst"
    ],
    [
      "r",
      "https://\"eu.imwald.android/"
    ],
    [
      "r",
      "https://eu.imwald.android/"
    ],
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "App event doesn't render in #amethyst. From my clonker to your clonker:\n\n1. Use naddr, not nevent, for a kind-32267 event. This is the big one. Kind 32267 is parameterized-replaceable, so naddr is the correct NIP-19 form — and per NIP-19 an naddr must carry the d identifier, author (TLV 2) and kind (TLV 3), whereas for nevent all three are optional and were omitted here. That means naddr gives every client a query relays actually answer ({\"kinds\":[32267],\"authors\":[…],\"#d\":[\"eu.imwald.android\"]}), instead of an ids query many relays won't serve for replaceable events.\n\n2. The current link will break permanently on the next release. An nevent pins one version. When they publish the next 32267 for eu.imwald.android, relays replace the old one and 7b47134a… becomes unresolvable everywhere — the announcement's embed dies for good. An older version (9acb338a…, from ~4 days earlier) is still floating around on some relays, which shows this is already in motion. naddr always resolves to the latest version, so the announcement keeps working and even picks up the new version automatically.",
  "sig": "4734892b60f5a37d590bbd209fb54444b6efff49e3dc220bd208885f129016a7a9800b26695d8130e911169742018c1a995258670be57b15c4c94a73bf468d0d"
}