<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Bloglines Is Broken (for me, at least)</title>
	<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/</link>
	<description>Nothing to do with standards, even less to do with wombats, only vaguely a blog</description>
	<pubDate>Thu, 21 Aug 2008 01:16:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Smotret</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-83695</link>
		<pubDate>Wed, 18 Jul 2007 17:39:08 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-83695</guid>
					<description>Actually I had the same problem with Firefox 2.0.0.4 but Opera was fine.
Login via http://www.bloglines.com/login didnt show up the feeds list in the left pane. So I use https://www.bloglines.com/login again and everything is ok again.</description>
		<content:encoded><![CDATA[<p>Actually I had the same problem with Firefox 2.0.0.4 but Opera was fine.<br />
Login via <a href='http://www.bloglines.com/login' rel='nofollow'>http://www.bloglines.com/login</a> didnt show up the feeds list in the left pane. So I use <a href='https://www.bloglines.com/login' rel='nofollow'>https://www.bloglines.com/login</a> again and everything is ok again.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Rang</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-52560</link>
		<pubDate>Thu, 26 Apr 2007 21:28:28 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-52560</guid>
					<description>I am using Firefox 2.0.2 now and sometimes get the same problem. I don't have that problem with IE. I always thought it was Firefox problem. But thanks Llyodi and others.- I know what is the problem now.
Regards</description>
		<content:encoded><![CDATA[<p>I am using Firefox 2.0.2 now and sometimes get the same problem. I don&#8217;t have that problem with IE. I always thought it was Firefox problem. But thanks Llyodi and others.- I know what is the problem now.<br />
Regards
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: No Relation&#187; Blog Archive &#187; Accessibility and Usability: Can I always use a 100% AJAX Solution?</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-20480</link>
		<pubDate>Fri, 12 Jan 2007 12:57:06 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-20480</guid>
					<description>[...] - Using a sledgehammer to crack a nut:  Ma.gnolia&amp;#8217;s  case. - Blogger: Can I get in please? - Bloglines is broken! (at least for me) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] - Using a sledgehammer to crack a nut:  Ma.gnolia&#8217;s  case. - Blogger: Can I get in please? - Bloglines is broken! (at least for me) [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Andrea Hill</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14130</link>
		<pubDate>Thu, 07 Dec 2006 12:10:16 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14130</guid>
					<description>Thanks for the heads-up... our organization is starting to adopt the dojo framework and this helps me go into it eyes-open.

Also found this blogpost http://brianmriley.com/blog/?p=8  related to dojo and firewalls not playing well together.</description>
		<content:encoded><![CDATA[<p>Thanks for the heads-up&#8230; our organization is starting to adopt the dojo framework and this helps me go into it eyes-open.</p>
<p>Also found this blogpost <a href='http://brianmriley.com/blog/?p=8' rel='nofollow'>http://brianmriley.com/blog/?p=8</a>  related to dojo and firewalls not playing well together.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Andrea Martines</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14101</link>
		<pubDate>Thu, 07 Dec 2006 09:03:46 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14101</guid>
					<description>It is a more general issue, not covering just Bloglines, but every Ajax-powered product. In particular, Ajax based feed aggregators (aka Start Pages) doesn't seem to be awared of degradable and unobtrusive techniques.

I suggest you take a look at the MIX (http://mix.excite.eu), the start page I'm developing for Excite Europe. It is conceived as a degradable product, so users will still be able to navigate it when js is disabled. We're still in beta, I hope to complete soon this concept. But in a rough way, it is already active.</description>
		<content:encoded><![CDATA[<p>It is a more general issue, not covering just Bloglines, but every Ajax-powered product. In particular, Ajax based feed aggregators (aka Start Pages) doesn&#8217;t seem to be awared of degradable and unobtrusive techniques.</p>
<p>I suggest you take a look at the MIX (http://mix.excite.eu), the start page I&#8217;m developing for Excite Europe. It is conceived as a degradable product, so users will still be able to navigate it when js is disabled. We&#8217;re still in beta, I hope to complete soon this concept. But in a rough way, it is already active.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lloydi</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14049</link>
		<pubDate>Thu, 07 Dec 2006 00:56:38 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14049</guid>
					<description>Different firewalls do different things, Tom. Some block based on regExp conditions (sometimes falsely) and they usually parse the .js file to see if it's trying to make certain JavaScript calls. The firewall is configured as per factory settings, so my point is that if it's happening to me at my place of work, it almost certainly is at others. But, the point that you've overlooked really, is that Bloglines does something that is essentially quite simple. A news reader could work without complicated JavaScript. It always used to for Bloglines.</description>
		<content:encoded><![CDATA[<p>Different firewalls do different things, Tom. Some block based on regExp conditions (sometimes falsely) and they usually parse the .js file to see if it&#8217;s trying to make certain JavaScript calls. The firewall is configured as per factory settings, so my point is that if it&#8217;s happening to me at my place of work, it almost certainly is at others. But, the point that you&#8217;ve overlooked really, is that Bloglines does something that is essentially quite simple. A news reader could work without complicated JavaScript. It always used to for Bloglines.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tom</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14008</link>
		<pubDate>Wed, 06 Dec 2006 20:00:13 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-14008</guid>
					<description>Why would a firewall block certain Javascripts? How does the firewall determine whether to block a script or not? Does it look at the filename of the script or does it parse its contents?

IMHO the firewall is broken and not bloglines...</description>
		<content:encoded><![CDATA[<p>Why would a firewall block certain Javascripts? How does the firewall determine whether to block a script or not? Does it look at the filename of the script or does it parse its contents?</p>
<p>IMHO the firewall is broken and not bloglines&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Henrik</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-13717</link>
		<pubDate>Mon, 04 Dec 2006 23:00:32 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-13717</guid>
					<description>I was thinking along the lines of configuring Firefox so it would have the dojo fw already present when loading the page. I should think that Greasemonkey could do that for you somehow. https://addons.mozilla.org/firefox/748/</description>
		<content:encoded><![CDATA[<p>I was thinking along the lines of configuring Firefox so it would have the dojo fw already present when loading the page. I should think that Greasemonkey could do that for you somehow. <a href='https://addons.mozilla.org/firefox/748/' rel='nofollow'>https://addons.mozilla.org/firefox/748/</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lloydi</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-13714</link>
		<pubDate>Mon, 04 Dec 2006 22:55:14 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-13714</guid>
					<description>Nope - the issue is that the dojo.js file won't make it through the firewall, so I can't work around that at all, I'm afraid :-(</description>
		<content:encoded><![CDATA[<p>Nope - the issue is that the dojo.js file won&#8217;t make it through the firewall, so I can&#8217;t work around that at all, I&#8217;m afraid :-(
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Henrik</title>
		<link>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-13702</link>
		<pubDate>Mon, 04 Dec 2006 20:53:01 +0000</pubDate>
		<guid>http://lloydi.com/blog/2006/09/29/bloglines-freedbacking-it-is-broken-now/#comment-13702</guid>
					<description>Ian,

Isn't there a way to save a user script for the site that will give you dojo support?</description>
		<content:encoded><![CDATA[<p>Ian,</p>
<p>Isn&#8217;t there a way to save a user script for the site that will give you dojo support?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
