Structure of Subscription Graph
You wondered if the subscription could be a tree. I don't think so, but it can
be directional and perhaps without loops, which may be about as good as a tree.
You can make it this way by having a subscription request have a unique ID so
that multiple subscriptions to the same data will each have their own ID on the
request. Then a subscription request will not join to itself if it collides
with itself, but will join and discontinue if it collides with another
subscription graph. A malicious attacker may be able to create cycles however
by repeating the subscription ID.
Vulnerability of Listen/Subscribe
The main reason we weren't doing this before was for fear of an attacker putting
a listen/subscribe on every node. Is this still as much an issue?
Properties of the subscription 'stream'
When I encounter "data stream" it usually has the properties of:
guaranteed ordered delivery;
maybe guaranteed delivery;
no packetizing, dissolution of packet boundaries in the stream.
I think that the freenet architecture is not conducive to supporting any of
these properties. Supporting them would be undesirable and ineffecient. Are
you intending to support these properties? Do you think it's a good idea?
