Channel
@devWithEyob
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,097subscribers
-1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002058435516 |
|---|---|
| Type | Channel |
| Username | @devWithEyob |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/devWithEyob |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 22:26 | 1,097 | -1 |
| 11 Aug 2026, 02:17 | 1,098 | first reading |
15 posts held, back to 6 August 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 13 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 15 (6 August 2026 – 10 August 2026) |
| Views total | 3,614 |
| Reactions total | 50 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 02:17 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
50 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 44.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 22 | 44.0% | |
| 🤯 | 8 | 16.0% | |
| 👀 | 5 | 10.0% | |
| 😁 | 5 | 10.0% | |
| 👍 | 4 | 8.00% | |
| 🔥 | 4 | 8.00% | |
| 👏 | 1 | 2.00% | |
| 🤔 | 1 | 2.00% |
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 13 of the 15 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 50reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 6 August 2026 to 10 August 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.
Article of the day Software engineers should avoid endless prompt refinement when working with AI and instead actively write code themselves. Rather than trying to perfect prompts to get AI to generate complete solutions, developers should engage with the code directly by refactoring AI-generated code, writing initial versions for AI review... read the full article 👉 here @devwitheyob #TechVibe #ArticleOfTheDay @a…
🔥3
One of the things I’m always fascinated by when I meet people older than me, and they don’t necessarily have to be 60+, even someone 5 or 10 years older, is wondering what they were thinking about 10 years ago. Like, how did they survive the things happened back then like corona? What did they learn along the way? What did life look like back then? I find myself comparing their time, experiences, and way of thinki…
❤6🤔1
ወንድም ኤሊያስ አዲስ ቻናል ጀምሮ ወዳጅ ዘመድ እየሰበሰበ ነው እና እስኪ ጎራ ጎራ ብለን ቤቱን እናሙቅለት 🔥 በዛ ላይ ፍሪክ ነገር ነች LOL @devwitheyob #TechVibe @freakycoder
😁4❤1👍1
Photo, posted without a caption
❤1😁1
Article of the day The OrderController-from-hell production pattern. One controller validates requests, checks permissions, applies business rules, calls the payment gateway, writes to multiple database tables, publishes Kafka events, sends email notifications, and logs audit records. Every developer on the team has touched it. A "small" tax-calculation fix takes days to review and weeks to QA — not because the chan…
❤3
Just found out that Abuki is .NET developer as well😊 @devwitheyob #TechVibe #random
🤯8👏1
Start watching smallville😊 @devwitheyob #TechVibe #movies
❤1🔥1
Microsoft Teams video call quality is far better than Zoom and Google Meet. @devwitheyob #TechVibe #MicrosoftTeams
👀5
Article of the day HTTP/3 isn't just a faster version of HTTP. It changes what's underneath it. HTTP/2 brought multiplexing, allowing multiple requests to share one connection. But because it still runs over TCP, one lost packet can hold up all those streams. HTTP/3 moves to QUIC over UDP, so packet loss in one stream doesn't have to stop everything else. It also brings faster connection setup and lets connections …
❤4
If you're selling to rich people, sell them time. If you're selling to students, sell them their dream. If you're selling to men, sell them what success looks like. If you're selling to women, sell them what success feels like. If you're selling to kids, sell to their parents. If you're selling to parents, sell them a break from their kids. @cyber_Guardian5
❤4
Introducing EthioDeploy Deploying applications shouldn't require hours of server setup, DevOps knowledge, or an international credit card. We built this to make hosting simple for developers, startups, and businesses. Connect your GitHub repository, push your code, and your application is online in seconds. Here's what you get with EthioDeploy: 1. Automatic stack detection Works out of the box with Next.js, Re…
Let me share this with you guys. Maybe some people won't like me sharing it, but it's already public on the internet anyway. It has data from the top 10k freelancers on Upwork, their estimated MRR, top skills, countries, lifetime earnings, earning trends, skills and a lot more. Spreadsheet Link @devwitheyob #Upwork #Freelancing
Showing the 12 most recent of 15 posts we hold for @devWithEyob. 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 — 732,428 of 1,160,990entries 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“TechVibe” (@devWithEyob), 1,097 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/devWithEyob.
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.