I tried to separate data from the nostr.info design by using...

Leo Wandersleb

npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6

hex

f4d377a1567c64524a3e8f29a8d560e2f50dd882f0c6cf66f12389d0cc07b648

nevent

nevent1qqs0f5mh59t8cezjfglg72dg64sw9agdmzp0p3k0vmcj8zwsesrmvjqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvungpk2qa2

Kind-1 (TextNote)

2026-04-28T08:11:15Z

↳ 回复 Max (npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt)

Yours had a bunch that I didnt know about. added to my existing list here. Thanks! nostr:nevent1qqsp4vu4rfmkmcrmypkn6ne97yxp7a5lpwqkefkmana7xcwejrctd3...

I tried to separate data from the nostr.info design by using the data via a sub repository https://github.com/Giszmo/nostrResources But I got stuck in analysis paralysis thinking that to really share that data with other projects, it should be in nostr events and not in a git repository.

But while nostr is great for single-author censorship resistant distribution of data, collaborative maintenance of some canon of data isn't yet solved in nostr to my knowledge. Hence the paralysis.

原始 JSON

{
  "kind": 1,
  "id": "f4d377a1567c64524a3e8f29a8d560e2f50dd882f0c6cf66f12389d0cc07b648",
  "pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
  "created_at": 1777363875,
  "tags": [
    [
      "e",
      "303331ed317fc458c4af7b3ed8439cb3fd19ca677b28e780ad4c6cd17b926a21",
      "wss://relay.towardsliberty.com/",
      "root",
      "b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc"
    ],
    [
      "e",
      "55179098ba9b5093159f96d47dad366fbf3ff070233ca9a0e22b046e3738999f",
      "wss://nos.lol/",
      "reply",
      "b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc"
    ],
    [
      "p",
      "9ec7a778167afb1d30c4833de9322da0c08ba71a69e1911d5578d3144bb56437"
    ],
    [
      "p",
      "b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc"
    ]
  ],
  "content": "I tried to separate data from the nostr.info design by using the data via a sub repository https://github.com/Giszmo/nostrResources\nBut I got stuck in analysis paralysis thinking that to really share that data with other projects, it should be in nostr events and not in a git repository.\n\nBut while nostr is great for single-author censorship resistant distribution of data, collaborative maintenance of some canon of data isn't yet solved in nostr to my knowledge. Hence the paralysis.",
  "sig": "c893e5aff5dab5c88da931881e5ec5d07f58970dd19c69d83a2be7b8a4f809d57467636b8ccf7cd1dea20b28daf0eabc27c6844d109fe6b13b3b2646ec4119f6"
}