Changing the event structure is okay (as it's mostly me writing those events) but as a longer term solution it's not. How are we gonna do this if nostr grows?
Custom NIP-50 immediately breaks interoperability.
Separate queries like hitting 50+ (maybe a lot more) times the database for one query, far from good. Not only the db, it's crossing the whole stack. These reqs are very common.
franzap
npub1wf…3dgh9
2025-05-26 20:02:20
in reply to nevent1q…l7ye
Author Public Key
npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9Published at
2025-05-26 20:02:20Event JSON
{
"id": "869b29536a8fa674b3d187ccd911dd0d8db04a041202da2c9ccd38d1164380e1",
"pubkey": "726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11",
"created_at": 1748289740,
"kind": 1,
"tags": [
[
"e",
"0e53e3e3b1dadb41ff07101e64a81fa0dd0ac7485962985b29ad307f31b4ce54",
"",
"root"
],
[
"e",
"8aff24caac40e8e059d23869b0c88b5a731a1463a3d24bd0c1f57fb0224d8891"
],
[
"e",
"cccae46c71b831005f6803d71d346f0981631f4d0c907e41a52ee9804734f4b4",
"",
"reply"
],
[
"p",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11"
],
[
"p",
"f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2"
],
[
"p",
"0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd"
]
],
"content": "Changing the event structure is okay (as it's mostly me writing those events) but as a longer term solution it's not. How are we gonna do this if nostr grows?\n\nCustom NIP-50 immediately breaks interoperability.\n\nSeparate queries like hitting 50+ (maybe a lot more) times the database for one query, far from good. Not only the db, it's crossing the whole stack. These reqs are very common.",
"sig": "c06d57b7dc3b34c285c0ba5a890bf670d46e4e96b2637155d4655aeeffa95c7d28dfe2ffcdeb49a902ae345646dff738b3b22eb65c0d5c4ff8c2972bf2493d46"
}