OK, here's the deal: from now on Parss server will only update a feed's URL if there's a HTTP 301 response code.

Thus, a feed owner needs to deliberately setup a permanent redirect, it's not enough to do temporary one (which happens most of the time).

Let's see how far we get with this solution (which is not very elegant, i admit).

This automatic URL update thing is still a pain in the neck; obviously, taking over the new address from an HTTP redirection leads to unexpected and unwanted results.

Right now, there is a bunch of URLs in the parss.info database that come from a (pretty rigid) redirection policy at some blog hosters when they signalled maintenance time by diversing the requests to a single static HTML file.

Unfortunately, parss recorded the URL of that file as the new feed URL of all the hoster's weblog feeds.

Of course, this needs some fixing. If I only got the time...