哦丢雷楼谋
👍1
Signed 辰 风(直奔主题)

Channel
@Lyuelian
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
4,630subscribers
-455 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001867340059 |
|---|---|
| Type | Channel |
| Username | @Lyuelian |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/Lyuelian |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|---|
| @Lyuelian/10386 · this entry30 Apr 2026, 20:58 UTC | @chenfengya/238430 Apr 2026, 21:08 UTC | 1.00 | 10 minutes |
| @Lyuelian/10387 · this entry1 May 2026, 07:59 UTC | @chenfengya/23851 May 2026, 08:00 UTC | 1.00 | 72 seconds |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @chenfengya | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 16 April 2026 to 23 June 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 @Lyuelian — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 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 |
|---|---|---|
| 17 Nov 2026, 13:09 | 4,630 | -30 |
| 12 Nov 2026, 00:10 | 4,660 | -16 |
| 7 Nov 2026, 22:46 | 4,676 | -11 |
| 4 Nov 2026, 15:28 | 4,687 | -9 |
| 1 Nov 2026, 21:47 | 4,696 | -14 |
| 29 Oct 2026, 14:37 | 4,710 | -14 |
| 26 Oct 2026, 06:15 | 4,724 | -14 |
| 23 Oct 2026, 02:20 | 4,738 | -9 |
| 20 Oct 2026, 04:48 | 4,747 | -15 |
| 17 Oct 2026, 09:40 | 4,762 | -21 |
| 14 Oct 2026, 07:06 | 4,783 | -11 |
| 10 Oct 2026, 17:37 | 4,794 | -29 |
| 4 Oct 2026, 17:40 | 4,823 | -52 |
| 25 Sept 2026, 03:56 | 4,875 | -34 |
| 17 Sept 2026, 01:20 | 4,909 | -6 |
| 13 Sept 2026, 11:16 | 4,915 | -21 |
| 9 Sept 2026, 15:58 | 4,936 | -23 |
| 4 Sept 2026, 06:15 | 4,959 | -14 |
| 1 Sept 2026, 00:08 | 4,973 | -20 |
| 28 Aug 2026, 13:16 | 4,993 | first reading |
21 posts held, back to 25 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 4 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 21 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
36 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 63.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 63.9% | |
| 🤡 | 8 | 22.2% | |
| 👍 | 2 | 5.56% | |
| 🤔 | 2 | 5.56% | |
| 🍌 | 1 | 2.78% |
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 15 of the 21 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 25 March 2026 to 12 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.
哦丢雷楼谋
👍1
Signed 辰 风(直奔主题)
新号好玩,航天黑屋
🤡1
Signed 辰 风(直奔主题)
小米pad6pro12+256 1150rmb出 急出,我要买刀皮号 要的私信我 @chenfengya13 我咸鱼让这傻子官方限制了
🤔2❤1
Signed 辰 风(直奔主题)
瞧一瞧看一看
🤡7👍1
Signed 辰 风(直奔主题)
EncryptBlitz 加密引擎 · 公测进度同步 当前定位: EncryptBlitz 正在建设面向 ARM64 Native 场景的高强度加密与函数级保护基础设施,覆盖 ELF / SO / SO-JNI 等目标形态。核心加密链路、Web/API/CLI 工作流和样本验证体系已完成多轮压测,目前进入兼容性攻坚阶段。 当前重点: 函数级虚拟化 VMP、VMP 强化、手选函数、运行时验证等能力正在持续优化。不同项目的编译器、函数结构、符号信息、入口形态差异很大,个别样本出现无法虚拟化、降级、任务异常或运行不一致,都属于我们当前重点收敛的问题。 遇到任何异常,请直接在群内反馈或私信管理。每一个真实 case 都会进入兼容性修复队列,是我们提升正式版质量的关键输入。 关于收费节奏: 安全产品零容忍。当前加密能力已经进入可公开测试阶段,但在兼容性体验和交付稳定性达到正式商业化标准前,我们会继续免费开放试用。我们宁愿晚一步收费…
❤6
EncryptBlitz 现已面向全网开放体验 访问地址: https://jm.byxly.vip/ EncryptBlitz 是面向 Native ARM64 目标的在线加固平台,支持 ELF、SO、SO-JNI 上传分析与保护配置。平台提供函数级选择、函数加密、函数混淆、函数 VMP、VMP 强化、Custom 自定义策略、任务进度、中文报告与加固产物下载,适合 SDK、游戏逻辑、授权校验、核心算法、风控模块等 Native 资产的上线前加固与交付测试。 本次开放免费体验卡密,每张卡额度 100 点。卡密无 IP 绑定,可自由登录使用;额度用完后仍可参与后续福利活动,更多免费额度、测试名额和优惠权益会陆续开放。 相比传统加固厂商,EncryptBlitz 更偏向“可控、透明、函数级”的 Native 保护体验: - 不只整包黑盒处理,支持函数级精确选择 - 不强制推荐策略,保护层由用户自行配置 - 不只给产物,也提…
❤2
想要免费提前体验满血版EncryptBlitz(免费防御全开,有函数级VMP等超强加密)加密 可联系企鹅:2987303932 目前支持:APK 安装包,AAB 应用包,APKS 分包集,ELF 可执行文件,SO / 普通共享库,SO-JNI / JNI 动态库,Shell 脚本,Script 脚本,EXE / Android ARM64 可执行文件
开源一下三角洲的过内存检测的一个思路 里面自带4个功能,露娜,无后,据点,范围 不100%保证稳定性 思路:“sub_4DEC14 负责维护一个全局 Patch 跳过池 qword_568F90`。该池采用 32 槽位的环形缓冲结构,每条记录占 24 字节,数据结构为 {uint64_t 绝对地址, uint32_t 长度, uint32_t 保留位(0), uint64_t 堆副本指针}`。 扫描链入口 `sub_4E0834` 首先调用 sub_4DED68 遍历此池,执行纯区间交集判定(`rec.start < scan_end && rec.start + rec.size > scan_start`)。若命中,则将匹配记录逐条拷贝至临时输出向量,输出指针每命中一条即推进 0x18 字节。需注意,`sub_4DED68` 固定返回 0,实际的命中信号完全通过输出指针的偏移量来传递。 控制流回到 sub_4E0834 后,…
EncryptBlitz加密项目预告 自研DEX、Native VMP及白盒密钥体系,解密难度对标Virbox、爱加密、360加固等头部企业,后续持续迭代优化。 项目开发周期近1个月,核心开发4-5人,协作支持团队共4-20人,累计代码量达100万行。新版本将重点优化兼容性、强化主动攻击防御能力以及新增自研DEX、Native VMP及白盒密钥体系,1-2周内上线网页端,主打极致高性价比实用加密,不做冗余虚标。
❤1
EncryptBlitz AI —— Android ARM64 商业级加固平台 一次接入,保护四种目标 APK / ELF / SO动态库 / Shell脚本 免费试用 7天全功能测试版,到期自动失效,无需付费即可验证效果 付费模式 一键开启 Max(VM High、完整反调试、防Hook、防Dump、运行时自防御) 安全设计 - 本地引擎执行,不上传客户代码 - Web后端管理额度与任务,不内置联网卡密 - 输出文件自带合规提示与到期检测 👉 立即使用:https://jm.byxly.vip/
EncryptBlitz AI 是一套面向商业交付的多目标加密保护平台,专注 APK、ELF、SO/JNI 与 Shell 四类核心目标的一站式加固。系统采用 CLI/Web-only 架构,网页端负责用户、额度、任务、上传下载与发布审计,服务端私有调用加固引擎完成保护流程。支持免费 7 天测试版与付费 Max / VM High / 深度 RASP 模式,覆盖 anti-debug、anti-hook、anti-dump、anti-tamper、完整性校验、运行时自保护、功能开关、报告输出与 release gate 验证,帮助开发者在发布前完成更可靠、更可解释的安全加固。 使用链接:https://jm.byxly.vip/
C/C++ LLVM混淆加固 适配 Android NDK、PC Clang 双版本 全量成熟功能: 字符串加密、间接调用混淆、间接跳转混淆、基本块切割、Switch降级、控制流平坦化、VM扁平化控制流、MBA算术混淆、虚假控制流、函数包装、常参特化克隆、别名访问混淆、AMA延时偏移加载、PAO参数结构化、函数分片 纯C/C++专属,强效防逆向,支持商用授权 购买联系QQ:2987303932
❤2
Showing the 12 most recent of 21 posts we hold for @Lyuelian. 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.
We recorded 2 posts on @Lyuelian as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“蓝月亮通知频道” (@Lyuelian), 4,630 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/Lyuelian.
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.