Pages

August 22, 2007

Secrets of the Cable Universe #2: Bandwidth, pt 1

As with previous installments (ok, the one :P), this post also isn't so much a "secret" as it is a clearer explanation, with some implications, of widely available information. There's been an increasing fervor building around bandwidth, bandwidth management, and its implications as consumers are now finally beginning to consume rich web content at scale (if "Monkeys kissing women" , "Man in underwear" or crappily digitized stolen content can be considered "rich" :P).

So how much bandwidth does the Cable infrastructure provide?
In past lives, I'd always heard that Cable was a "shared" pipe, while technologies like DSL were not - so let's explore what that means.

To go back to first principles, the coaxial cable coming in from the street to your house delivers about 750mhz (or so that's usable) of information spectrum (I'm not going to get into RF modulation and how it works here). In the old days, that 750mhz was split into 6mhz channels, which turned out to be about what you needed to deliver a single ucompressed "standard defintion" (NTSC) audio/video signal - a channel, basically.

And that's why you basically had about 100 or so channels on Cable, and no more, really - there's a limited capacity to what the "cable" from the Cable head-end into your home could deliver. Fundamentally, it was constructed as a multicast technology - broadcast from the Cable company's head-ends, down your street, and split into homes in your neighborhood. Each node from the head end could pump a signal of sufficient strength to service from 200 to 2000 or so homes (really, really, roughly).

And everybody got basically the same content (though so-called "Conditional Access" would encrypt at the head-end and decrypt either at entry to your house, or on your settop box - again, beyond the scope of this discusion).

Then came digital signals, and things got interesting. Turns out, that over these 6mhz bands, you could send, oh, about 40Mbps of information (still multicast, of course - meaning everyone gets the same information). And if you MPEG-2 compressed your video, that worked out to - for Standard-def (SD) video - about 10 or so video streams per channel (figuring 3.5 to 4Mb per video) - or to put it another way, you could pack 10 or more digital "channels" into the bandwidth occupied by a single analog channel.

In part 2, I'll cover how this maps to Internet Connectivity and your Cable modem and how much bandwidth Cable really delivers to the home(its not the number you think - do the math implied above) .

August 15, 2007

Facebook, baby

(First: Sorry for the post dearth - its August, what can I say?)

It started a bit slowly, but since Facebook opened up its doors to all comers, its become quite the deluge from my social circles (way behind on friend approvals still) - it took LinkedIn many years to achieve any critical mass for me.

Zero to hero very quickly... obviously curiosity and, quite frankly, a well thought out product with a positive developer eco-system have been rewarded (remember this idea?). In fact, no coincidence, I think, that developer APIs coincide with Facebook's recent rapid rise beyond the college crowd... this is how you go from narrow to general: by letting your application become a platform.

That is, you succeed best by letting others success feed you.

So, I'd been meaning to blog about this upswing for a few weeks now... and then I ran into this today:
Ick, old married guys on Facebook

It speaks for itself: Perspective is everything :)

August 2, 2007

The Future's A. Kay

In discussing past lives with a new colleague, I found that he worked (back in the day) at Atari, with, of all folks, Alan Kay (who knew Alan was at Atari?!?).

In any case, it reminded me of one of my all-time favorite quotes, uttered by the aformentioned Mr. Kay:

"The best way to predict the future is to invent it."

There's a boldness there that rarely fails to get my blood pumping.

But its occurred to me: Alan's expression is also a rather clever, oh-so-polite and positive (if slightly passive aggressive) way for a technologist to say: "When I want your opinion, I'll give it you" (think about it) - no wonder I like it so much :)

How about you guys in the peanut gallery? Any favorite sayings that spin on multiple axes of rotation?

July 30, 2007

Filling the Gap (AKA Ideas are cheap)

So betwixt my last work environment and my current one, I had begun going down the path of (again) building my own software. I had (have) a number of ideas - but that's really the easy part. And I'd say "good ideas", but, in my humble opinion, the difference between a "good idea" and a "bad idea" is in the execution.

Which is to say, its value you accrue in arrears, not a judgement you can really make a priori.

I suppose - best case - you hope its a good idea before you start doing it.

