The CSS lh unit Use the lh unit to size and space elements relative to their computed line height.

Channel
Frontend Info
@frontend_info
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
5,308subscribers
-37 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001359079489 |
|---|---|
| Type | Channel |
| Username | @frontend_info |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/frontend_info |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 23:59 | 5,308 | -1 |
| 2 Sept 2026, 13:42 | 5,309 | -5 |
| 30 Aug 2026, 08:35 | 5,314 | -4 |
| 27 Aug 2026, 06:17 | 5,318 | -4 |
| 24 Aug 2026, 13:54 | 5,322 | -8 |
| 20 Aug 2026, 22:53 | 5,330 | -2 |
| 18 Aug 2026, 06:31 | 5,332 | +1 |
| 15 Aug 2026, 10:27 | 5,331 | -6 |
| 12 Aug 2026, 06:44 | 5,337 | -5 |
| 9 Aug 2026, 07:52 | 5,342 | -3 |
| 6 Aug 2026, 07:00 | 5,345 | no change |
| 6 Aug 2026, 06:54 | 5,345 | first reading |
Engagement
21 posts held, back to 18 May 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 8 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.50%
- avg views ÷ 5,308 subscribers
- Avg views / post
- 292
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 21 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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 21 (18 May 2026 – 11 August 2026) |
| Views total | 292 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 04:25 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
103 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 68.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 70 | 68.0% | |
| ❤ | 19 | 18.4% | |
| 👏 | 6 | 5.83% | |
| 😁 | 5 | 4.85% | |
| 🔥 | 2 | 1.94% | |
| 👨💻 | 1 | 0.971% |
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 18 of the 21 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 103 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 18 May 2026 to 11 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
Props, Composers, and Providers: the composition pattern ladder we use at Orus Choose progressively more powerful React composition patterns only when simpler prop-based APIs stop scaling #react
👍4
Rebuilding FIFA Standings Layout with CSS Subgrid Use CSS Grid and subgrid to recreate a responsive tournament bracket without restructuring the markup. #css
👍4
All this week articles at Frontend Info #27 Fetch needs error codes, staggered animations in CSS
👍4
Scroll-Driven Animations: Opposing Scroll Directions Create opposing scroll animations with CSS scroll-driven animations instead of JavaScript. #css #animation
I let React Compiler handle memoization: Here’s what actually broke React Compiler removes most manual memoization but still requires opt-outs for libraries and patterns it can’t safely optimize. #react
Modern CSS theming Build flexible light, dark, and custom themes using modern CSS variables and color features. #css
👍4
What are Git worktrees and why should I use them? Use Git worktrees to work on multiple branches simultaneously. #tools
👍5👏1
How to Evaluate an npm Package - 2026 Edition Use a repeatable checklist to evaluate npm packages beyond download counts by verifying provenance, maintenance, and supply-chain security. #tools
👍5🔥2
Everything you need to know about Sourcemaps Source maps improve debugging but can unintentionally expose your original source code if shipped publicly. #tools
👍4❤1👨💻1😁1
CSS vs JavaScript for animations Compare CSS and JavaScript animation approaches and choose based on control, performance, and complexity needs. #js #css
👍6❤1
Moving away from Tailwind - and learning to structure my CSS A practical reflection on replacing utility-first styling with more structured and maintainable CSS architecture. #css
👏5😁4
Showing the 12 most recent of 21 posts we hold for @frontend_info. 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
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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@fedevelopment · 28,790
Telegram ranks this channel #7 of 88 here — alongside 87 others — read 9 September 2026
@webde · 31,984
Telegram ranks this channel #12 of 84 here — alongside 83 others — read 5 September 2026
@javascript · 31,224
Telegram ranks this channel #19 of 76 here — alongside 75 others — read 6 September 2026
@frontendnoteschannel_ru · 31,509
Telegram ranks this channel #35 of 95 here — alongside 94 others — read 6 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Frontend Info” (@frontend_info), 5,308 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/frontend_info.
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.