<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" xml:lang="en" xml:base="http://qwang.net/wp-atom.php">
	<title type="text">making time</title>
	<subtitle type="text" />

	<updated>2009-06-03T21:20:06Z</updated>
	<generator uri="http://wordpress.org/" version="2.8">WordPress</generator>

	<link rel="alternate" type="text/html" href="http://qwang.net" />
	<id>http://qwang.net/feed/atom/</id>
	

			<link rel="self" href="http://feeds.feedburner.com/makingtime" type="application/atom+xml" /><feedburner:emailServiceId>makingtime</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.feedburner.com%2Fmakingtime" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fmakingtime" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://feeds.feedburner.com/makingtime" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Ffeeds.feedburner.com%2Fmakingtime" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2Fmakingtime" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.plusmo.com/add?url=http%3A%2F%2Ffeeds.feedburner.com%2Fmakingtime" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare href="http://www.live.com/?add=http%3A%2F%2Ffeeds.feedburner.com%2Fmakingtime" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[Federation and cash cows]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/KJdQjaD4O2E/" />
		<id>http://qwang.net/?p=465</id>
		<updated>2009-06-03T21:20:06Z</updated>
		<published>2009-06-03T21:20:06Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[Google Wave wants to reinvent email, the original killer app, but it raises an old question: who actually made money from email?  Thinking back on computing history, I can think of 4 killer apps that are in a league of their own: the window-based operating system, the office suite, email, and web search.  Three of [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20090603/federation-and-cash-cows/">&lt;p&gt;&lt;a href="wave.google.com"&gt;Google Wave&lt;/a&gt; wants to reinvent email, the &lt;em&gt;original&lt;/em&gt; killer app, but it raises an old question: who actually made money from email?  Thinking back on computing history, I can think of 4 killer apps that are in a league of their own: the window-based operating system, the office suite, email, and web search.  Three of those four are industry-defining cash cows:  Windows and office for Microsoft, and web search for Google.  That makes email the odd one out; sure some people make money from the technology, e.g.,  spammers, but email does not fund an Microsoft or Google-esque empire.  How can something so fundamentally important to the world reap so little profits?  Well of the four killer apps, email is the only one that is federated, and couldn&amp;#8217;t exist any other way.  Painted in that sense, email is a rather heroic transfer of economic surplus from its creators to the users.  Regardless of whether or not Google has some genius plan to make Waves into its second cash cow,  hats off to them for taking one of the boldest moves in technology in a long time.&lt;/p&gt;
&lt;p&gt;Lots of other things have been said about Waves, so I&amp;#8217;m not going to revisit them.  I particularly like &lt;a href="http://radar.oreilly.com/2009/05/google-wave-what-might-email-l.html"&gt;Tim O&amp;#8217;Reilly&amp;#8217;s take&lt;/a&gt;.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=KJdQjaD4O2E:2dHvaEc-1wg:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=KJdQjaD4O2E:2dHvaEc-1wg:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090603/federation-and-cash-cows/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090603/federation-and-cash-cows/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	<feedburner:origLink>http://qwang.net/20090603/federation-and-cash-cows/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[A new mashup experience]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/dtXQfLOR7Zs/" />
		<id>http://qwang.net/?p=448</id>
		<updated>2009-04-30T05:12:03Z</updated>
		<published>2009-04-30T04:28:53Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[There&#8217;s a lot of controversy over the politics of DiggBar &#8212; over ownership of the content and control of the landing URL.  However, I don&#8217;t really see it so much as a political issue as it is a technical problem.   The fact is there simply isn&#8217;t a good way of overlaying 3rd party functionality into [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20090429/a-new-mashup-experience/">&lt;p&gt;There&amp;#8217;s a lot of controversy over the &lt;a href="http://www.techcrunch.com/2009/04/15/despite-huge-activity-digg-offers-a-compromise-on-diggbar/"&gt;politics of DiggBar&lt;/a&gt; &amp;#8212; over ownership of the content and control of the landing URL.  However, I don&amp;#8217;t really see it so much as a political issue as it is a technical problem.   The fact is there simply isn&amp;#8217;t a good way of overlaying 3rd party functionality into the browsing experience without resorting to a plugin install or hijacking the outbound link like the DiggBar does.  I don&amp;#8217;t really believe it is Digg&amp;#8217;s intention to steal anybody&amp;#8217;s &amp;#8220;link juice&amp;#8221;, but their actions result from a technical limitation—either they settle for an install, which would have appalling uptake, or do the nasty iframe.  What&amp;#8217;s a potential technical solution?  We need a new class of browser plugins that 1) activates immediately without install 2) dispatched from the cloud, thus portable outside of a single browser installation, and 3) protected from malicious cross-site-scripting&lt;/p&gt;
&lt;h3&gt;A new class of browser plugins&lt;/h3&gt;
&lt;h4&gt;What I&amp;#8217;m really describing is really a fast, safe, and fully managed framework for accomplishing cross-site-scripting, a concept generally associated with malicious deeds but is also the underlying functionality most social toolbars are trying to accomplish.&lt;/h4&gt;
&lt;p&gt;To distinguish these from regular browser plugins, I will henceforth refer to them as XSS (cross-site-scripts):&lt;/p&gt;
&lt;p&gt;Now how do we achieve instant-on without install (criteria #1)?  I think this is the easiest of the three, as the Greasemonkey architecture already allows you to instantly enable functionality overlayed over 3rd party sites.  While Greasemonkey scripts are limited to Javascript injections and lack the full power of Firefox plugins, I&amp;#8217;d argue that most of the battle is already won with just JS.  You can implement a variety of content and functionality overlays including the DiggBar, StumbleBar, and even the Meebo chat bar.&lt;/p&gt;
&lt;p&gt;The portability criteria (#2) is based on the idea that each XSS is a piece of enhanced functionality sanctioned by a particular user, and thus should be attached to that user wherever he goes, NOT attached to the browser installation.  By electing to allow the DiggBar to appear over other web sites, I&amp;#8217;m really setting a browsing preference for my Digg user account, not a preference within the browser.  When I logon to Digg from a friend&amp;#8217;s or a public computer, that functionality should follow me, and the opposite should be true when a friend borrows my computer and signs on with his credentials.  That means we need a web service to manage a user&amp;#8217;s libary of XSS and dispatch/activate them all at once whenever a user logs in from a different computer.  If I want a Meebo bar, a Digg button in the context menu, and a Gmail notifier, I shouldn&amp;#8217;t need through the motion of signing into all three to enable that functionality!&lt;/p&gt;
&lt;p&gt;Ensuring safety is probably the hardest one, and is the one thing that can make this whole idea buckle.  I can suggest a few precautions, but I most certainly wouldn&amp;#8217;t catch all the corner cases.  Functionality of XSS should be limited to approximately what Javascript can do.  That means XSS should live in a runtime that cannot access the file system (but a sandboxed DB can come in handy ala Google Gears) nor touch the local OS in any way.  To prevent theft of sensitive data, all XSS should be turned off by default for https pages.&lt;/p&gt;
&lt;h3&gt;User choice&lt;/h3&gt;
&lt;p&gt;Another benefit of this XSS model is that it shifts the choice back to the user in terms of what kind of enhanced functionality should be activated.  I really like the &lt;a href="http://www.snap.com/"&gt;SnapShots&lt;/a&gt; popups, and I have deployed them on this site as the webmaster.  But it what if I, as a visitor wants the same functionality on other sites?   Sure I can go install the Firefox plugin, or worse the Explorer plugin in .exe form, but I belive this will &lt;em&gt;never&lt;/em&gt; become standard behavior for non-techies.  To drive uptake rates, we should start pushing browser functionality and behavior preferences into the cloud as well.  With something like the Meebo chat bar , I find it rather backwards that site owners have the burden and choice of implementing what is essentially an overlay interface, when it fact, it makes much more sense as the users&amp;#8217; choice.  The browsing experience is increasingly comprised of multiple content &amp;amp; service providers cohabiting a single tab/frame.  Thus far, this kind of mashup experience is initiated and implemented by the site owner.  With a plugin framework that has a real shot of getting installed by the masses, we can have a real user-selected mashup experience.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=dtXQfLOR7Zs:3hmMRzNrtPk:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=dtXQfLOR7Zs:3hmMRzNrtPk:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090429/a-new-mashup-experience/#comments" thr:count="1" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090429/a-new-mashup-experience/feed/atom/" thr:count="1" />
		<thr:total>1</thr:total>
	<feedburner:origLink>http://qwang.net/20090429/a-new-mashup-experience/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[Overlapping shares]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/0ogt3vgVT9w/" />
		<id>http://qwang.net/?p=431</id>
		<updated>2009-04-29T05:30:55Z</updated>
		<published>2009-04-28T21:26:14Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[Yes, there’s a deluge of data from social media, and people are clamoring for proper filtering mechanisms.  Before you even start a conversation about filters, there’s a quick-win to reduce the noise: collapsing identical shares from multiple sources.  As I comb through my daily news sources, I’m starting to bump into the same [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20090428/overlapping-shares/">&lt;p&gt;Yes, there’s a deluge of data from social media, and people are clamoring for proper filtering mechanisms.  Before you even start a conversation about filters, there’s a quick-win to reduce the noise: collapsing identical shares from multiple sources.  As I comb through my daily news sources, I’m starting to bump into the same news entry or awesome-must-see-video! from different people or blogs.  Now, if all those shares happen to be on Friendfeed, then it’d collapse all of them into a single line item and just credit that share to multiple sources.  This needs to happen everywhere for any post that is essentially an redirect (in other words, a link to the content without any real additional content or commentary).  This is especially necessary on Twitter where I hear about the same viral link multiple times from different people, often days apart!&lt;/p&gt;
&lt;p&gt;There’s two ways to fix this.  The temporary patch is to have smarter aggregators that can spot non-unique or “redirect” content and collapse them, but that’s hard work and isn’t 100% accurate.  The squeeky-clean solution is to develop formal, machine-readable conventions for labeling this type of content, but requires essentially adding meta-data baggage to things as simple as tweets =(&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=0ogt3vgVT9w:NiQHEW2UJU8:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=0ogt3vgVT9w:NiQHEW2UJU8:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090428/overlapping-shares/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090428/overlapping-shares/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	<feedburner:origLink>http://qwang.net/20090428/overlapping-shares/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[A departure from freemium]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/1lZun1v5pe4/" />
		<id>http://qwang.net/?p=425</id>
		<updated>2009-04-29T05:31:37Z</updated>
		<published>2009-03-14T23:59:11Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[Quake Live: say the technology matures, and scales.  How hard will it be to fork the game and bring back the old mods?  And if so, could they create a marketplace for modders and collect reve-share ala iPhone App store?  Best part about this is that  the Quake 3 mods already exist, the experiment is [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20090314/bring-back-the-mods/">&lt;p&gt;Quake Live: say the technology matures, and scales.  How hard will it be to fork the game and bring back the old mods?  And if so, could they create a marketplace for modders and collect reve-share ala iPhone App store?  Best part about this is that  the Quake 3 mods already exist, the experiment is in porting over and launching a market where real-money is spent on these mods.  The one other site doing something similar, but with flash games is &lt;a href="http://whirled.com"&gt;Whirled&lt;/a&gt;.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=1lZun1v5pe4:P27nXE9BRq4:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=1lZun1v5pe4:P27nXE9BRq4:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090314/bring-back-the-mods/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090314/bring-back-the-mods/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	<feedburner:origLink>http://qwang.net/20090314/bring-back-the-mods/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[A browser feature request]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/Wd0aPh4QlNw/" />
		<id>http://qwang.net/?p=417</id>
		<updated>2009-04-29T05:31:53Z</updated>
		<published>2009-02-01T21:42:00Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[
I have a simple feature request for browsers: a visual indicator for which tabs are playing music
Between Hype Machine, The Next Big Sound, and The Sixty One, I use my browser increasingly more as a music player; and managing music vs content tabs is a rather unrefined art.  Too bad though, for as far as [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20090201/a-browser-feature-request/">&lt;p&gt;&lt;img class="alignnone size-full wp-image-418" title="sound_indicator" src="http://qwang.net/wordpress/wp-content/uploads/2009/02/sound_indicator.jpg" alt="sound_indicator" width="574" height="127" /&gt;&lt;/p&gt;
&lt;p&gt;I have a simple feature request for browsers: a visual indicator for which tabs are playing music&lt;/p&gt;
&lt;p&gt;Between &lt;a href="http://hypem.com"&gt;Hype Machine&lt;/a&gt;, &lt;a href="http://thenextbigsound.com"&gt;The Next Big Sound&lt;/a&gt;, and &lt;a href="http://thesixtyone.com"&gt;The Sixty One&lt;/a&gt;, I use my browser increasingly more as a music player; and managing music vs content tabs is a rather unrefined art.  Too bad though, for as far as I know, this is technically quite challenging for even a FF plugin to do as it requires tapping into the Flash plugin&amp;#8217;s run-time environment.  Another reason &lt;a href="http://qwang.net/20081105/the-role-of-the-browser/"&gt;why the browser UI needs an overhaul&lt;/a&gt; and become as robust as that of an OS.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=Wd0aPh4QlNw:ZSzbhC74HHo:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=Wd0aPh4QlNw:ZSzbhC74HHo:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090201/a-browser-feature-request/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090201/a-browser-feature-request/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	<feedburner:origLink>http://qwang.net/20090201/a-browser-feature-request/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[The innovation is in social messaging]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/oND0k2TiBsY/" />
		<id>http://qwang.net/?p=414</id>
		<updated>2009-04-29T05:31:58Z</updated>
		<published>2009-01-18T00:40:06Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[I&#8217;m totally digging the concept of a MySpace email product.  I&#8217;ve expressed before the importance of bridging social networks with day-to-day communication, and we&#8217;ve heard before that Mark Zuckerberg identies Facebook as primarily a communication tool.  What traditional social network provides is a form of what I&#8217;d call &#8220;passive&#8221; communication—users generating feeds of information and [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20090117/the-innovation-is-in-social-messaging/">&lt;p&gt;I&amp;#8217;m totally digging the concept of a &lt;a href="http://www.techcrunch.com/2009/01/15/confirmed-myspace-building-stealth-webmail-product/"&gt;MySpace email&lt;/a&gt; product.  I&amp;#8217;ve expressed before the importance of &lt;a href="http://qwang.net/20080511/approaching-social-email-from-the-other-side/"&gt;bridging social networks with day-to-day communication&lt;/a&gt;, and we&amp;#8217;ve heard before that &lt;a href="http://www.viddler.com/explore/allfacebook/videos/13/"&gt;Mark Zuckerberg identies Facebook as primarily a &lt;em&gt;communication tool&lt;/em&gt;&lt;/a&gt;.  What traditional social network provides is a form of what I&amp;#8217;d call &amp;#8220;passive&amp;#8221; communication—users generating feeds of information and consuming it in a distributed and asynchronous fashion.  Email, on the other hand, is active communication—with people usually addressing one or few individuals with a direct message.&lt;/p&gt;
&lt;p&gt;But why are they separate?  Its clear that either form can benefit immensely from being connected to a social graph!  Email can be prioritized by the graph, or it can &lt;em&gt;generate&lt;/em&gt; a prioritization based frequency and reciprocity of contact.  New forms of direct messaging that used to clog up the inbox can be categorized and presented in new UI regimes: for example event invitations can be pulled out of the inbox and into a calendar layer, social game envents (like being bitten by yet another vampire) can be grouped into its own river of minor news, messages can be easily visualized by contact.  Here&amp;#8217;s another idea: imagine adding pictures and videos to email without the the dreaded &amp;#8220;attachment&amp;#8221;  process—just pull content from the network&amp;#8217;s internal libraries.&lt;/p&gt;
&lt;p&gt;Social networking will be the best thing that ever happened to email (since webmail), and vice versa.&lt;/p&gt;
&lt;p&gt;&lt;object width="437" height="333" data="http://www.viddler.com/player/e7440ffc/" type="application/x-shockwave-flash"&gt;&lt;param name="id" value="viddler" /&gt;&lt;param name="allowScriptAccess" value="always" /&gt;&lt;param name="allowFullScreen" value="true" /&gt;&lt;param name="wmode" value="transparent" /&gt;&lt;param name="src" value="http://www.viddler.com/player/e7440ffc/" /&gt;&lt;param name="name" value="viddler" /&gt;&lt;param name="allowfullscreen" value="true" /&gt;&lt;/object&gt;&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=oND0k2TiBsY:8NWPN8WpEiA:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=oND0k2TiBsY:8NWPN8WpEiA:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090117/the-innovation-is-in-social-messaging/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090117/the-innovation-is-in-social-messaging/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	<feedburner:origLink>http://qwang.net/20090117/the-innovation-is-in-social-messaging/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[Futurists]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/x13CX3ZUGiY/" />
		<id>http://qwang.net/?p=408</id>
		<updated>2009-04-29T05:32:02Z</updated>
		<published>2009-01-17T23:16:59Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[Technological prediction is a tough art:

Worse yet, you look like a fool when you get it wrong!  But every techie and VC is tasked with attempting exactly the kind of prediction above.
]]></summary>
		<content type="html" xml:base="http://qwang.net/20090117/futurists/">&lt;p&gt;Technological prediction is a tough art:&lt;/p&gt;
&lt;p&gt;&lt;img align="center" src="http://qwang.net/wordpress/wp-content/uploads/2009/01/telephonephono.jpg" alt="telephonephono" width="659" height="400" /&gt;&lt;/p&gt;
&lt;p&gt;Worse yet, you look like a fool when you get it wrong!  But every techie and VC is tasked with attempting exactly the kind of prediction above.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=x13CX3ZUGiY:rtgmGXmtwzY:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=x13CX3ZUGiY:rtgmGXmtwzY:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090117/futurists/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090117/futurists/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	<feedburner:origLink>http://qwang.net/20090117/futurists/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[Trading down performance]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/qF7TlMS_1Eo/" />
		<id>http://qwang.net/?p=394</id>
		<updated>2009-01-10T21:10:06Z</updated>
		<published>2009-01-10T21:02:40Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[When Blu-Ray beat HD-DVD, it seemed like an historic moment of validation for Sony.  They had won the next format war, and can look forward to the next half a decade owning the standard distribution format for video.  Not to mention, those damn Betamax jokes can finally go away.
Too bad the next standard distribution format [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20090110/trading-down-performance/">&lt;p&gt;When Blu-Ray beat HD-DVD, it seemed like an historic moment of validation for Sony.  They had won the next format war, and can look forward to the next half a decade owning the standard distribution format for video.  Not to mention, those damn Betamax jokes can finally go away.&lt;/p&gt;
&lt;h4&gt;Too bad the next standard distribution format for is actually choppy, grainy, SD video streamed over YouTube, Hulu, Net-Flix, and others alike.&lt;/h4&gt;
&lt;p&gt;Perhaps its a matter of diminishing returns, but with video, the masses have cast their vote for convenience over quality.  It happened with processors too: around the end of the Pentium age in 2003, Intel recognized that pumping out more powerful CPUs isn&amp;#8217;t going to help you check your email or surf the web any further — what accounts for most of consumer usage anyway.  Instead, people needed to use laptops on-the-go, so power consumption and embedded connectivity were the real problems that needed to be addressed.  This trading down of performance for mobility is the winning philosphy behind the original Centrino and Intel&amp;#8217;s continued control of the laptop space today.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;em&gt;On another note: are HDTVs a dud then? &lt;/em&gt;&lt;/strong&gt; I don&amp;#8217;t think so.  However the primary benefit of HD is not going to be superior picture quality, but the ability to render a robust user interface to pave the way to more interactive living room experiences.  Some recent announcements at CES &lt;a href="http://venturebeat.com/2009/01/07/ces-samsung-dives-into-connected-tv-market/"&gt;corroboate that&lt;/a&gt;&amp;#8230;though I do think the real winner will be a set-top box that can be easily and cheaply attached to existing, not so high-end HDTVs.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=qF7TlMS_1Eo:rvBqF0WLzMQ:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=qF7TlMS_1Eo:rvBqF0WLzMQ:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20090110/trading-down-performance/#comments" thr:count="1" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20090110/trading-down-performance/feed/atom/" thr:count="1" />
		<thr:total>1</thr:total>
	<feedburner:origLink>http://qwang.net/20090110/trading-down-performance/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[The search market share game]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/4mVeXmcksnw/" />
		<id>http://qwang.net/?p=347</id>
		<updated>2009-01-07T21:48:09Z</updated>
		<published>2008-12-27T04:32:11Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[I&#8217;ve noticed that Microsoft have begun inking deals with PC OEMs to include Live Search as the default search engine.  Besides the obvious comparisons to the Netscape vs Explorer bundling conflict, there&#8217;s one other interesting facet here:
There isn&#8217;t an obvious way to &#8220;buy&#8221; market share when it comes to search.  Unlike direct monetization where lowering [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20081226/the-search-market-share-game/">&lt;p&gt;I&amp;#8217;ve noticed that Microsoft have begun inking deals with PC OEMs to include Live Search as the default search engine.  Besides the obvious comparisons to the Netscape vs Explorer bundling conflict, there&amp;#8217;s one other interesting facet here:&lt;/p&gt;
&lt;h4&gt;There isn&amp;#8217;t an obvious way to &amp;#8220;buy&amp;#8221; market share when it comes to search.  Unlike direct monetization where lowering prices will attract greater volume, ad-monetized businesses don&amp;#8217;t really have a pricing lever one could pull to influence market share.&lt;/h4&gt;
&lt;p&gt;Microsoft has tried a cash back campaign which should prove to be an embarrassing failure any day now.   You simply can&amp;#8217;t win everyday consumers over by paying them pennies at a time.  On the other hand the OEM path seems like the right way to go, for now.  After all default-bundling is MS&amp;#8217;s sweet spot, but it does raise the question: what are ultimately the true drivers of market share in search?&lt;/p&gt;
&lt;p&gt;Does anyone really know the answer to how Google became #1 in search?  I have strong doubts about the most common explanation: that superior search quality is the king-maker.   I highly doubt that unsophisticated internet users switched to Google purely for notably superior search results.  But what else could it be?  A function of branding and momentum? but didn&amp;#8217;t Yahoo and Lycos have plenty of that?  Was it the simplicity of the Google brand and front page?&lt;/p&gt;
&lt;h3&gt;Update&lt;/h3&gt;
&lt;p&gt;This &lt;a href="http://www.techcrunch.com/2009/01/05/2009-tech-prediction-faceoff-jp-morgan-vs-barclays-capital/"&gt;iBanker prediction&lt;/a&gt; caught my eye:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Prediction: Increased Competition For Search Distribution Via Toolbars, OEM Deals, and Partnerships&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Winning over toolbars, OEM deals, and partnerships are all examples of securing &lt;em&gt;default positioning&lt;/em&gt; and is a hot battleground between every search engine.  Again, I suspect most users carelessly follow the whims of their default search box and are rather apathetic to the quality of search results between the big three.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=4mVeXmcksnw:6WY0vHZ882A:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=4mVeXmcksnw:6WY0vHZ882A:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20081226/the-search-market-share-game/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20081226/the-search-market-share-game/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	<feedburner:origLink>http://qwang.net/20081226/the-search-market-share-game/</feedburner:origLink></entry>
		<entry>
		<author>
			<name>Q dub</name>
						<uri>http://qwang.net</uri>
					</author>
		<title type="html"><![CDATA[The role of the browser]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/makingtime/~3/KxgJG-w2jik/" />
		<id>http://qwang.net/?p=201</id>
		<updated>2008-12-28T07:00:50Z</updated>
		<published>2008-11-06T00:45:49Z</published>
		<category scheme="http://qwang.net" term="Uncategorized" />		<summary type="html"><![CDATA[With Google Chrome, it is ample clear that browsers will evolve into application environments.   Its first design give good hints as to where this is all going.  For example, the inversion of the tab bar and navigation controls is not merely a cosmetic preference, but a reversal of the containment hierarchy: where as before, [...]]]></summary>
		<content type="html" xml:base="http://qwang.net/20081105/the-role-of-the-browser/">&lt;p&gt;With Google Chrome, it is ample clear that browsers will evolve into application environments.   Its first design give good hints as to where this is all going.  For example, the inversion of the tab bar and navigation controls is not merely a cosmetic preference, but a reversal of the containment hierarchy: where as before, navigation was a universal control which manipulated tabs, now tabs are a universal control (task management) which manipulates work flows (some of which are browser like, others not so much).  The bigger picture here is that the browser is taking on some of the responsibilities of the OS GUI, &lt;em&gt;specifically, managing applications&lt;/em&gt;.  As more user activities such as music playing, document editing move inside the browser, the existing browser interface will quickly become unfit for the job.&lt;/p&gt;
&lt;h3&gt;From tabs to tasks, the evolution of web activities&lt;/h3&gt;
&lt;p&gt;Computers have made us all into multi-taskers.  The original innovation around tabs is conceptually similar to the collapsing of task buttons introduced in Windows XP: group a bundle of similar tasks under a single container.  And similar they were.  In the old web, the everything you did was more or less a browsing sequence of documents connected via hyperlinks.  However in the past few years, web activities have evolved significantly away from sequential document browsing. How would you classify the activity of having Pandora in the background?  Or editing a new blog post?  These activities would originally reside in WinAmp and MS Word and have little resemblance to document browsing, and thus should have little resemblance to a browser interface.&lt;/p&gt;
&lt;h4&gt;Classically offline activities are now shifting into the browser window.  They are diverse in 3 major dimensions: (1) their multiplicity, (2) degree of engagement, and (3) control schema compared to traditional document browsing.&lt;/h4&gt;
&lt;p&gt;Pandora, for example, is a single-instance (1) activity that usually occurs in the background (2) and almost never uses the standard back-forward-reload-locationbar browser widgets (3).  Blog editing, other otherhand, is likely a single-instance foreground activity with again, totally different controls.  This necessitates different task management interfaces beyond a horizontal tab list.  Does it make sense that Pandora occupies a whole tab, like its a document waiting to be read (2)?  No, I think many people would prefer to &amp;#8221;&lt;a href="https://addons.mozilla.org/en-US/firefox/addon/3780"&gt;faviconize&lt;/a&gt;&amp;#8221; it.  Single-instance apps, such as email or RSS readers make more sense as master tabs or container groups, not as yet-another-tab in a sea of open documents (1).  Finally, the standard browser controls don&amp;#8217;t always make sense for highly specialized, non-document and non-browsing applications (3).  Take the email example: I rarely ever use the back-foward button, and certainly never the location bar (unless I navigate away).  Back-foward interfaces make no sense in email: you&amp;#8217;re navigating through a &lt;em&gt;hierarchy&lt;/em&gt; (inbox-&amp;gt;label-&amp;gt;conversation-&amp;gt;message) as opposed to a &lt;em&gt;sequence&lt;/em&gt;.&lt;/p&gt;
&lt;h3&gt;Borrowing from prior work&lt;/h3&gt;
&lt;p&gt;So what is the correct GUI behavior for a Pandora or word processing task? Just look to desktop applications!  The Pandora air app sits inconspicuously in the system tray, and when active, doesn&amp;#8217;t feature the standard browser navigation controls.  Popular blog editing tools are single-instance and sit outside of the browser, and again, feature no navigation controls.&lt;/p&gt;
&lt;h4&gt;The app management problem has already been solved before, just look to the behavior of desktop applications and how they interact with the OS&amp;#8217;s provided task management interfaces (e.g. taskbar + system tray, dock + expose)&lt;/h4&gt;
&lt;p&gt;Browser developers should be keen to borrow these interfaces and extend such access to web apps.&lt;/p&gt;
&lt;h3&gt;The road forward&lt;/h3&gt;
&lt;p&gt;I think ultimately, this is about web apps catching up to desktop apps in richness of their GUIs.  You can have the sexiest possible GUI for your webapp, but it&amp;#8217;s still constrained within the window.  Can a web app pop up balloon notifications?  Run as a minimized background process?  Register contexual actions on desktop icons e.g., &amp;#8220;Upload to Box.net&amp;#8221;?  The true role of the browser will not simply to &amp;#8220;display and view webpages&amp;#8221;, but to bridge every available aspect of the GUI with a web application.&lt;/p&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/makingtime?a=KxgJG-w2jik:wqf1BOn3_I8:AuYIl38yNd0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/makingtime?i=KxgJG-w2jik:wqf1BOn3_I8:AuYIl38yNd0" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content>
		<link rel="replies" type="text/html" href="http://qwang.net/20081105/the-role-of-the-browser/#comments" thr:count="1" />
		<link rel="replies" type="application/atom+xml" href="http://qwang.net/20081105/the-role-of-the-browser/feed/atom/" thr:count="1" />
		<thr:total>1</thr:total>
	<feedburner:origLink>http://qwang.net/20081105/the-role-of-the-browser/</feedburner:origLink></entry>
	</feed>
