<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Encoding, decoding, and&#8230; monkeys?</title>
	<atom:link href="http://mroth.info/blog/2005/02/28/encoding-decoding-and-monkeys/feed/" rel="self" type="application/rss+xml" />
	<link>http://mroth.info/blog/2005/02/28/encoding-decoding-and-monkeys/</link>
	<description>Infrequent updates from a social technologist.</description>
	<pubDate>Wed, 19 Nov 2008 03:41:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Geeko Tuck</title>
		<link>http://mroth.info/blog/2005/02/28/encoding-decoding-and-monkeys/#comment-2852</link>
		<dc:creator>Geeko Tuck</dc:creator>
		<pubDate>Mon, 18 Jul 2005 22:21:17 +0000</pubDate>
		<guid isPermaLink="false">/?p=79#comment-2852</guid>
		<description>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!</description>
		<content:encoded><![CDATA[<p>WYSIWYG has been replaced by integrated &#8220;accessibility&#8221; 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&#8217;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 &#8220;Best viewed with browser xxxxx&#8221;. Firefox has taken an excellent interim step by selectibly disabling functions of javascript that inhibit accessibility.</p>
<p>PS. Off site adaptive document behavior modification has been around since cookies&#8230; Sun designs Java to be intepreted by the recipient. About popup blocking being integrated into their browser&#8230; Try downloading from download.microsoft.com and you will see a popup that breezes right past their own blocker:(</p>
<p>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&#8217;s advertisments on the field of a TV sports program, they just have to be ignored but then they become subliminal!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zilla Smash!</title>
		<link>http://mroth.info/blog/2005/02/28/encoding-decoding-and-monkeys/#comment-826</link>
		<dc:creator>Zilla Smash!</dc:creator>
		<pubDate>Tue, 01 Mar 2005 11:08:02 +0000</pubDate>
		<guid isPermaLink="false">/?p=79#comment-826</guid>
		<description>&lt;strong&gt;GreaseMonkey Is Cool&lt;/strong&gt;
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...</description>
		<content:encoded><![CDATA[<p><strong>GreaseMonkey Is Cool</strong><br />
I was linked from mozdev.org - greasemonkey this evening by a good friend&#8217;s blog and I have to say, this is really cool.  It&#8217;s an extension for FireFox that allows you to inject custom JavaScript into any pages that match a certain URL regex.  It app&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Dunck</title>
		<link>http://mroth.info/blog/2005/02/28/encoding-decoding-and-monkeys/#comment-825</link>
		<dc:creator>Jeremy Dunck</dc:creator>
		<pubDate>Tue, 01 Mar 2005 04:21:32 +0000</pubDate>
		<guid isPermaLink="false">/?p=79#comment-825</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>If you like Greasemonkey and have access to Safari, check out PithHelmet.</p>
<p>GM&#8217;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.</p>
<p>I concur w/ Ryan, though; this is a bit of a different animal than a proxy.</p>
<p>Leveraging the widespread knowledge of DOM/JS in this way is important.  The web is changing indeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Shaw</title>
		<link>http://mroth.info/blog/2005/02/28/encoding-decoding-and-monkeys/#comment-824</link>
		<dc:creator>Ryan Shaw</dc:creator>
		<pubDate>Mon, 28 Feb 2005 23:37:30 +0000</pubDate>
		<guid isPermaLink="false">/?p=79#comment-824</guid>
		<description>I think Greasemonkey and other browser extensions go beyond what Proximotron does in that they can change &lt;em&gt;behavior&lt;/em&gt; 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 &lt;a href="http://www.readwriteweb.com/archives/002637.php"&gt;Richard McManus's post on remixing RSS&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I think Greasemonkey and other browser extensions go beyond what Proximotron does in that they can change <em>behavior</em> 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.</p>
<p>Still, I like your take on the phenomenon of user-remixed data streams. You might be interested in <a href="http://www.readwriteweb.com/archives/002637.php">Richard McManus&#8217;s post on remixing RSS</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
