Cluster

Back in the day, Mac programmers had to deal with what their tattered copies of Inside Macintosh called handles: doubly indirected pointers to data structures. Handles made memory management easier — the actual data structures can be created anywhere, and moved around, without software authors having to explicitly deal with garbage collection and other memory management issues. Good Mac programming involved always working on objects only through their handles (^^PictRect for example).

Back to digital media: the progression {unique original to instance of clones, to pointer to — not originals — but architectures in flux, constantly being revisted and tweaked by their authors (c.f. the Web!)}. A culture where this is anticipated requires rapid, near zero-cost perfect distribution. In my version of DRM, content owners effectively license not content, but handles to content: consumers would purchase a signed key which only (doubly?) indirectly points back to the media source. Not only lightweight and respectful of consumer needs, this model supports the current acceleration of mutable media: {remix culture -> director’s cut -> reduxes (sic)}. DRM as secure handles, coupled with a robust versioning and inheritance model, enables many interesting possibilities for content creators, licensors and consumers. And an inheritence model where you can fork version trees also suggests a possible future form of {scarcity -> value -> market}, even with instances: version 1.00.34.7 of Apocalypse Now might still be an object with a specific, market driven value… more on this later…