So that you can continue to work on the same project between the tablet-like environment and the desktop-like environment without having to bounce everything off Dropbox and eat into your monthly cap.

Depends on what kind of boat. If it's a coracle (bowl-shaped 1-person boat intended to be carried on a man's back), and it's in usable condition, I'll take it.

No musical recordings have entered the public domain due to expiration of copyright. Ever. When the U.S. Congress expanded copyright to sound recordings in 1972, it allowed existing sound recording copyright laws at the state level, some of which provide for a perpetual term, to continue for one full work-made-for-hire copyright term. This means all sound recordings produced before 1972 are under copyright in at least one U.S. state until 2067 (17 USC 301(c)). If the songs were first published on or after January 1, 1923, the songs are not in the public domain in the United States. If at least one songwriter was surviving on or after January 1, 1944, the songs are not in the public domain in the European Union.

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.

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.

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.

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.

IE on Windows Server 2003 has the same lack of SNI support as IE 8 on Windows XP, and Windows Server 2003 isn't even EOL yet.

I read Slashdot's non-mobile site without problems on my first-generation Nexus 7 tablet. Chrome and Firefox both do a good job of blowing up the text so that it's readable without having to scroll sideways. I have Slashdot set never to use the mobile site because the mobile site didn't support the Preview button when I checked.

Good point. Correct it to "stick it for when the sun don't shine".

SoylentNews is people. Like Slashdot, SoylentNews runs Slash software. But unlike Slashdot, SoylentNews is secure and Unicode-capable.

That would require Slashdot to switch to an ad network that supports HTTPS, such as Google AdSense. Which others do?

But if your site is behind a CDN proxy and highly cacheable, then you can probably get away with cheap hosting like WebFaction or something.

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.

Have an Amish family live in your house for a year. Then that family can plead freedom of religion, as Amishism forbids connection to public utilities.

"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. :p