— знаешь, как хаято расчёску называют? — и как же? — кусера — кусера? — точняк — а как мелководье? — писи
❤18⚡5😁3🐳1😭1

Channel
@japonicposting
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
462subscribers
+3 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002344889183 |
|---|---|
| Type | Channel |
| Username | @japonicposting |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/japonicposting |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 14:14 | 462 | +3 |
| 8 Aug 2026, 16:01 | 459 | first reading |
18 posts held, back to 26 February 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 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 18 (26 February 2026 – 6 August 2026) |
| Views total | 495 |
| Reactions total | 52 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 16:01 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.
446 reactions across 18 posts, in 19 distinct kinds. The most used accounts for 40.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 181 | 40.6% | |
| 😭 | 75 | 16.8% | |
| 🐳 | 38 | 8.52% | |
| 🔥 | 26 | 5.83% | |
| 🙏 | 18 | 4.04% | |
| 🤯 | 17 | 3.81% | |
| ❤🔥 | 16 | 3.59% | |
| 👍 | 12 | 2.69% | |
| 💘 | 12 | 2.69% | |
| 🥰 | 10 | 2.24% | |
| 👾 | 8 | 1.79% | |
| 💋 | 7 | 1.57% | |
| 🌭 | 6 | 1.35% | |
| 🍓 | 6 | 1.35% | |
| ⚡ | 5 | 1.12% | |
| 😁 | 3 | 0.673% | |
| 😎 | 3 | 0.673% | |
| 🤔 | 2 | 0.448% | |
| 🤝 | 1 | 0.224% |
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 18 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 446reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 26 February 2026 to 6 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.
— знаешь, как хаято расчёску называют? — и как же? — кусера — кусера? — точняк — а как мелководье? — писи
❤18⚡5😁3🐳1😭1
продолжаем(?) разрушать образ монолитной моноэтнической моноязычной японии и вспоминаем про древний народ Хаято. и их древний язык. от которого до нас дошло ажно целых два слова. жили они в провинциях Сацума и Осуми на юге Кюсю в период Нара. собственно в сохранившихся фрагментах Осумикуни Фудоки ("Описание обычаев земли Осуми" 大隅国風土記) есть, помимо прочего, слова из их языка. с первым сразу беды — оно записано лого…
❤16💘7👾1
рандомные невнятные заметки: вариативность naderu~nazeru 'гладить, ласкать' (撫でる・撫ぜる) существует потому, что выравнивание основ при коллапсе нидан-глаголов ("двухосновных" (хотя мне нравится западный анализ с беглым гласным)) в этом случае пошло двумя путями. вариант с -d- это ожидаемый рефлекс среднеяп. nade- (аттрибутивная форма naduru). nazeru получилось благодаря фонетическому слиянию фонем /d/ и /z/ перед гласны…
❤16🍓5👍1
японцы были настолько готовы к переходу на латиницу, что... а, в общем, читайте сами: “Rōmaji” no Rakugaki. Nakayama tarō. Rōmaji no Ojisan:— Rōmaji ga okonawaruru koto ni naruto, bokura no kaku Iroha-tengu ya Henoheno-Mohei ga nakunaru. Sorede bokuwa okawari ni Abc-tengu to Memebō to wo koshiraeta, naka-naka umaku dekita deshō. ーーーーーーーーーー «Ромадзи»-граффити Накаяма Таро. Дядя Ромадзи: — Когда ромадзи войдёт в оби…
🐳18🤔2🌭1👾1
до полноценного перехода на годзюон в качестве эдакого алфавитного порядка в японии использовалась и сосуществовала с ним "ироха-ута" — стихотворение-панграмма, в которой каждый знак хираганы употребляется ровно один раз. гораздо реже говорят о другой панграмме — амэцути-но ута (天地の歌) 'песня земли и неба', пожалуй, гораздо менее поэтичной в сравнении с "ирохой", но не менее интересной. Минамото-но Ситаго (源順) написа…
❤12💘5🐳2
[2/2] первое — считать /z/ первично именно аффрикатой, а не фрикативом. это не я придумал это и поливанов и арисака и вообще очень много кто много раз такое сказал. главное преимущество такого решения — оглушение dz > ts становится тривиальным, магия с [±cont] не нужна. второе — отказаться от синхронной дебуккализации /p/ нахрен она создаёт больше проблем чем решает и неспособна описать некоторые слова третье — оп…
😭13😎3❤1🌭1
[1/2] рассказать что-ли вам про курсач свой, раз уж решил, что не буду его дописывать до полноценной статьи. в диалекте Мицукайдо (преф. Ибараки) наблюдаются забавные поверхностные чередования: s~ts и ɸ~p. на поверхности выглядит как фортиция, но на примерах можно показать, что всё сложнее: есть слова suki 'нравится' и futon 'футон', и компаунды с этими корнями: [sewatsɯ̥ki] 'заботливый человек' и [dzapɯ̥toɴ] 'подуш…
😭13🌭1
— ЭТО НЕ БУКВА РИ ЭТО БУКВА РО — ЧТО ЭТО ЗА СЛОВО — ЭТО СЛОВО ETORO — НЕТУ В ЯПОНСКОМ ЯЗЫКЕ ТАКОГО СЛОВА — А КТО ТЕБЕ СКАЗАЛ ЧТО ЭТО СЛОВО НА ЯПОНСКОМ ЯЗЫКЕ #щитпост
😭27❤🔥6
признавайтесь (год назад был точно такой же опрос, подписчиков с тех пор стало вчетверо больше. интересно посмотреть актуальную статистику)
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
🥰3
(ой я даже не заметил что вас теперь четыреста людей всем большое спасибо! в последний раз как я обещал "вернуться в скором времени" я пропал на ещё более долгий срок. а сейчас ещё и учебный год скоро начнёт заканчиваться так что вообще ничего не обещаю. но я всё равно всем вам очень рад! всех люблю!)
🔥26👾1
я НЕ УМЕР я УМИРАЮ но я ЖИВОЙ и я принёс вам ПРИКОЛ , найденный в процессе поиска примеров для курсовой. в словаре 1903 года ибараки хогэн сюран (茨城方言集覧) есть НАИЗАМЕЧТАЛЬНЕЙШЕЕ слово: ehhittare 'обоссаться на месте' えっひったれ 居ナガラ尿ニ浸ルコト нихон кокуго дайдзитэн даёт это слово как диалектный вариант ibitare. соответствие начального i в Токио начальному e в Ибараки — это нормально, похожие переходы есть в соседних диале…
❤18🐳11😭7🌭2👾1
коллеги, если у вас есть умение, время и желание, вы можете помочь людям с оцифровкой материалов по айнскому на minna de honkoku. задача в том, чтобы затранскрибировать страницы в электронный текст там, где не справляется автоматический OCR https://app.honkoku.org/projects/ainu/info https://x.com/i/status/2044398290553459131 (если что, я к этому проекту отношения не имею (и не могу нынче позволить себе им заняться …
🙏8❤5🐳2❤🔥1💋1
Showing the 12 most recent of 18 posts we hold for @japonicposting. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
признавайтесь (год назад был точно такой же опрос, подписчиков с тех пор стало вчетверо больше. интересно посмотреть актуальную статистику)
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 18 most recent posts we hold, published 26 February 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 440,442 of 1,481,217entries 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.
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.
Named by 1 registered channel — 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“*tunpaki” (@japonicposting), 462 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/japonicposting.
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.