No, because you would want to keep the fact that you read something private.

Yes, and Roy's claim is that TLS doesn't provide that privacy, so is still basically useless for public content.

His argument is mostly based on analysing the size of the data transferred. Let's assume HTTP/2 for the moment. You have a single encrypted channel to a particular website that contains multiple interleaved opaque streams. It's not easily possible to extract the exact size of a single request from this. Furthermore, for a typical news website, for example, there will be an huge number of pages, they are dynamic and constantly changing and they will all have a very similar size.

You do get privacy. If anyone claims otherwise, he should go and prove that it's possible and easy by providing a firesheep-like tool. It would make for a nice research paper.

Here's an article describing how to find out what someone is watching on Google Maps by analyzing the encrypted traffic. http://blog.ioactive.com/2012/02/ssl-traffic-analysis-on-goo...

Fair enough, the HTTP request path can be hidden through TLS. I'm not sure if privacy is a goal of HTTPS, though.

On the internet layer, IP packets can still be traced from origin to client. I'm probably not involved enough to formulate an educated opinion, however.

Poland has more than double the number of people than Serbia + Croatia + Bosnia + Montenegro.

Fourth. While Ukraine is a bilingual country, it still much bigger than former Yugoslavia. Most people there consider it their native language and a majority know it. So if you are strongly biased for a small number you'll get 30 million speakers, if you are biased for a big number it might be 50 million.

And on top of that you must use the same criterion for the S-C language, not counting Slovenians, Albanians, Macedonians, etc who know the language but don't use it much anymore.

That's not really true, as all new members are required to start using Euro as a currency.

Thanks, fixed.

Ember's object model is really awesome (http://emberjs.com/guides/object-model/computed-properties/) By writing our charting library with Ember we can make use of their object model while also making it super easy to use the charts inside Ember applications.

As per my example below:

  {{time-series-chart
    barData=barData
    lineData=lineData
    selectedInterval=selectedInterval
  }}

By using Ember we get all the bindings for free.

I can see the benefit there, but why make Ember a hard dependency? It seems you want the chart stuff totally decoupled, and then you could provide the above functionality as a built in wrapper or plugin. Then people who wanted to use Angular (or whatever their favorite framework is) can write their own wrappers, or you could add support for others as you saw fit.

Making a wrapper is a lot of work and you end up with an unsatisfying solution. One of my first projects was an Ember wrapper for Slickgrid, but very soon you end up hitting the walls of the abstraction, which is why we wrote Ember-table. If we use Ember throughout, we also get to use bindings and computed properties for writing the charts as well. I think in the future it might be easier to have charts depends only on specific parts of Ember and not the whole framework.

The main difference is that because we use Ember's object model throughout our charts, it is very easy to extend them and tie them in to your application with bindings and computed properties in a generic way. For example binding the charts interval to a dropdown is just a matter of declaring a binding in you handlebars:

  {{time-series-chart
    barData=barData
    lineData=lineData
    selectedInterval=selectedInterval
  }}

I think this is our 3rd or 4th attempt at making a charting library, but the first one we are actually happy with. Good APIs for charts are surprisingly hard to get right. It was actually one of our interns (https://github.com/raykyri) who did most of the work on rewriting charts. Open source libraries are a really great match for intern projects.

THIS IS AWESOME. I was looking for something like this, and was really sad I was going to have to write something myself.... THANK YOU.

No it wouldn't. This statistic is highly misleading and the article author is basically lying by putting it in the article. If there are twice as many women who are married than there are those who are cohabitating then cohabitating is on average better than marriage.

I'm guessing she took that from this graphic:

http://twentysomethingmarriage.org/wp-content/uploads/2013/0...

Note that 33 + 29 + 47 = 109, not 100. Her wording makes it sound like they computed from one pool of "very satisfied" people the amount that were single, cohabitating and married, but the numbers in the infographic don't support that interpretation. It looks like instead they separated the groups by gender and status, and then tallied up the number that said they were "very satisfied" which I don't think is vulnerable to your rebuttal.

You are missing that when bruteforcing a one time pad you will get all possible arrangements of all letters. How do you tell all the plausible looking strings apart? What kind of a sort function could you apply?

You can also come meet us at our office in Mountain View. We have food and beer and can show you some cool Ember things we are working on(we are also constantly hiring, my email is in the profile).