Channel
@oldherls
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
31subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001991000449 |
|---|---|
| Type | Channel |
| Username | @oldherls |
| Description | oldherl's random words and links |
| Created | 12 April 2024 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/oldherls |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 03:02 | 31 | no change |
| 7 Aug 2026, 22:49 | 31 | first reading |
20 posts held, back to 12 April 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 22 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
23 reactions across 6 posts, in 11 distinct kinds. The most used accounts for 21.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 5 | 21.7% | |
| 🤡 | 4 | 17.4% | |
| ❤ | 3 | 13.0% | |
| 🥰 | 3 | 13.0% | |
| 🔥 | 2 | 8.70% | |
| 🌚 | 1 | 4.35% | |
| 🎃 | 1 | 4.35% | |
| 👍 | 1 | 4.35% | |
| 👏 | 1 | 4.35% | |
| 😁 | 1 | 4.35% | |
| 🤓 | 1 | 4.35% |
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 6 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 23reactions 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 12 April 2024 to 22 May 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.
记录一下最近遇到的一个糟心事儿。 最近两个月开始又开始找工作机会，总的来说很不顺利，托朋友联系了两个内推也是石沉大海。（各位要是有远程工作的机会也请联系 job@laisky.com ） 昨天在 Linkedin 上有个 web3 背景的猎头联系我说有个不错的 contract 工作，就是需要先完成一个 code assessment。这个测试放在 notion 上，指向一个 github repo。但实际上，只要你在本地运行 npm start，就会启动恶意脚本，偷偷下载一个 js 脚本并执行。 这个攻击手法相当低劣，低级且恶劣，低级到了随手搜一下 eval 就能发现。 各位都小心一点，不要在本地运行任何来历不明的代码。即使源码里没有搜出可疑的内容也并不可靠，完全可以把攻击代码放在第三方依赖里。vscode 用户可以使用 devcontainer 来执行这些临时项目，能极大的缓解威胁。
❤1
跟风凑热闹！ https://my9.shatranj.space/anime/s/274ea651fcec58d6
又到了植树节！想和大家一起再种一颗 tgcn 频道树🌳！（这次有更多功能可以玩哦~） 这里是 oldherl's channel，是 @azaneko 的树枝 🌿 在频道树的第 2 层~ （如果你也有公开频道，想成为这个频道的树叶的话，就点击下面的「成为树叶」吧！ > <）
File, posted without a caption
这还真的是那个年代的东西呢……
🔥1
https://www.unixlinux.online/unixlinux/gdliunx/linuxzx/linuxwh/201702/14463.html 老新闻： 百資Linux 7登錄中國
龟壳云 Oracle Cloud Compute 的 x86-64 实例的监控终端什么时候变成 /dev/ttyS0 而不是 tty1 的？我的内核和getty都在往 tty1 写东西，监控终端里全看不到，我还以为死机了。用 netboot 启动其他救援系统也一样看不到。断电重启好几次，后来还是把这盘挂另一实例上才明白的。 （感谢 @lilydjwg 的协助！）
https://en.m.wikipedia.org/wiki/Pump.fun 居然有这种玩意：摆明了就是要骗你！连图标都是药丸（要完）
呀，我的准考证怎么找不到了？
https://x.com/the_liyanage/status/1910626529052418565
Cursor told me I should learn coding instead of asking it to generate it (🔥 Score: 157+ in 1 hour) Link: https://readhacker.news/s/6qRHt Comments: https://readhacker.news/c/6qRHt
https://www.androidauthority.com/pixel-4a-battery-downgrade-investigation-3521524/
Showing the 12 most recent of 20 posts we hold for @oldherls. 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 — 696,628 of 1,183,361entries 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.
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.
“oldherl's channel” (@oldherls), 31 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/oldherls.
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.