when choosing the middle nodes, it excludes the exit node and other middle nodes first.<br>and then exclude itself if it's a or. and randomly choose a node in the running routers list which contains all those routers only if it's now running and valid and you think it's reliable enough.<br>
so actually i don't see there's some policy to exlude those exit nodes<br><br><div class="gmail_quote">On Sun, Nov 2, 2008 at 9:50 PM, Erilenz <span dir="ltr"><<a href="mailto:erilenz@gmail.com">erilenz@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If you run as an exit node, it's my understanding that you also act as a<br>
middleman node. Would it be possible, and would it be a good idea, to<br>
add an option such that you only act as an exit node?<br>
<br>
It seems a bit of a waste to use potential exit bandwidth as middleman<br>
relaying bandwidth when exit bandwdith is more scarce.<br>
<br>
--<br>
<font color="#888888">Erilenz<br>
</font></blockquote></div><br>