File, posted without a caption
❤3

Channel
@very_complicated
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
40subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002215305809 |
|---|---|
| Type | Channel |
| Username | @very_complicated |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/very_complicated |
Technology — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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, 15:14 | 40 | +2 |
| 15 Aug 2026, 01:36 | 38 | +1 |
| 10 Aug 2026, 21:32 | 37 | no change |
| 7 Aug 2026, 13:44 | 37 | first reading |
19 posts held, back to 2 October 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 4 July 2026. An engagement rate over an empty window would be a number about nothing.
43 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 58.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25 | 58.1% | |
| 🤣 | 7 | 16.3% | |
| 😭 | 3 | 6.98% | |
| 😱 | 3 | 6.98% | |
| 🔥 | 2 | 4.65% | |
| 🥰 | 2 | 4.65% | |
| 👍 | 1 | 2.33% |
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 18 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 43 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 2 October 2025 to 4 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.
File, posted without a caption
❤3
今天有空改了一下我的博客模板,其实也就只是改了点样式,不过嘛倒是让我想起很多很头疼的地方 HTML 里有一个 code 标签,它默认的样式有: display: inline (行内元素) line-break: auto (自动换行) 我给它加上了: display: inline-block (行内块级元素,需要换行时拓展成多行显示) line-break: strict (严格换行,实际上与上方差别不大) 虽然这样它比较能看了,但如果我往这个元素里放的是一个长链接,这个元素就没法换行,然后顶穿它的各个父元素,让屏幕右侧留出一大块空白区域(图 1) 而在 Apple 系的 Safari 浏览器中效果稍微好了那么一点点,因为 Safari 会把链接的斜杠 / 认为是可以换行的符号,若链接实在过长,依然会跟上面一样(图 2)
❤3
最新发现: 在部分 Telegram 客户端中,打开来自 Telegram 的大部分第一方网页,在客户端拉起浏览器的同时,会自动在链接后方附加登录密钥,等到网页加载完成,你会发现自己已经无感登录了 目前在 iOS 和 Windows 客户端中尝试过都能成功,下面是几个可以无感登陆的第一方 Telegram 网页: https://bugs.telegram.org/ https://translations.telegram.org/ 其实 Telegram 网页版也可以,但是真的一点进去就直接登陆了,所以我就没贴上链接 而且以这个方式登录网页版的话,会直接跳过设定的两步验证,方便是方便了,但感觉有点不是很安全
😱3❤1
File, posted without a caption
👍1
在几天前把我的 Pixelbook Go 挂上闲鱼,因为机器有点硬件问题加上成色伊拉克,只挂了行情价的一半(还是最近才知道闲鱼搜索页有行情这个页面,能看最近成交记录很方便估价) 在详情里写明了各种硬件问题和软件 bug(因为我刷了 Windows),不到半天就有位买家找上了,下单很爽快,同时要求我刷回原系统再给他发过去,原系统很难用,但买家还是觉得 Windows bug 多用不来,经过劝阻之后卖家表示没问题 今天起床后发现买家在将近凌晨五点的时候给我发了消息问如何刷 Windows 大家一定不要买 Chromebook...
🤣7
Vacation - FRENSHIP
🔥2
Sticker, posted without a caption
❤2
Channel photo updated
今日在公开群组中分享了一个关于本聊天软件使用限制的链接和截图,转了好久发不出去,取消后再次尝试发送,发现本人喜提五天账号限制,望周知 也不排除是在其他地方发的内容被举报了,正好在这个时间点通过审核被限制 原因找到了,被 Aggressive Anti-Spam 送走了 虽然朋友和那个群组的管理员都很好心的帮了我,但还是得等五天 感谢两位 🥰
❤2
因为这个,昨天晚上做鱼汤的时候,因为锅过热了,刚把鱼放进锅里煎的时候表面就快接近糊了,导致判断失误直接加了水 结果从鱼汤变成水煮鱼了
🥰2
最近家里换了一个新的煤气灶,因为旧的煤气灶已经是房子刚建起来的时候连着厨房一起装的,到现在估计也有快十年了 期间也换过其中的各种零件来修,直到最近我爸看它有点大问题,又打算修修看,然后就装不好了... 找到店铺问了问,人家说:“你这个煤气灶基本上哪个零件都坏了个遍,又用了那么久,不如直接换一个新的” 于是我照着台面的尺寸量了量,在网上下单了一个同品牌的,但由于这种东西基本上只会有新装修和我们家这种煤气灶坏了的人才会买,最后花了五天才送到,期间只能用单边灶台做菜 安装还算方便,因为嵌入式的灶台也只是放在原来的孔位,靠台面支撑就行了 与原来那个煤气灶相比感觉有改进也有退步?原本需要装两个一号电池,新的只需要装一个 但似乎打火感应没有那么灵敏,打着火后点火器还是会继续工作几秒,感觉电池会没那么耐用 熄火自动断气的灵敏度也不如旧的煤气灶,新的这个熄火后需要大概十秒才会关闭电磁阀停止漏气,而旧的只需要一两秒 但火力相比旧的明…
❤1
前一台 Xbox 在使用中会出现偶尔几秒没有声音的问题,还以为是机子散热不好或者其他问题,在卖掉的时候明确描述出来还主动降了点价 前不久买了一台新款的 Xbox,偶尔还会有这个问题,开始怀疑是不是 HDMI 线问题 最近问题愈发频繁,点开电视自检,原来是电视出问题了
❤2
Showing the 12 most recent of 19 posts we hold for @very_complicated. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
“奇奇怪怪” (@very_complicated), 40 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/very_complicated.
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.