✈️ 关于登录过程中 跳邮箱 / sms fee 问题 ,一些补充 我就用我这边出去的号在登录时候出现的情况单独作出一个讲解 🕜 1️⃣ 先从设备方面来看📱 鸿蒙系统和OPPO出现的几率是非常大的 基本上都会有 鸿蒙的话出现了就只能用带会员的号(除了会捣鼓可以安装第三方来登录) 鸿蒙之外的都可以正常安装第三方来登录(我们会给推荐的)这是最经济的方式💡 不额外花钱 ⚠️ 除此之外 有的人第一个手机登录出现了 用其他手机却可以正常登录 这个可以自行尝试 2️⃣ 然后是IP方面 🌎 大多数用户可能对这个不太懂 用的梯子都默认了香港的 ❗️香港ip非常容易出现smsfee 甚至换绑都无法正常换绑 ⚠️ 尝试切换其他ip登录时尽量重装软件再登录 不然结果都是一样的 3️⃣ 地区性 📍 除了上述两种因素外 有些地区是超高概率会有 甚至可以说100%会出现 比如+31、+852、+54……(当然…
Content that also appears on other registered channels
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 |
|---|---|---|---|
| @mianbaowu/1318 Sept 2026, 02:59 UTC | @mbpdgjx/32 · this entry18 Sept 2026, 12:16 UTC | 1.00 | 9.3 hours |
| @mianbaowu/1418 Sept 2026, 04:22 UTC | @mbpdgjx/33 · this entry18 Sept 2026, 12:16 UTC | 1.00 | 7.9 hours |
| @mianbaowu/1518 Sept 2026, 07:38 UTC | @mbpdgjx/34 · this entry18 Sept 2026, 12:16 UTC | 1.00 | 4.6 hours |
| @mianbaowu/2320 Sept 2026, 07:37 UTC | @mbpdgjx/44 · this entry20 Sept 2026, 07:38 UTC | 1.00 | under a minute |
| @mianbaowu/2421 Sept 2026, 11:52 UTC | @mbpdgjx/45 · this entry21 Sept 2026, 11:52 UTC | 1.00 | under a minute |
| @mianbaowu/2521 Sept 2026, 18:59 UTC | @mbpdgjx/46 · this entry21 Sept 2026, 18:59 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @mianbaowu | 11 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @mianbaowu (10–1) |
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. 10 of the 10 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 12 comparable posts for this entry, running 18 September 2026 to 23 September 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.
- Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
- 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
- shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
- Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @mianbaowu. That is a statement about our reading window, not a claim of authorship.
