Channel
@U2FPlus1s
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
237subscribers
-1 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001058143795 |
|---|---|
| Type | Channel |
| Username | @U2FPlus1s |
| Created | Between 1 May 2016 and 31 January 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/U2FPlus1s |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:08 | 237 | -1 |
| 7 Aug 2026, 02:33 | 238 | no change |
| 5 Aug 2026, 23:21 | 238 | first reading |
20 posts held, back to 31 January 2022 — 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 pageof 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 20 posts for this entry, the most recent from 10 February 2025. An engagement rate over an empty window would be a number about nothing.
18 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 72.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13 | 72.2% | |
| 🔥 | 3 | 16.7% | |
| ❤ | 2 | 11.1% |
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 9 of the 20 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 18reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 January 2022 to 10 February 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.
发现了个有意思的事 Linux 如果想要重启的话，需要以下系统调用 syscall(SYS_reboot, LINUX_REBOOT_MAGIC1, LINUX_REBOOT_MAGIC2, LINUX_REBOOT_CMD_RESTART, NULL); 其中 SYS_reboot 没什么特别的 但是 LINUX_REBOOT_MAGIC1 为 0xfee1dead 即"feel dead" 而 LINUX_REBOOT_MAGIC2 为 0x28121969 即 Linus 的生日（1969年12月28日） 这个 MAGIC2 也可以是 0x05121996 或 0x16041998 或 0x20112000 分别是 Linus 三个女儿的生日 扩展阅读：https://en.wikipedia.org/wiki/Hexspeak
👍5
Signed U2F sdGVkX1
然后通过 vnc 彻底夺舍！
Signed U2F sdGVkX1
https://t.me/milkice_portal/2024 工具来自
Signed U2F sdGVkX1
由于没有扩展坞，而键鼠都是 USB-A，故使用手机激活 mac mini🌚 #行为艺术
Signed U2F sdGVkX1
https://oasis.decart.ai AI 脑补的 Minecraft 画面，可操作游玩 （警告，十分梦核，略微掉 SAN
Signed U2F sdGVkX1
🌚半冷半热的知识 Windows 进程的 PID 都可以被 4 整除
🔥3
Signed U2F sdGVkX1
春节快乐！:P
Signed U2F sdGVkX1 | 我在线上
调侃了许久，这天还是来了 R.I.P
Signed U2F sdGVkX1 | 我在线上
【快讯】新华社：中国共产党中央委员会、中华人民共和国全国人民代表大会常务委员会、中华人民共和国国务院、中国人民政治协商会议全国委员会、中国共产党和中华人民共和国中央军事委员会，极其悲痛地向全党全军全国各族人民通告：我们敬爱的江泽民同志患白血病合并多脏器功能衰竭，抢救无效，于2022年11月30日12时13分在上海逝世，享年96岁。
❤1
Signed U2F sdGVkX1 | 我在线上
有消息说，在即将发行的Telegram版本中，使用频道身份发言会变为 Premium 功能。根据 GitHub 的代码变动可以看到这一点。
Signed U2F sdGVkX1✨
接：
Signed U2F sdGVkX1✨
Photo, posted without a caption
👍2
Signed U2F sdGVkX1✨
Showing the 12 most recent of 20 posts we hold for @U2FPlus1s. 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.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“回忆的梦想赞助商️” (@U2FPlus1s), 237 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/U2FPlus1s.
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.