如何评价全民大耍起时代?
Signed @ym_ass 投稿系统

Channel
@ymsd8
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
14,212subscribers
+1,718 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001535727939 |
|---|---|
| Type | Channel |
| Username | @ymsd8 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/ymsd8 |
Memes & entertainment — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 00:37 | 14,212 | +292 |
| 17 Sept 2026, 15:57 | 13,920 | +35 |
| 15 Sept 2026, 17:20 | 13,885 | +22 |
| 14 Sept 2026, 03:15 | 13,863 | +57 |
| 12 Sept 2026, 09:40 | 13,806 | +39 |
| 10 Sept 2026, 09:39 | 13,767 | +71 |
| 7 Sept 2026, 07:20 | 13,696 | +65 |
| 4 Sept 2026, 13:38 | 13,631 | +30 |
| 3 Sept 2026, 00:45 | 13,601 | +29 |
| 2 Sept 2026, 01:56 | 13,572 | +21 |
| 1 Sept 2026, 04:26 | 13,551 | +41 |
| 31 Aug 2026, 03:25 | 13,510 | +57 |
| 30 Aug 2026, 00:56 | 13,453 | +50 |
| 29 Aug 2026, 03:53 | 13,403 | +30 |
| 28 Aug 2026, 01:22 | 13,373 | +25 |
| 27 Aug 2026, 02:33 | 13,348 | +34 |
| 26 Aug 2026, 00:52 | 13,314 | +30 |
| 24 Aug 2026, 22:23 | 13,284 | +75 |
| 23 Aug 2026, 05:14 | 13,209 | +67 |
| 21 Aug 2026, 13:59 | 13,142 | first reading |
53 posts held, back to 22 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 47 pages 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 53 posts for this entry, the most recent from 2 September 2026. An engagement rate over an empty window would be a number about nothing.
145 reactions across 31 posts, in 12 distinct kinds. The most used accounts for 28.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 41 | 28.3% | |
| 😁 | 34 | 23.4% | |
| 😨 | 21 | 14.5% | |
| 👍 | 12 | 8.28% | |
| 🫡 | 12 | 8.28% | |
| 😭 | 9 | 6.21% | |
| ✍ | 5 | 3.45% | |
| 🍾 | 4 | 2.76% | |
| 🌭 | 3 | 2.07% | |
| 👏 | 2 | 1.38% | |
| 🤯 | 1 | 0.69% | |
| 🥰 | 1 | 0.69% |
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 36 of the 53 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 145 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 53 most recent posts we hold, published 22 July 2026 to 2 September 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.
如何评价全民大耍起时代?
Signed @ym_ass 投稿系统
三观重要还是五官重要
Signed @ym_ass 投稿系统
寿司味道好 遥想当年硫磺岛 队友板载我逃跑 天皇算个屌
Signed @ym_ass 投稿系统
另外,你能来北京吗? 我沉默了。 她以为我不想去。 我们的故事并不算美丽 却如此难以忘记~
❤1😁1
Signed @ym_ass 投稿系统
房子跌了,工资少了,感觉越来越好 工时长了,睡觉少了,感觉越来越好
❤4👏2
Signed @ym_ass 投稿系统
老哥们,我这种情况是不是要割包皮啊。我平常有点包茎,但是包皮很容易就能完整剥下来,就算硬起来了也很容易。 上周跟女朋友破了处,我发现因为包皮过长,戴了安全套之后再插入,抽查的时候感觉是阴茎在包皮里动而不是跟阴道摩擦。换个说法就是包皮跟阴道相对静止,然后阴茎在包皮里面动这种感觉。 虽然龟头是完全露出来的,但是插入的时候还是没什么感觉,除非我用手在根部把阴茎上的皮往后拽才有种跟阴道壁摩擦的感觉。 本来我之前一直以为我能把龟头拨开就不用割,但是现在遇到这种情况也挺影响体验的,想问下老哥们这是安全套戴好就能解决还是说必须要割包皮了
❤1
Signed @ym_ass 投稿系统
手机耍起嘛😍游戏打起嘛😉空调开起嘛🤗甜水喝起嘛😋小钱小耍😛打钱大耍😎没钱硬耍😏借钱来耍🤓
❤1
Signed @ym_ass 投稿系统
认识很多年的一个女性朋友,暗恋多年之前发现她在北京做外围。 她本人长得有点像杨超越,颜值八分,身材至少十分,腰细腿长,穿衣服特别辣,也是个有点粉丝的小网红。平时看起来挺清纯、高冷,朋友圈也都是精致生活,完全想不到私下会陪大哥出去。 知道以后,我特别想找人玩她 北京有没有大哥愿意交流下 该怎么找人去操她呢绝对极品 via: 6 6
Signed @ym_ass 投稿系统
不懂就问系列,kpop现在为什么完全不骚了啊 以前的aoa以前的少女时代各种大长腿骚屁股扭得飞起,各种商演也是榨精舞,现在的女团搞尼玛还装逼整点概念mv说是,我都想笑了,看个骚逼还要被教育说是 骚逼kpop,你崛起吧!
❤2
Signed @ym_ass 投稿系统
国内为什么没有走进大滥交时代? 才发现女的也很压抑。刚刚刷抖音,看到一个肌肉男评论区各种性压抑,什么美甲又掉了什么又想挖了,我还以为男的搞节目效果,看了一圈真是女号。又找了一些别的擦边男视频,评论区真让我刷新三观,压抑程度已经在我之上。 既然男的女的都这么压抑了,为什么没有变成灯塔国上世纪那种全民大滥交时代? 理性讨论一下
❤7
Signed @ym_ass 投稿系统
上次有堆血雾和我表白我一拳把它打成女孩了
😁2
Signed @ym_ass 投稿系统
是时候聊点成年人的话题了! 你们说,许家印到底是不是现实版平账大圣?
Signed @ym_ass 投稿系统
Showing the 12 most recent of 53 posts we hold for @ymsd8. 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.
Named by 2 registered channels — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“YM 银梦树洞” (@ymsd8), 14,212 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/ymsd8.
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.