Telegram RegisterThe public register of Telegram

Channel

Pseudorandom Thoughts

@prdm_thoughts

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

687subscribers

+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-1001351521225
TypeChannel
Username@prdm_thoughts
Description我将开口,同时爽到爆。
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held2
On Telegramt.me/prdm_thoughts

Growth

6876 Aug 2026, 03:50 — 687 subscribers6 Aug 2026, 16:38 — 687 subscribers6 Aug 2026, 03:506 Aug 2026, 16:38
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 686–688 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 16:38687no change
6 Aug 2026, 03:50687first reading

Engagement

20 posts held, back to 28 May 2026the 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.

ERR · 30 days
294.5%
avg views ÷ 687 subscribers
Avg views / post
2,020
5 posts measured
Reaction rate
0.457%
reactions ÷ views · ER floor
Posts in window
5
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held20 (28 May 20264 August 2026)
Views total10,116
Reactions total40
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 16:38 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
104
Videos
1
Links
370

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

123 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 52.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉6452.0%
💊5948.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 10 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 123reactions 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 28 May 2026 to 4 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.

Recent posts

4 Aug 2026, 09:48 UTC188 views6 reactionsread 6 August 2026
Forwarded from @usr_bin_cat

RTOS 要点:叮咚鸡(指等中断),大狗叫(看门狗),一段一段待一段(指优先级调度)

🎉6

29 Jul 2026, 11:54 UTC≈3,700 views19 reactionsread 6 August 2026

书接上文。AI对公安和Staatssicherheit工作真正的影响是什么呢。 AI真正的大问题之一,它是回音壁(echo chamber),哪怕你通过提示词让AI跟你展开精神分析和自我批评,按目前训练的风格他就是会align到人类,会刻意去迎合你的,而显然,越垃圾的AI,它就越迎合你。遑论更多使用AI(豆包)的人根本意识不到这一点,他觉得这是个助手,可能有点像给领导开车的司机或者大秘的角色,搁那聊,给自己聊进去了。对于ego稍微大点的人(尤其是各类领导),这种激化放大个人意见巩固自信的效应会更加增强。 那对于本身精神状态就异乎常人的用户,比如本来就玉玉的小孩,比如反人类人格有杀心的用户,AI的道德围栏的优先级是远小于遵从用户的优先级的,最后确实可能导致异常情况会被放大。 再比如在国内企业从事AI safety工作的读者应该知道,今年有司也重点排查了情感陪伴类的AI,懂的都懂。并不是说对AI产生情感陪伴依赖是错误的,但是我们整个

🎉17💊2

29 Jul 2026, 00:35 UTC≈4,860 views15 reactionsread 6 August 2026

A\的一项丰功伟绩是把AI safety、AI security和AI for security三件事情混为一谈,然后再把这个混杂的概念当成excuse。然后这种坏习惯传染到了一整个学术圈。 safety是对你使用过程中保持稳态的担保,你正常开着AI不会给你文件全删了是safety,AI不去帮你主动下单海量切糕导致家破人亡是safety。 security则是一定围绕攻防展开讨论的(保安说是),基础设施被日了模型被偷了agent被提示词注入了这叫ai security,而你拿ai去给fastjson一秒三棍出0day,这是ai for security。 但在A\那儿这几个词是混为一谈的,包括但不限于滥用red team这个概念,只要逼模型输出unwanted output都叫red team,嚯嚯嚯,红队是这么好当的哦。 所以Amodei一开始就想给大家卖的恐慌是AI for state security,嗯吹CBRN。但一个

🎉14💊1

21 Jul 2026, 11:58 UTC808 viewsread 6 August 2026

直到现在都无法理解fastjson加个@type的意义,首先我寻思这也不在JSON协议标准里,其次允许从字面量映射到非record更是神人。一个小feature,养活多少人,感谢阿里开源

5 Jul 2026, 18:08 UTC958 views10 reactionsread 6 August 2026

盘了几天,这玩意是真的好使,个人认为可以是甲方构建自己起夜级AI代码安全审计设施的playbook 而且同样是vulnerability harness,甲方和乙方关注点是不一样的,如果你接触过别的一些厂商的设计,不难发现 实际上cf这一套harness里面也没有什么过人之处(我反而觉得wishlist是最有亮点的设计),但它面面俱到该考虑的都考虑到了,所以我觉得它是衡量起夜ai代码审计流的及格线,甲方该补足的可以对着补足,而安全公司的产品如果低于这条线可以重开了

🎉10

29 Jun 2026, 12:55 UTC≈1,120 views34 reactionsread 6 August 2026

不知道本频道在蹬AI的读者们会不会有一种羡慕或者享受仍然在慢速运转的世界生活的感觉。我在本领域蹬了几个月后感觉收入并没有增加,人反而更忙更疲惫了,又FOMO,节奏快得有种推背感,而且不太想浪费时间在sb身上/和sb沟通,尽管这很可能是不对的,但上述情绪油然而生

💊34

26 Jun 2026, 03:05 UTC≈1,780 viewsread 6 August 2026

https://blog.cloudflare.com/build-your-own-vulnerability-harness/

24 Jun 2026, 11:42 UTC968 viewsread 6 August 2026
Video

哦对了,金门对面这片海确实好看,如果今年还有人去参加美亚杯,建议比完了去看看,比美亚送的东西有意义,毕竟你不知道再过几年这片地方会不会爆!了

24 Jun 2026, 11:26 UTC≈1,620 views0 reactionsread 6 August 2026
Photo

我承认你们杯和HK警务处出的场景真的酣畅淋漓,但是你在正经取证机里面内置解题模块当卖点是何意味,原来现实中犯人给人噶完腰子之后会觉得不够过瘾现场拿rust写一个堆风水pwn 1000,晶格拼尽全力getshell之后自动弹出犯人三要素

16 Jun 2026, 16:21 UTC627 viewsread 6 August 2026
Forwarded from @vxunderground

Tired of noobs complaining the WINAPI for malware development is weird. It's not. How do you create a file? The CreateFile function. How do you open a file for reading? The CreateFile function. How do you open a file for writing? The CreateFile function. How do you get a handle to a directory? The CreateFile function. How do delete a file? The CreateFile function. How do you get access to a physical disk? The C

14 Jun 2026, 18:23 UTC669 viewsread 6 August 2026

一些怪思考 1. 有了LLM之后,网络安全管理方面能不能也作对抗分析?,众所周知ISO27001和等保作用几乎等同于摆设,传统审计总是假定一个多级文档的playbook拴住人,然后人栓机器。问题是人并不是机器,只要你抽取可观测性指标,人对交付给你的观测结果就会“优化”。但现时的LM有着极强的主观观测能力。比如说,经验老到的金融口大黑阔可能可以结合银行业务条线、大致用的系统/供应商、目标过往安全记录等,去判断还有哪些口子可以打,这其实是总抓安全管理漏洞,那么LM的时代能不能有一套逆炼安全管理原则的方法,让LM科学地观测和给出组织安全管理层面的脆弱性见解(而不是幻觉写稿)? 2. 今年年初以来发现大家对模型的观感和评价分化越来越大了,感觉评价模型好不好用不能再单纯看跑分了,用户有哪些世界知识,模型有哪些世界知识,所工作的世界能给模型多少知识,工作具体需要哪些知识,指定场景要发散思维还是要严格执行,这些都会严重影响实际跑着的表现。反而

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

Citation-graph rank

Citation-graph rank — 65,992 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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

“Pseudorandom Thoughts” (@prdm_thoughts), 687 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/prdm_thoughts.

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.