Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝙍𝙞𝙣𝙞𝙗𝙖 日常

Channel

𝙍𝙞𝙣𝙞𝙗𝙖 日常

@riniba_channel

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

65subscribers

+5 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-1002231657938
TypeChannel
Username@riniba_channel
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live9 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/riniba_channel

Topic

Personal blog — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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

606562.57 August 2026 — 60 subscribers10 August 2026 — 60 subscribers15 August 2026 — 61 subscribers23 August 2026 — 60 subscribers29 August 2026 — 61 subscribers14 September 2026 — 60 subscribers28 September 2026 — 63 subscribers9 October 2026 — 65 subscribers7 August 20269 October 2026
8 measurements spanning 63 days, net +5. 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 59–66 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 07:3865+2
28 Sept 2026, 14:2263+3
14 Sept 2026, 16:5560-1
29 Aug 2026, 18:3661+1
23 Aug 2026, 08:1360-1
15 Aug 2026, 06:4861+1
10 Aug 2026, 05:0160no change
7 Aug 2026, 12:5460first reading

Engagement

19 posts held, back to 12 August 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 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 30 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

15 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍640.0%
❤533.3%
🙈213.3%
👏16.67%
🔥16.67%

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 8 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 15 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 12 August 2025 to 30 July 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

5 Nov 2025, 14:24 UTC≈1,140 views1 reactionsread 10 August 2026
Photo

有些爱情 注定无法得到

👍1

24 Sept 2025, 04:54 UTC≈1,450 views1 reactionsread 10 August 2026

最近超忙 于是我在自杀和自残当中,选择了自慰 共勉🫵

❤1

15 Sept 2025, 13:31 UTC≈1,610 views7 reactionsread 10 August 2026

使用ai编程的一些小经验 《代码有一点bug你修一修》 《我不要部分代码你把修改后的完整代码发给我》 《你的代码还是有问题》 《那你重新改,把改好的完整代码给我》 《不是刚刚还能跑怎么现在跑都跑不了了?》 《你没听懂我的意思吗?不要改变我原来的代码》 《不要给我打印任何调试功能*》 《我没让你做的你就别做》 《给我生成完整代码》 《用中文回答我》 《我让你做的功能哪去了》 《听不懂人话是吧》 《不要给我省略代码》 《给我完整的代码》 《我让你写的是完整代码不是部分函数》 《我的意思是让你改进我的代码,不是重新写一个新的代码》 《你怎么就听不懂啊》 《都说了参考我之前的代码》 《新的代码运行不了给我回去之前的版本》 《都说了回退版本你怎么给我写新代码了》 《都说了用C嘎嘎你怎么给我用Python+》 《请不要添加不必要的注释》 《请不要修改我原先的代码基本逻辑》 《帮我修改代码》 《在我的代码上修改..》 《不要改我的变量名!!…

👍5❤1🔥1

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

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

“𝙍𝙞𝙣𝙞𝙗𝙖 日常” (@riniba_channel), 65 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/riniba_channel.

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.