Channel
@polyhedron
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
2,426subscribers
+9 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001139763956 |
|---|---|
| Type | Channel |
| Username | @polyhedron |
| Created | 28 June 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/polyhedron |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 05:01 | 2,426 | -4 |
| 3 Sept 2026, 19:55 | 2,430 | +20 |
| 31 Aug 2026, 17:42 | 2,410 | -1 |
| 28 Aug 2026, 10:04 | 2,411 | -2 |
| 25 Aug 2026, 16:35 | 2,413 | -3 |
| 22 Aug 2026, 10:06 | 2,416 | -1 |
| 19 Aug 2026, 01:06 | 2,417 | -1 |
| 12 Aug 2026, 16:04 | 2,418 | +1 |
| 6 Aug 2026, 05:37 | 2,417 | no change |
| 6 Aug 2026, 03:58 | 2,417 | first reading |
12 posts held, back to 15 March 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 2 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 12 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
#藏文 #字體 #SansSerif 以往的藏文字體要麼是Himalaya之類的有頭體襯線字體，但接近宋體，和一般手機、ppt的無襯線字體環境不太搭；要麼是無頭體，非衞藏地區的或者初學者都不太好認，所以一直在找藏文有頭體（印刷體，dbu-can དབུ་ཅན་ 烏金體）的無襯線字體。今天終於發現了一個，是小米做的MiSans Tibetan字體。和Arial、黑體等字體從視覺上能夠很好融合！ 而且說是可以免費商用。 https://hyperos.mi.com/font/details/tibetan 如果有其它家的藏文有頭黑體也歡迎推薦！
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
2025年Nature非常厲害的文章，整個俄羅斯東歐到西伯利亞的森林南緣的中石器到青銅時代的古DNA。尤其是Seima-Turbino文化現象（認爲可能與烏拉爾語系相關）。
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
【藏語拉薩話聲調總結 ལྷ་སའི་སྐད་ཀྱི་སྒྲ་ཕྱེད།-哔哩哔哩】 https://b23.tv/0YKr2tL https://youtu.be/Hi6ZlH-7WKU
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
千字文中古漢語切韻音系（2026年重製版） https://www.bilibili.com/video/BV1UQTJ69EK8/ https://www.youtube.com/watch?v=VJh-cFsmQX0 千字文1500年前由梁朝周興嗣作，是最有名的小學蒙學讀本（三字經、百家姓、千字文）之一，1000個漢字整，四字一句，沒有重字（按現行簡化字有五六對字相同了）。這裏按當代構擬的南北朝當時的發音（切韻音系）來朗讀。 這次的朗讀與我2010年讀的版本在擬音上有一些區別，比如上聲的調值、見組非三等改爲小舌、3C類韻淡化介音、部分韻主元音的高度有所調整等，但中古漢語拼音保持不變。歡迎點讚、關注、投幣、發彈幕、評論、探討具體字音、擬音方案及讀音。
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
十幾年前的敎程繼續塡坑了：中古漢語語音敎程-20 臻攝 b站： https://www.bilibili.com/video/BV1ahL961EQ9/ 油管： https://www.youtube.com/watch?v=H5PG2e2mfJI 中古漢語語音敎程-21 止攝 https://www.bilibili.com/video/BV1Uyj86kEB2 https://www.youtube.com/watch?v=MB2kZF0CO08
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
#語言類型學 #翻譯 今天在一個語言學羣裏，有人說這個“圖書館是爲每個人服務的”很有翻譯腔的感覺。我就說，東亞感覺的說法就會說“圖書館誰都能用”。 然後想到這種【疑問詞（interrogative）+添加類小詞（additive particle）】來表示總括（universal）的說法在東亞非常常用，是標準表達方法，比如“什麼都不”表示“所有東西都不”，日語“だれも”表示“每個人”，即後面用一個表示“也”的小詞。 然後問了一下ChatGPT，這種情況是否普遍，回答說漢語、日語、朝鮮語（누구도）、蒙古語（ᠬᠡᠨ ᠴᠦ）、維吾爾語（كىممۇ）、藏語（ག་པར་ཡང་）、印地語（कहीं भी）、梵語（यत्रापि < yatra api）都有這種用法。 但英語就不能用 *Who also can see. 表示Everyone can see.。所以以後要翻譯"every..." "any..." 這種詞可以攷慮換一種表…
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
https://www.bilibili.com/video/BV1HtRsBkEba/
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
我的党項語网站更新，包括字體下載、安裝方法等。 https://www.ngiam.cn/tangut/index.html
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
党項語拼音和擬音方案發佈。 完整顯示及字表下載見我的個人网站： https://ngiam.cn/tangut/tangut_phone20260416.html
Signed 𗷲𗒅 Zsjit Ngiam@Pok-kieng
G8838: Pok-zjin, Paux-tex nom, Paux-tex, Hiang-gha, Dad-chjangx, Pok-kieng.
Signed 𗷲𗒅 Zsjit Ngiam@Hiang-krungx
張雪峰去世了，據說是早起跑步時猝死，被發現得晚了，沒搶救過來。纔41歲。 🕯🕯🕯
Signed 𗷲𗒅 Zsjit Ngiam@Hiang-krungx
Photo, posted without a caption
Signed 𗷲𗒅 Zsjit Ngiam@Hiang-krungx
Showing the 12 most recent of 12 posts we hold for @polyhedron. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“polyhedron” (@polyhedron), 2,426 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/polyhedron.
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.