Channel
@gotoshare
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
17,124subscribers
-25 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001296114136 |
|---|---|
| Type | Channel |
| Username | @gotoshare |
| Description | 程序员资源分享频道 |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/gotoshare |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 07:45 | 17,124 | -5 |
| 12 Aug 2026, 09:06 | 17,129 | -9 |
| 11 Aug 2026, 07:37 | 17,138 | -7 |
| 10 Aug 2026, 09:35 | 17,145 | -1 |
| 9 Aug 2026, 10:51 | 17,146 | +4 |
| 8 Aug 2026, 12:43 | 17,142 | -6 |
| 7 Aug 2026, 12:52 | 17,148 | -1 |
| 6 Aug 2026, 18:00 | 17,149 | no change |
| 6 Aug 2026, 17:56 | 17,149 | first reading |
20 posts held, back to 26 April 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 18 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 10 November 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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.
The owner of this channel has been inactive for the last 11 months. 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.
https://youtu.be/QePKvqLIsP0
这两天技术圈头条的【Amazon的流媒体平台 Prime Video 从微服架构到单体架构”】我以为 Prime Video 遇到不是技术问题，而是AWS Step Function处理能力不足，而且收费很贵的问题。如果 可以无限扩展且白菜价，那么他们还会有动力改成单体吗？会不会反过来吹爆 Serverless？ https://coolshell.cn/articles/22422.html
吴恩达的新课 https://twitter.com/andrewyng/status/1651605660382134274
两年前，我找视频制作公司花了半年做了个二十年来【软件架构的演进】的视频（ https://youtu.be/6X74pEJ58-E ），从单体架构到SOA，再到微服务，再到云原生架构。今天终于把这个视频做成了一个平台：MegaEase Cloud - 国内 http://cloud.megaease.cn / 国外 http://cloud.megaease.com，欢迎试用和反馈！
《使用 Easegress 实现 Telegram 翻译机器人》 https://megaease.cn/zh/blog/2022/09/10/build-a-telegram-translation-bot-with-easegress/ 体验：https://t.me/+9NVypHszklJhNWM1
这个群里总是会有一些找程序员做项目的事，为了避免不必要纠纷或相互之前的白嫖，我在这里给大家几个建议： 1）商务上的东西一定要签合同，那怕是私人对私人。最好对方是有个公司。 2）前期的需求调研很重要，要做什么，不做什么，要描述清楚，也就是需求规格说明书，包括界面是啥样，都应该先mockup好。当需求文档出来后，就可以进行进行项目排期和时间承诺。所以，需求说明和项目排期，以及交付物要说的清清楚楚，没有任何的二义性。以免后面扯皮。 3）关于付款。按商业惯例，当需求说明和项目排期出来后，要支付项目款的30%，当软件功能做完后，交付前，按照第二部分所约定的功能点进行验收，验收完成后，要收剩下的50%的款，最后10%的是给bug-fix用的。 4）对于已约定好功能的调度，15%以内是正常的，可以不收费，但是超过了，就要收费了。 5）对于一些长期成本，比如：云服务费，域名费用，以及运维服务，最好也一并谈了，可以按每个月或每年来谈。 …
这几天好些人来问我对 ChatGPT 的看法，正好周末有时间，写了这篇关于 ChatGPT 的文章。这篇文章主要是讨论了一下，基于“内容生成套路”，而不是基于正确和有价值的内容的ChatGPT，和基于正确和有价值，但不生成内容的搜索引擎连姻，会产生出什么样的化学反应？ https://coolshell.cn/articles/22398.html
本文包括 nostr协议简介，如何对抗审查，如何对抗Spam和骗子，以及我对审查的理解和看法。 https://coolshell.cn/articles/22367.html
注意文后的彩蛋 https://coolshell.cn/articles/22320.html
相关编程语言或技术中文讨论群组： - Java：@Javaer - Scala：@scala_zh - Kotlin：@kotlin_cn - Hadoop 大数据：@bigdatazh - Android：@AndroidDevCn - PostgresQL：@PostgresQLCN - Python：@pythonzh - C：@Clanguagezh - C++：@cpluspluszh - Rust：@rust_zh1 - Go：@GolangCN - Docker：@dockertutorial - 前端：@FrontendToday - 机器学习：@ml_cn - Vim： @vimzh_real - OT讨论群：@coder_ot
https://www.oxeye.io/blog/golang-parameter-smuggling-attack
Showing the 12 most recent of 20 posts we hold for @gotoshare. 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 — 1,051,011 of 1,336,469entries 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.
Named by 5 registered channels — 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.
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.
@gotoshare 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“程序员资源分享频道” (@gotoshare), 17,124 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/gotoshare.
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.