NodeRSSBot Status

The recent two releases both contains fetch-related improvements. In release v0.9.0 I have added handling of ttl values in RSS. We know that ttl values may not be understood in the same way, so there is a strict_ttl configuration for you to turn off this feature. If you turn it on, fetch_gap will be the fallback of ttl, and the fetch interval will be the ttl value. This may cause the delay in updates to be extended by up to one ttl. HTTP Caching support was added in release v0.10.0, a feature that honestly should have been implemented in the first place, but I never noticed it before. Every qualified RSS aggregators should implement this feature. This is a great help in reducing traffic to RSS feeds. This is especially true for Telegram RSSBot, which usually has a relatively short fetch interval. I hope that NodeRSSBot will be as eco-friendly as possible, rather than putting pressure on sites that still provide RSS feeds. This is why I recommend upgrading your own instance. Both of these releases include changes to the database table structure so their version numbers will look like this. But thanks to kenx migration such changes can usually be done automatically.

www.tgoop.com/NodeRSSBotStatus/17

963 viewsedited  Mar 10, 2021 at 16:09

The recent two releases both contains fetch-related improvements. In release v0.9.0 I have added handling of ttl values in RSS. We know that ttl values may not be understood in the same way, so there is a strict_ttl configuration for you to turn off this feature. If you turn it on, fetch_gap will be the fallback of ttl, and the fetch interval will be the ttl value. This may cause the delay in updates to be extended by up to one ttl. HTTP Caching support was added in release v0.10.0, a feature that honestly should have been implemented in the first place, but I never noticed it before. Every qualified RSS aggregators should implement this feature. This is a great help in reducing traffic to RSS feeds. This is especially true for Telegram RSSBot, which usually has a relatively short fetch interval. I hope that NodeRSSBot will be as eco-friendly as possible, rather than putting pressure on sites that still provide RSS feeds. This is why I recommend upgrading your own instance. Both of these releases include changes to the database table structure so their version numbers will look like this. But thanks to kenx migration such changes can usually be done automatically.

BY NodeRSSBot Status