Channel
@FiasAIAnnouncements
On this record: Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry
600subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001509908960 |
|---|---|
| Type | Channel |
| Username | @FiasAIAnnouncements |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/FiasAIAnnouncements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 06:26 | 600 | +1 |
| 16 Aug 2026, 18:04 | 599 | -3 |
| 8 Aug 2026, 22:20 | 602 | no change |
| 8 Aug 2026, 08:03 | 602 | first reading |
20 posts held, back to 1 April 2026 — 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 18 July 2026. An engagement rate over an empty window would be a number about nothing.
799 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 67.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 541 | 67.7% | |
| ❤ | 91 | 11.4% | |
| 👍 | 71 | 8.89% | |
| ❤🔥 | 33 | 4.13% | |
| 👌 | 15 | 1.88% | |
| 👏 | 15 | 1.88% | |
| 😁 | 9 | 1.13% | |
| 🙏 | 5 | 0.626% | |
| 🤣 | 5 | 0.626% | |
| 💯 | 4 | 0.501% | |
| ⚡ | 3 | 0.375% | |
| 🏆 | 3 | 0.375% | |
| 😎 | 2 | 0.25% | |
| 🤯 | 2 | 0.25% |
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 20 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 799reactions 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 1 April 2026 to 18 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Hey everyone, I wanted to give an update that I'm feel very excited about. I have implemented a first mvp for Fias AI in the Fias platform. It is incredibly powerful, and I'm realizing the extent of that statement now that I'm using it. The idea that you can have all of your applications in one spot, all of your data in one spot, and then have a general purpose AI to interact with all of the functionality and data at…
🔥24❤2
This also points to what Fias really becomes as a platform for our contributors. Anyone building an application has to decide how and where to build their work. With Fias, you can integrate your own arches into this ever growing ecosystem. You can tie in with all of the existing arches - email, chat, data, SaaS products, images, voice, video, etc and have your own application utilize Fias AI, MCP servers, web search,…
🔥34🤯2❤1😁1
Hey Everyone, here is the video I made from the community session. Let me know any comments or questions. thx https://youtu.be/xoUWZNzuT_4
🔥22
Nice feature we just added in - people can now utilize semantic search in your arches (i.e. a RAG database). Semantic search is an information retrieval method that understands the contextual meaning and intent behind a user's query, rather than just matching exact keywords. This means that you can create search for the users of your arche, where they type in plain english sentences, and the search gives answers base…
🔥25❤7👍4😁2
Everyone... today is the day! We're launching the beta today!!! Remember the date June 3rd 2026. Perhaps it will be remembered as a day that changed AI.
🔥74❤10👏5👍2😁2😎2
Hey all, here is the second video showing how to build arches (apps) in Fias. In this video I demonstrate the Plugin System - a very powerful way to make web apps. Please have a look and let us know what you think! https://youtu.be/MOI7E9uttAE
🔥29❤1
Hey Everyone, here is a first video that gives instructions on creating Arches in the Fias Platform. Please have a look and let us know what you think... https://youtu.be/-BuPCjaXKMc
🔥28❤4👍2
Hey everyone, I took the roadmap down for a few days. This is a good example of why it’s good to get final infrastructure in place before we onboard beta users. We made some changes to the ways we’re storing data and it was easier to wipe the data rather than port it and provide backwards compatibility. I saved everything and I’ll add it back shortly. After we get external users on the platform, we’ll need to assure …
👍17👌8🔥6❤3
Hey everyone, here is an update on the Beta launch. If you go back to the beginning of the month, there were three big foundational concepts for the platform I wanted to get in place, though all three would create delays in getting the beta out. One was a security audit. Second was an upgrade to our data systems including the RBAC features. Third was a scalability audit. The security audit was critical, so I just did…
🔥41👍13👌7👏5🙏5
I had an amazing experience on Fias last week, building powerful applications for a customer who gave us a challenge. We took their challenge, that they thought was aggressive, and not only did what they thought might be impossible, but did 4x the work they were expecting! This is a one-two punch alongside the other video I just posted. Have a look: We Replaced Salesforce, Docusign, and Quickbooks in 5 Days with AI …
❤31🔥7⚡3🏆3
First look at Fias!!! Fias Beta Launch First Look
❤🔥33🔥7👍3
Hey Everyone, here is an update on progress. The Fias platform is basically ready for the private beta launch. There were a couple last things I needed to do before that, including submitting another patent and getting instruction videos made for creating Fias Arches (web apps). I was also going over our internal arches to finalize which ones we have available at launch. That was going well, and we were on track to l…
🔥53👍6❤3
Showing the 12 most recent of 20 posts we hold for @FiasAIAnnouncements. 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 — 554,875 of 1,622,561entries 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Fias AI Announcements” (@FiasAIAnnouncements), 600 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/FiasAIAnnouncements.
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.