I can just see two articles from May 2022 in the original feed, so they are older than these from April 2023.
And remember, the free version of Full-Text RSS just returns three items.
On the webpage there are more recent postings, but they are not in the feed. If I am wrong, please post the links to the missing articles.
Last 3 articles in the original feed:
- Mon, 15 May 2023 09:45:40 +0000
- Tue, 09 May 2023 20:03:37 +0000
- Mon, 24 Apr 2023 07:19:42 +0000
Those posts are missing after running through FullTextRSS. We use the full paid self-hosted version, we just used the demo to show the bug reproduced.
Sorry, I have loaded that feed by windows and by curl on linux, I even tried it via VPN Service in Italy. The feed header said, the feed is crated at
<lastBuildDate>Sun, 07 May 2023 20:20:46 +0000
The newest article/item ist from
<pubDate>Mon, 24 Apr 2023 07:19:42 +0000
I don’t see the other two articles. Maybe there is some kind of geofencing at this site? And it is recognising my VPN as a try to break the fence.
I have uploaded the original feed (version Windows via VPN) at pastebin and there is nothing newer in, than April 2023. Maybe you could send us your original feed. And once again: please post the links to the single articles!
Maybe you can use FeedCreator (another service from FiveFilters) to generate a feed from the main page:
On THIS PAGE I prefilled some arguments for you. Just copy the RSS-link in the upper right corner and paste this one to Full-Text RSS service
Oh, you are right, I just tested with CURL from one of our servers and now I got an outdated feed just like you reported
I think the Wordpress site has some issues with the page cache… Could be either a cache plugin, or just Cloudflare Page Cache incorrectly configured to cache the RSS feed
Currently, this URL returns May 7 as lastBuildDate
iniziativanarchica.noblogs . org/feed/
But adding a random URL parameter bypass the page cache and now it shows May 15 as lastBuildDate
iniziativanarchica.noblogs . org/feed/?jkfghfkdjgf=gfddgfdg
So I will fix this with a dirty workaround, just add some random parameter to the URL query string