> but discoverability of “unpopular” content is slower

weev

npub1weev88wc43slz6jjlq2h30ltmd0ccu9utfe8wet2kkax0w6epavqw409xg

hex

701643bcecc3c720388564c43963f283885ca10ec7b9cd1e5bc2fe8875a16752

nevent

nevent1qqs8q9jrhnkv83eq8zzkf3pev0eg8zzu5y8v0wwdredu9l5gwkskw5sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs8vukrnhv2cc03dff0s9tchl4akhuvwz795unhv44ttwn8hdvs7kqzsknqj

Kind-1 (TextNote)

2026-04-20T21:02:45Z

↳ Reply to Technical Debt (npub14w4qnk43lsllls2qnldj3vfcxtx5qvtsf3xlvxv9yha8afrxhmfqju3rwx)

DHT is not a silver bullet. Torrents get spam attacks, CJDNS routing tables have grown enough to require offloading the routing to dedicated nodes (...

but discoverability of “unpopular” content is slower

Sure, but a social pinning model and IPFS peer graph makes this irrelevant. We’re not talking about an ancient file. We’re talking about a message that I just posted that is being ostensibly served by my followers. Your first IPFS node to check could be one I offer via the same tor onion as my relay. And I’m sure to have it, it’s my file. An easy place to query for a hash that is not me, in this instance, would be my followers, who are, in this hypothetical, pinning my content. You don’t need to search the entire IFPS network.

Regardless, this is a side channel. It doesn’t have to be a silver bullet! It just has to make my content more available than it already is, and reduce immediate stress during peak hours upon public relays and media servers.

Raw JSON

{
  "kind": 1,
  "id": "701643bcecc3c720388564c43963f283885ca10ec7b9cd1e5bc2fe8875a16752",
  "pubkey": "7672c39dd8ac61f16a52f81578bfebdb5f8c70bc5a7277656ab5ba67bb590f58",
  "created_at": 1776718965,
  "tags": [
    [
      "e",
      "ace6846e172101ee88ee9ce48880539e77923bddb1ff7e0b0fc2376290a5ca98",
      "",
      "root"
    ],
    [
      "e",
      "f2ff4d1ad7549a036107eeb6209610afdf0e1bc89ed45beaa240c10a6d5884ac",
      "",
      "reply"
    ],
    [
      "p",
      "23d12ef8751e5ee267fb6341d7c41b9434a1b99869e0212eb34d56abb6b12e8a"
    ],
    [
      "p",
      "7672c39dd8ac61f16a52f81578bfebdb5f8c70bc5a7277656ab5ba67bb590f58"
    ],
    [
      "p",
      "abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
    ],
    [
      "p",
      "930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
    ]
  ],
  "content": "\u003e but discoverability of “unpopular” content is slower\n\nSure, but a social pinning model and IPFS peer graph makes this irrelevant. We’re not talking about an ancient file. We’re talking about a message that I *just posted* that is being ostensibly served by my followers. Your first IPFS node to check could be one I offer via the same tor onion as my relay. And I’m sure to have it, it’s my file. An easy place to query for a hash that is not me, in this instance, would be my followers, who are, in this hypothetical, pinning my content. You don’t need to search the entire IFPS network. \n\nRegardless, this is a side channel. It doesn’t have to be a silver bullet! It just has to make my content more available than it already is, and reduce immediate stress during peak hours upon public relays and media servers. ",
  "sig": "fb01ee6cee525a1a57d3646908ecc66a49c1612e081ccb79eb49a6d789d631fa8d02e26da76cb79ec6a106ded5d97690b2e46534a9060ddb1bec79bd0169e4b7"
}