<?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: Site Specific Browser - WebRunner</title>
	<atom:link href="http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/feed/" rel="self" type="application/rss+xml" />
	<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/</link>
	<description></description>
	<pubDate>Fri, 25 Jul 2008 03:54:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: leslie</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-1056</link>
		<dc:creator>leslie</dc:creator>
		<pubDate>Thu, 22 Mar 2007 18:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-1056</guid>
		<description>Neat.

I've since written an Apollo-based Gmail.app, and I have to say that that was roughly 5x easier to get running than the equivalent XULRunner-based Gmail.app.

Have you guys ever thought about whether or not SSBs (I started to call them minibrowsers, but site-specific minibrowser might be more apropos) have any place in reducing security risks for knowledgable users?

I don't think it solves the end-user phishing / trusted path problem, but for power users, I can imagine it's a lot easier to trust a downloaded SSB which has almost no chrome and no extensions, and is launched separately like a desktop application.

If each SSB has its own cookiespace, then CSRF-style attacks become more difficult.

Ka-Ping Yee has done some work in making voting more secure (http://zesty.ca/voting/), and I wonder if SSBs would at least be a step in a more secure direction for power users.

At the very least, SSBs ought to make it easier to prototype trusted path browsers...

I'll probably be at the Mtn View dev day if you'd like to chat more about this.

~L</description>
		<content:encoded><![CDATA[<p>Neat.</p>
<p>I&#8217;ve since written an Apollo-based Gmail.app, and I have to say that that was roughly 5x easier to get running than the equivalent XULRunner-based Gmail.app.</p>
<p>Have you guys ever thought about whether or not SSBs (I started to call them minibrowsers, but site-specific minibrowser might be more apropos) have any place in reducing security risks for knowledgable users?</p>
<p>I don&#8217;t think it solves the end-user phishing / trusted path problem, but for power users, I can imagine it&#8217;s a lot easier to trust a downloaded SSB which has almost no chrome and no extensions, and is launched separately like a desktop application.</p>
<p>If each SSB has its own cookiespace, then CSRF-style attacks become more difficult.</p>
<p>Ka-Ping Yee has done some work in making voting more secure (http://zesty.ca/voting/), and I wonder if SSBs would at least be a step in a more secure direction for power users.</p>
<p>At the very least, SSBs ought to make it easier to prototype trusted path browsers&#8230;</p>
<p>I&#8217;ll probably be at the Mtn View dev day if you&#8217;d like to chat more about this.</p>
<p>~L</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Smedberg</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-932</link>
		<dc:creator>Benjamin Smedberg</dc:creator>
		<pubDate>Thu, 08 Mar 2007 15:21:29 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-932</guid>
		<description>Right now, if you use a separate process, you also get a separate cache/history store, which is probably not desirable. For Moz2 we will hopefully have cross-process shared cache and history, but in the meantime I think we should focus on making this work within the Firefox process. We could do this with an extension now, I'd bet. Link targeting is still the hard part... how do you decide which links are "external"? I've written up a proposal for a link rel="external" that would allow webapps to specify that explicitly, but nobody has implemented that yet.</description>
		<content:encoded><![CDATA[<p>Right now, if you use a separate process, you also get a separate cache/history store, which is probably not desirable. For Moz2 we will hopefully have cross-process shared cache and history, but in the meantime I think we should focus on making this work within the Firefox process. We could do this with an extension now, I&#8217;d bet. Link targeting is still the hard part&#8230; how do you decide which links are &#8220;external&#8221;? I&#8217;ve written up a proposal for a link rel=&#8221;external&#8221; that would allow webapps to specify that explicitly, but nobody has implemented that yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-927</link>
		<dc:creator>Allan</dc:creator>
		<pubDate>Thu, 08 Mar 2007 05:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-927</guid>
		<description>I am reasonably new to programing web application and am still feeling my way, so please for give me if I have the concept wrong. I think that in my case SSBâ€™s would be a god send! I write applications that I deploy on customers systems and then they use them with what ever browser they have installed. Then they upgrade the browser or it upgrades automatically, hay presto my applications no longer runs. 

The ability to install a scaled down version of say Firefox, ( no need fo toolbars etc... ) when installing my web app and point the web app to that browser to run in would mean my web app would run first time ever time. My customer would be much happier to. Bring it on, the sooner the better.</description>
		<content:encoded><![CDATA[<p>I am reasonably new to programing web application and am still feeling my way, so please for give me if I have the concept wrong. I think that in my case SSBâ€™s would be a god send! I write applications that I deploy on customers systems and then they use them with what ever browser they have installed. Then they upgrade the browser or it upgrades automatically, hay presto my applications no longer runs. </p>
<p>The ability to install a scaled down version of say Firefox, ( no need fo toolbars etc&#8230; ) when installing my web app and point the web app to that browser to run in would mean my web app would run first time ever time. My customer would be much happier to. Bring it on, the sooner the better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rebron.org &#187; site specific browsers</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-921</link>
		<dc:creator>rebron.org &#187; site specific browsers</dc:creator>
		<pubDate>Thu, 08 Mar 2007 00:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-921</guid>
		<description>[...] of site specific browsers since 2001 when iTunes was first released.Â  There&#8217;s some talk of site specific browsers now and we&#8217;ll likely see more discussion around [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] of site specific browsers since 2001 when iTunes was first released.Â  There&#8217;s some talk of site specific browsers now and we&#8217;ll likely see more discussion around [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: biodecay</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-919</link>
		<dc:creator>biodecay</dc:creator>
		<pubDate>Wed, 07 Mar 2007 21:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-919</guid>
		<description>I dare say that this is a champion concept. The ideal incarnation, for me, would be the means to custom-configure an existing platform such as Firefox on a per-site basis. Specifically, a bit of code can be placed on the site indicating that it supports a custom interface. Firefox then prompts the user whether they would like to use the custom interface and if so, it is downloaded, installed and used. This preference is then remembered.

This is a neat solution to a number of problems.
One, it's convenient for users.
Two, users retain control over their experience.
Three, an enhanced experience can be delivered through the SSB; however, users with other browsers or environments may still access the app.
Four, the web app code can still be standards-compliant, globally-renderable code... but specific, cleanly degrading hooks can be added for the SSB to do things in a more efficient manner.
Five, because the custom interface can be tied to a domain, a shortcut can simply be created by way of a link to that URI. Simple!

I agree that XULRunner seems a promising basis.

-Rob.</description>
		<content:encoded><![CDATA[<p>I dare say that this is a champion concept. The ideal incarnation, for me, would be the means to custom-configure an existing platform such as Firefox on a per-site basis. Specifically, a bit of code can be placed on the site indicating that it supports a custom interface. Firefox then prompts the user whether they would like to use the custom interface and if so, it is downloaded, installed and used. This preference is then remembered.</p>
<p>This is a neat solution to a number of problems.<br />
One, it&#8217;s convenient for users.<br />
Two, users retain control over their experience.<br />
Three, an enhanced experience can be delivered through the SSB; however, users with other browsers or environments may still access the app.<br />
Four, the web app code can still be standards-compliant, globally-renderable code&#8230; but specific, cleanly degrading hooks can be added for the SSB to do things in a more efficient manner.<br />
Five, because the custom interface can be tied to a domain, a shortcut can simply be created by way of a link to that URI. Simple!</p>
<p>I agree that XULRunner seems a promising basis.</p>
<p>-Rob.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: enefekt</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-917</link>
		<dc:creator>enefekt</dc:creator>
		<pubDate>Wed, 07 Mar 2007 16:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-917</guid>
		<description>"I am not suggesting that an SSB be tied to any XULRunner runtime shipped with Firefox"

Assuming multiple SSBs share a single runtime, then part of this WebRunner endeavor would be creating a decent install/update experience of the WebRunner runtime. This would be a cool (though difficult) effort, if Mozilla doesn't do this with Firefox 3.

But, IF Firefox 3 did end up coming with XULRunner, then why not use it? If a perfectly good, recent, "official" XULRunner runtime exists already, why install another one?</description>
		<content:encoded><![CDATA[<p>&#8220;I am not suggesting that an SSB be tied to any XULRunner runtime shipped with Firefox&#8221;</p>
<p>Assuming multiple SSBs share a single runtime, then part of this WebRunner endeavor would be creating a decent install/update experience of the WebRunner runtime. This would be a cool (though difficult) effort, if Mozilla doesn&#8217;t do this with Firefox 3.</p>
<p>But, IF Firefox 3 did end up coming with XULRunner, then why not use it? If a perfectly good, recent, &#8220;official&#8221; XULRunner runtime exists already, why install another one?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Faaborg</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-915</link>
		<dc:creator>Faaborg</dc:creator>
		<pubDate>Wed, 07 Mar 2007 15:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-915</guid>
		<description>I would really like users to be able to right click on a bookmark and turn it into an application (or maybe an option in the File menu for the current site).  Firefox then dumps it on their desktop, and when the user opens it they get a SSB that has its own icon, place in alt/command-tab, in the taskbar/dock, etc.</description>
		<content:encoded><![CDATA[<p>I would really like users to be able to right click on a bookmark and turn it into an application (or maybe an option in the File menu for the current site).  Firefox then dumps it on their desktop, and when the user opens it they get a SSB that has its own icon, place in alt/command-tab, in the taskbar/dock, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Finkle</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-914</link>
		<dc:creator>Mark Finkle</dc:creator>
		<pubDate>Wed, 07 Mar 2007 14:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-914</guid>
		<description>Luis &#038; Abdulkadir - The browser will likely stay the predominant way people use webapps, I agree. There are advantages / disadvantages in both approaches. A SSB is just an alternative.

enefekt - I am not suggesting that an SSB be tied to any XULRunner runtime shipped with Firefox.

Wladimir - WebRunner is a XULRunner application with a few extra parameters that allow it to wrap different webapps.  This is not a new platform.</description>
		<content:encoded><![CDATA[<p>Luis &#038; Abdulkadir - The browser will likely stay the predominant way people use webapps, I agree. There are advantages / disadvantages in both approaches. A SSB is just an alternative.</p>
<p>enefekt - I am not suggesting that an SSB be tied to any XULRunner runtime shipped with Firefox.</p>
<p>Wladimir - WebRunner is a XULRunner application with a few extra parameters that allow it to wrap different webapps.  This is not a new platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wladimir Palant</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-913</link>
		<dc:creator>Wladimir Palant</dc:creator>
		<pubDate>Wed, 07 Mar 2007 13:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-913</guid>
		<description>I fail to see the point in having another platform for this. XULRunner is the platform of choice for standalone applications once the deployment/installation issues are sorted out. So IMO this makes sense as a XULRunner application generator that would generate such an application from a few parameters like starting page, sites the application should be limited to and maybe some custom XUL/JavaScript code. Unless of course a WebRunner extension is supposed to have lower privileges than a XULRunner application but that might be difficult given your requirements.</description>
		<content:encoded><![CDATA[<p>I fail to see the point in having another platform for this. XULRunner is the platform of choice for standalone applications once the deployment/installation issues are sorted out. So IMO this makes sense as a XULRunner application generator that would generate such an application from a few parameters like starting page, sites the application should be limited to and maybe some custom XUL/JavaScript code. Unless of course a WebRunner extension is supposed to have lower privileges than a XULRunner application but that might be difficult given your requirements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: enefekt</title>
		<link>http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-912</link>
		<dc:creator>enefekt</dc:creator>
		<pubDate>Wed, 07 Mar 2007 12:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2007/03/site-specific-browser-webrunner/#comment-912</guid>
		<description>"Platform with extensions"

How do you see this one being delivered? As a separate-from-Firefox platform "WebRunner"? Or utilizing XULRunner with Firefox 3?

If it is the last one, the information on the Firefox3/Gecko Feature List seems to throw a little cold water on the prospect. "Firefox on XULRunner (and shipping XULRunner platform)" is only given a P3 priority, and the comments read:
"In Progress; we can ship without it"
- http://wiki.mozilla.org/Firefox3/Gecko_Feature_List

Doesn't seem like it's too high up on the radar.</description>
		<content:encoded><![CDATA[<p>&#8220;Platform with extensions&#8221;</p>
<p>How do you see this one being delivered? As a separate-from-Firefox platform &#8220;WebRunner&#8221;? Or utilizing XULRunner with Firefox 3?</p>
<p>If it is the last one, the information on the Firefox3/Gecko Feature List seems to throw a little cold water on the prospect. &#8220;Firefox on XULRunner (and shipping XULRunner platform)&#8221; is only given a P3 priority, and the comments read:<br />
&#8220;In Progress; we can ship without it&#8221;<br />
- <a href="http://wiki.mozilla.org/Firefox3/Gecko_Feature_List" rel="nofollow">http://wiki.mozilla.org/Firefox3/Gecko_Feature_List</a></p>
<p>Doesn&#8217;t seem like it&#8217;s too high up on the radar.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
