Channel
@SaitoIOann
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Referenced elsewhere · Cite this entry
1,841subscribers
-50 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001353346454 |
|---|---|
| Type | Channel |
| Username | @SaitoIOann |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/SaitoIOann |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 07:21 | 1,841 | -6 |
| 13 Sept 2026, 14:58 | 1,847 | -1 |
| 10 Sept 2026, 04:01 | 1,848 | -14 |
| 4 Sept 2026, 16:17 | 1,862 | -6 |
| 31 Aug 2026, 21:05 | 1,868 | -4 |
| 29 Aug 2026, 05:47 | 1,872 | -3 |
| 26 Aug 2026, 00:12 | 1,875 | -6 |
| 23 Aug 2026, 03:05 | 1,881 | -1 |
| 19 Aug 2026, 14:28 | 1,882 | -4 |
| 16 Aug 2026, 19:28 | 1,886 | -5 |
| 12 Aug 2026, 23:12 | 1,891 | +1 |
| 10 Aug 2026, 07:27 | 1,890 | -1 |
| 7 Aug 2026, 10:52 | 1,891 | no change |
| 6 Aug 2026, 23:46 | 1,891 | first reading |
20 posts held, back to 6 May 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 2 pages of 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
🚨 Attention folks! 🚨 With the refactor Release Candidate 1 now out for all to test It is time to gear up for a bug squashing contest. Report a bug, win 50 USD worth of Saito! 300 USD worth of Saito up for grabs Report as many bugs as possible and the team will award the top 3 desktop AND the top 3 mobile bugs contributors with 50 USD worth of Saito each. Here’s the link to RC1 rc1.testnet.saito.io/ Plea…
Signed Tucho🟥
🚨🚨🚨🚨🚨🚨 Release Candidate 1 is now available for all to try! Experience the new look, speed and functionality On Saito Network- desktop and mobile! Check it out now 👇 Here’s the link to RC1: rc1.testnet.saito.io Please report the bugs on the RC1 Red Square app rc1.testnet.saito.io/redsquare/ When reporting please include the Saito app's name, browser used, and OS used. Have fun and break things! 😎
Signed Tucho🟥
🎙🎙Open Internet Podcast🎙🎙 Audiobooks you bought disappear from your library Games you thought you owned are just licenses The fight for Digital Ownership is the same as The fight for the Open Internet. Find out why this Thursday from 12 PM UTC ❕❕Digital Ownership & the Open Internet ❕❕ ⏰: July 23rd, 12 PM UTC 🚨 set a reminder! 🔗 on X
Signed Tucho🟥
🚨Update: Saito Refactor 2026🚨 After thousands of hours of development and testing we are happy to announce: Release Candidate 1 (RC1) Target Release Date: August 3. Check out what it it's all about on the Saito Wiki: https://wiki.saito.io/refactor-2026
Signed Tucho🟥
🎙🎙Open Internet Podcast🎙🎙 The man in the arena gets all the criticism. Every builder knows this. Every creator feels it. Waiting for someone else to fight for our digital rights Is how we got here in the first place. Now is the time to fight back! ❕❕The Man in the Arena❕❕ ⏰: July 16th, 12 PM UTC 🚨 set a reminder! 🔗 on X
Signed Tucho🟥
All existing mainnet SAITO holders have received a 5% bonus to their current holdings. Thank you for supporting the SAITO Mainnet! More 🟥 to come. Keep your 👀 on our feed!
Signed Tucho🟥
Native Saito holders (BEP-20) should look forward To a surprise come Monday 👀 🟥SAITO tokens are intensifying...
Signed Tucho🟥
🎙🎙Open Internet Podcast🎙🎙 First it was Social Media Bans Then it became Digital IDs Now the state is coming after our YouTube Feeds As luck would have it, there’s more than one way Skin this cat 🙀 Join us Live this Thursday 👇 ❕❕State Compliant Algorithms❕❕ ⏰: July 9th, 12 PM UTC 🚨 set a reminder! 🔗 on X
Signed Tucho🟥
🎙🎙SaitoLive🎙🎙 Chat Control is back on the floor of the E.U. Parlament Kids Act passed the House of Representatives EUDI is being rolled out this summer The surveillance state is being built in public But so is the alternative! ❕❕Building in Public❕❕ ⏰: July 2nd, 12 PM UTC 🚨 set a reminder! 🔗 on X
Signed Tucho🟥
🎙🎙SaitoLive🎙🎙 As compliance becomes more and more difficult Centralized networks face an existential crisis. Saito Network was built in order to combat this issue, And to ensure the continuation of the Open Internet. ❕Computer says NO❕ ⏰: June 23rd, 12 PM UTC 🚨 set a reminder! 🔗 on X
Signed Tucho🟥
🎙🎙SaitoLive🎙🎙 After Australia now the UK is also banning Social Media This is a de facto Digital ID implementation But also a single point of failure in the relationship Between citizens and the government. ❕Digital ID. Single Point of Failure❕ ⏰: 18th June, 12 PM UTC 🚨 set a reminder! 🔗 on X
Signed Tucho🟥
Hey Saitozens! 🟥 A fresh dev update from our co-founders is out now. Join us as we discover: 🔴 The latest on Outreach and Community 🔴 Massive dev backlog under testing 🔴 David’s adventures in academia 🔴 New themes/UI …and much more - don’t miss it! Watch the full video in YouTube🎥
Signed Tucho🟥
Showing the 12 most recent of 20 posts we hold for @SaitoIOann. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Hacker News
This handle was named once in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Saito Announcements” (@SaitoIOann), 1,841 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/SaitoIOann.
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.