#19 randomly direct connect, or find better path?

[Anonymous]

No compromise on the privacy issue? if you randomly
direct connected, still not knowing if you are directly
connected, but maybe if it always or randomly seeked
the fastest path for a download?

Point being if some downloads direct conneted (without
actually telling the other side that the file is
actually direct) there would be no way to tell if it
was direct or just rhough a faster "proxy" node. So
privacy is still ok.

I can see abuse, someone keeps trying till he gets
fastest connection, or removes the random code and
makes it always direct connect.

Maybe like gambling, both nodes have to be in the
"direct connection mood" meaning both of them both
happen to have selected the random mode at exactly the
same time.

[Maarten Maathuis]

Logged In: YES
user_id=781921

I think it does try to find a better paths, because when you
search or download nodes are added without any being in your
seed list. Once and a while a direct connections will be used,
for example when the data is on a node you're directly
connected to, but most of the time it's routed trough one or
more nodes.

[Nobody/Anonymous]

Logged In: NO

No. MUTE should never conect directly. this could later a
gnutella-mute hybrid cleint do.
But mute should stay mute, so not directly.
If you want direct connections, mute should go hybrid with
waste friendslist. There you can have direct connections
encrypted over WASTE app.