Tweet
Dear TelCat,
Stick to taking pictures of your tities, you obviously don't know shit. THIS ISN'T A PROBLEM THAT CAN BE FIXED. TRUST ME. IF INTERNET GIANTS LIKE E-BAY AND KEEBLER.COM ARE SUSCEPTIBLE TO THE VERY SAME ATTACKS, AND STILL CAN'T DO SHIT TO REMEDY THE SITUATION, THEN TW CAN'T EITHER, SPECIALLY NOT VIA YOUR "let's bond together and fix this problem!" THREAD. That thread would only cause more idiots like you to post their thoughts on a topic they don't understand. Listen, there are ways of... easing... the attacks... But no real way of stopping them (Unless you shut the server, or direct your firewall to block every incoming IP through any port, at which point your wall will probably crash too). Now, if our server was running on a ipv6 multisync system (which would require a large number of nodes to be any help at all), TW might still be up. But because it doesn't, and because ipv6 is still not in general use (companies are hesitant to switch because of cost, and because some servers may invoke attack [personal shells that run botnets, sites, etc...], they don't want other clients bearing bandwidth costs that stem from attacks on one particular server), then there is nothing you can do but shut down the server, wait it out, and maybe install some additional filters/routers/walls/ etc etc etc... oh yea, in Conclusion, dumb bitch, shut up- we all know you love yourself, stop trying to incite threads that will get all controversial just so you can up your post count.
Kind Regards,
*slaps TelCat in the face*
Stick to taking pictures of your tities, you obviously don't know shit. THIS ISN'T A PROBLEM THAT CAN BE FIXED. TRUST ME. IF INTERNET GIANTS LIKE E-BAY AND KEEBLER.COM ARE SUSCEPTIBLE TO THE VERY SAME ATTACKS, AND STILL CAN'T DO SHIT TO REMEDY THE SITUATION, THEN TW CAN'T EITHER, SPECIALLY NOT VIA YOUR "let's bond together and fix this problem!" THREAD. That thread would only cause more idiots like you to post their thoughts on a topic they don't understand. Listen, there are ways of... easing... the attacks... But no real way of stopping them (Unless you shut the server, or direct your firewall to block every incoming IP through any port, at which point your wall will probably crash too). Now, if our server was running on a ipv6 multisync system (which would require a large number of nodes to be any help at all), TW might still be up. But because it doesn't, and because ipv6 is still not in general use (companies are hesitant to switch because of cost, and because some servers may invoke attack [personal shells that run botnets, sites, etc...], they don't want other clients bearing bandwidth costs that stem from attacks on one particular server), then there is nothing you can do but shut down the server, wait it out, and maybe install some additional filters/routers/walls/ etc etc etc... oh yea, in Conclusion, dumb bitch, shut up- we all know you love yourself, stop trying to incite threads that will get all controversial just so you can up your post count.
Kind Regards,
*slaps TelCat in the face*
Comment