<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gea-Suan Lin&#039;s BLOG</title>
	<atom:link href="https://blog.gslin.org/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.gslin.org</link>
	<description>幹壞事是進步最大的原動力</description>
	<lastBuildDate>Fri, 21 Aug 2026 19:12:36 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com"/>
<atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com"/>
<atom:link rel="hub" href="https://websubhub.com/hub"/>
<atom:link rel="self" href="https://blog.gslin.org/feed/"/>
<site xmlns="com-wordpress:feed-additions:1">21326247</site>	<item>
		<title>Casio 復古造型的「智慧」錶</title>
		<link>https://blog.gslin.org/archives/2026/08/22/13162/casio-%e5%be%a9%e5%8f%a4%e9%80%a0%e5%9e%8b%e7%9a%84%e3%80%8c%e6%99%ba%e6%85%a7%e3%80%8d%e9%8c%b6/</link>
					<comments>https://blog.gslin.org/archives/2026/08/22/13162/casio-%e5%be%a9%e5%8f%a4%e9%80%a0%e5%9e%8b%e7%9a%84%e3%80%8c%e6%99%ba%e6%85%a7%e3%80%8d%e9%8c%b6/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Fri, 21 Aug 2026 18:56:06 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[bluetooth]]></category>
		<category><![CDATA[casio]]></category>
		<category><![CDATA[classic]]></category>
		<category><![CDATA[digital]]></category>
		<category><![CDATA[watch]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13162</guid>

					<description><![CDATA[Casio 推出復古造型的「智慧」手錶：「Classic Casio digital watch F-B100W-1A (via)」，防水液晶手錶，可以透過藍芽傳輸，將步數資訊傳到手機上面： 而且價位其實不貴，英國版是 £55.00，日幣賣 ¥8,800 (CASIO Collection STANDARD F-B100W-1AJF)。 不是充電的，但使用的鈕扣電池 CR2016 大約可以用兩年： Power supply and battery life Approx. battery life: 2 years on CR2016 可以透過 app 同步時間，如果不同步的話，精確度大約是每個月約差 15 秒內： Accuracy Accuracy: ±15 seconds per month (with no mobile link function) 以目前資料看起來應該就只有步數，沒有其他的資訊，主要是賣這個設計... 超懷念 (?) 用 coding agent (codex) 找台灣的情況，在「電信設備審驗合格清單」這邊可以查到目前通過的清單，台灣在 2026/08/18 已經過型式認證了 &#8230; <a href="https://blog.gslin.org/archives/2026/08/22/13162/casio-%e5%be%a9%e5%8f%a4%e9%80%a0%e5%9e%8b%e7%9a%84%e3%80%8c%e6%99%ba%e6%85%a7%e3%80%8d%e9%8c%b6/" class="more-link">Continue reading<span class="screen-reader-text"> "Casio 復古造型的「智慧」錶"</span></a>]]></description>
										<content:encoded><![CDATA[<p><a href="https://en.wikipedia.org/wiki/Casio">Casio</a> 推出復古造型的「智慧」手錶：「<a href="https://www.casio.com/uk/watches/casio/product.F-B100W-1A/">Classic Casio digital watch F-B100W-1A</a> (<a href="https://news.ycombinator.com/item?id=49362887">via</a>)」，防水液晶手錶，可以透過藍芽傳輸，將步數資訊傳到手機上面：</p>
<picture><source type="image/webp" srcset="https://i.gslin.com/s/1787337795-ad487315.webp" /><img decoding="async" src="https://i.gslin.com/s/1787337795-ad487315.png" alt="" /></picture>
<p>而且價位其實不貴，英國版是 £55.00，日幣賣 ¥8,800 (<a href="https://www.casio.com/jp/watches/casio/product.F-B100W-1A/">CASIO Collection STANDARD F-B100W-1AJF</a>)。</p>
<p>不是充電的，但使用的鈕扣電池 <a href="https://en.wikipedia.org/wiki/Button_cell">CR2016</a> 大約可以用兩年：</p>
<blockquote><p>Power supply and battery life<br />
Approx. battery life: 2 years on CR2016</p></blockquote>
<p>可以透過 app 同步時間，如果不同步的話，精確度大約是每個月約差 15 秒內：</p>
<blockquote><p>Accuracy<br />
Accuracy: ±15 seconds per month (with no mobile link function)</p></blockquote>
<p>以目前資料看起來應該就只有步數，沒有其他的資訊，主要是賣這個設計... 超懷念 (?)</p>
<p>用 coding agent (<a href="https://en.wikipedia.org/wiki/OpenAI_Codex_(AI_agent)">codex</a>) 找台灣的情況，在「<a href="https://data.gov.tw/dataset/5996">電信設備審驗合格清單</a>」這邊可以查到目前通過的清單，台灣在 2026/08/18 已經過型式認證了 (CCAQ24LP0144T0)，申請人是台灣卡西歐股份有限公司，驗證機構是優力國際安全認證有限公司：</p>
<pre>LP,24,CCAQ24LP0144T0,CCAQ24LP0144T0,Watch,CASIO,F-B100W,台灣卡西歐股份有限公司,,優力國際安全認證有限公司,,N,N,,,20260818,,,,Y,</pre>
<p>看起來應該會是會有公司貨...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/22/13162/casio-%e5%be%a9%e5%8f%a4%e9%80%a0%e5%9e%8b%e7%9a%84%e3%80%8c%e6%99%ba%e6%85%a7%e3%80%8d%e9%8c%b6/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13162</post-id>	</item>
		<item>
		<title>GitHub 前幾天 outage 主要是因為量太大就炸掉了...</title>
		<link>https://blog.gslin.org/archives/2026/08/21/13161/github-%e5%89%8d%e5%b9%be%e5%a4%a9-outage-%e4%b8%bb%e8%a6%81%e6%98%af%e5%9b%a0%e7%82%ba%e9%87%8f%e5%a4%aa%e5%a4%a7%e5%b0%b1%e7%82%b8%e6%8e%89%e4%ba%86/</link>
					<comments>https://blog.gslin.org/archives/2026/08/21/13161/github-%e5%89%8d%e5%b9%be%e5%a4%a9-outage-%e4%b8%bb%e8%a6%81%e6%98%af%e5%9b%a0%e7%82%ba%e9%87%8f%e5%a4%aa%e5%a4%a7%e5%b0%b1%e7%82%b8%e6%8e%89%e4%ba%86/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Fri, 21 Aug 2026 13:06:41 +0000</pubDate>
				<category><![CDATA[Azure]]></category>
		<category><![CDATA[Cloud]]></category>
		<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[ai]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[azure]]></category>
		<category><![CDATA[capacity]]></category>
		<category><![CDATA[github]]></category>
		<category><![CDATA[growth]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[outage]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[sla]]></category>
		<category><![CDATA[system]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13161</guid>

					<description><![CDATA[一般來說已經是全球領先的產品了，不太會有短時間翻倍等級的成長，但在這一波 AI 浪潮的關係，讓 GitHub 的用量在半年翻倍，結果 capacity 不夠用直接炸掉了... 這次是新任 CTO Vlad Fedorov 貼的：「The August 17 outage, and the work ahead (via)」。 裡面幾張圖就蠻能解釋問題了，首先是各種指標，包括 merged PR 數量、commit 數量、新的 repo 數量，都可以看到 AI 時期的爆炸性成長： 然後提到美國中部機房沒撐住導致 authentication failure： Our investigation found that the outage began when traffic reached a new peak, and a critical infrastructure component in our Central US data &#8230; <a href="https://blog.gslin.org/archives/2026/08/21/13161/github-%e5%89%8d%e5%b9%be%e5%a4%a9-outage-%e4%b8%bb%e8%a6%81%e6%98%af%e5%9b%a0%e7%82%ba%e9%87%8f%e5%a4%aa%e5%a4%a7%e5%b0%b1%e7%82%b8%e6%8e%89%e4%ba%86/" class="more-link">Continue reading<span class="screen-reader-text"> "GitHub 前幾天 outage 主要是因為量太大就炸掉了..."</span></a>]]></description>
										<content:encoded><![CDATA[<p>一般來說已經是全球領先的產品了，不太會有短時間翻倍等級的成長，但在這一波 <a href="https://en.wikipedia.org/wiki/Artificial_intelligence">AI</a> 浪潮的關係，讓 <a href="https://en.wikipedia.org/wiki/GitHub">GitHub</a> 的用量在半年翻倍，結果 capacity 不夠用直接炸掉了...</p>
<p>這次是新任 CTO <a href="https://www.linkedin.com/in/vladimir-fedorov-b2a9302/">Vlad Fedorov</a> 貼的：「<a href="https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/">The August 17 outage, and the work ahead</a> (<a href="https://news.ycombinator.com/item?id=49378957">via</a>)」。</p>
<p>裡面幾張圖就蠻能解釋問題了，首先是各種指標，包括 merged PR 數量、commit 數量、新的 repo 數量，都可以看到 AI 時期的爆炸性成長：</p>
<picture><source type="image/webp" srcset="https://i.gslin.com/s/1787316945-23974d59.webp" /><img decoding="async" src="https://i.gslin.com/s/1787316945-23974d59.png" alt="" /></picture>
<p>然後提到美國中部機房沒撐住導致 authentication failure：</p>
<blockquote><p>Our investigation found that the outage began when traffic reached a new peak, and a critical infrastructure component in our Central US data center failed to scale with it. The resulting capacity pressure spread through our systems, causing authentication failures and disrupting multiple GitHub services.</p></blockquote>
<p>他說明這些成長壓力不是炸掉的直接主因 (上面提到的 authentication 才是，但其實也跟量有關...)：</p>
<blockquote><p>Since April, monthly commits have grown from 1.4 billion to 2.9 billion. That growth explains the pressure on our systems, but it does not excuse these outages.</p></blockquote>
<p>然後打了母公司 <a href="https://en.wikipedia.org/wiki/Microsoft_Azure">Azure</a> 的廣告，提到大多數的擴充都是透過 Azure 撐起來：</p>
<blockquote><p>Today, Azure serves roughly 58% of GitHub’s platform load and half of all Git operations, up from 12% of platform load in May.</p></blockquote>
<p>但看起來還是有關鍵的基礎設施沒進到 Azure 擴充...</p>
<p>話說很少在領跑地位還看到這種等級的成長，算是受益者還是受害者...？</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/21/13161/github-%e5%89%8d%e5%b9%be%e5%a4%a9-outage-%e4%b8%bb%e8%a6%81%e6%98%af%e5%9b%a0%e7%82%ba%e9%87%8f%e5%a4%aa%e5%a4%a7%e5%b0%b1%e7%82%b8%e6%8e%89%e4%ba%86/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13161</post-id>	</item>
		<item>
		<title>Unsloth 的 UD 3.0</title>
		<link>https://blog.gslin.org/archives/2026/08/20/13160/unsloth-%e7%9a%84-ud-3-0/</link>
					<comments>https://blog.gslin.org/archives/2026/08/20/13160/unsloth-%e7%9a%84-ud-3-0/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Wed, 19 Aug 2026 23:16:17 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[ai]]></category>
		<category><![CDATA[dynamic]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[large]]></category>
		<category><![CDATA[llm]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[quantization]]></category>
		<category><![CDATA[ram]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[vram]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13160</guid>

					<description><![CDATA[本地端跑 LLM 基本上都會用 quantization 版本以降低 VRAM 的壓力，因為原始 model 大多都是使用 fp16，在 5090 的 32GB VRAM 等於只能跑 16B 模型 (先不算其他執行時需要的 cache)，而 4-bit quantization 版本就有機會上到 64B。 實務上 KV cache 以及其他的東西加起來差不多與 model 佔同樣大小，所以 32GB VRAM 大概跑 30B 左右的 4-bit quantization model 還 OK，最近幾天很紅的就是 Qwen3.8-27B 了，可以看到各家都有出來轉檔。 一般的 quantization 是直接對每個參數轉換，而 Unsloth 針對 GGUF 格式支援動態取 quantization 的技術，挑出「比較重要的參數」給予更多的 bit，用少量額外的空間來換取更好的精確度，而這次看到 3.0 版的技術，看起來又再比之前 2.0 提升了一些：「Unsloth &#8230; <a href="https://blog.gslin.org/archives/2026/08/20/13160/unsloth-%e7%9a%84-ud-3-0/" class="more-link">Continue reading<span class="screen-reader-text"> "Unsloth 的 UD 3.0"</span></a>]]></description>
										<content:encoded><![CDATA[<p>本地端跑 <a href="https://en.wikipedia.org/wiki/Large_language_model">LLM</a> 基本上都會用 quantization 版本以降低 <a href="https://en.wikipedia.org/wiki/Video_random-access_memory">VRAM</a> 的壓力，因為原始 model 大多都是使用 fp16，在 <a href="https://en.wikipedia.org/wiki/GeForce_RTX_50_series">5090</a> 的 32GB VRAM 等於只能跑 16B 模型 (先不算其他執行時需要的 cache)，而 4-bit quantization 版本就有機會上到 64B。</p>
<p>實務上 KV cache 以及其他的東西加起來差不多與 model 佔同樣大小，所以 32GB VRAM 大概跑 30B 左右的 4-bit quantization model 還 OK，最近幾天很紅的就是 <a href="https://huggingface.co/Qwen/Qwen3.8-27B">Qwen3.8-27B</a> 了，可以看到各家都有出來轉檔。</p>
<p>一般的 quantization 是直接對每個參數轉換，而 <a href="https://unsloth.ai/">Unsloth</a> 針對 <a href="https://en.wikipedia.org/wiki/GGUF">GGUF</a> 格式支援動態取 quantization 的技術，挑出「比較重要的參數」給予更多的 bit，用少量額外的空間來換取更好的精確度，而這次看到 3.0 版的技術，看起來又再比之前 2.0 提升了一些：「<a href="https://unsloth.ai/docs/basics/dynamic-3.0-ggufs">Unsloth Dynamic 3.0 GGUFs</a>」。</p>
<p>官方說 <a href="https://huggingface.co/unsloth/Qwen3.8-27B-GGUF">unsloth/Qwen3.8-27B-GGUF</a> 有放上 3.0 版，剛剛試著重跑 <code>UD-Q4_K_XL</code> 版本就發現重新下載了，應該是直接用就可以了...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/20/13160/unsloth-%e7%9a%84-ud-3-0/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13160</post-id>	</item>
		<item>
		<title>OpenRouter 正式被 Stripe 併購了</title>
		<link>https://blog.gslin.org/archives/2026/08/20/13158/openrouter-%e6%ad%a3%e5%bc%8f%e8%a2%ab-stripe-%e4%bd%b5%e8%b3%bc%e4%ba%86/</link>
					<comments>https://blog.gslin.org/archives/2026/08/20/13158/openrouter-%e6%ad%a3%e5%bc%8f%e8%a2%ab-stripe-%e4%bd%b5%e8%b3%bc%e4%ba%86/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Wed, 19 Aug 2026 21:37:43 +0000</pubDate>
				<category><![CDATA[API]]></category>
		<category><![CDATA[Computer]]></category>
		<category><![CDATA[Financial]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[ai]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[large]]></category>
		<category><![CDATA[llm]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[openrouter]]></category>
		<category><![CDATA[stripe]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13158</guid>

					<description><![CDATA[前幾天就有消息了，剛剛看到正式併購的新聞稿出來了：「OpenRouter is Joining Stripe (via)」、「Stripe will reportedly acquire AI gateway startup OpenRouter for $7B+ (via)」。 當時有些人在猜是不是因為現在 AI 的金流太大，而 OpenAI 剛跑掉所以直接綁樁：(id=49324302) I wonder if this deal is primarily just to buy payment volume. OpenAI just announced earlier this week that Ayden would become their payment provider (when it was previously Stripe). And OpenRouter has a large &#8230; <a href="https://blog.gslin.org/archives/2026/08/20/13158/openrouter-%e6%ad%a3%e5%bc%8f%e8%a2%ab-stripe-%e4%bd%b5%e8%b3%bc%e4%ba%86/" class="more-link">Continue reading<span class="screen-reader-text"> "OpenRouter 正式被 Stripe 併購了"</span></a>]]></description>
										<content:encoded><![CDATA[<p>前幾天就有消息了，剛剛看到正式併購的新聞稿出來了：「<a href="https://openrouter.ai/blog/announcements/openrouter-is-joining-stripe/">OpenRouter is Joining Stripe</a> (<a href="https://news.ycombinator.com/item?id=49364559">via</a>)」、「<a href="https://techcrunch.com/2026/08/16/stripe-will-reportedly-acquire-ai-gateway-startup-openrouter-for-7b/">Stripe will reportedly acquire AI gateway startup OpenRouter for $7B+</a> (<a href="https://news.ycombinator.com/item?id=49323381">via</a>)」。</p>
<p>當時有些人在猜是不是因為現在 AI 的金流太大，而 <a href="https://en.wikipedia.org/wiki/OpenAI">OpenAI</a> 剛跑掉所以直接綁樁：(<a href="https://news.ycombinator.com/item?id=49324302">id=49324302</a>)</p>
<blockquote><p>I wonder if this deal is primarily just to buy payment volume.</p>
<p>OpenAI just announced earlier this week that Ayden would become their payment provider (when it was previously Stripe).</p>
<p>And OpenRouter has a large percentage of overall AI payment volume for all the major labs.</p>
<p>Both OpenAI and OpenRouter represent ~$100B in payment volume, whereas Stripe in total doing ~$2T. Two customer doing ~5% of your total volume who didn’t even exist a few years ago, must be kind of scary for Stripe.</p></blockquote>
<p>但不是很確定，畢竟這種併購都是要談蠻久的，時間線未必對的上... 從新聞稿也看不出什麼東西。</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/20/13158/openrouter-%e6%ad%a3%e5%bc%8f%e8%a2%ab-stripe-%e4%bd%b5%e8%b3%bc%e4%ba%86/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13158</post-id>	</item>
		<item>
		<title>GPT-5.6 Sol 在 OpenRouter 的 50% off</title>
		<link>https://blog.gslin.org/archives/2026/08/20/13157/gpt-5-6-sol-%e5%9c%a8-openrouter-%e7%9a%84-50-off/</link>
					<comments>https://blog.gslin.org/archives/2026/08/20/13157/gpt-5-6-sol-%e5%9c%a8-openrouter-%e7%9a%84-50-off/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Wed, 19 Aug 2026 17:05:22 +0000</pubDate>
				<category><![CDATA[API]]></category>
		<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[discount]]></category>
		<category><![CDATA[gpt-5.6]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[large]]></category>
		<category><![CDATA[llm]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[openai]]></category>
		<category><![CDATA[openrouter]]></category>
		<category><![CDATA[pricing]]></category>
		<category><![CDATA[token]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13157</guid>

					<description><![CDATA[昨天 OpenRouter 上的 OpenAI: GPT-5.6 Sol 打了 50% off 變成 $2.5/$15，而且是由 OpenAI 提供的，不過這個價錢是沒有 ZDR policy 的 (所以會留 prompt 資訊)，Hacker News 上也有不少討論：「GPT-5.6 Sol Pricing Cut by 50% on OpenRouter (openrouter.ai)」。 Hacker News 上有些人提到中國的 model 競爭性，不過中國的 model 已經出來一段時間了，我覺得時間點上真的有給出壓力的應該是 Grok 4.6 吧，美國籍的 model，但 $2/$6 對上 GPT-5.6 Sol 與 Opus 5 的價錢實在太殺？ 我是跑去買 subscription plan，這一個禮拜用起來發現 CP 值不錯，方案的層級是 $10/mo、$30/mo、$100/mo 然後是 &#8230; <a href="https://blog.gslin.org/archives/2026/08/20/13157/gpt-5-6-sol-%e5%9c%a8-openrouter-%e7%9a%84-50-off/" class="more-link">Continue reading<span class="screen-reader-text"> "GPT-5.6 Sol 在 OpenRouter 的 50% off"</span></a>]]></description>
										<content:encoded><![CDATA[<p>昨天 <a href="https://en.wikipedia.org/wiki/OpenRouter">OpenRouter</a> 上的 <a href="https://openrouter.ai/openai/gpt-5.6-sol">OpenAI: GPT-5.6 Sol</a> 打了 50% off 變成 $2.5/$15，而且是由 <a href="https://en.wikipedia.org/wiki/OpenAI">OpenAI</a> 提供的，不過這個價錢是沒有 ZDR policy 的 (所以會留 prompt 資訊)，<a href="https://en.wikipedia.org/wiki/Hacker_News">Hacker News</a> 上也有不少討論：「<a href="https://news.ycombinator.com/item?id=49337602">GPT-5.6 Sol Pricing Cut by 50% on OpenRouter (openrouter.ai)</a>」。</p>
<p>Hacker News 上有些人提到中國的 model 競爭性，不過中國的 model 已經出來一段時間了，我覺得時間點上真的有給出壓力的應該是 <a href="https://en.wikipedia.org/wiki/Grok_(chatbot)">Grok</a> 4.6 吧，美國籍的 model，但 $2/$6 對上 GPT-5.6 Sol 與 Opus 5 的價錢實在太殺？</p>
<p>我是跑去買 subscription plan，這一個禮拜用起來發現 CP 值不錯，方案的層級是 $10/mo、$30/mo、$100/mo 然後是 $300/mo，升級的步調大約都是三倍左右，不像其他兩家 $20/mo 後就直接跳 $100/mo 了。</p>
<p>不確定這個 discount 會維持多久，但目前看起來有愈來愈多 model 跟上來了...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/20/13157/gpt-5-6-sol-%e5%9c%a8-openrouter-%e7%9a%84-50-off/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13157</post-id>	</item>
		<item>
		<title>Claude 的 System Prompts</title>
		<link>https://blog.gslin.org/archives/2026/08/17/13155/claude-%e7%9a%84-system-prompts/</link>
					<comments>https://blog.gslin.org/archives/2026/08/17/13155/claude-%e7%9a%84-system-prompts/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sun, 16 Aug 2026 16:47:35 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[anthropic]]></category>
		<category><![CDATA[claude]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[large]]></category>
		<category><![CDATA[llm]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[prompt]]></category>
		<category><![CDATA[system]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13155</guid>

					<description><![CDATA[Anthropic 官方把 Claude 的 system prompt 放出來了，從 2024 年的 Haiku 3 到最新的 Opus 5 都列出來了：「System Prompts (via)」。 因為設計上 system prompt 放在 client 端，所以先前有人用 MITM proxy 抓過，不算什麼秘密... 但比較好奇的是，這種東西應該是放在 server 端才對？當初設計放在 client 是什麼原因？為了通用 API 的設計嗎？ 回到 Hacker News 上面，有人找到不少有趣的內容，像是在 Opus 5 與 Fable 5 的 system prompt 補上被美國政府禁止提供服務的知識： Claude Fable 5 and Claude Mythos 5 were first &#8230; <a href="https://blog.gslin.org/archives/2026/08/17/13155/claude-%e7%9a%84-system-prompts/" class="more-link">Continue reading<span class="screen-reader-text"> "Claude 的 System Prompts"</span></a>]]></description>
										<content:encoded><![CDATA[<p><a href="https://en.wikipedia.org/wiki/Anthropic">Anthropic</a> 官方把 <a href="https://en.wikipedia.org/wiki/Claude_(AI)">Claude</a> 的 <a href="https://en.wikipedia.org/wiki/System_prompt">system prompt</a> 放出來了，從 2024 年的 Haiku 3 到最新的 Opus 5 都列出來了：「<a href="https://platform.claude.com/docs/en/release-notes/system-prompts">System Prompts</a> (<a href="https://news.ycombinator.com/item?id=49319556">via</a>)」。</p>
<p>因為設計上 system prompt 放在 client 端，所以先前有人用 <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM</a> proxy 抓過，不算什麼秘密... 但比較好奇的是，這種東西應該是放在 server 端才對？當初設計放在 client 是什麼原因？為了通用 API 的設計嗎？</p>
<p>回到 <a href="https://en.wikipedia.org/wiki/Hacker_News">Hacker News</a> 上面，有人找到不少有趣的內容，像是在 Opus 5 與 Fable 5 的 system prompt 補上被美國政府禁止提供服務的知識：</p>
<blockquote><p>Claude Fable 5 and Claude Mythos 5 were first released on June 9, 2026. On June 12, 2026, Anthropic suspended access to both models to comply with U.S. Department of Commerce export controls; the Department lifted those controls on June 30, 2026, and Anthropic restored access on July 1, 2026 (Anthropic's statement: https://www.anthropic.com/news/fable-mythos-access). These events are after Claude's training-data cutoff, so Claude knows about them only from this notice. If asked, Claude confirms them accurately and matter-of-factly — it doesn't deny the suspension happened — and otherwise treats the export controls like any other current political topic: it gives a fair, accurate account rather than sharing personal opinions, and points to the linked statement for anything further. Things may have developed since this notice, so Claude checks for newer information when it can search, and otherwise suggests checking Anthropic's site.</p></blockquote>
<p>還有 Opus 4.6 關於 <a href="https://en.wikipedia.org/wiki/Donald_Trump">Trump</a> 選上總統的部分：</p>
<blockquote><p>There was a US Presidential Election in November 2024. Donald Trump won the presidency over Kamala Harris. If asked about the election, or the US election, Claude can tell the person the following information:</p>
<p>Donald Trump is the current president of the United States and was inaugurated on January 20, 2025. Donald Trump defeated Kamala Harris in the 2024 elections. Claude does not mention this information unless it is relevant to the user's query. </p></blockquote>
<p>會選擇加這些知識進 system prompts 大概是 PR team 的想法吧？一般 engineering team 應該對這個比較沒興趣...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/17/13155/claude-%e7%9a%84-system-prompts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13155</post-id>	</item>
		<item>
		<title>電梯演算法</title>
		<link>https://blog.gslin.org/archives/2026/08/16/13154/%e9%9b%bb%e6%a2%af%e6%bc%94%e7%ae%97%e6%b3%95/</link>
					<comments>https://blog.gslin.org/archives/2026/08/16/13154/%e9%9b%bb%e6%a2%af%e6%bc%94%e7%ae%97%e6%b3%95/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sun, 16 Aug 2026 06:52:28 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[algo]]></category>
		<category><![CDATA[algorithm]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[drive]]></category>
		<category><![CDATA[elevator]]></category>
		<category><![CDATA[hard]]></category>
		<category><![CDATA[look]]></category>
		<category><![CDATA[scan]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13154</guid>

					<description><![CDATA[幾個禮拜前看到「Elevators (via)」這個在講電梯演算法的，裡面給了不少有趣的動畫效果，算是入門等級的教材？ 找資料的時候發現維基百科的「Elevator algorithm」這個條目，反而提到了硬碟中磁頭的演算法： The elevator algorithm, or SCAN, is a disk-scheduling algorithm to determine the motion of the disk's arm and head in servicing read and write requests. 主要是因為兩者的行為很像？磁頭在跑的過程中會有其他的 i/o 需求進來，就像是電梯的人潮： This algorithm is named after the behavior of a building elevator, where the elevator continues to travel in its current direction (up or &#8230; <a href="https://blog.gslin.org/archives/2026/08/16/13154/%e9%9b%bb%e6%a2%af%e6%bc%94%e7%ae%97%e6%b3%95/" class="more-link">Continue reading<span class="screen-reader-text"> "電梯演算法"</span></a>]]></description>
										<content:encoded><![CDATA[<p>幾個禮拜前看到「<a href="https://john.fun/elevators">Elevators</a> (<a href="https://news.ycombinator.com/item?id=49124218">via</a>)」這個在講電梯演算法的，裡面給了不少有趣的動畫效果，算是入門等級的教材？</p>
<p>找資料的時候發現維基百科的「<a href="https://en.wikipedia.org/wiki/Elevator_algorithm">Elevator algorithm</a>」這個條目，反而提到了硬碟中磁頭的演算法：</p>
<blockquote><p>The elevator algorithm, or SCAN, is a disk-scheduling algorithm to determine the motion of the disk's arm and head in servicing read and write requests.</p></blockquote>
<p>主要是因為兩者的行為很像？磁頭在跑的過程中會有其他的 i/o 需求進來，就像是電梯的人潮：</p>
<blockquote><p>This algorithm is named after the behavior of a building elevator, where the elevator continues to travel in its current direction (up or down) until empty, stopping only to let individuals off or to pick up new individuals heading in the same direction.</p>
<p>From an implementation perspective, the drive maintains a buffer of pending read/write requests, along with the associated cylinder number of the request, in which lower cylinder numbers generally indicate that the cylinder is closer to the spindle, and higher numbers indicate the cylinder is farther away.</p></blockquote>
<p>不過也提到現代的 OS 對硬碟的操作已經跟這些演算法無關了，SSD 的存取已經是固定時間，而且就算是傳統機械硬碟，存取架構已經從傳統指定物理位置的 <a href="https://en.wikipedia.org/wiki/Cylinder-head-sector">CHS</a> 變成邏輯位置 <a href="https://en.wikipedia.org/wiki/Logical_block_addressing">LBA</a> 了：</p>
<blockquote><p>The algorithm is largely obsolete for data storage. With the current generation of magnetic disks it is not possible to know the location of specific data on the disk and solid state memory devices have a constant seek time independent of location.</p></blockquote>
<p>但回到電梯的情境，這些演算法還是存在需求的，從維基百科上面可以看到 SCAN 類的演算法與 <a href="https://en.wikipedia.org/wiki/LOOK_algorithm">LOOK</a> 類的演算法，以及多台時的變化。</p>
<p>當作有趣的知識來看...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/16/13154/%e9%9b%bb%e6%a2%af%e6%bc%94%e7%ae%97%e6%b3%95/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13154</post-id>	</item>
		<item>
		<title>Meta 在美國新墨西哥州因為危害兒童心理健康被罰鉅款</title>
		<link>https://blog.gslin.org/archives/2026/08/15/13153/meta-%e5%9c%a8%e7%be%8e%e5%9c%8b%e6%96%b0%e5%a2%a8%e8%a5%bf%e5%93%a5%e5%b7%9e%e5%9b%a0%e7%82%ba%e5%8d%b1%e5%ae%b3%e5%85%92%e7%ab%a5%e5%bf%83%e7%90%86%e5%81%a5%e5%ba%b7%e8%a2%ab%e7%bd%b0%e9%89%85/</link>
					<comments>https://blog.gslin.org/archives/2026/08/15/13153/meta-%e5%9c%a8%e7%be%8e%e5%9c%8b%e6%96%b0%e5%a2%a8%e8%a5%bf%e5%93%a5%e5%b7%9e%e5%9b%a0%e7%82%ba%e5%8d%b1%e5%ae%b3%e5%85%92%e7%ab%a5%e5%bf%83%e7%90%86%e5%81%a5%e5%ba%b7%e8%a2%ab%e7%bd%b0%e9%89%85/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sat, 15 Aug 2026 01:56:03 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Political]]></category>
		<category><![CDATA[Social]]></category>
		<category><![CDATA[child]]></category>
		<category><![CDATA[children]]></category>
		<category><![CDATA[court]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[fb]]></category>
		<category><![CDATA[health]]></category>
		<category><![CDATA[ig]]></category>
		<category><![CDATA[instagram]]></category>
		<category><![CDATA[mental]]></category>
		<category><![CDATA[meta]]></category>
		<category><![CDATA[mexico]]></category>
		<category><![CDATA[new]]></category>
		<category><![CDATA[state]]></category>
		<category><![CDATA[states]]></category>
		<category><![CDATA[united]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13153</guid>

					<description><![CDATA[前幾天看到 Meta 被罰鉅款的消息：「New Mexico court orders Meta to pay $567m over harms to children’s mental health (via)」。 Hacker News 上面給了某些角度的分析，考慮到新墨西哥州大約 212 萬人口，未成年人口大約 44 萬人，累積的罰款到 9.42 億美金可以看出來有多高： A lot of people on this story are making the usual snarky remarks that, oh, this is just a slap on the wrist—some trivial proportion of Meta’s global revenue. &#8230; <a href="https://blog.gslin.org/archives/2026/08/15/13153/meta-%e5%9c%a8%e7%be%8e%e5%9c%8b%e6%96%b0%e5%a2%a8%e8%a5%bf%e5%93%a5%e5%b7%9e%e5%9b%a0%e7%82%ba%e5%8d%b1%e5%ae%b3%e5%85%92%e7%ab%a5%e5%bf%83%e7%90%86%e5%81%a5%e5%ba%b7%e8%a2%ab%e7%bd%b0%e9%89%85/" class="more-link">Continue reading<span class="screen-reader-text"> "Meta 在美國新墨西哥州因為危害兒童心理健康被罰鉅款"</span></a>]]></description>
										<content:encoded><![CDATA[<p>前幾天看到 <a href="https://en.wikipedia.org/wiki/Meta_Platforms">Meta</a> 被罰鉅款的消息：「<a href="https://www.theguardian.com/technology/2026/aug/06/new-mexico-court-meta">New Mexico court orders Meta to pay $567m over harms to children’s mental health</a> (<a href="https://news.ycombinator.com/item?id=49204352">via</a>)」。</p>
<p><a href="https://en.wikipedia.org/wiki/Hacker_News">Hacker News</a> 上面給了某些角度的分析，考慮到新墨西哥州大約 212 萬人口，未成年人口大約 44 萬人，累積的罰款到 9.42 億美金可以看出來有多高：</p>
<blockquote><p>A lot of people on this story are making the usual snarky remarks that, oh, this is just a slap on the wrist—some trivial proportion of Meta’s global revenue. And that is true, but unlike the EU, for example, New Mexico is a tiny jurisdiction. It only has a little bit more than 2 million people.</p>
<p>So actually, a fine—or a judgment—of $942 million that applies just to New Mexico is enormous. If you look at Meta’s revenue from the U.S. and Canada and assign it proportionally by population, you find that Meta only earned about $1.5 billion to $2 billion total from New Mexico over the past five years. The exact figure depends on whether you allocate purely by population or account for purchasing power, which makes the estimate a little lower because New Mexico is a poorer state than the U.S. average.</p></blockquote>
<p>不愧是電子毒品平台...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/15/13153/meta-%e5%9c%a8%e7%be%8e%e5%9c%8b%e6%96%b0%e5%a2%a8%e8%a5%bf%e5%93%a5%e5%b7%9e%e5%9b%a0%e7%82%ba%e5%8d%b1%e5%ae%b3%e5%85%92%e7%ab%a5%e5%bf%83%e7%90%86%e5%81%a5%e5%ba%b7%e8%a2%ab%e7%bd%b0%e9%89%85/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13153</post-id>	</item>
		<item>
		<title>uBlock Origin 的社群停止維護阻擋 Facebook 廣告的工作</title>
		<link>https://blog.gslin.org/archives/2026/08/14/13151/ublock-origin-%e7%9a%84%e7%a4%be%e7%be%a4%e5%81%9c%e6%ad%a2%e7%b6%ad%e8%ad%b7%e9%98%bb%e6%93%8b-facebook-%e5%bb%a3%e5%91%8a%e7%9a%84%e5%b7%a5%e4%bd%9c/</link>
					<comments>https://blog.gslin.org/archives/2026/08/14/13151/ublock-origin-%e7%9a%84%e7%a4%be%e7%be%a4%e5%81%9c%e6%ad%a2%e7%b6%ad%e8%ad%b7%e9%98%bb%e6%93%8b-facebook-%e5%bb%a3%e5%91%8a%e7%9a%84%e5%b7%a5%e4%bd%9c/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Thu, 13 Aug 2026 19:24:54 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Social]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[ad]]></category>
		<category><![CDATA[advertisement]]></category>
		<category><![CDATA[community]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[meta]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[origin]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[ublock]]></category>
		<category><![CDATA[userscript]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13151</guid>

					<description><![CDATA[看到「uBlock Origin Is Giving Up the Fight to Keep Ads Off Facebook (via)」這則在講 uBlock Origin 的社群後續不會再繼續維護阻擋 Facebook 上廣告的工作，社群的說明公告在 Reddit 上：「About disgusting Facebook devs」。 先前有提到「在桌機上擋 Facebook 各種廣告與演算法推薦文章的 userscript」，不過作者後來停止更新了，在「Is this userscript still maintained #85」這邊有提到需要幾個月的時間恢復： I will be updating in a few months. I am currently incapacity and will take a few months to recover. 但後續沒看到回來，目前是有在 Artificial-Sweetener/facebook-clean-my-feeds 這邊看到 &#8230; <a href="https://blog.gslin.org/archives/2026/08/14/13151/ublock-origin-%e7%9a%84%e7%a4%be%e7%be%a4%e5%81%9c%e6%ad%a2%e7%b6%ad%e8%ad%b7%e9%98%bb%e6%93%8b-facebook-%e5%bb%a3%e5%91%8a%e7%9a%84%e5%b7%a5%e4%bd%9c/" class="more-link">Continue reading<span class="screen-reader-text"> "uBlock Origin 的社群停止維護阻擋 Facebook 廣告的工作"</span></a>]]></description>
										<content:encoded><![CDATA[<p>看到「<a href="https://digitalescapetools.com/2026/08/ublock-origin-stops-chasing-facebook-ads.html">uBlock Origin Is Giving Up the Fight to Keep Ads Off Facebook</a> (<a href="https://news.ycombinator.com/item?id=49270726">via</a>)」這則在講 uBlock Origin 的社群後續不會再繼續維護阻擋 Facebook 上廣告的工作，社群的說明公告在 <a href="https://en.wikipedia.org/wiki/Reddit">Reddit</a> 上：「<a href="https://old.reddit.com/r/uBlockOrigin/comments/1vgcjg5/about_disgusting_facebook_devs/">About disgusting Facebook devs</a>」。</p>
<p>先前有提到「<a href="https://blog.gslin.org/archives/2024/02/03/11634/%e5%9c%a8%e6%a1%8c%e6%a9%9f%e4%b8%8a%e6%93%8b-facebook-%e5%90%84%e7%a8%ae%e5%bb%a3%e5%91%8a%e8%88%87%e6%bc%94%e7%ae%97%e6%b3%95%e6%8e%a8%e8%96%a6%e6%96%87%e7%ab%a0%e7%9a%84-userscript/">在桌機上擋 Facebook 各種廣告與演算法推薦文章的 userscript</a>」，不過作者後來停止更新了，在「<a href="https://github.com/zbluebugz/facebook-clean-my-feeds/issues/85">Is this userscript still maintained #85</a>」這邊有提到需要幾個月的時間恢復：</p>
<blockquote><p>I will be updating in a few months. I am currently incapacity and will take a few months to recover.</p></blockquote>
<p>但後續沒看到回來，目前是有在 <a href="https://github.com/Artificial-Sweetener/facebook-clean-my-feeds">Artificial-Sweetener/facebook-clean-my-feeds</a> 這邊看到 fork 出來的版本...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/14/13151/ublock-origin-%e7%9a%84%e7%a4%be%e7%be%a4%e5%81%9c%e6%ad%a2%e7%b6%ad%e8%ad%b7%e9%98%bb%e6%93%8b-facebook-%e5%bb%a3%e5%91%8a%e7%9a%84%e5%b7%a5%e4%bd%9c/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13151</post-id>	</item>
		<item>
		<title>網拍電視棒的跳板類後門</title>
		<link>https://blog.gslin.org/archives/2026/08/14/13149/%e7%b6%b2%e6%8b%8d%e9%9b%bb%e8%a6%96%e6%a3%92%e7%9a%84%e8%b7%b3%e6%9d%bf%e9%a1%9e%e5%be%8c%e9%96%80/</link>
					<comments>https://blog.gslin.org/archives/2026/08/14/13149/%e7%b6%b2%e6%8b%8d%e9%9b%bb%e8%a6%96%e6%a3%92%e7%9a%84%e8%b7%b3%e6%9d%bf%e9%a1%9e%e5%be%8c%e9%96%80/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Thu, 13 Aug 2026 18:27:42 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[ad]]></category>
		<category><![CDATA[advertisement]]></category>
		<category><![CDATA[backdoor]]></category>
		<category><![CDATA[box]]></category>
		<category><![CDATA[fruad]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[proxy]]></category>
		<category><![CDATA[residential]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[television]]></category>
		<category><![CDATA[tv]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13149</guid>

					<description><![CDATA[這篇放一陣子了，兩個禮拜前看到的，在講電視棒的跳板類後門：「Read This Before You Buy That TV Streaming Stick」，作者提到的研究看起來就是對 Amazon 上面的商品分析： 在這些網拍上面會看到不少便宜的電視棒，其實是把木馬放回家裡了，這些電視棒會變成廣告惡意點擊的跳板，或是直接變成 residential proxy 的跳板： In addition to enlisting the user’s TV box in ad fraud networks, these off-brand streaming devices almost universally come with residential proxy software pre-installed. 這邊研究室透過註冊過期 C2 server 的網域後去觀察的： Pedro Falé is a threat researcher with the security firm Bitsight. Falé &#8230; <a href="https://blog.gslin.org/archives/2026/08/14/13149/%e7%b6%b2%e6%8b%8d%e9%9b%bb%e8%a6%96%e6%a3%92%e7%9a%84%e8%b7%b3%e6%9d%bf%e9%a1%9e%e5%be%8c%e9%96%80/" class="more-link">Continue reading<span class="screen-reader-text"> "網拍電視棒的跳板類後門"</span></a>]]></description>
										<content:encoded><![CDATA[<p>這篇放一陣子了，兩個禮拜前看到的，在講電視棒的跳板類後門：「<a href="https://krebsonsecurity.com/2026/07/read-this-before-you-buy-that-tv-streaming-stick/">Read This Before You Buy That TV Streaming Stick</a>」，作者提到的研究看起來就是對 <a href="https://en.wikipedia.org/wiki/Amazon_(company)">Amazon</a> 上面的商品分析：</p>
<picture><source type="image/webp" srcset="https://i.gslin.com/s/1786644353-4e497207.webp" /><img decoding="async" src="https://i.gslin.com/s/1786644353-4e497207.png" alt="" /></picture>
<p>在這些網拍上面會看到不少便宜的電視棒，其實是把木馬放回家裡了，這些電視棒會變成廣告惡意點擊的跳板，或是直接變成 residential proxy 的跳板：</p>
<blockquote><p>In addition to enlisting the user’s TV box in ad fraud networks, these off-brand streaming devices almost universally come with residential proxy software pre-installed.</p></blockquote>
<p>這邊研究室透過註冊過期 C2 server 的網域後去觀察的：</p>
<blockquote><p>Pedro Falé is a threat researcher with the security firm Bitsight. Falé told KrebsOnSecurity he was able to peer inside a vast and complex ad fraud network by registering an expired domain name that was used to coordinate fake ad clicks across a particularly popular brand of these streaming devices known as H96.</p></blockquote>
<p>然後光是這個過期的 domain 就可以追蹤到大約 38k 個 device，在這些灰色 &amp; 黑色產業上面就可以產生 US$50k/day 左右的利潤：</p>
<blockquote><p>Bitsight said it tracked approximately 38,000 TV boxes globally phoning home to the expired Fengwo Group domain, and based on that number the report estimates this ad fraud network brings in revenues of close to $50,000 a day (not counting substantial revenue from the residential proxy side of the business). However, Falé emphasized that these estimates are highly conservative and based on telemetry from just one of the Fengwo Group’s core (but older) domains.</p></blockquote>
<p>雖然知道問題，但要擊破其實很難，像是 multi-domain backup + signed commands + onion hidden services 之類的...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/08/14/13149/%e7%b6%b2%e6%8b%8d%e9%9b%bb%e8%a6%96%e6%a3%92%e7%9a%84%e8%b7%b3%e6%9d%bf%e9%a1%9e%e5%be%8c%e9%96%80/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13149</post-id>	</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 40/53 objects using APC
Page Caching using APC (Page is feed) 
Minified using APC
Database Caching using APC

Served from: blog.gslin.org @ 2026-08-22 03:27:21 by W3 Total Cache
-->