The image for Phnom Penh has some terrible compression artifacts, the other images and videos are beautiful and worth the bandwidth

http://graphics8.nytimes.com/newsgraphics/2015/11/10/places-...

See this great interactive, What Size Am I?, by Anna Powell-Smith

http://sizes.darkgreener.com/

Looks very good.

For the size legend, the defaults are a bit odd. You should almost always be using d3.scale.sqrt() as you're comparing area, also zero in the domain should usually map to zero on the range.

I made a similar legend for circle areas, but they are stacked within each other. http://bl.ocks.org/aubergene/4723857

Side note, but this would be great for some creative graffiti uses

So many acronyms, this page could certainly benefit from using the <abbr> tag to explain, or link off to a definition of what they stand for.

From the article:

ISRG - Internet Security Research Group - Let's Encrypt was in stealth mode for a while before they announced the project, and they used this generic name as the official certificate authority so they could fly under the radar while starting to lay the ground work to get the project going. https://en.wikipedia.org/wiki/Internet_Security_Research_Gro...

OCSP - Online Certificate Status Protocol - If Let's Encrypt wants to revoke certificates, they need broadcast those revocations. This is one of the protocols to do this, and it requires a different key pair. https://en.wikipedia.org/wiki/Online_Certificate_Status_Prot...

CA - Certificate Authority - This is someone who signs certificates for other websites. Browsers and operating systems have a list of CAs they trust, so if you want the https lock to show up without warning, you need to get your https certificate signed by one of the trusted CA (Let's Encrypt is going to be a free CA). https://en.wikipedia.org/wiki/Certificate_authority

CRL - Certificate Revocation List - This is another way to broadcast certificate revocations. https://en.wikipedia.org/wiki/Revocation_list

RSA - Rivest Shamir Adleman - A public key cryptography algorithm that most CAs use for their root and intermediate certificates. It's been battle tested for 40+ years, so it's a safe bet. https://en.wikipedia.org/wiki/RSA_%28cryptosystem%29

ECDSA - Elliptic Curve Digital Signature Algorithm - The next generation in public key cryptography algorithms that has many advantages over RSA. It's still relatively new (10 years), so CAs are hesitant to adopt it right now. https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signatu...

From this discussion thread:

PKI - Public Key Infrastructure - The general term for a network of public keys. The PKI used by browsers is their list of trusted CAs plus any certificates from websites that are signed by those CAs (or chained to the CA through an intermediate). https://en.wikipedia.org/wiki/Public_key_infrastructure

DV, OV, EV - Domain Validation, Organization Validation, Extended Validation - These are different levels of audits done by CAs before they sign a certificate for a website. DV just checks that you have control over that domain (this is what Let's Encrypt will only do), OV checks that you are the organization you claim to be (usually by calling you), and EV does a lot more checking around to make sure that your organization is real and you are running the website (this is the level that gives you a green bar in your URL). https://www.globalsign.com/en/ssl-information-center/types-o...

S/MIME - Secure/Multipurpose Internet Mail Extensions - A protocol for signing email with a certificate that has been signed by a CA. Most CAs have a different key pair to sign keys with for this protocol, but Let's Encrypt will only be doing DV certs, so it doesn't need one. https://en.wikipedia.org/wiki/S/MIME

I was given a Firefox OS phone at Mozfest last year. I lost my other phone earlier this year and so used it exclusively for four weeks. I'm sorry to say it's pretty terrible at this stage. I was using v2 of Firefox OS.

The problems are broadly that it was slow, unreliable and poorly designed. It would just become completely unresponsive a couple of times a week, requiring the battery to be removed to restart. There are very few well known apps. Twitter seems to be the only one, and it was so slow for scrolling that I gave up using it. The included apps were just placeholders to install apps, almost all of them only worked online. I wouldn't recommend getting one to anybody. I'm sure you could buy a cheap secondhand Android and have a better experience. It was worse than Android 1.6.

There's such a huge mountain of work for the Mozilla developers to get this to be in anyway competitive to Android. I think Mozilla would be better to concentrate their resources elsewhere.

Maybe Mozilla just needs to launch their own Android AOSP implementation and provide developers with a way to build fully native Android apps with JavaScript.

Or is AOSP not going to run on the kind of hardware FFOS is targeting?

Mozilla has already developed technology to make web apps appear as native on Android. Go and check out the Firefox Marketplace.

I've been considering using CartoDB to replace Heroku. I only use basic geo stuff and their maps would be handy. The specs don't really tell you want you get for you money, there's a $29 which might be ok. http://cartodb.com/pricing/

There's no syntactic difference between an attribute, an object and an array.

you can't nest tags into attributes

That isn't well formed, you're missing two </src>.

I dislike XML, the confusion between attributes and sub elements is one of the worst bits.

Hey, one of the Bloomberg developers here. Thanks for the comments.

The prominent most likely score is a bit confusing, if you click through to the match detail then the histogram shows a range of goal differences. So for the first match we predict a goal difference of >2 to Brazil, although the highest probability for an actual score result is 2-0 (16%). Our model makes projections for up to 8-0 in both directions, but we aggregate them for display in this interactive.