FIRST AND FINAL WARNING!!!!<br>
You have 48 hours to remove me from your mailing list.<br>
If you do NOT remove me, I will DDOS (Distributed Denial of Service) your server until you are broke.<br>
<br>
Try me, I got 10 OC192's, 15 OC48's, and 8 OC12's just waiting for shit
like this...and I'm getting pissed. If you are working for yourself or
some spam king, either way the "customer" who is paying you to
"advertise" will NOT be happy when they spent their money to be only be
attacked in return.<br>
<br>
Remove me or else I remove your source of revenue.<br>
<br>
Again, FIRST AND FINAL WARNING!!!!<br>
<br>
Have a nice day and get a real fucking job.<br>
<br><br><div><span class="gmail_quote">On 5/26/07, <b class="gmail_sendername">Michael_google gmail_Gersten</b> <<a href="mailto:keybounce@gmail.com">keybounce@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I finally realized what feature I'd like to see. CircuitMinimumBandwidth.<br><br>Have a config option to tell Tor how much CPU time it can expect to<br>give to processing onions (which will tell it how many active<br>
connections it can handle) (Or tell it directly how many active ones<br>it can handle).<br><br>Tor knows the total bandwidth it has to use.<br>There's good heuristics for telling how much bandwidth a connection<br>will need. (Most will need a high initial push, and then occasional,
<br>intermittent spikes; if a connection needs a lot for more than <N><br>seconds, it's likely to need a lot for a while longer. Etc.)<br>There's a way to tell when the CPU limit will prevent any more data<br>
transmission.<br><br>Combined, this would allow a node to refuse non-specific node requests<br>(normal circuits would be blocked if the tor server is busy, but a<br>".node.exit" would still be allowed).<br><br>This would also eliminate any perceived "slowness" of tor -- no longer
<br>would I see 22 MB nodes in my path, yet dialup users could still use<br>them. If I have a 1300 MB node in my path, I know it can handle my 150<br>request, and not be either so swamped that I'm only seeing 15, or so
<br>overloaded that it's past it's CPU limit. Equally, I know that I can<br>tell tor (without having to use "nice") not to steal all my CPU while<br>I'm using my computer.<br><br>Potential problems? What would we do if we could not find a viable
<br>circuit? What if every node is asked and reports "Busy" -- how do we<br>tell the user that "Tor is full", or should a lowspeed connection be<br>made anyways?<br></blockquote></div><br>