@crossingthethreshold @maique Knowing a bit about how caching works for my experimental feeds might shed some light on the phenomena and inform your decision if Feedbin is for you or not. Caches are shared among us, but to make it easier to reason about, let's pretend that you (or rather your Feedbin account) is the only person in the whole world fetching my experimental feeds… It goes like this:
- You make a request to the URL
- If it's less than two minutes ago since the last request, you will get the cached version of the feed.
- If more than two minutes have elapsed since the last request, you will still get the cached version of the feed, but my service will also fetch the latest version in the background and update the cache. The next time you make a request, this newly fetched version will be returned.
So, the maximum age of the feed you get depends on how often you (or Feedbin rather) check the feed for updates. Say, for example, that Feedbin checks the feed every minute, then you will always get a version of the feed that is no older than two minutes. If the feed is checked every 5 minutes, you can get a version of the feed that is up to 10 minutes old. Check it every hour, and you can get a cached version from two hours ago in the worst case. And so on.
As I mentioned earlier, cached versions are shared among all of us. That means, the more people subscribed to a feed, the higher chance that you will get up-to-date content. (Someone else might have already triggered an update of the stale content for you.)
If the freshness of the feed is important to you, you should choose a feed reader service or app with the ability to set the fetch frequency or to manually trigger a refresh. That way, you can make sure to always have the latest possible version of the feed.