@tryst @beka_valentine @hipsterelectron @ireneista I was thinking more a different ID per piece of data.
For the I2P case more on the level of "every torrent has its own ephemeral ID".
I'm not quite sure if Veilid's block-based structuring of data sharing should be the level of granularity for ID separation, because after a few thousand blocks, the overhead probably becomes considerable. So maybe ID separation at a higher level similarly to torrents (they do have reference blocks) would work.
> iām vaguely hopeful about a friend network over an privately routed network. if you all rotate node identifiers such that you only send messages to an identifier of generation n from an identifier of generation n, there may be a chance of cleanly separating identifiers from each other (from anyone whoās not your friend that is). then you just have the problem of how much you trust your friends and finding content in a friend networkā¦
My concern with friend-to-friend networks is that their security tends to fail catastrophically the second someone gets compromised and an infiltrator is substituted onto the network.
It's somewhat similar to the failure mode of Hyphanet/Freenet's with the trackability of particular file transfers with known/leaked/guessed metadata.