The article seems to focus too much on the consumer side of the bandwidth equation. I think the real win for Netflix is the aggregate egress bandwidth savings from their DCs. If Netflix can halve their bandwidth (as the article seems to claim) without any appreciable loss in quality, they've just saved substantially in the infrastructure and peering contracts needed to deliver their content. I have no idea how much money Netflix currently spends on bandwidth/CDN, but I'd guess it's certainly in the 100s of millions. I can imagine that Amazon and Apple would be very interested in emulating those savings.
While this is a good idea to prevent folks from brute-forcing their way into your machine, the article is talking about DDoS attacks. If you have 150G pointed at your network the issue isn't going to be your servers. It's going to be congestion at your network links. Your SSH settings and Fail2Ban won't help at all in this case. You'll need something like CloudFlare's DDoS protection to identify and block DDoS requests from ever reaching your network.
EDIT: Oops, just saw that the article does talk about SSH brute-forcing. Your point is quite valid.
Was this in the past week? Because just a few days ago I was experiencing a similar problem. I attempted to access https://rememberthemilk.com and chrome complained about the SSL cert, as I was receiving the cert for their CDN and not for rememberthemilk itself. I couldn't find anyone that could reproduce the issue, but it occurred consistently on my computer regardless of browser. It resolved itself 20 min after I first noticed it, but I'm still really curious as to why it happened in the first place.
Usually the CDN will have a single certificate which then has multiple SAN entries. What can happen depending on the size of the CDN is it can take a long time for the SSL to be added to the SAN entries on all the edge servers. So if a site just starts moving to a CDN they sometimes jump the gun and instead of waiting for all the edge servers to have the SSL they just change DNS records.
You then have a scenario where the DNS is waiting to propagate and the SSL is still propagating around the CDN. Hence you get soem users without a problem, some with and it eventually all clears itself up.
A large part of this is that the Second Amendment to the US Constitution explicitly protects people's right to bear arms. This has led to gun-ownership being an important topic to many American citizens, initially by people using to utilize guns (ranch rifles, etc) and then by collectors and other hobbyists.
As for your second question, the difficultly of obtaining a gun in the US varies largely by state. However, it generally is not exceedingly difficult. As an example, here is how purchasing a firearm works in California:
If you don't mind me asking, what country did you move too that has better personal rights? I know that Canada and most of the EU have a worse track record than the US when it comes to this.
IMHO moving out of the US just avoids the problem, instead of solving it. We need to put more support behind advocacy groups like the EFF who's mission statement is to fight against the infringement of personal rights.
You know that Canada (and the EU) has a worse track record... Can you provide a link to support this rather bold assertion? I am fairly familiar with Canadian law and strongly disagree with your statement.
I have had to deal with Human Rights Commissions in two provinces over the course of 10 years and have never seen anything like what is referenced: HRCs do not have the capacity to access email and documents without the owner of such being informed. Your argument is just an attempt at changing the topic at hand. The orginal comment ended with "when it comes to this" thus referencing warrantless access to email and such.
At least Canada is not involved in wars of aggression and is a relatively peaceful nation (in comparison to the US). The point is not where we are now that is of concern, it's when the shit hits the fan, which will inevitably happen. When this happens, first thing out of the window is personal rights.
Canada is an an interesting choice, until you read some history and realize that every fascist state eventually turns its wars of aggression toward its closest neighbors. The odds that America will turn fascist on its own people, act on continuous wars of aggression globally, but never attack Canada - is roughly zero. It's a matter of time, unless the fascist state creep is rolled back and quickly.
It's a message board comment that says if you believe the US is on its way to being a fascist state, read a history book sometime on exactly how fascist countries operate.
I wouldn't expect it in the next decade. However, if you cycle forward the progression of laws and behavior represented by the last 10 to 15 years, then it seems likely that at a minimum the US will begin to intrude on Canadian sovereignty either through direct or indirect coercion.
Fascist countries don't tend to be very tolerant of their friendly neighbors.
MySQL, though written in C++, reads more like C with classes. Even then, a large portion of the code is procedural instead of OO. They are slowly moving towards an OO style, but it will take a while before a reasonable percentage of the code base has been re-written.
How is this "beyond astonishing"? 27 years is minuscule on in a geologic time scale. Climate trends are measured in hundreds and thousands of years, if not more.
I would disagree with this article. Most posts through third-party applications will have a motivation to reach the largest possible audience. This will lead to an excessive amount of public posts. Not only will this defeat the purpose of "circles", it will also flood G+ search with noise. This will destroy much of the usefulness of the network.
