Telegram RegisterThe public register of Telegram

Channel

Sky of Beginning

@raspberry_stories

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

67subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002057152156
TypeChannel
Username@raspberry_stories
Description讲讲树莓酱每天的奇怪日常,权当心理记录,当无人区发
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/raspberry_stories

Growth

678 August 2026 — 67 subscribers10 August 2026 — 67 subscribers8 August 202610 August 2026
2 measurements spanning 2 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 66–68 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 01:3167no change
8 Aug 2026, 01:3467first reading

Engagement

13 posts held, back to 19 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
109.1%
avg views ÷ 67 subscribers
Avg views / post
73.1
13 posts measured
Reaction rate
3.40%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 5 of 13 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 5 August 2026
Posts held13 (19 July 20265 August 2026)
Views total950
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 01:31 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
473
Videos
4
Links
62

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

Reaction mix

10 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣440.0%
🥰440.0%
🌚220.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 5 of the 13 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 10reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 19 July 2026 to 5 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

5 Aug 2026, 04:50 UTC222 viewsread 10 August 2026
Photo

对的对的 海报墙是对的

Signed Raspberry Kan

3 Aug 2026, 11:38 UTC38 viewsread 10 August 2026
Photo

Steam 硬件调查,DX12 GPU+Pre-Win10 这个组合强势增加,但已知 Pre-Win 10 的 Steam 客户端支持几乎都停了,除了我这种闲的没事真在 Win 7 上强开 Steam 的 只有 wine+DXVK 这个组合能解释哪来的理论上不存在的组合(wine 默认回报 XP,proton 默认回报 Win 10)

Signed Raspberry Kan

2 Aug 2026, 09:10 UTC43 views4 reactionsread 10 August 2026
Photo

坐在高铁上,驶向日落,也驶向归途。 这一年,说平凡也平凡——我还是那个容易紧张、怕生的我;说不平凡也不平凡——大学像一道分水岭,许多事要开始独自面对、独自承担。 但幸运的是,我遇见的每个人都成了我的“缓冲垫”。 室友脾气极好,懂得分寸与关照,最重要的是,他推荐的饭菜从未让我踩雷。班长尊重每一份微小的付出,有时我只是顺手帮了点小忙,他却会认真地准备礼物,或拉我去喝杯东西。身边大部分同学都很友善,其中几个尤其上进,和他们交换经验,总能让我偷偷记满几页笔记。 小组作业的日子里,x:Interactive 和 EasyToDo 项目组的伙伴们不仅靠谱负责,还时常投喂美食,那份心意比成绩更让我感动。也要感谢 HQU 的各位老师与工作人员,正是他们的保驾护航,才让我在学业和生活的摇摆中有了支点。 还有 StoryTeller Studios 的开发者们、“捡垃圾群”里的群友,以及 Amagi_Yukisaki、chn_alpha、

🥰4

Signed Raspberry Kan

28 Jul 2026, 07:20 UTC63 views2 reactionsread 10 August 2026

我知道阿姨也有自己的工作 但是 您把我用来垫高笔记本的四个瓶盖拿走了 今天上课,风扇狂转 95°C

🌚2

Signed Raspberry Kan

27 Jul 2026, 15:21 UTC57 viewsread 10 August 2026
Forwarded from @xinjingdailyVideo

via 匿名

Signed Raspberry Kan

27 Jul 2026, 15:13 UTC61 viewsread 10 August 2026
Photo

啥时候 Google Authenticator 改叫做身份验证器了 害我找半天

Signed Raspberry Kan

23 Jul 2026, 13:06 UTC93 viewsread 10 August 2026

作为组长,面对“不动脑”又想顺利过关的5人大一小组,你的核心任务就是:让每个人有清晰、独立、够数的功能模块,能各讲各的,还能集成到一个项目里。 老师的要求很明确: - 每人不少于2个功能模块(登录+注册算一个模块,用户管理的增删改查整体算一个模块)。 - 答辩时谁做的谁讲,成绩按个人算。 - 需要提交需求文档,组长统筹分工。 基于这个前提,我帮你分析两个方案,再给你一套可以直接拿来用的安排。 --- ## 一、两个方案的可行性分析 ### 方案一:做一个 AI 群聊系统 可行,且更符合老师规则。 AI群聊可以拆解出多个独立模块,适合多人并行开发,即使代码风格不完全统一,只要提前约定接口和数据库字段,集成也不难。而且“AI”听起来有亮点,答辩时能带点技术感。 ### 方案二:一人先做初始版,其他人再完善出2、3版 不太建议。 这种方式会让第一个人工作量大,但模块边界模糊;后面的人做的“完善”很可能依附于同一模块,不好拆

Signed Raspberry Kan

23 Jul 2026, 11:04 UTC66 viewsread 10 August 2026

中东风景好 朋友送我一块表 指针倒着跑

Signed Raspberry Kan

22 Jul 2026, 08:50 UTC53 views4 reactionsread 10 August 2026
Forwarded from @hatschannel

GPT-4 那会儿,我的编程能力还很青涩,写出来的代码常遭人嘲笑。那时我便暗暗发誓:总有一天,我要成为真正的天才程序员。时过境迁,我的编程水平突飞猛进。曾经困扰我几天的问题,如今片刻便能解决;以前想都不敢想的项目,现在也是信手拈来。偶尔我也会怀疑:我今天的成就,是否借助了太多外力?直到今天,我回顾来时的路 —— 从 GPT-4,到 GPT-4o;从 Sonnet,到 GLM5.2;再到如今的 * Incubating... Session paused Fable 5's safeguards flagged this message. The safeguards are intentionally broad right now and may flag safe and routine coding, cybersecurity, or biology work. These measures let us bring

🤣4

Signed Raspberry Kan

21 Jul 2026, 12:29 UTC80 views0 reactionsread 10 August 2026
Photo

小学期,实训老师提供的套餐(不是我们班) 信这个的可以去买脑白金了 我甚至去查SSM是啥 Spring/Spring MVC(正确的,合理的) 你这个MyBatis不是被Spring JPA肘飞了吗 还不考虑.NET的EntityFramework

Signed Raspberry Kan

20 Jul 2026, 16:45 UTC45 viewsread 10 August 2026
Forwarded from @xinjingdailyPhoto

via 猫又云云

Signed Raspberry Kan

19 Jul 2026, 16:18 UTC55 views0 reactionsread 10 August 2026
Photo

Spotify 真的把我玩明白了 最近听了KAMACHO 然后 Spotify 自动随机到了 Wishing Umbrella 我:还不错诶()

Signed Raspberry Kan

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Sky of Beginning” (@raspberry_stories), 67 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/raspberry_stories.

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.