creator of #fediblock :verified::makemeneko: on Nostr: Alex Gleason rees Vitor Pamplona so my point here is that for nostr to gain the ...
Alex Gleason (npub108p…yev6) rees (npub1j3v…qxec) Vitor Pamplona (npub1gcx…nj5z) so my point here is that for nostr to gain the abilities of ipfs would be quite a leap. whereas for ipfs to gain an additional low latency ability for content selected by the node operator seems quite trivial. you literally just give a hint to the client about where to look first (list of nodes that you paid)
if you pay a node to host content for you then queries to it don't need to do a bunch of hops, indirections, block lookups, etc. you just ask the specified address (ie centralized server) for the object and it sends it back to you immediately because it has the entire thing sitting there because that's what you paid them for
you could literally reuse existing ipfs http relays for this. set one up that only fulfills queries for stuff it has pinned locally and then charge to pin stuff on it. I'm not saying that's a particularly elegant solution but it would work at which point I'm really wondering what the point of nostr is in this scenario
if you pay a node to host content for you then queries to it don't need to do a bunch of hops, indirections, block lookups, etc. you just ask the specified address (ie centralized server) for the object and it sends it back to you immediately because it has the entire thing sitting there because that's what you paid them for
you could literally reuse existing ipfs http relays for this. set one up that only fulfills queries for stuff it has pinned locally and then charge to pin stuff on it. I'm not saying that's a particularly elegant solution but it would work at which point I'm really wondering what the point of nostr is in this scenario