Telegram RegisterThe public register of Telegram

Channel

Lobste.rs

@lobste_rs

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

1,779subscribers

+12 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001219200087
TypeChannel
Username@lobste_rs
Created15 December 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/lobste_rs

Growth

1,7671,7791,7736 August 2026 — 1,767 subscribers6 August 2026 — 1,768 subscribers10 August 2026 — 1,771 subscribers13 August 2026 — 1,779 subscribers6 August 202613 August 2026
4 measurements spanning 6 days, net +12. 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,765–1,781 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:331,779+8
10 Aug 2026, 06:311,771+3
6 Aug 2026, 21:011,768+1
6 Aug 2026, 18:021,767first reading

Engagement

40 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.15%
avg views ÷ 1,779 subscribers
Avg views / post
145
40 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
40
of 40 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held40 (6 August 20267 August 2026)
Views total5,798
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:36 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.

Recent posts

7 Aug 2026, 15:19 UTC92 viewsread 7 August 2026

A new model for source control by Alcides Fonseca Comments via wiki.alcidesfonseca.com by alcides

7 Aug 2026, 14:19 UTC114 viewsread 7 August 2026

How a device finds encrypted DNS by itself Comments via blog.dundns.eu by amir

7 Aug 2026, 13:19 UTC130 viewsread 7 August 2026

John Henry in the age of AI Comments via davepedu.com by dpedu

7 Aug 2026, 13:19 UTC126 viewsread 7 August 2026

Informing HTTP Extension Design with Data Comments via mnot.net via Exagone313

7 Aug 2026, 11:19 UTC138 viewsread 7 August 2026

From constraint models to playable puzzle games Comments via zayenz.se by mzl

7 Aug 2026, 11:19 UTC138 viewsread 7 August 2026

Notes Compound, Blogs Compile: When I Update a Note vs. Publish a Post Comments via ssp.sh by sspaeti

7 Aug 2026, 10:19 UTC140 viewsread 7 August 2026

What are you doing this weekend? Feel free to tell what you plan on doing this weekend and even ask for help or feedback.Please keep in mind it’s more than OK to do nothing at all too! via by caius

7 Aug 2026, 09:19 UTC153 viewsread 7 August 2026

Some ways to navigate through 'git blame' over time in GNU Emacs Comments via utcc.utoronto.ca via mattofr

7 Aug 2026, 09:19 UTC157 viewsread 7 August 2026

Nix Evaluation Is a Scheduling Problem Comments via notashelf.dev via abhin4v

7 Aug 2026, 07:19 UTC166 viewsread 7 August 2026

Introducing Kitesurf: The agent-first browser that runs in V8 isolates on Cloudflare Workers Comments via blog.cloudflare.com via sanxiyn

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

Citation-graph rank — 123,069 of 1,189,255entries 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.

Forward network

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.

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

“Lobste.rs” (@lobste_rs), 1,779 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/lobste_rs.

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.