Channel
@johndoe_blog
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
102subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002561838950 |
|---|---|
| Type | Channel |
| Username | @johndoe_blog |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/johndoe_blog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 08:21 | 102 | -2 |
| 30 Aug 2026, 13:19 | 104 | -1 |
| 22 Aug 2026, 20:57 | 105 | -1 |
| 9 Aug 2026, 08:46 | 106 | no change |
| 7 Aug 2026, 16:38 | 106 | first reading |
13 posts held, back to 6 December 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 page 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 13 posts for this entry, the most recent from 31 December 2025. An engagement rate over an empty window would be a number about nothing.
42 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 35.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 15 | 35.7% | |
| 🔥 | 10 | 23.8% | |
| 👍 | 6 | 14.3% | |
| 🤣 | 5 | 11.9% | |
| ❤ | 3 | 7.14% | |
| 👀 | 3 | 7.14% |
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 9 of the 13 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 6 December 2025 to 31 December 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.
I built auth starter template for Fastapi > Secure JWT implementation > Google OAuth2 for google social login. > Password hashing using Bcrypt. > Refresh token rotation and revocation (database-backed). https://github.com/yohaboy/Fastapi-auth-starter @johndoe_blog
❤3
Photo, posted without a caption
Found this python package that enables you to use dark theme swagger in FastAPI 👉 Pypi 👉 Github @johndoe_blog
👍2
Did some system architecture stuff today and also am back to FastAPI after a while 🤩 . i will be sharing interesting FastAPI resources I find stay tuned. @johndoe_blog
🔥5
Facts😂 @johndoe_blog
🤣5
Give him a break ; 😂 @johndoe_blog
😁6
What my friends think when I say I work remotely @johndoe_blog
😁5
I was today years old when i found out i can send scheduled SMS @johndoe_blog
😁3
Here are some of the syntaxes @johndoe_blog
Cron uses a simple 5-part time format: minute | hour | day | month | weekday u fill these with numbers or * to set exactly when your task should run. */5 * * * * → runs every 5 minutes 0 */6 * * * → runs every 6 hours @johndoe_blog
#CRON_JOBS A cron job is a Linux scheduler that automatically runs your scripts or commands at fixed times or intervals like every minute, daily, weekly, or on custom schedules and here is how it works... @johndoe_blog
I’ve been building this job tracking site for the past two days, and I’ll be deploying it soon. What do you think of the dashboard? @johndoe_blog
🔥5
Showing the 12 most recent of 13 posts we hold for @johndoe_blog. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“John Does” (@johndoe_blog), 102 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/johndoe_blog.
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.