Telegram RegisterThe public register of Telegram

Channel

privacy.noarch

@privacy_noarch

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

212subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001293568571
TypeChannel
Username@privacy_noarch
Description你的监控自我保护指南。 电子书: privacy.n0ar.ch 讨论群跳转: privacy.n0ar.ch/chat (目前无法工作,请 pm @noarchwastaken) GitHub: github.com/noarchwastaken/privacy 目前是稳定的月更频道,绝不会辜负你的 UNMUTE!
CreatedBetween 1 March 2018 and 11 February 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/privacy_noarch

Growth

2126 Aug 2026, 22:51 — 212 subscribers7 Aug 2026, 03:33 — 212 subscribers6 Aug 2026, 22:517 Aug 2026, 03:33
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 211–213 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 03:33212no change
6 Aug 2026, 22:51212first reading

Engagement

20 posts held, back to 11 February 2021the 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.

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 29 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
14
Videos
1
Links
46

Lifetime counters from Telegram’s own channel header, read 7 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.

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.0%

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 3 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 3reactions 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 11 February 2021 to 29 March 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.

Recent posts

29 Mar 2026, 07:26 UTCviews —

The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

21 Jun 2025, 21:10 UTCviews —

The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

3 Feb 2023, 20:34 UTC920 viewsread 7 August 2026
Forwarded from @ZGQincLiqun

重磅:MIUI13 EU版(官改欧洲版)也存在国家反诈中心组件 也会向小米服务器传输应用列表 https://www.coolapk1s.com/feed/42719865 环境:ROM:MIUI13.0.6 EU版 MIUI安全组件版本:1.3.8 包名:com.miui.guardprovider 网页存档:WebArchive APK存档:Onedrive MIUI14再次被石锤 https://www.coolapk1s.com/feed/42944139 网页存档:WebArchive 解决方案 用于屏蔽MIUI的国家反诈中心组件的模块: https://github.com/MinaMichita/AntiAntiDefraud/ ADB shell: https://t.me/MeAndMyPY/9901 DNS/host屏蔽域名: https://t.me/DNSP

Signed .noarch | Check them out!

26 Jun 2022, 18:26 UTC≈1,030 viewsread 7 August 2026

https://privacy.n0ar.ch/Extras/flowers-p2/ 下篇来了!其实 noarch 三天前就已经把初稿发到群里了,但我按照群友的建议做出了不少修改,昨天早上才推到了 master 分支。 noarch 在下篇里填完了之前开的坑:用 Textractor 翻译生肉。这篇文章里还会讲到机翻生肉以及 Wine 上运行 Textractor 的一些问题和 workaround。 虽然 FLOWERS 冬篇官方中文版即将发布,但希望本文给你以后玩生肉提供一定帮助。

Signed .noarch | argv[1]

26 May 2022, 15:47 UTC≈1,030 views1 reactionsread 7 August 2026

https://privacy.n0ar.ch/Extras/flowers-p1/ 爷爷,你关注的频道主更新了! 这次的主题是 Wine + galgame,因为种种原因(文章最后有写)分成两次发布,敬请期待。 除了一波 Void Linux 硬广(诶?)之外,可能很多 GNU/Linux 用户都能从里面学到新东西(反正 noarch 打开了新世界的大门),因为我猜很多人如果要玩 Windows 游戏都用预先配置好的 Proton,而不是尝试自己用 Wine 从零开始。

👍1

Signed .noarch | argv[1]

26 Apr 2022, 10:50 UTC937 viewsread 7 August 2026

noarch 昨天突然想起来有个 Zowie 的鼠标刷新率测试,去年某个时候被撤下来了;因为它在过去五年内基本上是玩家测试游戏鼠标的必备工具,搜索引擎能看到一堆人尝试搜这个但找不到。 遂尝试复活它,改了一下 Wayback Machine 的存档,移除了 Google Fonts 和 Wayback Machine analytics。 https://n0ar.ch/mouse-rate-checker 这个单文件的 html 也可以拉下来离线运行。

Signed .noarch | argv[1]

11 Apr 2021, 23:57 UTC≈2,470 viewsread 7 August 2026
Sticker

Sticker, posted without a caption

Signed .noarch | TRAPit!

6 Apr 2021, 06:06 UTCviews —

privacy.noarch pinned «privacy.noarch 应该搬到 Cloudflare Pages 吗?现有的明网站点本来就经过 Cloudflare, 洋葱版会继续保留 privacy-pages.n0ar.ch»

6 Apr 2021, 06:06 UTC≈2,430 views1 reactionsread 7 August 2026

CF pages 的优势见 https://blog.cloudflare.com/cloudflare-pages/ 主要是为 noarch 节省服务器维护成本和时间,以及带来更快的页面加载速度 这样做未免会带来中心化问题,但目前的明网版本就走 Cloudflare, 且洋葱版会继续以对 noarch 更便利的形式保留(例如从目前的 VPS 转移到 noarch 家里的一个树莓派)

👍1

Signed .noarch | TRAPit!

6 Apr 2021, 06:03 UTC≈1,920 viewsread 7 August 2026
Poll

privacy.noarch 应该搬到 Cloudflare Pages 吗?现有的明网站点本来就经过 Cloudflare, 洋葱版会继续保留 privacy-pages.n0ar.ch

  1. 64%
  2. 不吼36%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Signed .noarch | TRAPit!

26 Feb 2021, 05:31 UTCviews —

privacy.noarch pinned «noarch 今天回来看前面几条消息,感觉自己简直因为急迫而语无伦次( 同时我也注意到了上次踢的有些人可能只是单纯潜水,因此想再发一条消息澄清一下。 首先,noarch 发布这些公告的原因是因为发现群内有几个帐号在其它群钓鱼,声称对应的群已被拉清单并终止活动,企图吓跑群员。 因此,为避免此类钓鱼发生在 privacy.noarch, 请在看到与重大变更相关的消息时验证它是否确实来自管理员: privacy.noarch 的管理员(也是创建者)目前只有 @noarchwastaken 一个,当你看到其它帐号发布重大变更消息…»

26 Feb 2021, 03:44 UTC≈3,280 viewsread 7 August 2026

Rust 绝赞学习中的 noarch 最近都干了些啥呢? https://github.com/noarchwastaken/vpn_killer 如果你在 Android 设备上翻墙,那么你可能需要怀疑下人生了... 因为任何网站都能通过浏览器一个多年未修复的 bug 将你的 VPN 杀死,同时发送请求然后获取你的真实 IP. 开启 kill switch 保平安...

Signed .noarch ::<Vec<_>>() -> &'static str {}

Showing the 12 most recent of 20 posts we hold for @privacy_noarch. 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.

Polls

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.

6 Apr 2021, 06:03 UTCFinal Results39 voters

privacy.noarch 应该搬到 Cloudflare Pages 吗?现有的明网站点本来就经过 Cloudflare, 洋葱版会继续保留 privacy-pages.n0ar.ch

  1. 64%
  2. 不吼36%

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 11 February 2021 to 29 March 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.

Forward network

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.

Mentions

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.

Cite this entry

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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“privacy.noarch” (@privacy_noarch), 212 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/privacy_noarch.

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.