<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Browsing, transcoding and intelligent proxies</title>
	<atom:link href="http://alindh.wordpress.com/2005/07/18/browsing-transcoding-and-intelligent-proxies/feed/" rel="self" type="application/rss+xml" />
	<link>http://alindh.wordpress.com/2005/07/18/browsing-transcoding-and-intelligent-proxies/</link>
	<description>whatever seems worth sharing</description>
	<lastBuildDate>Thu, 29 Jul 2010 14:02:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Linen Mania</title>
		<link>http://alindh.wordpress.com/2005/07/18/browsing-transcoding-and-intelligent-proxies/#comment-21</link>
		<dc:creator>Linen Mania</dc:creator>
		<pubDate>Sat, 15 Jul 2006 15:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://alindh.iki.fi/blog/?p=3#comment-21</guid>
		<description>On a side note, the dotMobi mTLD (mobile top level domain) has just been released and is in the sunrise registration period...the promise of dotMobi is to ensure that those sites with dotMobi extension will be tuned to mobile browsing...

one can expect a number of .mobi web sites - those that conform with standards for mobile browsing - to be online starting Oct 2006

More info on dotMobi can be found at &lt;b&gt;&lt;a href=&quot;http://www.mobinomy.com&quot; rel=&quot;nofollow&quot;&gt;Mobinomy.com - the .mobi Directory&lt;/a&gt;&lt;/b&gt;, this site also plans to start a dotMobi directory soon

