How can I read @noderssbotstatus without a Telegram account?

TGViewer shows the public web preview Telegram publishes for NodeRSSBot Status: recent posts, photos, videos and the subscriber count, with no app, login or account.

How many subscribers does NodeRSSBot Status have?

NodeRSSBot Status (@noderssbotstatus) has 82 subscribers on Telegram, refreshed roughly every 30 minutes.

Does NodeRSSBot Status know I viewed it here?

No. Public channel previews carry no viewer identity, and TGViewer has no accounts or tracking of what you look up.

Channel Public Channel

NodeRSSBot Status

@noderssbotstatus

Information about NodeRSSBot and status of public demo @noderss_bot. Please read the document before asking question https://git.io/JtAF4

Open in Telegram

Subscribers: 82
Photos: 2
Videos: 0
Links: 13

Recent Posts 20 shown

Post #34 170 Nov 25, 2025, 14:01 UTC

NodeRSSBot Status The bot demo will be temporarily suspended for operating system and VPS maintenance. It will be restored as soon as possible.

Recovered

Post #33 173 Nov 25, 2025, 06:56 UTC

The bot demo will be temporarily suspended for operating system and VPS maintenance. It will be restored as soon as possible.

Post #32 482 Nov 8, 2024, 18:03 UTC

NodeRSSBot Status The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the…

Supabase charge for Egress bandwith. Recently Demo comsure over 8G per month which exceeded their free plan. So I just increase the fetch gap for the demo. I may consider some alternatives for supbase when I have some free time from my job. The database is a PostgreSQL which a pg_cron extension to fixes some dead feed. It is around 50MB but read bandwidth is around 8G per month. Any suggestion?

Post #31 778 Jan 31, 2024, 06:11 UTC

NodeRSSBot Status The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the…

Recoved after switching the pooling config to session mode in supabase dashboard.

Post #30 752 Jan 29, 2024, 09:27 UTC

The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the bot restores to normal. The detailed reasons are still under investigation.

Post #29 828 Sep 14, 2023, 11:14 UTC

NodeRSSBot Status @noderss_bot will be down for maintenance now. Will recover soon

Service are being gradually restored

Post #28 778 Sep 13, 2023, 12:09 UTC

@noderss_bot will be down for maintenance now. Will recover soon

Post #27 1.39K Jul 21, 2022, 05:33 UTC

out.mp46.4 MB

300 stars~

Post #25 1.56K Feb 12, 2022, 11:45 UTC

Release notes from NodeRSSBot
Version 0.11.0

Post #24 1.73K Oct 26, 2021, 23:41 UTC

Demo is down for maintain.

Post #23 1.86K Jul 28, 2021, 18:18 UTC

A downtime occur from 2021-07-28T17:56 to 2021-07-28 18:16:08, everything should return to normal now.

Post #22 1.77K Jun 27, 2021, 08:55 UTC

NodeRSSBot Status 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…

All (1654) wechat-feeds subscribes are removed. https://github.com/hellodword/wechat-feeds/issues/3882
@noderss_bot itself is still working as usual.

GitHub 停止服务 · Issue #3882 · hellodword/wechat-feeds 抱歉让各位失望了，本项目经历 278 天，在此要和各位说再见了。也没有什么别的原因，就是单纯成本激增（原本在我一番操作后每月成本已经为 0），这一点我也曾多次预料到，只是没想到来得这么快。决定暂时 archive，后面如果能恢复还是会继续服务（对本项目来说很渺茫）。 #3824 #2471

Post #21 1.55K Jun 1, 2021, 13:31 UTC

NodeRSSBot Status @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.

Post #20 1.33K Jun 1, 2021, 12:21 UTC

@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.

Post #19 1.31K Apr 14, 2021, 08:31 UTC

Release notes from NodeRSSBot
v0.10.1

GitHub Release Version 0.10.1 · fengkx/NodeRSSBot Features feat: version command b1c3b61 chore: multi platform docker image 9d866e5 bc06b37 136cf7d Fixes perf: optimize sql performance 8801682 fix: add admin right error check 88e8219 fix: feed con...

Post #18 1.09K Mar 14, 2021, 15:45 UTC

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.

Post #17 991 Mar 10, 2021, 16:09 UTC

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.

Post #16 786 Mar 10, 2021, 15:21 UTC

Release notes from NodeRSSBot
Version 0.10.0

Post #15 769 Mar 7, 2021, 18:23 UTC

Release notes from NodeRSSBot
Version 0.9.0

Post #14 787 Mar 2, 2021, 10:53 UTC

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.

Older posts →

About this channel

How can I read @noderssbotstatus without a Telegram account?: TGViewer shows the public web preview Telegram publishes for NodeRSSBot Status: recent posts, photos, videos and the subscriber count, with no app, login or account.
How many subscribers does NodeRSSBot Status have?: NodeRSSBot Status (@noderssbotstatus) has 82 subscribers on Telegram, refreshed roughly every 30 minutes.
Does NodeRSSBot Status know I viewed it here?: No. Public channel previews carry no viewer identity, and TGViewer has no accounts or tracking of what you look up.