UPS drivers work for UPS and drive UPS-owned vehicles. Many Fedex last-mile deliveries are made by contractors who Fedex really bends over. They're even forced to buy their own trucks. This probably explains the service difference.
You need to go to the top of this thread. You thumb-thugged "knew it was Joogle shills the other day" right in this thread thinking I wouldn't see it. I handed you your ass and you were pissed about it.
Since the original DDoS was 600+Gbps why would you even post small scale solutions? Pay attention to the thread and respond appropriately, don't cut-and-paste boilerplate. I sense a future of "needs to improve communication" on employer reviews.
Since I neither launched the DDoS nor had any suggestions as to how to mitigate it, how did you "hand me my ass" and "get the best of me"? I offered nothing.
I don't understand how this sort of thing happens anymore. In every one of these DDoS threads, a fellow slashdotter (anon, of course) is giving "expert" advice on how to easily manage such DDoS activities by configuring Windows NT.
Continuum isn't a cross-compiler, MS bet the mobile farm on Intel producing mobile chipsets. MS can't target ARM for crap, that's why they dropped RT and is also why they're now screwed in mobile.
Were you actually using the navigation feature? It will show congestion in minutes in South Florida. It's amazing how quickly the data is updated from even minor congestion, usually within a few minutes. Perhaps you were expecting it to re-route but the current route was still the fastest.
The service is actually available to anyone serving news, human rights, or election monitoring, or human rights content. A slashdotter actually suggested the service in the article that appeared here a few days ago.
This DDoS is 600+ Gbps but the DDoS devices you link to handle 40 Gbps. How does that work? In another post, you suggest using a CDN. Did you read the original article? Akamai IS a CDN! It's very clear you have no concept of the traffic levels involved. It's hundreds and hundreds of servers involved, it's traffic levels where expensive routers start to fall over due to load. It's not something you manage with $200 appliances or shell scripts.
Part of being intelligent is realizing that some things are above your current understanding. That's why I have no solutions. However, I do understand enough to know that your solutions are amateur, given the sheer size of the data flow under discussion. You don't even recognize the scale and present solutions that are completely unworkable in that scale.
It seems like you don't understand the scale and scope of these attacks. You're approaching it the way you'd approach someone pointing a few circuits at you. These are millions upon millions of requests all coming from different addresses in an insanely short period of time. Nothing outside of a few highly-specialized tools can meaningfully inspect traffic at those rates. The reason Amazon, eBay, Microsoft, etc can handle it is just sheer size... there's no special technology, they're just already scaled out to handle everyone shopping on Black Friday, which is inherently a larger set of requests than any DDoS.
I think that the storage for flat discs with no cases is not as cheap as you might think or Netflix would like. They've thinning the plastic disc collection just like they've closed nearly half of their hubs.
If the app targeted 8.1 the port to 10 isn't bad, if it targeted 8 then it can be a pain. It's still 3 fairly substantial API changes in a short period of time. Not a great way to gain developers to a platform that really needed quick traction to survive. It's painfully clear that MS bet the farm on an Intel-based phone only to have Intel pull out of the handset market for now. This leaves MS stuck developing on ARM, something that they clearly wanted to move away from and had all but pulled out of. This means that MS's snail-paced phone development will be even slower.
You had to switch back because the Windows phone OS is not "head and shoulders above", you had to switch back because the OS sucks. The APIs are a moving target, the OS had 3 major rewrites in 5 years that broke virtually every app each time and that's why there is poor developer adoption. Even base OS features are far, far behind - notifications weren't even supported until 18 months ago. Windows phone OS' is more at crotch-level, versus "head and shoulders above", when compared to competitors.
On AWS you're paying a premium for the ability to scale. The entire design is for dynamic computing requirements, such as ad-hoc computation or solutions that need to temporarily scale (think of Amazon's ecommerce site itself). If you just need a fixed number of servers it's not the economical choice.
Yes, Oracle has a planner that doesn't resort to guessing when presented with a query with more than 12 joins. Its plan cache is also shared across backends.
Slashdot Mirror
UPS drivers work for UPS and drive UPS-owned vehicles. Many Fedex last-mile deliveries are made by contractors who Fedex really bends over. They're even forced to buy their own trucks. This probably explains the service difference.
You need to go to the top of this thread. You thumb-thugged "knew it was Joogle shills the other day" right in this thread thinking I wouldn't see it. I handed you your ass and you were pissed about it.
Since the original DDoS was 600+Gbps why would you even post small scale solutions? Pay attention to the thread and respond appropriately, don't cut-and-paste boilerplate. I sense a future of "needs to improve communication" on employer reviews.
Since I neither launched the DDoS nor had any suggestions as to how to mitigate it, how did you "hand me my ass" and "get the best of me"? I offered nothing.
I don't understand how this sort of thing happens anymore. In every one of these DDoS threads, a fellow slashdotter (anon, of course) is giving "expert" advice on how to easily manage such DDoS activities by configuring Windows NT.
Continuum isn't a cross-compiler, MS bet the mobile farm on Intel producing mobile chipsets. MS can't target ARM for crap, that's why they dropped RT and is also why they're now screwed in mobile.
Microsoft can't have the contract because they don't own their own map data, they use Navionics, which you may better know as HERE.
That makes sense then, they're going to keep the featureset in the same era as the HERE map cartography.
Were you actually using the navigation feature? It will show congestion in minutes in South Florida. It's amazing how quickly the data is updated from even minor congestion, usually within a few minutes. Perhaps you were expecting it to re-route but the current route was still the fastest.
Sorry to ruin your zeal but I'm not nearly smart enough to work for Google. I make my living as a lowly "business application" developer.
The service is actually available to anyone serving news, human rights, or election monitoring, or human rights content. A slashdotter actually suggested the service in the article that appeared here a few days ago.
I offered no viable solution. Neither did you.
This DDoS is 600+ Gbps but the DDoS devices you link to handle 40 Gbps. How does that work? In another post, you suggest using a CDN. Did you read the original article? Akamai IS a CDN! It's very clear you have no concept of the traffic levels involved. It's hundreds and hundreds of servers involved, it's traffic levels where expensive routers start to fall over due to load. It's not something you manage with $200 appliances or shell scripts.
Part of being intelligent is realizing that some things are above your current understanding. That's why I have no solutions. However, I do understand enough to know that your solutions are amateur, given the sheer size of the data flow under discussion. You don't even recognize the scale and present solutions that are completely unworkable in that scale.
It seems like you don't understand the scale and scope of these attacks. You're approaching it the way you'd approach someone pointing a few circuits at you. These are millions upon millions of requests all coming from different addresses in an insanely short period of time. Nothing outside of a few highly-specialized tools can meaningfully inspect traffic at those rates. The reason Amazon, eBay, Microsoft, etc can handle it is just sheer size... there's no special technology, they're just already scaled out to handle everyone shopping on Black Friday, which is inherently a larger set of requests than any DDoS.
I see him up there now - can't believe the crap he posts, he really believes he has the solution...
The first link looks like the solution, send it to Akamai, they just need to enable SYN cookies on their Windows machine!
Great idea!
Where's that Slashdotter from the thread last week who posted 5 easy steps to stopping a DDoS! Akamai needs your "expertise"!
Wow, what did they spend the money on?
Unions.
I think that the storage for flat discs with no cases is not as cheap as you might think or Netflix would like. They've thinning the plastic disc collection just like they've closed nearly half of their hubs.
If the app targeted 8.1 the port to 10 isn't bad, if it targeted 8 then it can be a pain. It's still 3 fairly substantial API changes in a short period of time. Not a great way to gain developers to a platform that really needed quick traction to survive. It's painfully clear that MS bet the farm on an Intel-based phone only to have Intel pull out of the handset market for now. This leaves MS stuck developing on ARM, something that they clearly wanted to move away from and had all but pulled out of. This means that MS's snail-paced phone development will be even slower.
You had to switch back because the Windows phone OS is not "head and shoulders above", you had to switch back because the OS sucks. The APIs are a moving target, the OS had 3 major rewrites in 5 years that broke virtually every app each time and that's why there is poor developer adoption. Even base OS features are far, far behind - notifications weren't even supported until 18 months ago. Windows phone OS' is more at crotch-level, versus "head and shoulders above", when compared to competitors.
On AWS you're paying a premium for the ability to scale. The entire design is for dynamic computing requirements, such as ad-hoc computation or solutions that need to temporarily scale (think of Amazon's ecommerce site itself). If you just need a fixed number of servers it's not the economical choice.
Is this just a shill for some printer ink site? The link to HPs site shows like 6 threads where maybe 2 or 3 people are complaining.
Yes, Oracle has a planner that doesn't resort to guessing when presented with a query with more than 12 joins. Its plan cache is also shared across backends.
Regardless, bluetooth versions are available, so removal of the headphone jack clearly isn't a path to payment domination for Apple.