Telegram RegisterThe public register of Telegram
Telegram profile photo for 鲲的碎碎念

Channel

鲲的碎碎念

@atashare

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

7,562subscribers

-100 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-1001495742009
TypeChannel
Username@atashare
Created11 March 2020measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live3 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/atashare

Growth

7,5627,6627,6126 August 2026 — 7,662 subscribers7 August 2026 — 7,661 subscribers9 August 2026 — 7,653 subscribers12 August 2026 — 7,641 subscribers15 August 2026 — 7,633 subscribers18 August 2026 — 7,616 subscribers21 August 2026 — 7,608 subscribers24 August 2026 — 7,588 subscribers28 August 2026 — 7,583 subscribers31 August 2026 — 7,570 subscribers3 September 2026 — 7,562 subscribers6 August 20263 September 2026
11 measurements spanning 27 days, net -100. 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 7,547–7,677 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 07:067,562-8
31 Aug 2026, 00:487,570-13
28 Aug 2026, 00:347,583-5
24 Aug 2026, 17:067,588-20
21 Aug 2026, 05:347,608-8
18 Aug 2026, 02:117,616-17
15 Aug 2026, 11:337,633-8
12 Aug 2026, 07:557,641-12
9 Aug 2026, 15:127,653-8
7 Aug 2026, 01:027,661-1
6 Aug 2026, 20:157,662first reading

Engagement

17 posts held, back to 6 February 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pages of 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 17 posts for this entry, the most recent from 4 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 34s
Average length
1m 34s

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

182 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7038.5%
🤯3117.0%
2714.8%
🤣2212.1%
😁168.79%
🤡84.40%
👏42.20%
🆒21.10%
😭10.549%
🤓10.549%

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 17 of the 17 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 182 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 6 February 2025 to 4 September 2025, 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

4 Sept 2025, 14:04 UTC≈8,230 views8 reactionsread 28 August 2026
Photo

Steam 被丝之歌玩家冲爆了 还是太幸压抑了

😁8

19 Aug 2025, 11:41 UTC≈9,260 views0 reactionsread 28 August 2026
Photo

哪位实习生不小心把官号当朋友圈了

13 Aug 2025, 08:02 UTC≈8,260 views12 reactionsread 28 August 2026
Photo

从今年 3 月份 Gemini 2.5 Pro 发布第一版直到现在,它的 vibe 都是我在一众 LLM 里面最喜欢的,不论是编程还是日常提问。 如果要我点评它,我会说:世界知识丰富,说话娓娓道来而不啰嗦,带有恰当的人情味。

12

9 Jul 2025, 00:58 UTC≈9,210 views4 reactionsread 28 August 2026

Vue 的第一大全栈框架 Nuxt 被 Vercel “收编”了 [1][2][3] 这下 Vue 和 React 生态下的两大巨头都在 Vercel 手里了😂很难说这是好事还是坏事 好事是 Nuxt 团队的资金压力减小很多,更专注于开源事业。 - Nuxt UI Pro 会免费 - 会开源 Nuxt Studio 允许自部署 坏事是 Vercel 在前端的话语权进一步扩大了,有形成垄断的风险。

👍21😭1

14 May 2025, 10:53 UTC≈9,270 views9 reactionsread 28 August 2026
Photo

幽默 Dify,大半年了,社区反馈多次还修不好

🤡63

21 Mar 2025, 16:04 UTC≈9,510 views9 reactionsread 28 August 2026

https://github.com/huggingface/transformers/pull/36878 Qwen3 要来了🤔

👍7🤡2

13 Mar 2025, 11:23 UTC≈8,490 views4 reactionsread 28 August 2026
Photo

https://developers.googleblog.com/en/experiment-with-gemini-20-flash-native-image-generation/ 昨天谷歌的 Gemini 支持多模态输入输出了,挺好玩的,大概是大厂里第一个发布的?最开始是 OpenAI 在 GPT-4 时期画的饼,然后一直没实现

👍4

12 Mar 2025, 02:17 UTC≈6,170 views13 reactionsread 28 August 2026
Photo

TypeScript 宣布原生移植计划,性能将提升 10 倍 TypeScript 团队宣布将编译器及工具链移植至原生代码(Go 语言),目标在 2025 年实现里程碑式性能突破。新版本 tsc 编译器在主流项目测试中展现出 10 倍速度提升:VS Code 代码库类型检查耗时从 77.8 秒缩至 7.5 秒,编辑器项目加载时间更从 9.6 秒优化至 1.2 秒。该方案还将内存占用降低约 50%。 原生版本预计 2025 年中发布命令行检查工具,年底完成全功能支持。现有 JavaScript 代码库(TypeScript 6.x)将与原生版本(TypeScript 7.0,代号 "Corsa")并行维护,确保平稳过渡。升级后将支持实时全项目错误检测、高阶重构功能,并为 AI 开发工具提供新基建。 团队将于 3 月 13 日举办问答活动,开发者可通过 GitHub 仓库追踪进展并参与测试。此次性能跃迁被视为开发体验的革命性升

👍112

2 Mar 2025, 06:08 UTC≈5,900 views43 reactionsread 28 August 2026
Photo

不是,中科院也部署了我的项目? https://data.aicnic.cn/dms-html/index.html

🤯31👍4👏4😁4

1 Mar 2025, 05:50 UTC≈5,540 views19 reactionsread 28 August 2026
Photo

https://zhuanlan.zhihu.com/p/27181462601 DeepSeek 官方直接把自己的成本和收入也“开源”了👀

👍17🆒2

24 Feb 2025, 13:00 UTC≈5,260 views0 reactionsread 28 August 2026
Photo

用 Claude 3.5 Sonnet 修 bug 改来改去最后用回了第一版方案(等于什么都没改),给我气笑了,但是看它这么真诚又不好说什么 最后我把文件删掉,自己总结了一下整个过程的要点,让它重新写了一份。一遍过😐

18 Feb 2025, 13:44 UTC≈5,660 views24 reactionsread 28 August 2026
Photo

xAI 的前端是谁写的(

🤣22👍1🤓1

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

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.

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.

油油の科技软件资源分享
@youyousharechannel · 89,723
Telegram ranks this channel #19 of 43 here — alongside 42 others — read 17 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“鲲的碎碎念” (@atashare), 7,562 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/atashare.

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.