<br><br><b><i>Michael Holstein <michael.holstein@csuohio.edu></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> > I agree that being behind someone else's firewall is a problem as the<br>> user may not understand the implications of this and thus advertise an<br>> impossible exit policy.<br><br>Suggestion for the coders .. make the client test itself and adjust the <br>exit policy on the fly.<br></blockquote>IMO making all Tor clients also function as MiddleMan Nodes, RPs, etc (all *except* Entry and Exit nodes) would be a good move. It might be good to also make Tor clients function as Entry nodes (not Entry Guards) to increase their usefulness.<br><br>Just a few quick thoughts:<br>A default bandwith rate on the low to minimum side would be a good. It may also be good to make two instances of Tor start when an end-user starts Tor. One instance would be the client
and the other would be the server (w/ "SocksPort 0"). <br><br>Anogeorgeo<br><br><br><br><br><p> 
<hr size=1>How low will we go? Check out Yahoo! Messenger’s low <a href="http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com"> PC-to-Phone call rates.