Ec from &lt;a href=&quot;http://www.linens.in&quot; rel=&quot;nofollow&quot;&gt;Home of Home Textiles @ Linens.in&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>On a side note, the dotMobi mTLD (mobile top level domain) has just been released and is in the sunrise registration period&#8230;the promise of dotMobi is to ensure that those sites with dotMobi extension will be tuned to mobile browsing&#8230;</p>
<p>one can expect a number of .mobi web sites &#8211; those that conform with standards for mobile browsing &#8211; to be online starting Oct 2006</p>
<p>More info on dotMobi can be found at <b><a href="http://www.mobinomy.com" rel="nofollow">Mobinomy.com &#8211; the .mobi Directory</a></b>, this site also plans to start a dotMobi directory soon</p>
<p>Ec from <a href="http://www.linens.in" rel="nofollow">Home of Home Textiles @ Linens.in</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: psp</title>
		<link>http://alindh.wordpress.com/2005/07/18/browsing-transcoding-and-intelligent-proxies/#comment-20</link>
		<dc:creator>psp</dc:creator>
		<pubDate>Fri, 17 Mar 2006 15:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://alindh.iki.fi/blog/?p=3#comment-20</guid>
		<description>My friend and myself have read your blog and thought I must leave a message to bring to your attention that I believe it was great to read. The best bit was the third post</description>
		<content:encoded><![CDATA[<p>My friend and myself have read your blog and thought I must leave a message to bring to your attention that I believe it was great to read. The best bit was the third post</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Perkins</title>
		<link>http://alindh.wordpress.com/2005/07/18/browsing-transcoding-and-intelligent-proxies/#comment-19</link>
		<dc:creator>Kevin Perkins</dc:creator>
		<pubDate>Tue, 28 Feb 2006 00:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://alindh.iki.fi/blog/?p=3#comment-19</guid>
		<description>Thanks for the mention...

We have been at work on a number of your suggestions/recommendations to improve the end-user experience for some time. The Javascript Problem is a major issue from the POV that 85%-90% of devices don&#039;t support this functionality. And most work-arounds are klugey at best. We leave it up to the Skweezer end-user to turn on/off this functionality in their Preferences--the same way you would with your Internet Options in IE, for example.

Also, from the Publisher&#039;s side: we&#039;re sensitive to how the ads (read: &quot;sources of revenue&quot;) are being removed as a function of this Javascript issue. Therefore, we are about to launch an innovative ad marketplace called Advertizer™ that aggregates the best possible ads from multiple suppliers (not just AdSense) so desktop and mobile publishers can maximize their revenues. There will also be a blog plug-in that will retrieve context-based ads and display the result as &quot;straight text&quot;... so no ads will be removed when these transcoding solutions help mobile users see blog content (or any other publisher using our Advertizer plug-ins).

Cheers,
Kevin Perkins
CEO, Greenlight Wireless

http://kevinperkins.wordpress.com/2006/02/27/skweezer-on-your-mobile-desktop-car-webtv-psp-what-next/</description>
		<content:encoded><![CDATA[<p>Thanks for the mention&#8230;</p>
<p>We have been at work on a number of your suggestions/recommendations to improve the end-user experience for some time. The Javascript Problem is a major issue from the POV that 85%-90% of devices don&#8217;t support this functionality. And most work-arounds are klugey at best. We leave it up to the Skweezer end-user to turn on/off this functionality in their Preferences&#8211;the same way you would with your Internet Options in IE, for example.</p>
<p>Also, from the Publisher&#8217;s side: we&#8217;re sensitive to how the ads (read: &#8220;sources of revenue&#8221;) are being removed as a function of this Javascript issue. Therefore, we are about to launch an innovative ad marketplace called Advertizer™ that aggregates the best possible ads from multiple suppliers (not just AdSense) so desktop and mobile publishers can maximize their revenues. There will also be a blog plug-in that will retrieve context-based ads and display the result as &#8220;straight text&#8221;&#8230; so no ads will be removed when these transcoding solutions help mobile users see blog content (or any other publisher using our Advertizer plug-ins).</p>
<p>Cheers,<br />
Kevin Perkins<br />
CEO, Greenlight Wireless</p>
<p><a href="http://kevinperkins.wordpress.com/2006/02/27/skweezer-on-your-mobile-desktop-car-webtv-psp-what-next/" rel="nofollow">http://kevinperkins.wordpress.com/2006/02/27/skweezer-on-your-mobile-desktop-car-webtv-psp-what-next/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the mobile experience &#187; Blog Archive &#187; Aggregating it all</title>
		<link>http://alindh.wordpress.com/2005/07/18/browsing-transcoding-and-intelligent-proxies/#comment-18</link>
		<dc:creator>the mobile experience &#187; Blog Archive &#187; Aggregating it all</dc:creator>
		<pubDate>Wed, 26 Oct 2005 17:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://alindh.iki.fi/blog/?p=3#comment-18</guid>
		<description>[...] The reason why I&#8217;ve been thinking about this is the problem I have with most of modern web services, i.e total lack of support for accessing them through mobile phones (low-resolutions devices with limited bandwidth where AJAX certainly isn&#8217;t an option). Mobile browsing will dominate the web in a few years, so this is a very, very important area. Things I&#8217;ve talked about before, like content transcoding, could be implemented very effectively in a service like this (as the problem domain is quite specific per service type, and not too general when compared to the overall web). Providing mobile optimized API&#8217;s for different types of services would allow for easier creating of mobile front-ends and mash-ups, a thing that certainly isn&#8217;t always easy. [...]</description>
		<content:encoded><![CDATA[<p>[...] The reason why I&#8217;ve been thinking about this is the problem I have with most of modern web services, i.e total lack of support for accessing them through mobile phones (low-resolutions devices with limited bandwidth where AJAX certainly isn&#8217;t an option). Mobile browsing will dominate the web in a few years, so this is a very, very important area. Things I&#8217;ve talked about before, like content transcoding, could be implemented very effectively in a service like this (as the problem domain is quite specific per service type, and not too general when compared to the overall web). Providing mobile optimized API&#8217;s for different types of services would allow for easier creating of mobile front-ends and mash-ups, a thing that certainly isn&#8217;t always easy. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the mobile experience &#187; Blog Archive &#187; aggravating aggregators</title>
		<link>http://alindh.wordpress.com/2005/07/18/browsing-transcoding-and-intelligent-proxies/#comment-17</link>
		<dc:creator>the mobile experience &#187; Blog Archive &#187; aggravating aggregators</dc:creator>
		<pubDate>Sun, 02 Oct 2005 20:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://alindh.iki.fi/blog/?p=3#comment-17</guid>
		<description>[...] Accessible and properly usable by any device/browser. Soon most of will be accessing the net through a phone, and accessibility is becoming an issue for increasingly many. Transcoding etc. on content could be quite hot? [...]</description>
		<content:encoded><![CDATA[<p>[...] Accessible and properly usable by any device/browser. Soon most of will be accessing the net through a phone, and accessibility is becoming an issue for increasingly many. Transcoding etc. on content could be quite hot? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
