Channel
@Easy_DevTalk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
26subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002289739781 |
|---|---|
| Type | Channel |
| Username | @Easy_DevTalk |
| Created | Between 1 September 2024 and 9 February 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/Easy_DevTalk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 17:43 | 26 | +1 |
| 11 Aug 2026, 09:33 | 25 | no change |
| 7 Aug 2026, 12:16 | 25 | first reading |
18 posts held, back to 9 February 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 18 posts for this entry, the most recent from 11 September 2025. An engagement rate over an empty window would be a number about nothing.
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.
14 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 42.9% | |
| 👏 | 3 | 21.4% | |
| 🔥 | 2 | 14.3% | |
| 🤓 | 2 | 14.3% | |
| ❤ | 1 | 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 18 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 14reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 9 February 2025 to 11 September 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.
So, here are a few things: -Recently I have experienced some bots failing to start, that's probably due to the increasing load on the server (I actually have no idea) -After many requests I made it possible to bypass the NSFW filter for supporting users -Users reported that the NSFW filter returns some false positives (no one complains about the false negatives), I'm not going to change it and there isn't anything…
Recently I have been working on an inline bot to easily explore AI generated images from public archives. The first version allows searching for specific keywords. In these images you can see some examples of how it would look like.
An interesting statistic, the detector has now limited over 200 users.
👏2
I am working on a new bot. This time i will give you a little spoiler on what it does: the bot will let users stream videos into their channels livestreams 🙀
🔥1
This bot has just been released. It all started as a simple way to get rid of all the announcements crowding the searches on google. Then i figured i could actually add other "filters", so i added news (I use it so maybe someone else does too). I also added the videos "filter", but google would mostly get youtube results so the youtube button just searches there. Then i also added the search for non youtube results. …
All the tutorials that have been published have now been turned into shorts.
From now on the AI NSFW detector is running in every bot. I suppose i could make a bot that people can put in groups to avoid having users spamming nsfw medias, but i don't usually make group tools.
👍1
Working on another inline bot
🔥1
I recently started experimenting with a nsfw detector. I am probably going to limit all the nsfw content in each bot. The detector is already running in multiple bots. Eventually it will be a feature in every bot.
❤1👍1
I have been working on a new bot, again... Releasing any day next week. It's a tool for communities.
New bot dropping tomorrow 🥱😮💨🌙
Password for ⭐️SUPPORTERS⭐️: I am not going to renew the current password, the password will stay active. All the current Supporters will keep their privileges for the time being. If you want, you can still buy it and it will still grant you access to limited bots. Bonus features for ⭐️SUPPORTERS⭐️: In the future, all the AI tools and various converters will offer a better product for Supporters. The first bonus has…
Showing the 12 most recent of 18 posts we hold for @Easy_DevTalk. 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 — 640,705 of 1,624,904entries 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“Easy DevTalk” (@Easy_DevTalk), 26 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/Easy_DevTalk.
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.