In any case, I had 3 things I did actual work on to a real degree (in terms of execution): some middleware, a web app-y thing, and a tool. They had some overlapping technology components but with reasonably distinct market segment targets. Given where I am now, I'm thinking I'll release them each in some form over the next few months - no sense letting them rot on my harddrive.

So - check back; more info soon.

July 16, 2007

GPL v3: A mess of your own making...

The GPL v3 was ratified and released a few weeks ago by the Free Software Foundation - which owns, and upgraded to GPL v3, the copyrights to an important swath of Open Source Software (OSS).

The intent of the GPL (GNU Public License) all along has been to empower people who were using software released under GPL ("copyleft" software) to make modifications to said software, and to use and redistribute modifications and improvements to others, for collective benefit. The primary legal intent of this latest revision, as I had mentioned previously, was to close the server and computing devices "holes" in previous versions - whereby companies were:

(a) using GPL software on their servers, but NOT releasing changes or improvements (because they were not distributing the software - which was the previous trigger for obligating a company to share its improvements to any GPL software) to anyone, per se, but rather letting users consume software services remotely, and/or

(b) preventing (effectively) modification and re-distribution of the software because their device was in some way preventing any modified software being loaded or running on the device (so called "TiVo-ization").

There are other OSS licenses which were always intended to be less radical: BSD, MIT, ZLIB, MPL, etc. These licenses have always been of the "do-what-you-want-but-its-not-our-fault" variety, and have arguably been as successful with their projects as the GPL - and the GPL has often been described as "viral" in that any GPL code may not be linked with non-GPL code.

But that's not the point.

The point is that they revised the license to close the loophole. And from there, much hilarity ensued:

Microsoft statement about GPLv3
Groklaw on Microsoft and GPLv3
GPL: fear is the key

Linux creator calls GPLv3 authors "Hypocrites"
Apple and the GPL

So, to summarize: group that OWNS the copyright to some software closes a loophole in how they intended that software to be consumed - and everybody's pissed (note that this is NOT retroactive - nor could it be; that's part of the intent of the philosophy of the license!). The big problem, of course, is all the folks who mistook the GPLv2 as (a) giving them rights they weren't supposed to have (e.g. using it to build closed source server software) and/or (b) took the license as contract for future commitments.

Oops. Sorry.

(btw, Linus Torvalds, of Linux fame, expressly does NOT seem to be confused. He just doesn't like it - and as copyright holder to the Linux kernel, he's free to do as he chooses - and I suppose to make overwrought analogies.)

July 9, 2007

Presence is not an Identity feature

I realized in my "Unique Visitors" post that I skipped some background - didn't "show my work" as every math teacher I had always said.

When Google released GTalk, I remember feeling like they had missed an opportunity to correct the
Presence, Identity, Messaging and Accounts model - that they should have made "location" more than just metadata, but I don't think that's right, actually.

On the PC side of the Instant Messaging (IM) universe, Presence is exerted by an Identity, and (nowadays) often qualified by Location (for Location Based Services) and/or Network of Origin (for interoperation messaging systems), but I think Presence, especially for Comcast, is really a device feature, and Identities are transiently bound to those devices, generally with an (essentially) eternal TTL (time-to-live), though in the case of PCs, that TTL amounts to IM session length.

Identity is a kind of user virtualization construct (usually reasonably synonymous with "Credentials": username and password - at least for our purposes), while Presence advertises availability for messaging, and Messaging is generally a point-to-point session negotiation and communication pipe, though it may be one-to-many (broadcast), or many-to-many (chat). Note that Messaging and Presence need not necessarily be interdependent. Finally, Accounts are a billing relationship construct.

A typical use case in a househould is likely to involve multiple STBs (set top box or other consumer electronics device on the Comcast networks), multiple .net IDs (e-mail addresses), and multiple PCs in the house, where Presence, Identity, Message and Accounts overlap each. And of course, wireless, school/office, and multiple residences complicate the picture.

Usually, scalability for Presence is scale limited by subscription/notfication events, and by that I mean the "m X n" implied by the "Buddy List" construct, where any user may be subscribed to presence notification of any n users (effectively O(n^2) ). Messaging is bound by active simultaneous communication sessions (and type - multimedia for example) and is usually O(n).

In any case, I'm just rambling now - all of that's a roundabout way of saying that messaging is a service feature, not a product :)