📰 最近消息
A downtime from 2021-03-02T01:54:49 (or earlier) to 2021-03-02T10:32:07 cause the @noderss_bot not sending any update. It is fixed in commit 70e5fab. It is cause by a feed which title contain html tag that telegram doesn't parse. Everything should return to normal now.
Release notes from NodeRSSBotVersion 0.9.0
Release notes from NodeRSSBotVersion 0.10.0
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
Thanks to docker buildx and GitHub action. Now pre-build docker image of multi architecture (linux/amd64,linux/arm64,linux/arm/v7,linux/arm/v6) is provided at fengkx/node_rssbot. You can now easily deploy NodeRSSBot on arm device like raspberry pi with docker.
Release notes from NodeRSSBotv0.10.1
@noderss_bot is down for maintenance now. Some user may have see lots of "lookup timeout" message in recent days. It may be the issue of the infrastructure provider(the demo is running on Oracle Cloud) since I have not updated the running docker image for 4 weeks.
@noderss_bot is down for maintenance now. Some user may have see lots of "lookup timeout" message in recent days. It may be the issue of the infrastructure provider(the demo is running on Oracle Cloud) since I have not updated the running docker image for…
Demo is back to normal now. A cron job is there to reduce the pressure of the server. Any subscribes to a feed which error count greater than 1350 (around 14 days because the fetch interval of the demo is 15min) will be deleted.
Recently, many of the new subscriptions in the demo came from a git repository called wechat-feeds that is mirrored at gitee. However this repository has been out of sync with the original GitHub repository for many days. All gitee subscriptions from this…