Not officially. but it's been on my mind a lot lately, now t...

原始 JSON

{
  "kind": 1,
  "id": "0000741431cbd36fc996fdc98c0e4538737f257d7092a94a2c0306373f194e3c",
  "pubkey": "2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331",
  "created_at": 1781874001,
  "tags": [
    [
      "e",
      "13422672a174eae24fe5b39ab0a6e7dece71f08e0ab31e074c53f1cfb057b1e7",
      "wss://nos.lol",
      "root"
    ],
    [
      "p",
      "daa41bedb68591363bf4407f687cb9789cc543ed024bb77c22d2c84d88f54153"
    ],
    [
      "client",
      "Wisp"
    ],
    [
      "nonce",
      "76838",
      "16"
    ]
  ],
  "content": "Not officially. but it's been on my mind a lot lately, now that we have decentralized lists curated by trust.  \nWhen I was playing with that idea, I had this standard list of nostr events that spec'd UI via JSON and would be rendered as live web components in the application. This was very neat, but it was single-player. with dlists and WoT curation,  communities could curate bespoke, dynamic UIs together from Lego-like blocks that automatically self-assemble and shift around as trust signals change.\n\nYou post a stupid note about how great parallax and scrolljacking is, and the UI component you authored stops being surfaced in some npubs' applications because **their** PoV of the components dlist just downgraded you on the \"UI expert\" topic, (while your PoV remains unchanged, so your UI stays the same) - with everyone using the same dlist ID\n\n😲😲",
  "sig": "98be2aeacf08b1fe839e1a6199ac71089f9135bcdc23165fe2d7b75286f5354ca71fe0694a4acd1b078d85734ea7f4b6611b7af2ebc2074ac6a39af55925c80f"
}