Comments on: Bloglines no like http://www.geekrant.org/2006/01/10/bloglines-rss-errors/ Fri, 27 Jan 2012 05:44:11 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: daniel http://www.geekrant.org/2006/01/10/bloglines-rss-errors/comment-page-1/#comment-5602 daniel Tue, 31 Jan 2006 01:42:19 +0000 http://www.geekrant.org/?p=488#comment-5602 With many thanks to Paul from Bloglines, who spotted this blog post, this has been resolved. The error message above wasn't very clear; in fact the Bloglines crawlers were getting a 403 Forbidden error. This is my fault, because a while ago I set up .htaccess to block a number of IP ranges because comment spammers and the like were <a href="http://www.geekrant.org/2005/07/14/spammers-bandwidth-thieves/" rel="nofollow">stealing heaps of bandwidth</a>. Evidently when Bloglines recently moved their servers, they got IP addresses in this range. Mea culpa. My stuff-up. Paul says they are working on making errors clearer. Thanks again Paul. With many thanks to Paul from Bloglines, who spotted this blog post, this has been resolved.

The error message above wasn’t very clear; in fact the Bloglines crawlers were getting a 403 Forbidden error. This is my fault, because a while ago I set up .htaccess to block a number of IP ranges because comment spammers and the like were stealing heaps of bandwidth. Evidently when Bloglines recently moved their servers, they got IP addresses in this range.

Mea culpa. My stuff-up.

Paul says they are working on making errors clearer. Thanks again Paul.

]]> By: daniel http://www.geekrant.org/2006/01/10/bloglines-rss-errors/comment-page-1/#comment-5582 daniel Wed, 18 Jan 2006 11:41:47 +0000 http://www.geekrant.org/?p=488#comment-5582 Yeah, I do plan upgrading to Wordpress 2 at some stage. But I'm not doing it just because - one aggregator fails (when all the others work) and I haven't changed anything to cause it - their support people haven't got back to me to clarify the error, which is clearly incorrect (the feed exists. If the feed is invalid, by all means say so, don't claim it doesn't exist though) - there's no guarantee WP2 will solve it The other issue is I don't have a lot of spare time, and won't go to WP2.0 until I'm confident it's very stable and I don't have to muck about with it a lot to keep it running. (Which by my usual rules means waiting for a couple of bugfix releases to go by before jumping in!) Yeah, I do plan upgrading to WordPress 2 at some stage. But I’m not doing it just because

- one aggregator fails (when all the others work) and I haven’t changed anything to cause it

- their support people haven’t got back to me to clarify the error, which is clearly incorrect (the feed exists. If the feed is invalid, by all means say so, don’t claim it doesn’t exist though)

- there’s no guarantee WP2 will solve it

The other issue is I don’t have a lot of spare time, and won’t go to WP2.0 until I’m confident it’s very stable and I don’t have to muck about with it a lot to keep it running. (Which by my usual rules means waiting for a couple of bugfix releases to go by before jumping in!)

]]> By: Titel http://www.geekrant.org/2006/01/10/bloglines-rss-errors/comment-page-1/#comment-5576 Titel Tue, 17 Jan 2006 15:56:26 +0000 http://www.geekrant.org/?p=488#comment-5576 Before anything else, upgrade to WordPress 2 and check the permalinks. For some reason, FeedValidator.org says "Temporary failure in name resolution" after pausing for almost a minute. Perhaps there are problems with the webhost's DNS servers? Before anything else, upgrade to WordPress 2 and check the permalinks.

For some reason, FeedValidator.org says “Temporary failure in name resolution” after pausing for almost a minute. Perhaps there are problems with the webhost’s DNS servers?

]]>