Telegram RegisterThe public register of Telegram
Telegram profile photo for 蜜柑不时抱

Channel

蜜柑不时抱

@mikan_no_times

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

294subscribers

+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-1001271769408
TypeChannel
Username@mikan_no_times
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/mikan_no_times

Topic

Technology — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

Growth

294295294.57 August 2026 — 294 subscribers8 August 2026 — 294 subscribers30 August 2026 — 295 subscribers14 September 2026 — 294 subscribers7 August 202614 September 2026
4 measurements spanning 38 days. 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 294–295 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 11:55294-1
30 Aug 2026, 00:23295+1
8 Aug 2026, 08:06294no change
7 Aug 2026, 13:47294first reading

Engagement

19 posts held, back to 3 July 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 page 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 19 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍375.0%
🤔125.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 2 of the 19 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 3 July 2026 to 7 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, 09:04 UTC50 viewsread 8 August 2026
Forwarded from @QC_Grove

https://pythonspeed.com/articles/faster-float-math-rust/ TL;DR: Rust 1.98 给浮点数加了 algebraic_{add,sub,mul,div,rem} 方法允许编译器做代数优化(类似 -ffast-math 但是细粒度)

5 Aug 2026, 02:10 UTC35 viewsread 8 August 2026
Photo

FFmpeg 9.0版本刚发布了。这个版本的代号是“Lei” 按照惯例,“Lei” 应该是哪个计算机科学家/数学家,可想了好久也对不起来这是谁。 查了一下FFmpeg的开发邮件列表,才发现原来是纪念已故的@雷霄骅 [蜡烛]。 他在 2013–2016 年间撰写了大量 FFmpeg API、源码分析及音视频编解码、封装和传输协议方面的中文教程与示例,帮助许多中国开发者入门音视频和 FFmpeg。于 2016 年疑似因过劳突然离世。 今年是离世10周年,FFmpeg用了这个大版本号来纪念他。 ▎Source

4 Aug 2026, 16:25 UTC46 viewsread 8 August 2026
Forwarded from @cute_protons

https://blog.rust-lang.org/2026/08/04/enabling-polonius-alpha-on-nighty/ 有生之年,泪目了

1 Aug 2026, 18:23 UTC97 viewsread 8 August 2026
Forwarded from @MeowMiniMeow

TIL: git commit --fixup + git rebase -i --autosquash

1 Aug 2026, 12:46 UTC108 viewsread 8 August 2026

https://www.parsonsmatt.org/2019/03/19/sum_types_in_sql.html

1 Aug 2026, 10:24 UTC102 views1 reactionsread 8 August 2026
Forwarded from @lobste_rs

Where .env Went Wrong Comments via secretspec.dev via fzakaria

🤔1

28 Jul 2026, 08:09 UTC124 viewsread 8 August 2026
Forwarded from @yahnc

Paged Out #9 [pdf] https://pagedout.institute/download/PagedOut_009.pdf

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

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

“蜜柑不时抱” (@mikan_no_times), 294 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/mikan_no_times.

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.