20 Feb 2022, 11:29 UTC≈4,790 viewsread 7 August 2026
Server migration completed! ✅ @RSS_Bot is now using the completely rewritten system I worked on in the past 6 months! It's much faster and more reliable now! Enjoy 🥳
Channel
Bot Changelog - RSS Bot updates
@BotChangelog
On this record: Growth · Engagement · Posts · Citations · Cite this entry
244subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001085728933 |
|---|---|
| Type | Channel |
| Username | @BotChangelog |
| Created | Between 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 20 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 20 August 2026 |
| On Telegram | t.me/BotChangelog |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 06:04 | 244 | -3 |
| 12 Aug 2026, 22:13 | 247 | -1 |
| 7 Aug 2026, 02:30 | 248 | no change |
| 6 Aug 2026, 00:18 | 248 | first reading |
Engagement
20 posts held, back to 15 August 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 20 February 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
17 Feb 2022, 10:16 UTC≈4,780 viewsread 7 August 2026
@RSS_Bot will we offline for about 2 hours on Sunday starting at around 8AM UTC while I migrate to new servers!
11 Feb 2022, 22:52 UTC≈4,740 viewsread 7 August 2026
Hi! It's been a while :) I spent the past weeks (or even months tbh) rewriting the RSS polling Backend for @RSS_Bot! It's not 100% finished yet but my first tests showed an incredible increase in performance and reliability 🥳 I'm getting everything in place to migrate the Bot to the new Backend (and some fancy new servers!) in the coming weeks. I'll let you know once I have any details! Have an amazing weekend!
20 Sept 2021, 22:48 UTC≈3,780 viewsread 7 August 2026
Hi everyone! First of all, I'm sorry for being offline in the past weeks, I'm quite busy these days. You may have noticed that @RSS_Bot is running a bit unstable lately, some post arriving pretty delayed and that the Bot isn't responsive at all sometimes (like today). That's because of two things: 1) My server is hitting its limit again as hundreds of new users start to use the Bot every day 2) I haven't had much ti…
11 Dec 2020, 20:08 UTC≈5,430 viewsread 7 August 2026
Update for @RSS_Bot Version: 2.7.2 (no change) - Fixed various small bugs - Optimized the way the RSS Feeds are fetched and increased the checking interval
26 Nov 2020, 09:45 UTC≈4,490 viewsread 7 August 2026
There was an issue with some buttons being unresponsive. This has been fixed now.
25 Nov 2020, 20:40 UTC≈4,500 viewsread 7 August 2026
There was an error with sending some Emojis in RSS Messages and in the Bot's interface. This mostly happened when setting a new RSS Autoposting Message Format (Template) which contained Emojis. This bug is fixed now. If you still have issues with Emojis in your RSS Messages or if you see a ? instead of an Emoji, please try to save your Message Format again. Sorry for the inconvenience. If you have any questions or is…
18 Nov 2020, 11:46 UTC≈3,290 viewsread 7 August 2026
Update: The migration is completed! Everything should work fine again now! 🎉 If you tryied to change a setting in @rss_bot in the last ~1,5 hours, please check if they are still saved correctly and change them if needed again now! Sorry for the (short) downtime! If you have any issues, please reply to this message!
18 Nov 2020, 10:39 UTC≈2,670 viewsread 7 August 2026
IMPORTANT: 4 days ago I migrated all scripts to the new server, today I'm moving the Database to the new server as well! Because of that, all changes you made to your Channel/Group's settings in @rss_bot in the last ~45 Minutes will be lost. I will notify you when the migration is completed and you can start making changes to your settings again. Also, it may happen that some RSS Feed messages may be posted two times…
14 Nov 2020, 20:05 UTC≈1,930 viewsread 7 August 2026
Update: The Server Migration went well and is completed now! The Bot and the Autoposting should work again now and the new server will slowly process all missed posts from the last hours and send them now! If you have any questions, please reply to this message! Thank you! 🥳
14 Nov 2020, 17:30 UTC≈1,670 viewsread 7 August 2026
Important: Since @RSS_Bot is growing faster and faster lately (thank you for using it!) I decided to move the bot to a new, more powerful server! I am now moving everything to the new server which means that the bot cannot post any new RSS feed messages for the next 2 hours or so! I'll post a message here as soon as the migration is done! 😃
20 Oct 2020, 18:21 UTC≈1,840 viewsread 7 August 2026
Update for @RSS_Bot Version: 2.7.2 - Fixed a bug with some special characters in RSS-Feed messages - There is now a one-second pause when posting multiple new RSS-Feed messages at once in a channel or group - New RSS-Feed messages should now be delivered much more efficient and reliable (also see the rssapi.net changelog for this: changelog) - Fixed some small spelling mistakes in some translations
Showing the 12 most recent of 20 posts we hold for @BotChangelog. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank
Citation-graph rank — 392,983 of 1,602,868entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 20 August 2026 — this entry's latest reading, not the date you are reading this.
“Bot Changelog - RSS Bot updates” (@BotChangelog), 244 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/BotChangelog.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.