Encoding, decoding, and… monkeys?

What is it with monkeys and the web anyhow?

Lot of talk lately about Greasemonkey, which is essentially a filtering proxy server integrated into a Firefox extension. It lets users share scripts that will alter websites via pattern matching, typically in ways that privilege the reader’s experience (e.g. automatic redirection to the printer friendly version of a NYTimes.com article, removing useless ad-content from a weather.com page). For those who run filtering web-proxies such as Proximitron this is nothing new at all, but the change to a browser plugin methodology will result in it being more accessible to less technically inclined users.

For several years now (beginning with my MA thesis at NYU), my research has focused on precisely the question of user-modified “reading” of technological documents via automated content mutation. Those of you who follow my work (yeah, right) will know that I spoke about the topic at MEA two years ago, where I predicted that that tools for such methodologies would soon be integrated into the browser itself. Looks like that’s now precisely what is happening, evidenced in the popularity of Greasemonkey.

These tools expose the fundamental nature of communication in an environment characterized by encoding and decoding of information into/from standardized interpreted formats. To quote from the abstract of my MEA2003 paper:

Rather than being simply “read,” digital network streams are interpreted by a client’s software agent–allowing for the possibility of constructing divergent (cooked) meanings from a single homogeneous (raw) source. Thus, in digital networks, the point of experience (e.g., the visual document) is in many ways a constructed fiction—the “document” being composed of network streams that are only assembled into coherence in the space of the user’s own domain, taking place as a process within the reader’s personal computer at the moment of interaction. During this transformation from a computer-readable format to a human-readable format, there exists a large degree of interpretative freedom: the ability for the reader to influence how the raw data will be represented via exercising control over the decoding process.

That’s what tools like Greasemonkey do: let the user exercise control over the decoding process, reading a document the way they want. To put it another way: WYSIWYG is dead.

I expect to see these sort of features being integrated directly into the main featureset of mainstream browsers in the short-term. Heck, even Microsoft has now integrated a popup-blocker into MSIE.

The next step is moving from mere content-mutation to the production of recombinant documents, that pull freely from multiple heterogeneous sources to produce a single “perspective” for viewing. Think of it as a DJ remixing songs, only for the web, and in a persistent fashion. Increasing protocol standardization is going to be the glue that drives this one. It’ll happen, just you wait.

Trackbacks & Pings

  1. Zilla Smash! on 01 Mar 2005 at 5:08 am

    GreaseMonkey Is Cool
    I was linked from mozdev.org - greasemonkey this evening by a good friend’s blog and I have to say, this is really cool. It’s an extension for FireFox that allows you to inject custom JavaScript into any pages that match a certain URL regex. It app…

Comments

  1. Ryan Shaw wrote:

    I think Greasemonkey and other browser extensions go beyond what Proximotron does in that they can change behavior of web applications, not just the content of more-or-less static documents. I suppose this is possible with filtering proxies in principle, but in practice changing the behavior of a complex DHTML application being delivered to the browser is difficult without access to a JavaScript interpreter and all the other browser APIs.

    Still, I like your take on the phenomenon of user-remixed data streams. You might be interested in Richard McManus’s post on remixing RSS.

  2. Jeremy Dunck wrote:

    If you like Greasemonkey and have access to Safari, check out PithHelmet.

    GM’s implmentation is actually pretty simple at the moment; it just does a URL match, and injects the user script (a regular javascript) into the document being loaded.

    I concur w/ Ryan, though; this is a bit of a different animal than a proxy.

    Leveraging the widespread knowledge of DOM/JS in this way is important. The web is changing indeed.

  3. Geeko Tuck wrote:

    WYSIWYG has been replaced by integrated “accessibility” ever since a user was allowed to override the original text colors/fonts and browsers zoomed images to fit the viewable area. Some level of accessibility is built-in but still not as well integrated with its browser as most plugins- extreme customizations still cause illegibility by overlaying page elements of a static WYSIWYG page; i.e. text that’s too big for the dimensions of a non scrollable box, and automatic formatting breaks lines of text at strange places. Once accessibility is expected, (hopefully:) webmasters may no longer have to design around “Best viewed with browser xxxxx”. Firefox has taken an excellent interim step by selectibly disabling functions of javascript that inhibit accessibility.

    PS. Off site adaptive document behavior modification has been around since cookies… Sun designs Java to be intepreted by the recipient. About popup blocking being integrated into their browser… Try downloading from download.microsoft.com and you will see a popup that breezes right past their own blocker:(

    Y3K DHTML! Like the textless unfilterable spam content of today, Future websites will consist of a single photo-audio file that is dynamically assembled at the website with integrated jig-saw pieces pre-supplied by advertisers. Try blocking today’s advertisments on the field of a TV sports program, they just have to be ignored but then they become subliminal!

Post a Comment

Your email is never published nor shared.