Jeff Dean 对于 Google 的重要性 https://github.com/LRitzdorf/TheJeffDeanFacts

Channel
DPS Build
@dps_build
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
959subscribers
+1 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 | -1001773536366 |
|---|---|
| Type | Channel |
| Username | @dps_build |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/dps_build |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 03:00 | 959 | +1 |
| 6 Aug 2026, 13:47 | 958 | no change |
| 6 Aug 2026, 03:48 | 958 | first reading |
Engagement
20 posts held, back to 30 May 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 79.8%
- avg views ÷ 959 subscribers
- Avg views / post
- 765
- 6 posts measured
- Reaction rate
- 1.06%
- reactions ÷ views · ER floor
- Posts in window
- 6
- 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 4 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (30 May 2026 – 5 August 2026) |
| Views total | 4,591 |
| Reactions total | 23 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 13:47 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.
Reaction mix
46 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 54.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 25 | 54.3% | |
| ❤ | 7 | 15.2% | |
| 😁 | 6 | 13.0% | |
| 👏 | 4 | 8.70% | |
| 🤣 | 4 | 8.70% |
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 13 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 46reactions 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 30 May 2026 to 5 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
震惊了,比老人页面更简洁的是英文界面,打开招商银行,转换成英文页面之后,只有这个极简页面了。 所以到底是蠢还是坏呢?
😁6👍1
关注这个频道的大部分都是程序员吧? 在这个 AI 时代,与其死命做 SaaS,不如找个靠谱的商业搭档一起看看传统行业的机会,说不定机会更多。 我认识我的合伙人十年了,我们去年底重新开始合作,小目标就是在不融资的情况下,把两个人的薪水先赚出来。 一开始也想做 SaaS,毕竟我们都有相关经验。做了三四个月发了 MVP,但是发现这个产品能解决的痛点有限,根本没人买单。 中间见了不少潜在客户,其中一个感叹自己的网站没什么流量,我们开玩笑说可以帮忙看看。过了一两周,他们说在看不同 seo agency 的报价,让我们把把关。我合伙人说,不如我们来吧。 然后我们就硬着头皮顶上去了,没想到效果立马显现,我也越来越有信心。三个月之后,不少网页都成为了 Google 头条,在 ChatGPT / Claude 之类的 AI 应用内也可以看到他们被引用。 客户相当满意,因为他们从网站上获得不少优质询价,甚至来自他们之前怎么也打不进去的市…
👍13
如果每周的 token 限量没有用完,其实最超值的用法是用最好的模型优化你的 skills,因为 skills 会反复被调用,不仅直接关系到最后实现效果的优劣,还直接影响 token 的消耗,妥妥的复利效应。
前阵子,为了现金流,接了一个与核心业务完全不相干的活,现在后悔不已。 核心业务已经搭好了工具库,有项目进来就可以上手,有些个例需要临时休整一下,可以同时接好几个项目,所以整体来说比较容易拓展。 这个不相干的活处处都是雷: 1. 每一个子项目都要按需抓取数据,而且是从不同的网站抓,能不能抓得到还是未知数; 2. 设计大量前端设计,客户非科技行业,非产品经理,无法提供详细量化目标; 3. 要用到的工具库非常小众,需要花大量时间试错。 4. 最要命的是这种项目几乎是一次性的,不太可能再有类似的需求。 完全就是时间黑洞,而且大量占用核心业务的时间精力。以后再也不能范这种错误了。
👍3
不知道哪个大聪明想出来的办法: 1. 在海外用 IPv4 打不开这个网站; 2. 在海外用 IPv6 可以正常打开 这样领导检查起来,嗯,我们的政府网站封禁了所有海外访问,浏览器根本打不开。 真要是有人想从海外浏览这个网站,走 IPv6 就可以 http://english.shanghai.gov.cn/
Photo, posted without a caption
GigaOM 的创始人 Om Malik 刚刚去世,那么多科技界名人都写了悼文: https://om.co/2026/06/24/1966-2026/ https://ma.tt/2026/06/om-forever/ https://daringfireball.net/linked/2026/06/25/om-malik-rip https://arun.is/blog/good-bye-om-malik/
帮朋友看了一下他的产品网站,已经跑了好多年了,在好几个渠道销售,很稳定的收入,但也没有爆发式的增长。 其实是很典型的 landing page,除了一个单页,就什么都没有了。视觉上蛮在线的,但是 google 什么的不会给曝光量。 一个月不到一万的曝光,点击率倒是奇高无比,有16%。大多数都是在其他渠道看到这个产品,直接搜产品名进来的,所以点击率有这么高。但是看 gsc 的数据,通过其他关键词进来的流量很小。 也就是说,哪怕在线时间够长,在其他渠道有不错的曝光,网站本身不做 SEO 优化的话,还是拿不到 google 的自然流量。 看了看他的几个竞品,也都没怎么做 SEO,所以有针对性地做了些调整,等他自己部署吧。
今年的收购有多疯狂呢?一个朋友的公司年初被收购,结果最近收购他的公司又被另一家公司收购。半年被收购了两次🤣
Telegram 终于直接支持 markdown 了
👍2
往好了讲,目前的工作状态基本上非常完美,日常只要和 AI 以及我的搭档交流。客户方面基本上都是搭档搞定,除了定期的进度更新,技术部分我和客户交流,基本上就不怎么需要和其他人交流。 当然从另一个角度而言,AI 是我的 agent,我是我搭档的 agent。看到有什么机会,就丢给我评估一下,我找 AI 评估一下,觉得问题不大就报价跟进。签完合同之后,所有问题就是客户找我,我找 AI,所以我成为了客户的 agent。🤣
🤣4
Showing the 12 most recent of 20 posts we hold for @dps_build. 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 — 146,676 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
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“DPS Build” (@dps_build), 959 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/dps_build.
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.