Setting up a burner number is pretty easy.
So long as someone else on Facebook didn't already use the same burner number before it was reassigned to you. And you still have to buy a phone on which to use the burner number.
Gingerbread is finally disappearing but it's taken a while.
I still haven't seen an iPod touch counterpart (that is, a 4"-class tablet without a cellular radio) that runs recent Android. Both the Archos 43 Internet Tablet and the Samsung Galaxy Player are stuck on 2.x without rooting and CMing the thing because they lack the RAM for 4.x.
aren't there privacy issues associated with SNI? [describes outline of attack]
Someone monitoring your DNS requests can see the same hostname that you're sending to the SNI server. Besides, pre-DNS, someone monitoring your TLS requests could see the IP address to which you connect and the certificate that the server returns.
Old browsers can still use the non-HTTPS site.
Here's how that breaks: Somebody uses the new browser to share a link to a page on the HTTPS site with somebody else, and somebody else uses an old browser to view that page. Certificate error.
CloudFlare's servers will use SNI for free accounts, which is unsupported for IE on Windows XP and older, and Android Browser on Android 2.2 and older.
Lack of support for EOL'd web browsers is one roadblock for affordable HTTPS hosting. The other is that many major ad networks lack support for HTTPS, leading web browsers to block the ads as "mixed content." (AdSense added HTTPS support only a year ago.) And this is why Slashdot is among sites that redirect non-subscribers from HTTPS to HTTP because they subcontract advertising.
That's [the electric power distribution companies'] future business, moving power around and storing it for use when the sun isn't shining.
"Are you generating more solar power than you can use? We'll give you somewhere to stick it when the sun don't shine." That'll go over nicely.