Version: (using KDE 4.3.4) OS: Linux Installed from: Debian testing/unstable Packages This is a propagation of Debian bug #577528 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577528). The RSS feed at http://habrahabr.ru/rss/ (that I was reading for years) for some reason became unloadable/unparseable in Akregator in the latest days. That is, when it is added to the feed list, Akregator/Kontact cannot load any messages from it, without any warnings; if I try to remove it from the RSS list and readd again, Akregator fails on "Downloading http://habrahabr.ru/rss/" phase with "Feed not found from http://habrahabr.ru/rss/." message. The other RSS readers can load the messages well, nevertheless (just tried Opera bultin RSS reader). After a quick glance at the content served by the http://habrahabr.ru/rss/ URL, it seems to be a properly formed RSS, though I am not enough proficient in feed to be fully sure. This might be the problem of the contents anyway, though it would be good to get the understanding what the problem is, to notify the site owners; but on the Akregator side, it would be better to at least inform the reason of the failure.
http://habrahabr.ru/blogs/habrahabr_bugs/39679/ akregator was blocked at habrahabr
(In reply to comment #1) > http://habrahabr.ru/blogs/habrahabr_bugs/39679/ > akregator was blocked at habrahabr Can you explain what's written in this article please ? afaics, this feed doesn't validate: http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fhabrahabr.ru%2Frss%2F
juks says, that akregator works out of habrahabr's rules and sometimes request 50 times per second sorry for bad english
Sek.to is generally right. The writer of the topic, Josser, asked the question why the akregator seemingly doesn't receive the feed at all and if it is an akregator' or site issue, and Juks (who is among the site developers) replied that in most of the cases the akregator behaviour is too destructive for the site as it occasionally my run up to 50 requests per second just from a single client, therefore they had to block akregator from using the site.
Thanks for the details. Closing as upstream as this is a site issue.
*** Bug 258114 has been marked as a duplicate of this bug. ***