Great piece. I have a couple of comments, here..<p><a href="http://scripting.com/stories/2011/01/11/krocCamenProvesRssIsVeryMu.html" rel="nofollow">http://scripting.com/stories/2011/01/11/krocCamenProvesRssIs...</a>
What's all this about forking the browser? That is WAY over complicating the matter.<p>Both Chrome and Firefox extensions are essentially Javascript. So while they aren't 1-to-1 compatible they could use 95% of the same code.<p>The real problem is there's seemingly no money to be made off the suggestions he gives and it will take a lot of effort so no one wants to do it. I don't know how to fix that problem but if there's someone out there who does want to put the effort into this they should know it wouldn't require forking a browser to do it.
Site’s currently down (8:24 PM GMT, 10th) due to massive bandwidth. It is just a shared host and it suffices for 99% of the site‘s uptime. Google cache here: <a href="https://webcache.googleusercontent.com/search?q=cache%3Ahttp%3A%2F%2Fcamendesign.com%2Fblog%2Frss_a_reply" rel="nofollow">https://webcache.googleusercontent.com/search?q=cache%3Ahttp...</a>