【建议收藏】一次搞懂所有 NAT 类型,实战各NAT类型之间的打洞可行性,通过p2p vpn实现无公网ip穿透家庭内网,p2p直连打洞,游戏联机,BT下载 https://youtu.be/T8Fx9b8z5w0

Channel
不良林
@buliang00
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
29,394subscribers
-309 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001166415755 |
|---|---|
| Type | Channel |
| Username | @buliang00 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/buliang00 |
Topic
Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 00:55 | 29,394 | -26 |
| 4 Oct 2026, 16:00 | 29,420 | -42 |
| 26 Sept 2026, 12:42 | 29,462 | -43 |
| 19 Sept 2026, 15:40 | 29,505 | -12 |
| 17 Sept 2026, 04:15 | 29,517 | +18 |
| 15 Sept 2026, 03:18 | 29,499 | -6 |
| 13 Sept 2026, 14:01 | 29,505 | -11 |
| 11 Sept 2026, 17:18 | 29,516 | -4 |
| 9 Sept 2026, 04:39 | 29,520 | -13 |
| 5 Sept 2026, 21:37 | 29,533 | -4 |
| 3 Sept 2026, 16:42 | 29,537 | -11 |
| 2 Sept 2026, 07:33 | 29,548 | -24 |
| 1 Sept 2026, 05:05 | 29,572 | -2 |
| 31 Aug 2026, 05:52 | 29,574 | -2 |
| 30 Aug 2026, 05:06 | 29,576 | +14 |
| 29 Aug 2026, 07:27 | 29,562 | -2 |
| 27 Aug 2026, 00:43 | 29,564 | -5 |
| 26 Aug 2026, 03:53 | 29,569 | -13 |
| 23 Aug 2026, 19:09 | 29,582 | -13 |
| 22 Aug 2026, 03:57 | 29,595 | first reading |
Engagement
18 posts held, back to 27 September 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 96 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 18 posts for this entry, the most recent from 13 December 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
【全网最细】无公网IP实现异地远程访问家里内网设备,通过stun打洞穿透运营商NAT,实现P2P直连满速下载,无需花钱搭建内网穿透,打洞通信流程分析,stun、fullcone、nat1、CGNAT https://www.youtube.com/watch?v=T5S5O2D1hqg
【跨境电商】详谈各种风控因素,刷机竟然毫无作用?实战演示TikTok注册运营全过程分享,硬件设备选择、网络环境伪装、住宅IP和机房IP的区别、视频质量对自然推流的影响,跨境电商社交媒体运营风控预防指南 https://youtu.be/tBdCWw7vk1Y
【零基础】2025最新保姆级纯小白节点搭建教程,人人都能学会,目前最简单、最安全、最稳定的专属节点搭建方法,手把手自建节点搭建教学,晚高峰高速稳定,4K秒开的科学上网线路体验 https://youtu.be/MgtOAVOXBWo
【全网首发】搭建最强伪装“AnyReality”节点,各代理协议抓包分析,实现任意协议搭配任意传输,ss+ws、ss+grpc+reality、无tls裸奔的trojan https://youtu.be/wK7pR0Sbtdo
【极致隐私】给你的节点加上暗网功能,被误解的tor网络,完全免费的三重"链式代理",普通浏览器上暗网,前置代理+tor+后置代理的配置方法|黑暗网络|tor网络|洋葱路由 https://youtu.be/lOLJ70bc-pA
【黑暗网络】最详细进入暗网方法大全,互联网中的罪恶都市,什么是暗网?暗网有多恐怖?Tor网络和黑暗网站的区别|dark web windows/mac/linux/ios/android进入洋葱网络(老番,之前的做了个18禁的恶搞暗网网页被youtube删了,再也不跟他玩梗了,一点幽默感都没有) https://youtu.be/24JK_b-2V4A
【别抽了我快干了】谨防加密货币挖矿偷算力,机场节点算力劫持实战演示,矿池中转抽水怎么办?不要再给别人打工了 | 加密货币安全科普 https://youtu.be/5Uq8uNVy0DE
建议重温经典:https://youtu.be/4AnapDDMlyI Clash Verge客户端1-Click RCE漏洞
【代理新姿势】科学上网最新AnyTLS协议快速上手,收集了两年的各代理协议反馈分享,reality依旧稳如老狗!mihomo搭建anytls节点教程 https://youtu.be/yUJ--0eUs_o
【全网最细】各种挖矿方式原理详解,solo独立挖矿、pool矿池挖矿、solo矿池挖矿,还有普通用户也能参与的零成本乐透彩票挖矿,中了直接成为百万富翁改写人生|加密货币新手科普 https://youtu.be/a41DMDfJjsU
【加密货币】零基础初识比特币,实战演示比特币挖矿,新手小白也能看懂的比特币网络运行流程 https://youtu.be/5hgdekVZb3A
Showing the 12 most recent of 18 posts we hold for @buliang00. 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.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“不良林” (@buliang00), 29,394 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/buliang00.
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.