连日本人都整😅
🤣14😁4🤡3

Channel
@wearemjj
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
9,732subscribers
+236 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001277013847 |
|---|---|
| Type | Channel |
| Username | @wearemjj |
| Description | 寸草不生 https://t.me/boost/wearemjj |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/wearemjj |
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @solidot/304777 Aug 2026, 16:05 UTC | @wearemjj/18849 · this entry10 Aug 2026, 07:35 UTC | 1.00 | 3 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @solidot | 7 (7/7 hand-verifiable sample passed) | 1.00 | 8.8 hours | @solidot (7–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 35 comparable posts for this entry, running 4 August 2026 to 15 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @solidot. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 16 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 11:16 | 9,732 | -3 |
| 11 Nov 2026, 01:20 | 9,735 | +2 |
| 7 Nov 2026, 20:28 | 9,733 | +2 |
| 4 Nov 2026, 19:48 | 9,731 | -3 |
| 2 Nov 2026, 03:57 | 9,734 | -3 |
| 30 Oct 2026, 10:28 | 9,737 | +16 |
| 27 Oct 2026, 16:31 | 9,721 | -3 |
| 24 Oct 2026, 18:26 | 9,724 | -8 |
| 21 Oct 2026, 23:19 | 9,732 | +28 |
| 18 Oct 2026, 10:41 | 9,704 | +26 |
| 15 Oct 2026, 06:10 | 9,678 | +20 |
| 12 Oct 2026, 13:00 | 9,658 | +54 |
| 5 Oct 2026, 09:17 | 9,604 | +17 |
| 26 Sept 2026, 22:16 | 9,587 | +23 |
| 17 Sept 2026, 21:21 | 9,564 | +12 |
| 13 Sept 2026, 18:22 | 9,552 | +1 |
| 9 Sept 2026, 18:36 | 9,551 | -7 |
| 4 Sept 2026, 15:56 | 9,558 | -6 |
| 1 Sept 2026, 12:25 | 9,564 | -2 |
| 29 Aug 2026, 20:17 | 9,566 | first reading |
236 posts held, back to 4 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 62 pages of 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. It is computed over the 55 of 75 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 236 (4 August 2026 – 16 November 2026) |
| Views total | 142,590 |
| Reactions total | 742 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 00:31 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.
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 45 videos 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.
2,212 reactions across 191 posts, in 49 distinct kinds. The most used accounts for 19.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 420 | 19.0% | |
| 😁 | 404 | 18.3% | |
| 🤣 | 301 | 13.6% | |
| 👾 | 128 | 5.79% | |
| 💅 | 110 | 4.97% | |
| 🌭 | 92 | 4.16% | |
| 👍 | 77 | 3.48% | |
| 😭 | 61 | 2.76% | |
| 🤮 | 51 | 2.31% | |
| ❤ | 47 | 2.12% | |
| 😱 | 45 | 2.03% | |
| 🍾 | 44 | 1.99% | |
| 🫡 | 42 | 1.90% | |
| 🥰 | 37 | 1.67% | |
| 🆒 | 32 | 1.45% | |
| 😍 | 29 | 1.31% | |
| 🤯 | 25 | 1.13% | |
| 👨💻 | 24 | 1.08% | |
| 👎 | 23 | 1.04% | |
| 🙏 | 21 | 0.949% | |
| 29 further kinds | 199 | 9.00% |
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 197 of the 236 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 2,212 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 236 most recent posts we hold, published 4 August 2026 to 16 November 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.
Telegram’s own ‘edited’ marker: 10 of 75 posts held from the last 30 days (13.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
连日本人都整😅
🤣14😁4🤡3
https://v2ex.com/t/1257459
https://www.nodeseek.com/post-1054597-1
🤮3😁3🌚2😈2
星舰创造历史,首次在发射塔接住星舰 SpaceX 完成了一项前所未有的壮举,在 Starship 航天器环绕地球近一整天后,在空中成功接住了这艘巨型飞船。 航天器在向其德克萨斯州发射场降落前,绕行地球完成了 14 圈,随后地面上方巨大的机械臂抓住了它。
👏9
开始低价收传家宝了,各位MJJ可以大刀阔斧砍价了😅
关于 LAX.EB 线路至中国电信方向网络波动及灵活保障方案 消息 · 2026-11-14 05:54 UTC 近期,我们监测到 LAX.EB 线路在通往中国电信方向时出现间歇性丢包与延迟波动。经网络工程团队排查,该问题的根源在于中国联通骨干网的上游互联拥塞及路由不稳定,且目前运营商方面对此类跨网波动并未提供任何 SLA 赔付保障。 由于故障节点位于中国联通与中国电信的跨网互联层面,直接修复已超出 DMIT 的网络管控边界。尽管如此,我们已将此问题升级至上游最高级别的技术支持,同时工程团队仍在持续监控链路指标并提供路由诊断数据。结合过往类似事件(如数年前 SJC AS4837 线路问题)的处理周期,本着对客户透明负责的原则,我们必须坦诚告知:目前无法给出保证的修复时间(ETA),具体恢复进度完全取决于中国联通方面。 从底层网络架构而言,中国联通 AS9929 属于标准纯 IP BGP 网络,且其美国本地 NOC 运维团队…
😱6🤡3❤2🌚1🤯1
瓦坎达forever🤣
🤡8💅1
鸡圈传来噩耗 https://www.nodeseek.com/post-1054341-1
🤡4🤣2
https://v2ex.com/t/1256928
⚡10😱2💅1
比考公难咯😅
🤡8🌭5🍌2
英伟达要开除黄仁勋,黄仁勋:我还是自己来吧
😁9
众所周知 A畜封了再开不用想太多 https://v2ex.com/t/1256766
Showing the 12 most recent of 236 posts we hold for @wearemjj. 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.
@wearemjj edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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.
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 13 seed channels' Telegram-generated recommendation lists 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“MJJ出征” (@wearemjj), 9,732 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/wearemjj.
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.