BattleScripts!

Automated disclaimer: This post was written more than 16 years ago and I may not have looked at it since.

Older posts may not align with who I am today and how I would think or write, and may have been written in reaction to a cultural context that no longer applies. Some of my high school or college posts are just embarrassing. However, I have left them public because I believe in keeping old web pages aliveā€”and it's interesting to see how I've changed.

As I watch my browser fill with extensions which enhance web pages by adding scripts (Greasemonkey, Platypus, Cocomment, ), I wonder whether some sites may start fighting back. Perhaps Google may detect Platypus removing a text ad, and add a page script to re-insert the ad. Will scripts begin to battle, wage wars of privilege, namespace, obfuscation, and timing? Will the javascript sandbox become a bloody battlefield, littered with object literals, new troops parachuting in via JSON headers and asynchronous XML HTTP requests? Will the DOM tree be hung with broken and battered functions? I envision closures spawning closures, surveiling the digital landscape, emerging from their window.setTimeout bunkers to strike again...

Responses: 2 so far Feed icon

  1. viperteq says:

    I think it would be messed up for Google, or any website for that matter, to do something like that. I think developers should design their sites how they want, with Standards and Accessibility in mind, but they should have some type of message acknowledging that visitors will likely do something that might hinder the viewing experience of the site. The message should say that while they respect the users rights to view a website in whatever fashion they please, users should understand that by doing so they may miss out on some functionality or other that is built into the site.

  2. Tim McCormack says:

    Sounds like a reasonable compromise.

    I know that Gmail was having a problem with one or another Greasemonkey scripts making too many requests on the server, and that they were trying to block the scripts, but that has since been worked out.

Self-service commenting is not yet reimplemented after the Wordpress migration, sorry! For now, you can respond by email; please indicate whether you're OK with having your response posted publicly (and if so, under what name).