两年了,核酸和封控已经过去,可别忘了,属于我们的自由和尊严还远未到来。
👍1,850🫡756🕊137❤80😢56🤡46🙏31👎12

Channel
@gh_ilovexjp
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
16,846subscribers
-73 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001833318599 |
|---|---|
| Type | Channel |
| Username | @gh_ilovexjp |
| Description | 邮箱已停用 不要核酸要吃饭 不要封控要自由 不要谎言要尊严 不要文革要改革 不要领袖要选票 不做奴才做公民 |
| Created | Between 1 October 2022 and 7 November 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/gh_ilovexjp |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 15:25 | 16,846 | -12 |
| 16 Aug 2026, 08:57 | 16,858 | -8 |
| 14 Aug 2026, 22:48 | 16,866 | -7 |
| 13 Aug 2026, 16:38 | 16,873 | -4 |
| 12 Aug 2026, 15:06 | 16,877 | -16 |
| 11 Aug 2026, 11:52 | 16,893 | -6 |
| 10 Aug 2026, 12:38 | 16,899 | -5 |
| 9 Aug 2026, 15:11 | 16,904 | -7 |
| 8 Aug 2026, 11:47 | 16,911 | -8 |
| 7 Aug 2026, 21:15 | 16,919 | first reading |
20 posts held, back to 7 November 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pagesof 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 20 posts for this entry, the most recent from 12 October 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 18 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
32,736 reactions across 19 posts, in 41 distinct kinds. The most used accounts for 71.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 23,467 | 71.7% | |
| 🫡 | 1,731 | 5.29% | |
| ❤ | 1,135 | 3.47% | |
| 🎉 | 1,011 | 3.09% | |
| 🤬 | 996 | 3.04% | |
| 🙏 | 930 | 2.84% | |
| 😭 | 879 | 2.69% | |
| 👏 | 430 | 1.31% | |
| 🕊 | 297 | 0.907% | |
| 🥰 | 296 | 0.904% | |
| 💯 | 244 | 0.745% | |
| 😢 | 206 | 0.629% | |
| 🔥 | 171 | 0.522% | |
| 😁 | 118 | 0.36% | |
| 🍾 | 92 | 0.281% | |
| 👎 | 92 | 0.281% | |
| 🤡 | 61 | 0.186% | |
| 💩 | 59 | 0.18% | |
| ❤🔥 | 57 | 0.174% | |
| 🏆 | 54 | 0.165% | |
| 21 further kinds | 410 | 1.25% |
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 19 of the 20 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 32,736reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 7 November 2022 to 12 October 2024, 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,850🫡756🕊137❤80😢56🤡46🙏31👎12
勿忘历史
👍2,290🫡975🕊146😭122🙏74❤48💩48😢15
陕西一码通模拟 更新 - 新增核酸检测详情页面 天津数字防疫模拟 更新 - 更新页面样式 - 优化配置流程及页面 - 场所扫码会调起摄像头,并在3秒后自动跳转 苏康码模拟 更新 - 增加了一组核酸检测记录 其它更新 - 修改目录页随申码卡片样式 - 修正河北健康码模拟姓名隐藏问题 - 更新四川天府健康通模拟首页公告 网页演示 | 常见问题 | Reddit | Codeberg
👍2,880😭441👏110❤86🙏52🥰51🎉31💯31
- 不分化、不割席、不告密 - 齐上齐下、共同进退 - "Be water",能进能退、能聚能散 https://t.me/VoiceofCN/8345
👍2,060❤95🙏70🔥59👎39😁29😢24👏20
【匿名调查】你最希望下一个健康码模拟是?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
👍1,660🙏279❤69👏40🎉33🍾23🐳22💯22
河北健康码模拟 现在可用 随申码模拟 更新 - 重新制作了场所码界面 - 增加了扫描和播放音频功能(暂不支持识别二维码文字) 渝康码模拟 更新 - 修正了一些界面错误 湖南电子健康卡模拟 更新 - 适配湖南健康码最新样式 粤康码模拟 更新 - 修正了一些颜色和文字错误 - 增加了一组核酸检测结果 若有余力,请考虑一下 捐赠项目;捐赠将与每一位参与贡献的开发者分享,谢谢每一位热心人士的支持! 网页演示 | 常见问题 | Reddit | Codeberg
👍960❤67🎉34🙏25🥰16😁11👏9🔥9
⚠️ 项目没有任何“收费服务”,只接受 自愿捐赠。所有主动向你索要钱财的、或是收费提供本项目代码的都是骗子。 ⚠️ 我没有开设任何 Telegram 群组,也没有使用过个人 Telegram 账号进行发言;请多留意假冒账号,不要向任何人提供个人信息。
👍1,550❤123👌41👏28🥰20🎉18❤🔥16🙏15
渝康码模拟 现在可用 苏康码模拟 更新 - 添加了支付宝样式的导航栏 其它更新 - 修复了“四川天府健康通”模拟和“福建健康码”模拟的姓名显示问题 - 修复了“陕西一码通”模拟中可能未显示采样时间的问题 - 修复了“北京健康宝”模拟中有时无法播放声音的问题 网页演示*:Cloudflare 源代码:Codeberg Releases 疑问与反馈:Reddit 在发帖或写邮件之前,请先阅读 常见问题,谢谢! * Netlify 版本的网页演示随时可能因流量超限中断,请迁移至 Cloudflare
👍1,040🥰37❤34💯28👏23🎉13💋12😁12
陕西一码通模拟 现在可用 - 点击二维码可以切换至“场所码” - 点击核酸检测时间可以切换小时数 - 点击“已采样”可以切换今日是否采样 其它更新 - 修正穗康码场所码上二维码及姓名的显示 网页演示 Cloudflare: https://ilovexjp.pages.dev 请正在使用 Netlify 版本的朋友迁移到这里。如果无法访问,请检查代理设置及代理规则。 社区 试验性地建立了一个 Reddit 社区:r/ILoveHealthCode ,目前不打算进行管理。希望能代替原来的 GitHub Discussions。 项目源代码 延续之前的计划,项目的未压缩代码已在 Codeberg 公开。但如果你不需要编辑代码,请在 Release 中直接下载发行版本。 参与协作 如果你想参与到项目的开发工作中,请选用信任的邮件提供商发送邮件至 [email protected] ,并简要说明一下自…
👍1,720❤115🎉55🙏35🥰29👏19🍾14🐳12
早些时候,项目的 GitHub 账号 ilovexjp 整体遭到封锁,给出的理由是 “a violation of our Terms of Service”;且截至目前,官方暂未回应查询请求。更新及其代码将暂时在此频道发布;意见及反馈请发送邮件至 [email protected](每封都会看,但可能无法一一回复,还请谅解)。 另外,由于免费版流量限制,Netlify 版本的网页演示可能会在未来中断,如果你正在使用这一版本,请考虑切换至 Cloudflare 或自行部署。
🤬996😭298🙏223👍181🤯22❤19🤡13😢13
Channel name was changed to «ilovexjp»
参与项目协作 由于担心被封锁,项目的源码目前放在 GitHub 的私有仓库。若有兴趣参与项目的开发,请发送邮件至 [email protected],简单说明一下能力或目的就可以。请注意个人安全,选择可以信任的邮件服务提供商,也可使用 PGP Key (README 末尾)将内容进行加密后发送。 所有源码将于之后的每次更新时另外公开。
👍903🙏75❤34💯22🥰22🤯8👀7👎5
Showing the 12 most recent of 20 posts we hold for @gh_ilovexjp. 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 2 polls we hold for this entry, as Telegram rendered them 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.
【匿名调查】你最希望下一个健康码模拟是?
Shares as published. 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 20 most recent posts we hold, published 7 November 2022 to 12 October 2024. 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.
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.
@gh_ilovexjp named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“ilovexjp” (@gh_ilovexjp), 16,846 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/gh_ilovexjp.
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.