Telegram RegisterThe public register of Telegram

Channel

堆栈

@libstack

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

644subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001324884809
TypeChannel
Username@libstack
DescriptionJust a Resource Site 正如我们享受他人带来的巨大便利一样,我们也应该乐于有机会让自己为他人服务,而且我们应该免费并慷慨地这么做 最后编辑于2019年1月29日 (星期二) 02:57
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 live8 August 2026
Measurements held2
On Telegramt.me/libstack

Growth

6447 Aug 2026, 11:47 — 644 subscribers8 Aug 2026, 02:48 — 644 subscribers7 Aug 2026, 11:478 Aug 2026, 02:48
2 measurements taken within a single day. 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 643–645 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 02:48644no change
7 Aug 2026, 11:47644first reading

Engagement

20 posts held, back to 27 June 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
26.5%
avg views ÷ 644 subscribers
Avg views / post
171
8 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
8
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 8 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 (27 June 20266 August 2026)
Views total1,365
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:48 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.

What this channel posts

Photos
125
Videos
4
Links
197

Lifetime counters from Telegram’s own channel header, read 8 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.

Video runtime
44s
Average length
44s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
360.0%
👏240.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 4 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 5reactions 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 27 June 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, 01:11 UTC73 viewsread 8 August 2026

QzoneArchive,找回你删掉的在开智前发的 qq 空间 GitHub地址:https://github.com/Gaoshu705/QzoneArchive 下载地址:https://pan.quark.cn/s/69baf8c8aadc

Signed Akalin233

31 Jul 2026, 11:24 UTC214 viewsread 8 August 2026

https://github.com/Hypostasis-Cat/HypoMux Windows 上的多网卡带宽叠加工具,能把电脑同时连着的几条网络(有线、WiFi、手机热点都行)捆在一起用,下载大文件的时候把连接分散到不同线路上,总速度能叠加起来 src github 淘金

Signed Akalin233

30 Jul 2026, 11:33 UTC158 viewsread 8 August 2026
Forwarded from @puddin_share

【高危漏洞预警】Gitea远程代码执行漏洞CVE-2026-60004 https://mp.weixin.qq.com/s/y5uGvhaPx9KBj3XIZQ3bXg

Signed Akalin233

30 Jul 2026, 07:55 UTC174 viewsread 8 August 2026

https://github.com/5LmQ/game-1 一个包含回合制 RPG 与终端音游的 C++ 游戏合集

Signed Akalin233

28 Jul 2026, 12:59 UTC182 viewsread 8 August 2026

TLDR 三阶段流程 第一级询问客服:获取客服明确拒绝的文字和确认余额 第二级正式投诉:通过官网表单提交正式投诉。核心诉求:要回余额。如果客服拒绝,直接索要 Deadlock Letter · 第三级通信办公室: 拿到 Deadlock Letter 后,或投诉 6 周后未解决,直接在线向 commsombudsman.org 提交免费申诉 绝对不能做的事 不要手动取消 PAC,会让转网失去效力 不要关闭账户,等于“自愿放弃”,自断退路 不要和一线客服争论条款,他们没权限,记录证据后直接切入二级投诉 不要在申诉里扯封号对不对 不要在 case 里拖太久,28 天内必须回应,否则视为已解决 请直接复制以下英文内容发往 giffgaff 的正式投诉渠道(官网 giffgaff.com/complaints,注意不要发给 Ask an agent 的一线客服)。发送前请替换括号里的占位符。邮件主题:Formal Complaint

Signed Akalin233

28 Jul 2026, 12:53 UTC149 viewsread 8 August 2026
Forwarded from @dejavuBlog

GiffGaff 退款维权流程 https://x.com/0xCatCrypto/status/2081700347748491768?s=20

Signed Akalin233

27 Jul 2026, 15:18 UTC138 views0 reactionsread 8 August 2026

Kimi K3 现已开源 https://huggingface.co/moonshotai/Kimi-K3

Signed Akalin233

9 Jul 2026, 07:24 UTC316 views3 reactionsread 8 August 2026
Forwarded from @geeksharePhoto

#设计 #工具 📦 用不惯 GIMP?这个项目把它改得更像 Photoshop 🌐 GIMP 官网 PhotoGIMP 是一个面向 GIMP 3+ 的开源补丁包,可以把 GIMP 的界面布局、快捷键和默认配置调整得更接近 Adobe Photoshop。 而且 Photoshop 支持的默认快捷键,它也基本都支持! 📮投稿 📢频道 💬吹水 🌐网站

3

Signed Akalin233

8 Jul 2026, 08:11 UTC291 viewsread 8 August 2026

https://github.com/NebuSec/CyberMeowfia https://rootme.nebusec.ai/

Signed Akalin233

4 Jul 2026, 10:54 UTC284 views2 reactionsread 8 August 2026
Photo

iconify一键抄作业 头图是webm(gif),已知问题是导入后不会动需要手动提取出来再应用一次

👏2

Signed Akalin233

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

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.

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

“堆栈” (@libstack), 644 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/libstack.

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.