请输入文本
👏3😁3👍1

Channel
@atashare
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
7,429subscribers
-233 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001495742009 |
|---|---|
| Type | Channel |
| Username | @atashare |
| Description | 分享实用的、小众的网络资源和资讯。 原神频道 @YuanShen ATA Bots @atabots 🎉 友链: RSS 订阅聚合 | @dailyrss 美图 | @beautygirls9527 CN导航 | @CN_DH 书墨资源 | @shumozy 404 KIDS SEES GHOSTS | @isaiahsystem 开源社区资讯 | @opencfdchannel |
| Created | 11 March 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/atashare |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 13:01 | 7,429 | -3 |
| 9 Nov 2026, 23:46 | 7,432 | -3 |
| 6 Nov 2026, 20:59 | 7,435 | -6 |
| 3 Nov 2026, 22:06 | 7,441 | +1 |
| 1 Nov 2026, 05:57 | 7,440 | +1 |
| 29 Oct 2026, 08:37 | 7,439 | -7 |
| 25 Oct 2026, 21:31 | 7,446 | -5 |
| 22 Oct 2026, 19:20 | 7,451 | -6 |
| 20 Oct 2026, 01:38 | 7,457 | -5 |
| 17 Oct 2026, 02:28 | 7,462 | -3 |
| 14 Oct 2026, 12:07 | 7,465 | -2 |
| 10 Oct 2026, 15:20 | 7,467 | -12 |
| 4 Oct 2026, 19:18 | 7,479 | -6 |
| 25 Sept 2026, 11:54 | 7,485 | -26 |
| 17 Sept 2026, 00:39 | 7,511 | -16 |
| 12 Sept 2026, 18:39 | 7,527 | -15 |
| 8 Sept 2026, 08:37 | 7,542 | -20 |
| 3 Sept 2026, 07:06 | 7,562 | -8 |
| 31 Aug 2026, 00:48 | 7,570 | -13 |
| 28 Aug 2026, 00:34 | 7,583 | first reading |
21 posts held, back to 6 February 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 39 pages of Telegram’s post history, 20 posts per page.
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 22 October 2026 |
|---|---|
| Posts held | 21 (6 February 2025 – 22 October 2026) |
| Views total | 1,360 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 18:02 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.
Lifetime counters from Telegram’s own channel header, read 14 November 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.
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.
194 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 36.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 71 | 36.6% | |
| ❤ | 31 | 16.0% | |
| 🤯 | 31 | 16.0% | |
| 🤣 | 23 | 11.9% | |
| 😁 | 19 | 9.79% | |
| 🤡 | 8 | 4.12% | |
| 👏 | 7 | 3.61% | |
| 🆒 | 2 | 1.03% | |
| 😭 | 1 | 0.515% | |
| 🤓 | 1 | 0.515% |
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 20 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 194 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 6 February 2025 to 22 October 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.
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
请输入文本
👏3😁3👍1
AA 依旧定制榜
❤1
https://blog.ferstar.org/posts/zcode-silent-workspace-snapshot-upload/ 国外 Grok Build 珠玉在前,国内的 Z\ 也跟上了
▎ Jev:一个不“写字”的大模型 官网 | 文档 | 发布博文 TypeSafe 发了一个比较特殊的模型,不做对话、不生成文本,只针对一份 state 做类型化的判断,返回代码能直接用的值。 三种问题原语: - Choice:从给定选项里选一个,返回选项 + 各选项概率 + 置信度 - Score:按量规给 state 打分,返回分数 + 概率 + 置信度 - Noul:这句话为真吗,返回 0~1 的概率 重点是又快又便宜,端到端 70ms~500ms,输入 $0.042/MTok,输出免费,比同级别 LLM 快 40~200 倍。当今 LLM 工作流里有一些情况要求时延低,而且结构化输出已经不可或缺,可以说这个创业公司找到了一个很不错的垂类。 社区已经拿它跑了一堆东西:浏览器 Agent(订票 7 秒左右)、Doom、五子棋、代码审查等。 把这些生态项目整理成了一个 awesome list,持续补充,欢迎 PR:…
❤2
Steam 被丝之歌玩家冲爆了 还是太幸压抑了
😁8❤1
哪位实习生不小心把官号当朋友圈了
从今年 3 月份 Gemini 2.5 Pro 发布第一版直到现在,它的 vibe 都是我在一众 LLM 里面最喜欢的,不论是编程还是日常提问。 如果要我点评它,我会说:世界知识丰富,说话娓娓道来而不啰嗦,带有恰当的人情味。
❤12
Vue 的第一大全栈框架 Nuxt 被 Vercel “收编”了 [1][2][3] 这下 Vue 和 React 生态下的两大巨头都在 Vercel 手里了😂很难说这是好事还是坏事 好事是 Nuxt 团队的资金压力减小很多,更专注于开源事业。 - Nuxt UI Pro 会免费 - 会开源 Nuxt Studio 允许自部署 坏事是 Vercel 在前端的话语权进一步扩大了,有形成垄断的风险。
👍2❤1😭1
幽默 Dify,大半年了,社区反馈多次还修不好
🤡6❤3
https://github.com/huggingface/transformers/pull/36878 Qwen3 要来了🤔
👍7🤡2
https://developers.googleblog.com/en/experiment-with-gemini-20-flash-native-image-generation/ 昨天谷歌的 Gemini 支持多模态输入输出了,挺好玩的,大概是大厂里第一个发布的?最开始是 OpenAI 在 GPT-4 时期画的饼,然后一直没实现
👍4
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 仓库追踪进展并参与测试。此次性能跃迁被视为开发体验的革命性升…
👍11❤2
Showing the 12 most recent of 21 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.
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.
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.
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.
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.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“鲲的碎碎念” (@atashare), 7,429 subscribers as measured 14 November 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.