Telegram RegisterThe public register of Telegram
Telegram profile photo for mkdev

Channel

mkdev

@mkdev_me

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

418subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001138300695
TypeChannel
Username@mkdev_me
CreatedBetween 1 March 2017 and 30 April 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live20 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 20 August 2026
On Telegramt.me/mkdev_me

Growth

418419418.56 August 2026 — 418 subscribers6 August 2026 — 418 subscribers13 August 2026 — 419 subscribers20 August 2026 — 418 subscribers6 August 202620 August 2026
4 measurements spanning 15 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 418–419 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 19:33418-1
13 Aug 2026, 05:33419+1
6 Aug 2026, 19:32418no change
6 Aug 2026, 04:12418first reading

Engagement

20 posts held, back to 10 July 2026the 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 · 30 days
9.70%
avg views ÷ 418 subscribers
Avg views / post
40.6
9 posts measured
Reaction rate
2.50%
reactions ÷ views · ER floor
Posts in window
9
of 20 held

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 1 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (10 July 20266 August 2026)
Views total365
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 19:32 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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍150.0%
🔥150.0%

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 2 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 2reactions 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 10 July 2026 to 6 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.

Recent posts

6 Aug 2026, 14:04 UTC18 viewsread 6 August 2026

AWS Lambda and Google Cloud Functions have both evolved, but the main lesson from our pricing comparison remains relevant in 2026: serverless costs depend heavily on the shape of your workload. Google’s second-generation Cloud Functions are now called Cloud Run functions and follow the Cloud Run pricing model. AWS Lambda continues to bill according to requests, execution duration and allocated resources. Billing gr

5 Aug 2026, 14:03 UTC31 viewsread 6 August 2026

The free Argo CD Lightning Course will teach you how Argo CD works, what problems it solves, and why it has become an important tool for managing Kubernetes deployments. Available as both articles and videos, the course also covers Argo CD’s essential features and how it structures projects and applications. Article series: https://mkdev.me/posts/what-is-argo-cd-and-why-would-you-need-gitops Video form: https://www.

4 Aug 2026, 14:05 UTC40 views1 reactionsread 6 August 2026

Serving a SaaS app on customer-owned domains gets complicated when every hostname needs TLS. AWS ALBs start with a quota of 25 additional certificates, while Cloudflare for SaaS offers a more scalable custom-domain workflow. Watch the video: https://www.youtube.com/watch?v=hy1feUVVejQ

👍1

3 Aug 2026, 14:03 UTC39 viewsread 6 August 2026

The more capable AI becomes, the easier it is to trust it too much. The current GPT-5 generation is better at understanding intent, reasoning across large amounts of context and using external tools. Its answers can be detailed, polished and highly convincing. But a convincing answer is not automatically a correct one, and an autonomous workflow is not automatically an appropriate one. AI literacy in 2026 therefore

31 Jul 2026, 14:03 UTC46 viewsread 6 August 2026

Your delivery pipeline should help you move faster without sacrificing stability. mkdev designs CI/CD systems around your team, product and business, from organizational challenges to technical implementation. Check out the page and schedule a call: https://mkdev.me/b/consulting/majestic-pipeline

30 Jul 2026, 14:03 UTC54 viewsread 6 August 2026

Should you define every GKE resource yourself or use a Terraform module? Building a basic cluster from individual resources is a good way to understand what Terraform is actually creating. A maintained module becomes useful once you need repeatable configurations, multiple environments and more advanced GKE features without duplicating large amounts of code. This article demonstrates both approaches, including VPC-

29 Jul 2026, 14:04 UTC44 viewsread 6 August 2026

In the 95th mkdev dispatch Kirill talks about cloud providers inventing new execution layers for AI Agents to operate in. Also inside: trusting Claude Code a bit too much, tracking Amazon Bedrock Costs, spinel and more! https://mkdev.me/posts/do-ai-agents-need-new-containers-95

28 Jul 2026, 14:03 UTC43 viewsread 6 August 2026

Struggling to decide what matters when learning a new technology? Start with the concepts, explore the details when a real project demands them, and don’t confuse theoretical knowledge with experience. Learn more through the Prometheus example in this article. https://mkdev.me/posts/how-to-learn-new-technologies-prometheus-example

27 Jul 2026, 14:03 UTC50 viewsread 6 August 2026

“We only use ChatGPT as a copilot, so the EU AI Act does not really apply to us.” That is an understandable assumption, but it is incorrect. Article 4’s AI literacy requirement applies to organisations whose employees use tools such as ChatGPT for professional purposes, including relatively ordinary tasks such as drafting marketing copy or translating text. A human reviewing the answer does not remove the requireme

24 Jul 2026, 14:01 UTC49 viewsread 6 August 2026

Kubernetes complexity can hide security gaps, wasted capacity and operational friction. mkdev audits your clusters and applications, then delivers practical recommendations and concrete backlog items. Check out the page and schedule a call: https://mkdev.me/b/audits/kubernetes-audit-assessment

23 Jul 2026, 14:04 UTC59 views1 reactionsread 6 August 2026

A request passing through a CDN can arrive at your backend with much more context than it had when it left the user’s browser. Depending on the provider and configuration, that context can include an approximate country, region, city, timezone, postal code and coordinates. Cloudflare and Amazon CloudFront can generate this information from the visitor’s IP address and forward it as HTTP headers. This is fast, inexp

🔥1

22 Jul 2026, 14:04 UTC53 viewsread 6 August 2026

Discover the foundations of OpenShift 4 cluster management, starting with its reimagined installation experience and continuing through its most important features. Free mkdev course — Articles: https://mkdev.me/posts/production-openshift-cluster-in-35-minutes-first-look-at-okd-4-and-the-new-openshift-installer Videos: https://www.youtube.com/playlist?list=PLozcbFx8FoPGM-Dk1jVBu58pwUGP9WGIX

Showing the 12 most recent of 20 posts we hold for @mkdev_me. 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.

Cite this entry

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 20 August 2026 — this entry's latest reading, not the date you are reading this.

“mkdev” (@mkdev_me), 418 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/mkdev_me.

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.