Channel photo updated

Channel
i365科技
@improve365
On this record: Topic · Growth · Engagement · Posts · Cite this entry
574subscribers
-12 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 | -1001236869464 |
|---|---|
| Type | Channel |
| Username | @improve365 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/improve365 |
Topic
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 11 Oct 2026, 08:17 | 574 | -5 |
| 1 Oct 2026, 19:57 | 579 | -2 |
| 16 Sept 2026, 13:15 | 581 | +1 |
| 1 Sept 2026, 02:06 | 580 | -1 |
| 24 Aug 2026, 13:26 | 581 | -2 |
| 15 Aug 2026, 20:24 | 583 | -2 |
| 7 Aug 2026, 19:47 | 585 | -1 |
| 6 Aug 2026, 23:01 | 586 | no change |
| 6 Aug 2026, 22:54 | 586 | first reading |
Engagement
16 posts held, back to 25 September 2021 — 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 page 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 16 posts for this entry, the most recent from 8 April 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel name was changed to «i365科技»
===== 评论区 ===== JERo👔: 老哥这个讨论组链接失效了请问可以补发一个吗谢谢呢
i365科技 pinned «最近一周一直在用 slack 作为讨论的平台,感觉非常棒。telegram 虽然用了两年了,但挺不适合作为群讨论的平台,无法在一个群里对某个话题做深度讨论。所以我会逐渐把 telegram 当作一个发布的渠道平台而非讨论的平台。如果你想讨论的话,可以加入我的 slack 频道: https://join.slack.com/t/bmpidev/shared_invite/zt-1r38f90n5-bOp~RZqoMYiYMOtmKZsbcw slack 的另外一个好处在于它不需要代理去访问,适合国内用户。而它相比…»
最近一周一直在用 slack 作为讨论的平台,感觉非常棒。telegram 虽然用了两年了,但挺不适合作为群讨论的平台,无法在一个群里对某个话题做深度讨论。所以我会逐渐把 telegram 当作一个发布的渠道平台而非讨论的平台。如果你想讨论的话,可以加入我的 slack 频道: https://join.slack.com/t/bmpidev/shared_invite/zt-1r38f90n5-bOp~RZqoMYiYMOtmKZsbcw slack 的另外一个好处在于它不需要代理去访问,适合国内用户。而它相比 discord 的一个缺点是历史记录只能看 90 天以内的,但这其实也有好处,毕竟讨论的话题比较私密货偏激,自动删除历史记录反而是一件好事吧。
===== 评论区 ===== 哎呦喂 🍭(ᵔᵕᵔ˶): 请问这本书叫什么名字?
https://mp.weixin.qq.com/s/YVU_OKL-penQ9LxTbHDy1A 关于百度SEO优化的一篇文章,推荐阅读。和Google SEO优化的共同点在于足够多的内容,但百度SEO有一些非常细节的微操,比如自动修改页面更新时间这类看起来很不可思议的操作。
https://web.archive.org/web/20220722132420/https://mp.weixin.qq.com/s/MjLvoz-BMGTmWirepYEo8g 这篇文章提到百度的一个快速排名方法是点击提权,尤其是国内可以通过众包的方式去点击某个关键词从而迅速排名。Google也有类似的问题,好像之前有个Twitter大V测试过让其follower帮助点击tweet里的页面链接,从而迅速被收录甚至获得某些关键词的排名。
今天和一个SEO优化师聊了之后,决定不继续优化了。原因是Google的中文搜索流量实在低,按英文优化方式就算能做到Top1的位置,流量可能并不高。 从Google Ads查询到这两个看起来搜索量应该不错的词每月搜索流量只有50多个,一开始我对此数据表示怀疑,但是在Top10的页面里刚好有个站的真实搜索流量数据我是知道的,和Ads的数据是相符的。这也意味着Google中文搜索用的人并不多,用Google搜索就算是中文技术人员,一般也都喜欢用英文来搜索,导致中文的搜索量很低,就算能优化上去,性价比也很低。 一般的优化方式无非是站内和站外优化,一般能排名到Top10的页面外链也都不差,内链很容易优化,把内容再多更新一些,加入更多的关键词进去,评论区也多互动起来,这种页面的排名是容易上去的。另外就是可以加入一些专业词汇的英文进去,这样可能也能获取一些英文关键词的流量。 那么优化百度可以吗?在百度搜索这些词后排名前面的大多是百度系的…
我的第一个想法是看到了第一页里一篇知乎问题,所以先在知乎上用这篇文章来回答这个问题👉 https://www.zhihu.com/question/25400195/answer/2560614777 但我们还需要一个系统优化的策略来指导,否则胡乱操作也属于瞎猫碰见死耗子般的运气式优化,以下是我的一些思路: 首先这篇文章在这两个搜索量可能还不错(无法查询到Google搜索中文关键词的量,只能靠索引量猜测)的词下已经排入top10了,说明不存在啥大的seo硬伤。 优化无非是站内和站外两种,最简单的就是内链和外链的优化。 其次是对关键词的契合度及用户搜索意图的优化。 之后我会针对这几个点来做具体的优化。
===== 评论区 =====
#SEO优化记录 https://www.bmpi.dev/dev/authentication-and-authorization-in-a-distributed-system/ 这篇文章在“认证 授权”及“认证系统设计”这两个索引页面达千万近亿的情况下分别排名到第9和第6名,本系列帖子会记录我的一些优化思路及操作,期望能近一步提升排名。
Showing the 12 most recent of 16 posts we hold for @improve365. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“i365科技” (@improve365), 574 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/improve365.
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.