Big change
I've been on leave this past term — playing to my strengths, planning my own schedule — and now school is starting tomorrow. So I don't have a blog post to offer. I'm glad to be going back to the classroom.
See you on the other side of tomorrow.
Up with Up — Big Clash Coming
About 18 months ago I wrote a little post called “Up With Up” — about the importance of uploading.
There are big clashes coming when users discover they can't upload predictably.
1. BitTorrent. John Waclawsky pointed me to this Wikipedia chart listing ISPs that block BitTorrent. How do the ISPs do it? And how do they decide between “good” and “bad” BitTorrent protocol uses? James Enck and others point out that there are many studios and virtual world companies using it for distribution — a legit, legally Torrent-able Harry Potter trailer, anyone? Huge headaches coming, and only getting worse with high definition files. (Top ten Torrent-ed files listed here.) Here's a paper about symmetric broadband use in Japan — where a small percentage of users is accounting for most of the upload traffic.
To block it, you need to sniff out the Torrent seeds and headers. Fascinating discussion here between admins trading tips on blocking a computer-literate Torrent user.
2. Not providing symmetrical upload. Carriers assume that people will download, not upload. Dave Burstein provided me with the following (paraphrasing, all mistakes are mine): For DSL, there's also a lot of interference caused by the strong user-side transmitter. So ADSL was originally designed for 6 Mbps down, 768K up. And, besides, telcos want to be able to hang onto enough bandwidth to sell videos. For the telcos, it would be simple (and incredibly inexpensive — pennies — to provide symmetric 768K up and down, but they want to upsell people to 3 Mbps down, 768K up. Same with cable — it would be easy to provide symmetrical upload, but DOCSIS 3.0 is designed for 1 Gbps down, 100 Mbps up because cable carriers don't make money on upload “services.”
In other countries where there's more competition, carriers tend to provide symmetric upload/download.
3. The Venice Project. From the people who brought us Kazaa and Skype. Here's a description:
“The Venice Project is a streaming video application, and so uses a relatively high amount of bandwidth per hour. One hour of viewing is 320MB downloaded and 105 Megabytes uploaded, which means that it will exhaust a 1 Gigabyte cap in 10 hours. Also, the application continues to run in the background after you close the main window.”
“For this reason, if you pay for your bandwidth usage per megabyte or have your usage capped by your ISP, you should be careful to always exit the Venice Project client completely when you are finished watching it.”
Here are some network operators mulling over the implications.
So — we've only just begun the upload battles.
[Heartfelt thanks to the members of Gordon Cook's list who sent along this information.]