to be automatically imported, relays would need to know all ...

𝖘𝖊𝖙𝖙𝖔𝖑𝖎𝖓𝖔 𝖕𝖎𝖓𝖌𝖚𝖎𝖓𝖔

npub18ug6hvhzxhdz6nw6t4k7ktcjx9e5w6n5tg7226y458g0vv4y9aqq3r20ex

hex

0be53d1a5b0188d4afe78a20b8918cb9314d7c930d09f206b245c2d5e3bc7531

nevent

nevent1qqsqhefarfdsrzx54lnc5g9cjxxtjv2d0jfs6z0jq6eytsk4uw782vgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsr7ydtkt3rtk3dfhd96m0t9ufrzu68df695099dz26r58kx2jz7sq3xts8q

Kind-1 (TextNote)

2026-01-04T18:29:57Z

↳ Reply to Hash Power Music (npub1zm95kw87nf6gkesg76jedyfejt0u2zgx2fxgxywdxc9ugq3z4w2q4m092t)

Ill look into importing. But why arent tracks being automatically imported? Is it to associate the uploader npub (that would make sense). What prevent...

to be automatically imported, relays would need to know all the feeds. Nothing prevents a user from claiming someone else's feed. But the same is true with podcast: anyone could mirror a feed and swap out the wallet addresses. This is a shared responability between publisher and audience: audience needs to verify, publisher needs to provide means of verification. In that particular context, i believe nostr has a greater chance, because cryptographic verification mechamisms are built in the protocol. But we'll only ever know what really works once we blow up and we start having big stars pulling in big figures.

there are two slightly more mature clients i recommend you try: nodecast.xyz nostria.app

don't raw dog your nsec though. Like ever. Extension, amber, or throwaway keys! 😅💜

Raw JSON

{
  "kind": 1,
  "id": "0be53d1a5b0188d4afe78a20b8918cb9314d7c930d09f206b245c2d5e3bc7531",
  "pubkey": "3f11abb2e235da2d4dda5d6deb2f123173476a745a3ca56895a1d0f632a42f40",
  "created_at": 1767551397,
  "tags": [
    [
      "e",
      "e65d7020d9f069e7cb02ec2a99fe1ad45c0dd88d38524444a36017f76ce49f41",
      "wss://basspistol.org/",
      "root",
      "605343ab36f8677a0d35f7e387927bdaff488a92b3d727fb2a43cf7a9573c8d4"
    ],
    [
      "e",
      "21a3b86a12e6a4e4e6702ca47e60637cd59554714872b79ff2b298404c630824",
      "wss://tortellino.basspistol.org/inbox",
      "reply",
      "16cb4b38fe9a748b6608f6a596913992dfc50906524c8311cd360bc40222ab94"
    ],
    [
      "p",
      "605343ab36f8677a0d35f7e387927bdaff488a92b3d727fb2a43cf7a9573c8d4"
    ],
    [
      "p",
      "3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
    ],
    [
      "p",
      "1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411"
    ],
    [
      "p",
      "17e2889fba01021d048a13fd0ba108ad31c38326295460c21e69c43fa8fbe515"
    ],
    [
      "p",
      "0adf67475ccc5ca456fd3022e46f5d526eb0af6284bf85494c0dd7847f3e5033"
    ],
    [
      "p",
      "a8d1560d6a647d501699167246f237b36fb123f89168fda11dc743533fec7a08"
    ],
    [
      "p",
      "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6"
    ],
    [
      "p",
      "16cb4b38fe9a748b6608f6a596913992dfc50906524c8311cd360bc40222ab94"
    ]
  ],
  "content": "to be automatically imported, relays would need to know all the feeds. Nothing prevents a user from claiming someone else's feed. But the same is true with podcast: anyone could mirror a feed and swap out the wallet addresses. This is a shared responability between publisher and audience: audience needs to verify, publisher needs to provide means of verification. In that particular context, i believe nostr has a greater chance, because cryptographic verification mechamisms are built in the protocol. But we'll only ever know what really works once we blow up and we start having big stars pulling in big figures.\n\nthere are two slightly more mature clients i recommend you try:\nnodecast.xyz\nnostria.app\n\ndon't raw dog your nsec though. Like ever. Extension, amber, or throwaway keys! 😅💜",
  "sig": "58867f0d12adae76c5ee2be0e55696dcd63798eaae0b1e007695c7a54afb43ebd4123fbc0159371510e721e13c7673a2a47566fcfad38e12490bd3aa3b763c02"
}