桐城某生,授餐于某监为童子师有年矣,宾主颇相得。一日,请于某监,欲向宫内一游,以护眼界。某监允之,为备腰牌,置衣帽,冒为内庭常供奉者。临入,戒之曰:“入午门时,侍卫必乘人猝不及防,猛声呼啸,非常入者必惊骇失措;惊则执之,性命不可保。每入一门,皆如此。然渐进,防间亦渐疏,呼声亦渐杀。盖谓已历入多门,必系常入宫者,非奸细也。” 某监既引生入,游览毕,小憩于某监坐起所。某监亦内庭有头脸者,其坐起所亦常为圣驾所临幸,谓生少坐即行,恐圣驾猝来,无避匿处也。正言时,忽闻宫监嘘气声,某监惊曰:“圣驾来矣,可奈何?无已,其暂藏炕床腹内。” 生入炕腹,从板缝外窥,颇清晰,见世宗盛气入,盘膝坐炕上。俄有力士数人,牵一人至,面惨无人色,命之跪,不跪,曰:“尔独不念手足情乎?曹丕称帝,即窘曹植,然固未置之死地也。尔谋夺大位,计陷储君,惧昆弟之不甘服,欲尽杀之以灭口。独不念众口史笔,难摧公理乎?”世宗大怒,立批其颊,命力士缚其手足,出药粉一小瓶,色白如雪…

Channel
随感、杂考、未来ダヨー
@weblogue
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
114subscribers
+1 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 | -1002755606411 |
|---|---|
| Type | Channel |
| Username | @weblogue |
| Description | https://t.me/weblogue/1015 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/weblogue |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 06:02 | 114 | no change |
| 8 Aug 2026, 19:22 | 114 | +1 |
| 8 Aug 2026, 00:13 | 113 | first reading |
Engagement
19 posts held, back to 7 August 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 34.3%
- avg views ÷ 114 subscribers
- Avg views / post
- 39.1
- 18 posts measured
- Reaction rate
- 4.76%
- reactions ÷ views · ER floor
- Posts in window
- 19
- of 19 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 2 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 19 (7 August 2026 – 8 August 2026) |
| Views total | 704 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 06:02 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
- 894
- Videos
- 169
- Links
- 194
Lifetime counters from Telegram’s own channel header, read 9 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.
- Video runtime
- 14s
- Average length
- 14s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
5 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😨 | 3 | 60.0% | |
| ❤ | 1 | 20.0% | |
| 🙏 | 1 | 20.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 5reactions 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 7 August 2026 to 8 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
Video, posted without a caption
「あさのうた (feat. 初音ミク)」- 大漠波新/初音ミク 专辑: あさのうた (feat. 初音ミク) #网易云音乐 #flac 29.75MB 1981.05kbps via @Music163bot
对 Wireless.pdf 和 棉花糖 @misncandy 等人的回应。 希望这可以是妳圈最后一篇PDF.
我想发这个试试看,有没有人有好的建议。 我不知道怎么办了,我是高位截瘫加尿毒症,焦虑症抑郁症(卖惨但真),二十多年了。 我是从小时候就对网络感兴趣,那时候就开始琢磨看看外面的世界是什么样的,后来和志同道合的网友组建了 QQ 群,开始合租,合租的人越来越多管理不过来,直接就搭建了面板搞起了机场,还能赚些钱。 我很注意加入的人,因为遇到过很可疑的人,所以我一般都会先各种恐吓警告后还能接受条件的人就让他加入。 一个破烂面板就这样坚持快十年,我买的服务器都是好东西,成本也越来越高,大概所有收入大概 1/4~1/5 才是利润,大概四千到五千人民币左右,也算是游戏里看上什么皮肤自由了。我没有存钱,我家人也不知道我一天天在搞啥,也不找他们要钱,水电气话费还有各种医疗护理用品费用都是我在出。 我现实里基本没有上过学,也没有任何朋友,我在这个小房间里通过手机这个窗口看世界,没法从其他的角度看待各种问题。如果出门别人对我说什么我只能傻笑应…
开心!获得了 beatMARIO 和 MARON 老师的签名~ 并且提出羞耻的要求让马里奥老师给我写了奇怪的话~
(宋前废)帝自以为昔在东宫,不为孝武所爱,及即位,将掘景宁陵,太史言于帝不利而止。乃纵粪于陵,肆骂孝武帝为“齇奴”。 屎?! 初,太后疾笃,遣呼帝。帝曰:“病人间多鬼,可畏,那可往。”太后怒,语侍者:“将刀来,破我腹,那得生如此宁馨儿!”及太后崩后数日,帝梦太后谓之曰:“汝不孝不仁,本无人君之相。子尚愚悖如此,亦非运祚所及。孝武险虐灭道,怨结人神,儿子虽多,并无天命。大运所归,应还文帝之子。”其后湘东王绍位,果文帝子也。故帝聚诸叔京邑,虑在外为患。 山阴公主淫恣过度,谓帝曰:“妾与陛下,虽男女有殊,俱托体先帝。陛下六宫万数,而妾唯驸马一人。事不均平,一何至此!”帝乃为主置面首左右三十人;进爵会稽郡长公主,秩同郡王,食汤沐邑二千户,给鼓吹一部,加班剑二十人。帝每出,与朝臣常共陪辇。主以吏部郎褚渊貌美,就帝请以自侍,帝许之。渊侍主十日,备见逼迫,誓死不回,遂得免。 帝所幸阉人华愿儿,官至散骑常侍,加将军带郡。 帝少好读书,颇识…
❤1
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
好玩吗华立
Photo, posted without a caption
Showing the 12 most recent of 19 posts we hold for @weblogue. 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.
Citation-graph rank
Citation-graph rank — 1,092,518 of 1,189,255entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“随感、杂考、未来ダヨー” (@weblogue), 114 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/weblogue.
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.