Telegram RegisterThe public register of Telegram

Channel

pan's channel

@bystartw_chan

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

111subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001317938896
TypeChannel
Username@bystartw_chan
Description放置個人的 coding 以及 OSS 日常。 Who I am → https://pan93.com
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/bystartw_chan

Growth

1117 Aug 2026, 20:31 — 111 subscribers9 Aug 2026, 07:02 — 111 subscribers7 Aug 2026, 20:319 Aug 2026, 07:02
2 measurements spanning 1 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 110–112 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 07:02111no change
7 Aug 2026, 20:31111first reading

Engagement

16 posts held, back to 14 January 2025the 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.

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 7 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
62
Videos
1
Links
50

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

20 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1050.0%
👍840.0%
🤔15.00%
🥰15.00%

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 9 of the 16 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 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 14 January 2025 to 7 March 2025, 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

7 Mar 2025, 03:07 UTC633 views6 reactionsread 9 August 2026

電腦科學中最難的事:置中對齊 https://nptr.cc/posts/2024-07/tonsky-blog-centering/ 下面是 Claude 的 summarization : 在電腦世界裡,看似簡單的元素置中對齊竟然是最令人頭疼的問題之一!即使是蘋果、Google、微軟等科技巨頭也常常無法完美解決。 雖然理論上置中很簡單(只需使用flex或grid),但實際應用中卻處處碰壁: 🔹 字型問題:大部分流行字型的度量值不平衡,導致視覺偏移 🔹 列高困境:不同容器中元素對齊幾乎不可能 🔹 圖示困擾:與文字一起放置的圖示難以精確對齊 🔹 圖示字型缺陷:使得對齊更加困難且無法精確設定大小 解決方案包括: - 設計師:使用緊湊文字框置中 - 字型設計師:平衡ascender和descender值 - 開發人員:透過計算加上適當的padding - 圖示:避免使用圖示字型,改用標準圖片格式

👍32🥰1

26 Feb 2025, 09:12 UTC555 viewsread 9 August 2026

另外你应该: docker run -it --rm --add-host "ports.ubuntu.com:$(dig +short mirror.twds.com.tw A | head -n1)" ubuntu

26 Feb 2025, 07:43 UTC747 views2 reactionsread 9 August 2026

TIL: 不改 Dockerfile,把 Ubuntu 映像的依賴下載速度加速 20 倍以上! Ubuntu 的 Docker 映像檔預設是連線到國外的 "archive.ubuntu.com" (amd64) 或 "ports.ubuntu.com" (arm64) 來安裝 apt 的依賴,台灣連線速度不快。可以把 Mirror 指向台灣的 "mirror.twds.com.tw" 來加速。 不過以往要這樣做,需要蓋掉 image 的 mirrors.list 檔案。今天發現到可以用改 hosts 的檔案來做,舉例來說: docker run -it --rm --add-host "ports.ubuntu.com:103.147.22.36" ubuntu "add-host" 會往 /etc/hosts 加入一條不持久的映射紀錄,這樣就能在不更改 Dockerfile 的情況下加速 apt 依賴安裝。dock

2

6 Feb 2025, 18:06 UTC406 views2 reactionsread 9 August 2026

#在SITCON前每天寫一篇CloudNative文章 這個系列的第四個主題是「服務探索」。從這個主題開始,我們要開始探討前三章說的微服務架構會有什麼問題,以及可以怎麼克服了。這篇會講到 IP:port 的問題,以及用戶端和伺服器端的服務探索方案~ BTW 我想徵求大家對於微服務的哪些實作內容感興趣。目前我的規劃包括負載平衡、服務溝通 (RPC)、非同步操作 (MQ) 等等的議題,但如果大家對某個特定主題特別感興趣,我會儘快寫出這部分的內容 🫡 文章

👍2

5 Feb 2025, 16:04 UTC317 views2 reactionsread 9 August 2026

#在SITCON前每天寫一篇CloudNative文章 不好意思今天比較晚,我花了一些時間把這次的文章改得更好讀一點 🥺 然後這次也玩玩看 UTM 標籤,看看會不會讓我這裡更好追蹤文章成效 (?) 這個 Tag 的第三個主題,就來補充我們昨天微服務中一直沒有提到的部分:「Gateway」吧!我們昨天聊了服務的拆法(領域拆分),以及 RPC 分查詢和更動的目的(CQRS),但是你會發現到有個服務長得和其他服務不太一樣:Gateway。Gateway 沒有 RPC 方法,而且是唯一一個連接到前端的服務。為什麼需要 Gateway,以及 Gateway 是怎麼和其他服務通訊的呢?這篇文章就來詳細解釋這個問題。最後,我們也會簡單說明微服務之間的通訊流程。 文章

👍2

