Telegram RegisterThe public register of Telegram

Channel

The weekly

@webWekkly

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

1,122subscribers

-3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001167945641
TypeChannel
Username@webWekkly
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 14 August 2026
On Telegramt.me/webWekkly

Growth

1,1221,1251,123.57 August 2026 — 1,125 subscribers8 August 2026 — 1,125 subscribers8 August 2026 — 1,124 subscribers11 August 2026 — 1,122 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net -3. 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 1,122–1,125 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:381,122-2
8 Aug 2026, 12:331,124-1
8 Aug 2026, 00:011,125no change
7 Aug 2026, 14:471,125first reading

Engagement

20 posts held, back to 2 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
11.5%
avg views ÷ 1,122 subscribers
Avg views / post
129
12 posts measured
Reaction rate
0.726%
reactions ÷ views · ER floor
Posts in window
12
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 3 of 12 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 (2 July 20266 August 2026)
Views total1,551
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:01 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

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.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 3 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 3reactions 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 2 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, 16:56 UTC63 viewsread 8 August 2026

JavaScript Weekly Next.js 16.3 https://nextjs.org/blog/next-16-3 Let's make the worst htmx ever! https://zserge.com/posts/worst-htmx-ever/ The secure way to release an npm package in 2026 https://evilmartians.com/chronicles/the-secure-way-to-release-an-npm-package mobx@7.0.0 https://github.com/mobxjs/mobx/releases/tag/mobx%407.0.0 JS to WebAssembly toolchain https://github.com/bytecodealliance/javy Your SPA Is

3 Aug 2026, 18:32 UTC104 viewsread 8 August 2026

Front-End Front Top Stories When You Need To Make a Triangle, Think Conic Gradients https://master.dev/blog/when-you-need-to-make-a-triangle-think-conic-gradients/ Cheatsheets for flex, grid, anchor positioning and invoker commands https://polypane.app/blog/cheatsheets-for-flex-grid-anchor-positioning-and-invoker-commands/ Fixing my tooltip accessibility mistake https://jakearchibald.com/2026/my-tooltip-a11y-mista

31 Jul 2026, 14:07 UTC136 viewsread 8 August 2026

Node Weekly The secure way to release an npm package in 2026 https://evilmartians.com/chronicles/the-secure-way-to-release-an-npm-package npm publish-time malware scanning and dual-use metadata https://github.blog/changelog/2026-07-28-npm-publish-time-malware-scanning-and-dual-use-metadata/ Check out the New Node.js API Documentation Preview https://nodejs.org/en/blog/announcements/new-api-docs-beta Disrupting su

29 Jul 2026, 18:43 UTC108 viewsread 8 August 2026

Frontend Focus WOFF 1.0: a milestone on W3C’s journey of fonts on the web https://www.w3.org/blog/2026/woff-1-0-a-milestone-on-w3cs-journey-of-fonts-on-the-web/ CSS Infinity Use Cases https://nerdy.dev/css-infinity-use-cases The Launch of CodePen 2.0 https://blog.codepen.io/2026/07/23/two-point-oh/ When You Need To Make a Triangle, Think Conic Gradients https://master.dev/blog/when-you-need-to-make-a-triangle-thi

28 Jul 2026, 18:55 UTC131 views1 reactionsread 8 August 2026

JavaScript Weekly Rust Is Eating JavaScript https://leerob.com/rust React’s programming model, compiled. https://octanejs.dev/ TypeScript 7 Is Here (And It's 10× Faster) https://www.youtube.com/watch?v=OytpXXeNmTQ My Agentic Coding Setup, July 2026 https://domenic.me/agentic-coding-setup/ How we built the new Table of Contents feature https://medium.engineering/how-we-built-the-new-table-of-contents-feature-c382

1

27 Jul 2026, 18:03 UTC129 views1 reactionsread 8 August 2026

Front-End Front Top Stories Masonry (with Animation) in CSS https://master.dev/blog/masonry-with-animation-in-css/ Under my radar: the highlight API, text-indent and font-family: math https://utilitybend.com/blog/under-my-radar-highlight-text-indent-and-font-family-math Use cases for aria-expanded https://piccalil.li/blog/use-cases-for-aria-expanded/ In-N-Out Animation using sibling-index() https://master.dev/blo

1

23 Jul 2026, 18:23 UTC186 viewsread 8 August 2026

Node Weekly No, We Can't Harden Node.js Against Prototype Pollution https://adventures.nodeland.dev/archive/no-we-cant-harden-nodejs-against-prototype/ Domenic Denicola's Agentic Coding Setup https://domenic.me/agentic-coding-setup/ better-sqlite3 13.0: The Popular SQLite Library Moves to N-API https://github.com/WiseLibs/better-sqlite3/releases/tag/v13.0.0 Unpacking the AsyncAPI npm Supply Chain Compromise https

23 Jul 2026, 07:39 UTC153 views1 reactionsread 8 August 2026

Frontend Focus Rebuilding FIFA's Standings Layout with CSS Subgrid https://ishadeed.com/article/fifa-layout/ Low and Mid-Tier Mobile for the Real World https://csswizardry.com/2026/07/low-and-mid-tier-mobile-for-the-real-world-2026/ How Figma Built Accessibility Into a Canvas-Based Product https://www.figma.com/blog/building-accessibility-into-a-canvas-based-product/ Time-Based Background Colour Transitions with

1

22 Jul 2026, 16:47 UTC115 viewsread 8 August 2026

JavaScript Weekly Framework Benchmarks https://framework-benchmarks.as93.net/ Nuxt 4.5 https://nuxt.com/blog/v4-5 New North Korean campaign uses fake coding interviews to steal developer credentials https://www.elastic.co/security-labs/contagious-interview-malware-svg-steganography Handling concurrency on the Web with Web Locks API https://tech.olx.com/handling-concurrency-on-the-web-with-web-locks-api-163b7e07ed

20 Jul 2026, 16:13 UTC124 viewsread 8 August 2026

Front-End Front Top Stories Do we still need build tools? https://olliewilliams.xyz/blog/no-build/ I stopped destructuring everything https://allthingssmitty.com/2026/07/13/i-stopped-destructuring-everything/ Lessons Learned Rewriting a Sticky Detector https://master.dev/blog/lessons-learned-rewriting-a-sticky-detector/ Boundary-Aware Styling in CSS https://master.dev/blog/boundary-aware-styling-in-css/ In defen

16 Jul 2026, 17:20 UTC162 viewsread 8 August 2026

node weekly Follow a Single HTTP Request Through Its ~200ms Life https://200ms.thenodebook.com/#act-0-prologue Fetch Needs Error Codes https://www.jasnell.me/posts/fetch-needs-error-codes Proxy and Reflect https://piccalil.li/blog/proxy-and-reflect/ Telegram Serverless: Run Telegram Bots on Telegram's Servers https://core.telegram.org/bots/serverless A fast, helpful, and open-source document parser https://githu

16 Jul 2026, 16:31 UTC140 viewsread 8 August 2026

Frontend Focus Do we still need build tools? https://olliewilliams.xyz/blog/no-build/ In defense of polyfills https://lea.verou.me/blog/2026/polyfills/ Visual design rules you can safely follow every time https://anthonyhobday.com/sideprojects/saferules/ A bug which only affected left-handed users https://shkspr.mobi/blog/2026/07/a-bug-which-only-affected-left-handed-users/ Thinking Horizontally in CSS @layer ht

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

Mentions

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.

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

“The weekly” (@webWekkly), 1,122 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/webWekkly.

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.