4 measurements spanning 15 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 222–224 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 22:53
222
-1
14 Aug 2026, 21:55
223
-1
8 Aug 2026, 10:31
224
no change
7 Aug 2026, 14:39
224
first reading
Engagement
20 posts held, back to 10 January 2025 — 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 1 May 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
3m 56s
Average length
3m 56s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
105 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 44.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
47
44.8%
👏
22
21.0%
❤
19
18.1%
👍
11
10.5%
⚡
4
3.81%
👎
2
1.90%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 14 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 105reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 10 January 2025 to 1 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Refining our craft, pushed a sizeable update to our mcp-core repo
https://github.com/stevohuncho/mcp-core/tree/main
- support for 2025.03.26 spec plus option to switch to older protocol for servers and clients
- mcp-core-macros tool_param! annotations testing and examples
- more in depth cargo doc updates
Note: mcp-core lives in our lead engineer's main repo for broader visibility
Check out our new repo
https://github.com/fabelis/mcp-core
and our updated docs
https://docs.fabelis.ai
Tune in to our twitter post coming up shortly for a better overview and some cool technical demos.
An in-depth README is also on its way.
This is the start of an exciting chapter for Fabelis, expect updates to be in the form of days not weeks!
Market down, project down? I don't think so! 🗣🚨
We've been hard at work revitalizing the vision for Fabelis with a new massive update.
tl;dr The team at Fabelis has honed in on exploring the frontiers of the model context protocol (MCP for short). A new technology spearheaded by anthropic with the goal of arming AI agents to accomplish real-life tasks.
You've probably seen Claude Desktop...
Imagine Claude Desktop p…
https://github.com/fabelis/agent/releases/tag/v0.6.0
Tackled two whales at once!
We added:
- Deepseek completion to Fabelis
- Docker support
These are both live at
https://fabelis.ai/playground
We got this quick update out, but there are some serious game changing updates coming soon!
It's here! Our latest release now includes an expanded section of our website with a brand new dashboard!
https://github.com/fabelis/agent/releases/tag/v0.5.0
We have deployed a massive new feature reminiscent of character.ai but built leveraging the flexibility of Fabelis and the power of rig.rs!
We will be adding a ton of features to this new section and looking to collaborate with other members of the complex a…
Showing the 12 most recent of 20 posts we hold for @fabelisAI. 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.
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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“Fabelis” (@fabelisAI), 222 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/fabelisAI.
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.