4 Feb 2025, 16:00 UTC250 views2 reactionsread 9 August 2026
Photo

#在SITCON前每天寫一篇CloudNative文章 今天 SITCON 的議程表出了!我在 SITCON 2025 投了一個跟微服務相關的議程,盡量用實際案例來和大家說明微服務和雲端的各種概念 🥰 非常歡迎大家在 SITCON 尾聲來 R3 捧場!https://sitcon.org/2025/agenda/a03517/ 這個 Tag 的第二個主題,還是延續我們上次的選課系統設計。昨天我們發現到單體的方式開始造成資源的浪費以及資料庫的瓶頸,所以我們或許可以看看怎麼把選課系統拆成雲端原生的微服務架構。 考慮到文章發在 Telegram 有著比較嚴重的排版問題,我決定把文章移到我的 Blog 上,也方便日後勘誤。當然互動還是會留在 Telegram 上,也很歡迎大家來這裡繼續分享見解和提出問題~ https://blog.pan93.com/posts/microservice-introducing-microser

2

3 Feb 2025, 15:21 UTC222 views3 reactionsread 9 August 2026
Photo

#在SITCON前每天寫一篇CloudNative文章 今年我 SITCON 有投一篇微服務的議程,應該最近就會出時程表了。在 SITCON 之前,我打算每天 (?!) 在 Telegram 上寫一篇和 Cloud Native 相關的短文,來當作議程的前導內容。當然針對每一篇短文的意見回饋(看不懂也是一種意見反饋 🥺),最終都有助於我產出更好的議程內容~ 這個 Tag 的第一個主題,就先從微服務這個主軸開始吧!但在這之前我們或許可以先聊聊「單體架構可能會遇到什麼樣的瓶頸」,以及我們要怎麼使用一些技術來稍微改善你的單體系統。 假設你今天要開發一套用比序來選課的系統,你或許會像圖 1 這樣來設計你的系統。其中後端就是一個很大的應用程式,前端去呼叫後端來選課。 乍看之下是個挺合理的設計吧?但我們設想一種情況(圖 2):假如現在已經到了選課的尾聲,大家都會想要看看「自己選的課是否可以上得了」,所以「選課人數」Endpoint

3

17 Jan 2025, 13:48 UTC800 viewsread 9 August 2026

小紅書 和 TikTok 都被中華電信的 DNS 解析到 127.0.0.1 了,簡單來說就是被遮掉了。使用 Cloudflare DNS (1.1.1.1) 或 Google DNS (8.8.8.8) 的應該不受影響。 感謝 Chris 和 Lester 的發現!

15 Jan 2025, 06:47 UTC230 viewsread 9 August 2026

甲骨文拒绝放弃“JavaScript”商标 甲骨文因拒绝放弃“JavaScript”商标所有权而面临Deno Land的法律挑战。该商标是甲骨文2009年收购Sun Microsystems时继承而来,但Deno Land认为“JavaScript”已成为通用术语,且甲骨文未积极使用或控制该名称。JavaScript创始人Brendan Eich及开发者社区广泛支持Deno Land的行动,认为此举将影响JavaScript品牌的未来及其在科技行业的开放使用。 Deno Land于2024年11月向美国专利商标局提交请愿书,要求取消甲骨文的商标。甲骨文需在2025年2月3日前作出回应,否则案件可能进入默认判决阶段。若甲骨文坚持不放弃,争议将进入法庭审理。开发者社区已发起公开信,获得超10,000个签名,呼吁甲骨文放弃商标控制权,以确保JavaScript名称的开放使用。 Deno 📮投稿 ☘️频道 🌸聊天

14 Jan 2025, 10:44 UTC216 views1 reactionsread 9 August 2026

首先「AI 翻译成对应的原生平台」這點基本上非常難搞,雖然現代 LLM 都稱自己有著 128K 的 context length,但實踐上超過一定的字數後,後面的內容會開始進入臆想的狀態。基本上你不能輸入整包程式碼甚至是整段 code 進去,你一定要自己花時間分解任務,然後寫個 Agent 來達成你的目標。 如果你不能輸入整段 code,通常只能靠 總結 或者是 只傳入一部分的 code 來逐步翻譯。通常你預期 code 是 1:1 的(行為到介面都應該一致),但一方面 Android 跟 iOS 很多邏輯不是 1:1 的,另一方面是 LLM 產不太出穩定的結果,比如說同一段 function 送進 LLM,產出的 function signature 不能相同。signature 不同就足以造成大問題,更不用講 LLM 可能會在邏輯上的細微差異出差錯了。你或許會想「我把新改好的 code 傳進去就好啦!」但是 LLM(至少在

👍1

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

Forward network

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

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

“pan's channel” (@bystartw_chan), 111 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/bystartw_chan.

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.