<?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>Thu, 18 Jun 2026 23:44:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</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>RFC 超過 10000 了</title>
		<link>https://blog.gslin.org/archives/2026/06/19/13075/rfc-%e8%b6%85%e9%81%8e-10000-%e4%ba%86/</link>
					<comments>https://blog.gslin.org/archives/2026/06/19/13075/rfc-%e8%b6%85%e9%81%8e-10000-%e4%ba%86/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Thu, 18 Jun 2026 23:40:57 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[10000]]></category>
		<category><![CDATA[10k]]></category>
		<category><![CDATA[comments]]></category>
		<category><![CDATA[document]]></category>
		<category><![CDATA[for]]></category>
		<category><![CDATA[request]]></category>
		<category><![CDATA[rfc]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13075</guid>

					<description><![CDATA[在 Hacker News 上看到「RFC 10008: The new HTTP Query Method (rfc-editor.org)」的第一個反應不是 HTTP 在搞什麼，而是 RFC 破萬了... 一萬之前最後一個是 9998 的「RFC 9998: Report from the IAB/W3C Workshop on Age-Based Restrictions on Content Access」，而一萬以後第一個是「RFC 10008: The HTTP QUERY Method」，中間跳過的部分在「[Tools-discuss] Re: [Rswg] Re: Re: March tools update」這邊有提到不需要用 RFC 10000 當作測試，而且 RFC 10000 不會留給愚人節用： There isn't a need to publish RFC &#8230; <a href="https://blog.gslin.org/archives/2026/06/19/13075/rfc-%e8%b6%85%e9%81%8e-10000-%e4%ba%86/" class="more-link">Continue reading<span class="screen-reader-text"> "RFC 超過 10000 了"</span></a>]]></description>
										<content:encoded><![CDATA[<p>在 <a href="https://en.wikipedia.org/wiki/Hacker_News">Hacker News</a> 上看到「<a href="https://news.ycombinator.com/item?id=48568502">RFC 10008: The new HTTP Query Method (rfc-editor.org)</a>」的第一個反應不是 <a href="https://en.wikipedia.org/wiki/HTTP">HTTP</a> 在搞什麼，而是 <a href="https://en.wikipedia.org/wiki/Request_for_Comments">RFC</a> 破萬了...</p>
<p>一萬之前最後一個是 9998 的「<a href="https://www.rfc-editor.org/info/rfc9998/">RFC 9998: Report from the IAB/W3C Workshop on Age-Based Restrictions on Content Access</a>」，而一萬以後第一個是「<a href="https://www.rfc-editor.org/info/rfc10008/">RFC 10008: The HTTP QUERY Method</a>」，中間跳過的部分在「<a href="https://mailarchive.ietf.org/arch/msg/tools-discuss/EpoQcVt_mR8mfvEoW3zu2pMb_j0/">[Tools-discuss] Re: [Rswg] Re: Re: March tools update</a>」這邊有提到不需要用 RFC 10000 當作測試，而且 RFC 10000 不會留給愚人節用：</p>
<blockquote><p>There isn't a need to publish RFC 10000 as a test document because we have a dedicated testing environment for the new queue management system and website. And RFC 10000 couldn't be issued as an April 1 RFC because the new infrastructure won't yet be in place to support it.</p></blockquote>
<p>不過中間跳過其他的部分就沒看到了，理論上有些應該是被 book 的，後續應該會看到... 另外也沒有說 10000 這組有沒有被 book，到時候一起看看？</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/19/13075/rfc-%e8%b6%85%e9%81%8e-10000-%e4%ba%86/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13075</post-id>	</item>
		<item>
		<title>Salesforce 買 Fin (Intercom)</title>
		<link>https://blog.gslin.org/archives/2026/06/16/13074/salesforce-%e8%b2%b7-fin-intercom/</link>
					<comments>https://blog.gslin.org/archives/2026/06/16/13074/salesforce-%e8%b2%b7-fin-intercom/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Tue, 16 Jun 2026 10:23:58 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Financial]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[acquire]]></category>
		<category><![CDATA[acquisition]]></category>
		<category><![CDATA[fin]]></category>
		<category><![CDATA[intercom]]></category>
		<category><![CDATA[merge]]></category>
		<category><![CDATA[salesforce]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13074</guid>

					<description><![CDATA[看到 Salesforce 打算要買下 Fin (Intercom) 的新聞稿：「Salesforce Signs Definitive Agreement to Acquire Fin (via)」。 預定是 US$3.6B： Under the terms of the agreement, Salesforce will acquire Fin for approximately $3.6 billion, subject to customary purchase price adjustments. 然後是時間表，看起來會在明年發生，會需要 antitrust 相關的審查？ The transaction is expected to close in the fourth quarter of Salesforce’s fiscal year 2027, subject to &#8230; <a href="https://blog.gslin.org/archives/2026/06/16/13074/salesforce-%e8%b2%b7-fin-intercom/" class="more-link">Continue reading<span class="screen-reader-text"> "Salesforce 買 Fin (Intercom)"</span></a>]]></description>
										<content:encoded><![CDATA[<p>看到 <a href="https://en.wikipedia.org/wiki/Salesforce">Salesforce</a> 打算要買下 Fin (<a href="https://en.wikipedia.org/wiki/Fin_(company)">Intercom</a>) 的新聞稿：「<a href="https://www.salesforce.com/news/press-releases/2026/06/15/salesforce-signs-definitive-agreement-to-acquire-fin/?bc=HL">Salesforce Signs Definitive Agreement to Acquire Fin</a> (<a href="https://news.ycombinator.com/item?id=48540126">via</a>)」。</p>
<p>預定是 US$3.6B：</p>
<blockquote><p>Under the terms of the agreement, Salesforce will acquire Fin for approximately $3.6 billion, subject to customary purchase price adjustments.</p></blockquote>
<p>然後是時間表，看起來會在明年發生，會需要 <a href="https://en.wikipedia.org/wiki/United_States_antitrust_law">antitrust</a> 相關的審查？</p>
<blockquote><p>The transaction is expected to close in the fourth quarter of Salesforce’s fiscal year 2027, subject to the satisfaction of customary closing conditions, including the receipt of required regulatory clearances. Based on the expected timing of closing of the transaction, there is no anticipated change to Salesforce’s fiscal year 2027 financial guidance, previously announced on May 27, 2026. The transaction will not impact Salesforce’s capital return program.</p></blockquote>
<p>要變成 <a href="https://en.wikipedia.org/wiki/Slack_Technologies">Slack</a> 的同伴了...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/16/13074/salesforce-%e8%b2%b7-fin-intercom/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13074</post-id>	</item>
		<item>
		<title>x86-64 轉 aarch64 的靜態翻譯</title>
		<link>https://blog.gslin.org/archives/2026/06/14/13073/x86-64-%e8%bd%89-aarch64-%e7%9a%84%e9%9d%9c%e6%85%8b%e7%bf%bb%e8%ad%af/</link>
					<comments>https://blog.gslin.org/archives/2026/06/14/13073/x86-64-%e8%bd%89-aarch64-%e7%9a%84%e9%9d%9c%e6%85%8b%e7%bf%bb%e8%ad%af/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sun, 14 Jun 2026 06:45:15 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[aarch64]]></category>
		<category><![CDATA[arm]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[compiler]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[size]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[static]]></category>
		<category><![CDATA[transcompiler]]></category>
		<category><![CDATA[transpiler]]></category>
		<category><![CDATA[x86-64]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13073</guid>

					<description><![CDATA[上個月看到這篇直接 x86-64 轉 aarch64 的靜態翻譯 (算是 assmelby 等級的 transpiler)：「Deterministic Fully-Static Whole-Binary Translation without Heuristics (via)」。 x86-64 到 aarch64 這個主題自從 Apple 搞出自己的方案後就變成熱門的主題了 (可憐的 Microsoft？)。 雖然是靜態翻譯 (執行事前就先翻譯好)，但跑出來的效能算能打的，比 QEMU 的模擬快，比較明顯的缺是是程式碼的大小，靜態翻譯出來的版本是 native 版本的 47.5～62.5 倍：(這邊有原始的 source code) Elevator’s translated .text is 47.5× to 62.5× larger than natively-compiled AArch64 .text across SPECint 2006[.] 其實蠻有趣的...]]></description>
										<content:encoded><![CDATA[<p>上個月看到這篇直接 <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a> 轉 <a href="https://en.wikipedia.org/wiki/AArch64">aarch64</a> 的靜態翻譯 (算是 assmelby 等級的 <a href="https://en.wikipedia.org/wiki/Source-to-source_compiler">transpiler</a>)：「<a href="https://arxiv.org/abs/2605.08419">Deterministic Fully-Static Whole-Binary Translation without Heuristics</a> (<a href="https://news.ycombinator.com/item?id=48117810">via</a>)」。</p>
<p>x86-64 到 aarch64 這個主題自從 <a href="https://en.wikipedia.org/wiki/Apple_Inc.">Apple</a> 搞出自己的方案後就變成熱門的主題了 (可憐的 <a href="https://en.wikipedia.org/wiki/Microsoft">Microsoft</a>？)。</p>
<p>雖然是靜態翻譯 (執行事前就先翻譯好)，但跑出來的效能算能打的，比 <a href="https://en.wikipedia.org/wiki/QEMU">QEMU</a> 的模擬快，比較明顯的缺是是程式碼的大小，靜態翻譯出來的版本是 native 版本的 47.5～62.5 倍：(這邊有原始的 source code)</p>
<blockquote><p>Elevator’s translated .text is 47.5× to 62.5× larger than natively-compiled AArch64 .text across SPECint 2006[.]</p></blockquote>
<p>其實蠻有趣的...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/14/13073/x86-64-%e8%bd%89-aarch64-%e7%9a%84%e9%9d%9c%e6%85%8b%e7%bf%bb%e8%ad%af/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13073</post-id>	</item>
		<item>
		<title>Chrome 的 Manifest V2 的拔除的末章</title>
		<link>https://blog.gslin.org/archives/2026/06/14/13072/chrome-%e7%9a%84-manifest-v2-%e7%9a%84%e6%8b%94%e9%99%a4%e7%9a%84%e6%9c%ab%e7%ab%a0/</link>
					<comments>https://blog.gslin.org/archives/2026/06/14/13072/chrome-%e7%9a%84-manifest-v2-%e7%9a%84%e6%8b%94%e9%99%a4%e7%9a%84%e6%9c%ab%e7%ab%a0/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sun, 14 Jun 2026 06:30:07 +0000</pubDate>
				<category><![CDATA[Browser]]></category>
		<category><![CDATA[Computer]]></category>
		<category><![CDATA[GoogleChrome]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[WWW]]></category>
		<category><![CDATA[ad]]></category>
		<category><![CDATA[advertisement]]></category>
		<category><![CDATA[block]]></category>
		<category><![CDATA[blocker]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[chromium]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[manifest]]></category>
		<category><![CDATA[mv2]]></category>
		<category><![CDATA[origin]]></category>
		<category><![CDATA[ublock]]></category>
		<category><![CDATA[v2]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13072</guid>

					<description><![CDATA[看起來 Manifest V2 (MV2) 要進入到末章了：「Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow [Update] (via)」。 之前還有各種 flag 可以繞過限制讓 MV2 開啟，現在是連這些 flag 都要拿掉了：(現在是 149) Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option 我是跳 Firefox 一陣子了...]]></description>
										<content:encoded><![CDATA[<p>看起來 Manifest V2 (MV2) 要進入到末章了：「<a href="https://www.neowin.net/news/google-chrome-is-killing-all-ublock-origin-bypasses-microsoft-edge-opera-to-follow/">Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow [Update]</a> (<a href="https://news.ycombinator.com/item?id=48471970">via</a>)」。</p>
<p>之前還有各種 flag 可以繞過限制讓 MV2 開啟，現在是連這些 flag 都要拿掉了：(現在是 149)</p>
<blockquote><p>Chromium 150 lost <code>ExtensionManifestV2Disabled</code> option<br />
Chromium 151 will loose <code>ExtensionManifestV2Unsupported</code> option<br />
Chromium 151 will loose <code>ExtensionManifestV2Availability</code> option<br />
Chromium 151 will likely loose <code>AllowLegacyMV2Extensions</code> option</p></blockquote>
<p>我是跳 <a href="https://en.wikipedia.org/wiki/Firefox">Firefox</a> 一陣子了...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/14/13072/chrome-%e7%9a%84-manifest-v2-%e7%9a%84%e6%8b%94%e9%99%a4%e7%9a%84%e6%9c%ab%e7%ab%a0/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13072</post-id>	</item>
		<item>
		<title>AWS 的 Graviton5 系列出了</title>
		<link>https://blog.gslin.org/archives/2026/06/14/13071/aws-%e7%9a%84-graviton5-%e7%b3%bb%e5%88%97%e5%87%ba%e4%ba%86/</link>
					<comments>https://blog.gslin.org/archives/2026/06/14/13071/aws-%e7%9a%84-graviton5-%e7%b3%bb%e5%88%97%e5%87%ba%e4%ba%86/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sun, 14 Jun 2026 05:24:12 +0000</pubDate>
				<category><![CDATA[AWS]]></category>
		<category><![CDATA[Cloud]]></category>
		<category><![CDATA[Computer]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Infrastructure]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[amazon]]></category>
		<category><![CDATA[arm]]></category>
		<category><![CDATA[aws]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[ec2]]></category>
		<category><![CDATA[graviton]]></category>
		<category><![CDATA[graviton5]]></category>
		<category><![CDATA[instance]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[service]]></category>
		<category><![CDATA[speed]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13071</guid>

					<description><![CDATA[看到 AWS 的 Graviton5 的消息：「Now available: Amazon EC2 M9g and M9gd instances powered by new AWS Graviton5 processors」。 官方宣傳 25%～35% 的提升： Graviton5 offers up to 25% better compute performance compared to Graviton4-based instances, with up to 35% faster performance for web applications, up to 35% for machine learning inference, and up to 30% for databases. &#8230; <a href="https://blog.gslin.org/archives/2026/06/14/13071/aws-%e7%9a%84-graviton5-%e7%b3%bb%e5%88%97%e5%87%ba%e4%ba%86/" class="more-link">Continue reading<span class="screen-reader-text"> "AWS 的 Graviton5 系列出了"</span></a>]]></description>
										<content:encoded><![CDATA[<p>看到 <a href="https://en.wikipedia.org/wiki/Amazon_Web_Services">AWS</a> 的 Graviton5 的消息：「<a href="https://aws.amazon.com/blogs/aws/now-available-amazon-ec2-m9g-and-m9gd-instances-powered-by-new-aws-graviton5-processors/">Now available: Amazon EC2 M9g and M9gd instances powered by new AWS Graviton5 processors</a>」。</p>
<p>官方宣傳 25%～35% 的提升：</p>
<blockquote><p>Graviton5 offers up to 25% better compute performance compared to Graviton4-based instances, with up to 35% faster performance for web applications, up to 35% for machine learning inference, and up to 30% for databases.</p></blockquote>
<p>看起來這次主力的點是六倍的 L3 cache (5 times more)：</p>
<blockquote><p>As the first CPU in the AWS fleet to support the latest generation of PCIe Gen6 and DDR5-8800 memory, AWS Graviton5 instances deliver the fastest memory of any processor instances in the cloud, and 5 times more L3 cache compared to the previous generation.</p></blockquote>
<p>然後是各類 i/o 頻寬的頻寬提升：</p>
<blockquote><p>Networking and storage bandwidth have been expanded to keep pace with compute growth. M9g and M9gd instances offer up to 15% higher network bandwidth and 20% higher Amazon Elastic Block Store (Amazon EBS) bandwidth on average across sizes, with up to twice the network bandwidth for the largest instance size.</p></blockquote>
<p>從 EC2 instance 這邊的價錢比較，看起來比上個世代貴 9% 左右。</p>
<p>比較好奇的是還沒撞到頂啊...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/14/13071/aws-%e7%9a%84-graviton5-%e7%b3%bb%e5%88%97%e5%87%ba%e4%ba%86/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13071</post-id>	</item>
		<item>
		<title>微軟刻意不發新的憑證以淘汰舊版的 Office 2019 (Mac)</title>
		<link>https://blog.gslin.org/archives/2026/06/14/13070/%e5%be%ae%e8%bb%9f%e5%88%bb%e6%84%8f%e4%b8%8d%e7%99%bc%e6%96%b0%e7%9a%84%e6%86%91%e8%ad%89%e4%bb%a5%e6%b7%98%e6%b1%b0%e8%88%8a%e7%89%88%e7%9a%84-office-2019-mac/</link>
					<comments>https://blog.gslin.org/archives/2026/06/14/13070/%e5%be%ae%e8%bb%9f%e5%88%bb%e6%84%8f%e4%b8%8d%e7%99%bc%e6%96%b0%e7%9a%84%e6%86%91%e8%ad%89%e4%bb%a5%e6%b7%98%e6%b1%b0%e8%88%8a%e7%89%88%e7%9a%84-office-2019-mac/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sun, 14 Jun 2026 00:01:08 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[MacOS]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[2019]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[digital]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[macos]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>
		<category><![CDATA[signature]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[support]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13070</guid>

					<description><![CDATA[微軟刻意不發 Office 2019 for Mac 的新版憑證，藉此淘汰掉舊版的 Office 2019：「Microsoft Office 2019 and 2021 for Mac view-only conversion (2026) (via)」。 以西方的習慣，在真的不提供後應該會有訴訟要打，因為從 2023 年的時候文字是可以看到有 continue to function 的文字，表示有承諾軟體即使在 2023 年以後也還是可以運作的： Support for Office 2019 for Mac will end on October 10, 2023. Rest assured that all your Office 2019 apps will continue to function—they won't disappear from your &#8230; <a href="https://blog.gslin.org/archives/2026/06/14/13070/%e5%be%ae%e8%bb%9f%e5%88%bb%e6%84%8f%e4%b8%8d%e7%99%bc%e6%96%b0%e7%9a%84%e6%86%91%e8%ad%89%e4%bb%a5%e6%b7%98%e6%b1%b0%e8%88%8a%e7%89%88%e7%9a%84-office-2019-mac/" class="more-link">Continue reading<span class="screen-reader-text"> "微軟刻意不發新的憑證以淘汰舊版的 Office 2019 (Mac)"</span></a>]]></description>
										<content:encoded><![CDATA[<p>微軟刻意不發 <a href="https://en.wikipedia.org/wiki/Microsoft_Office_2019">Office 2019</a> for Mac 的新版憑證，藉此淘汰掉舊版的 Office 2019：「<a href="https://consumerrights.wiki/w/Microsoft_Office_2019_and_2021_for_Mac_view-only_conversion_(2026)">Microsoft Office 2019 and 2021 for Mac view-only conversion (2026)</a> (<a href="https://news.ycombinator.com/item?id=48341578">via</a>)」。</p>
<p>以西方的習慣，在真的不提供後應該會有訴訟要打，因為從 2023 年的時候文字是可以看到有 <strong>continue to function</strong> 的文字，表示有承諾軟體即使在 2023 年以後也還是可以運作的：</p>
<blockquote><p>Support for Office 2019 for Mac will end on October 10, 2023. Rest assured that all your Office 2019 apps will continue to function—they won't disappear from your Mac, nor will you lose any data. However, you could expose yourself to serious and potentially harmful security risks.</p></blockquote>
<picture><source type="image/webp" srcset="https://i.gslin.com/s/1781394696-7196dc56.webp" /><img decoding="async" src="https://i.gslin.com/s/1781394696-7196dc56.png" alt="" /></picture>
<p>2026 年的時候可以看到 <strong>continue to function</strong> 的文字被拔掉了：</p>
<blockquote><p>Support for Office 2019 for Mac ended on October 10, 2023. Rest assured that all your Office 2019 apps won't lose any data. Your data can be accessed on any supported Microsoft 365 or Office product. However, you could expose yourself to serious and potentially harmful security risks.</p></blockquote>
<picture><source type="image/webp" srcset="https://i.gslin.com/s/1781394752-81e02128.webp" /><img decoding="async" src="https://i.gslin.com/s/1781394752-81e02128.png" alt="" /></picture>
<p>這邊有幾個議題可以拿出來討論，第一個當然是為什麼要有 digital signature 才能跑的老問題，第二個則是微軟違反合約的問題。</p>
<p>這邊剛好有個蘋果本家在今年年初，替老設備展延憑證的事情剛好與這件事情有點類似的地方：「<a href="https://blog.gslin.org/archives/2026/01/27/12869/%E9%9A%94%E4%BA%86%E4%B8%89%E5%B9%B4-ios-12-%E6%9B%B4%E6%96%B0%EF%BC%9A12-5-8/">隔了三年 iOS 12 更新：12.5.8</a>」，這個 <a href="https://en.wikipedia.org/wiki/IOS_12">iOS 12</a> 的更新不是安全性更新，而是展延憑證，讓 <a href="https://en.wikipedia.org/wiki/IMessage">iMessage</a> 與 <a href="https://en.wikipedia.org/wiki/FaceTime">FaceTime</a> 可以繼續使用。</p>
<p>七月後再看新消息...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/14/13070/%e5%be%ae%e8%bb%9f%e5%88%bb%e6%84%8f%e4%b8%8d%e7%99%bc%e6%96%b0%e7%9a%84%e6%86%91%e8%ad%89%e4%bb%a5%e6%b7%98%e6%b1%b0%e8%88%8a%e7%89%88%e7%9a%84-office-2019-mac/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13070</post-id>	</item>
		<item>
		<title>FFmpeg 又被拿出來鞭安全問題了，這次有 21 個 0-day</title>
		<link>https://blog.gslin.org/archives/2026/06/14/13069/ffmpeg-%e5%8f%88%e8%a2%ab%e6%8b%bf%e5%87%ba%e4%be%86%e9%9e%ad%e5%ae%89%e5%85%a8%e5%95%8f%e9%a1%8c%e4%ba%86%ef%bc%8c%e9%80%99%e6%ac%a1%e6%9c%89-21-%e5%80%8b-0-day/</link>
					<comments>https://blog.gslin.org/archives/2026/06/14/13069/ffmpeg-%e5%8f%88%e8%a2%ab%e6%8b%bf%e5%87%ba%e4%be%86%e9%9e%ad%e5%ae%89%e5%85%a8%e5%95%8f%e9%a1%8c%e4%ba%86%ef%bc%8c%e9%80%99%e6%ac%a1%e6%9c%89-21-%e5%80%8b-0-day/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sat, 13 Jun 2026 17:52:59 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[0-day]]></category>
		<category><![CDATA[ai]]></category>
		<category><![CDATA[ffmpeg]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[large]]></category>
		<category><![CDATA[llm]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13069</guid>

					<description><![CDATA[FFmpeg 的安全性問題為人詬病許久，所以如果 LLM 找不出東西的話，代表你用的 model 可能太弱了，所以看到 AI 相關的公司拿 FFmpeg 出來秀肌肉的話，你心裡大概就有底是什麼東西了：「21 Zero-Days in FFmpeg (via)」。 比較有趣的反而是 Hacker News 上面有人提到十多年前 Google 搞的「FFmpeg and a thousand fixes」，這個有點印象，當時用 fuzzing 的方式撈出了很多問題，有些是 software bug，而有些是 security issue： One internal fuzzing effort we have been running continuously for the past two years is the testing process of FFmpeg, a large cross-platform solution to &#8230; <a href="https://blog.gslin.org/archives/2026/06/14/13069/ffmpeg-%e5%8f%88%e8%a2%ab%e6%8b%bf%e5%87%ba%e4%be%86%e9%9e%ad%e5%ae%89%e5%85%a8%e5%95%8f%e9%a1%8c%e4%ba%86%ef%bc%8c%e9%80%99%e6%ac%a1%e6%9c%89-21-%e5%80%8b-0-day/" class="more-link">Continue reading<span class="screen-reader-text"> "FFmpeg 又被拿出來鞭安全問題了，這次有 21 個 0-day"</span></a>]]></description>
										<content:encoded><![CDATA[<p><a href="https://en.wikipedia.org/wiki/FFmpeg">FFmpeg</a> 的安全性問題為人詬病許久，所以如果 <a href="https://en.wikipedia.org/wiki/Large_language_model">LLM</a> 找不出東西的話，代表你用的 model 可能太弱了，所以看到 AI 相關的公司拿 FFmpeg 出來秀肌肉的話，你心裡大概就有底是什麼東西了：「<a href="https://depthfirst.com/research/21-zero-days-in-ffmpeg">21 Zero-Days in FFmpeg</a> (<a href="https://news.ycombinator.com/item?id=48510046">via</a>)」。</p>
<p>比較有趣的反而是 <a href="https://en.wikipedia.org/wiki/Hacker_News">Hacker News</a> 上面有人提到十多年前 <a href="https://en.wikipedia.org/wiki/Google">Google</a> 搞的「<a href="https://security.googleblog.com/2014/01/ffmpeg-and-thousand-fixes.html">FFmpeg and a thousand fixes</a>」，這個有點印象，當時用 fuzzing 的方式撈出了很多問題，有些是 software bug，而有些是 security issue：</p>
<blockquote><p>One internal fuzzing effort we have been running continuously for the past two years is the testing process of FFmpeg, a large cross-platform solution to record, convert and stream audio and video written in C.</p></blockquote>
<p>好像是當時對 fuzzing 這個方法的火力展示？</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/14/13069/ffmpeg-%e5%8f%88%e8%a2%ab%e6%8b%bf%e5%87%ba%e4%be%86%e9%9e%ad%e5%ae%89%e5%85%a8%e5%95%8f%e9%a1%8c%e4%ba%86%ef%bc%8c%e9%80%99%e6%ac%a1%e6%9c%89-21-%e5%80%8b-0-day/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13069</post-id>	</item>
		<item>
		<title>美國政府出手禁止 Anthropic 提供 Fable 5 服務</title>
		<link>https://blog.gslin.org/archives/2026/06/13/13068/%e7%be%8e%e5%9c%8b%e6%94%bf%e5%ba%9c%e5%87%ba%e6%89%8b%e7%a6%81%e6%ad%a2-anthropic-%e6%8f%90%e4%be%9b-fable-5-%e6%9c%8d%e5%8b%99/</link>
					<comments>https://blog.gslin.org/archives/2026/06/13/13068/%e7%be%8e%e5%9c%8b%e6%94%bf%e5%ba%9c%e5%87%ba%e6%89%8b%e7%a6%81%e6%ad%a2-anthropic-%e6%8f%90%e4%be%9b-fable-5-%e6%9c%8d%e5%8b%99/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Sat, 13 Jun 2026 02:04:17 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Political]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[5]]></category>
		<category><![CDATA[ai]]></category>
		<category><![CDATA[anthropic]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[export]]></category>
		<category><![CDATA[fable]]></category>
		<category><![CDATA[government]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[large]]></category>
		<category><![CDATA[llm]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[mythos]]></category>
		<category><![CDATA[national]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[states]]></category>
		<category><![CDATA[united]]></category>
		<category><![CDATA[us]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13068</guid>

					<description><![CDATA[如標題，炸了：「Statement on the US government directive to suspend access to Fable 5 and Mythos 5 (via)」。 下出口管制禁令，而且包括 Anthropic 內非美國籍的員工： The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign &#8230; <a href="https://blog.gslin.org/archives/2026/06/13/13068/%e7%be%8e%e5%9c%8b%e6%94%bf%e5%ba%9c%e5%87%ba%e6%89%8b%e7%a6%81%e6%ad%a2-anthropic-%e6%8f%90%e4%be%9b-fable-5-%e6%9c%8d%e5%8b%99/" class="more-link">Continue reading<span class="screen-reader-text"> "美國政府出手禁止 Anthropic 提供 Fable 5 服務"</span></a>]]></description>
										<content:encoded><![CDATA[<p>如標題，炸了：「<a href="https://www.anthropic.com/news/fable-mythos-access">Statement on the US government directive to suspend access to Fable 5 and Mythos 5</a> (<a href="https://news.ycombinator.com/item?id=48511072">via</a>)」。</p>
<p>下出口管制禁令，而且包括 <a href="https://en.wikipedia.org/wiki/Anthropic">Anthropic</a> 內非美國籍的員工：</p>
<blockquote><p>The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees. The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance. Access to all other Anthropic models will not be affected.</p></blockquote>
<p>目前只能先 rollback 回 Opus 4.8 了，剛好來感覺一下差異...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/13/13068/%e7%be%8e%e5%9c%8b%e6%94%bf%e5%ba%9c%e5%87%ba%e6%89%8b%e7%a6%81%e6%ad%a2-anthropic-%e6%8f%90%e4%be%9b-fable-5-%e6%9c%8d%e5%8b%99/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13068</post-id>	</item>
		<item>
		<title>npm v12 要預設關掉 post install script 了</title>
		<link>https://blog.gslin.org/archives/2026/06/13/13067/npm-v12-%e8%a6%81%e9%a0%90%e8%a8%ad%e9%97%9c%e6%8e%89-post-install-script-%e4%ba%86/</link>
					<comments>https://blog.gslin.org/archives/2026/06/13/13067/npm-v12-%e8%a6%81%e9%a0%90%e8%a8%ad%e9%97%9c%e6%8e%89-post-install-script-%e4%ba%86/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Fri, 12 Jun 2026 23:07:25 +0000</pubDate>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[chain]]></category>
		<category><![CDATA[ecosystem]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[js]]></category>
		<category><![CDATA[manager]]></category>
		<category><![CDATA[npm]]></category>
		<category><![CDATA[package]]></category>
		<category><![CDATA[post]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[supply]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13067</guid>

					<description><![CDATA[npm 的 post install script 一直都是許多資安事件的破洞，其他各家 package manager 因為包袱比較少，都已經關的差不多了，像是 pnpm 的「Mitigating supply chain attacks」，或是 Bun 的「Add a trusted dependency」。 現在 npm 本家也進一步要處理這個問題了，npm v12 預設要關掉 post install script 了，因為這個行為可能會影響到相容性，所以有發通知出來：「Upcoming breaking changes for npm v12 (via)」。 查資料的時候發現 yarn 看起來預設還是開的，在 npm 本家都關掉的情況下應該也會關... 吧？]]></description>
										<content:encoded><![CDATA[<p><a href="https://en.wikipedia.org/wiki/Npm">npm</a> 的 post install script 一直都是許多資安事件的破洞，其他各家 package manager 因為包袱比較少，都已經關的差不多了，像是 <a href="https://en.wikipedia.org/wiki/Pnpm">pnpm</a> 的「<a href="https://pnpm.io/supply-chain-security">Mitigating supply chain attacks</a>」，或是 <a href="https://en.wikipedia.org/wiki/Bun_(software)">Bun</a> 的「<a href="https://bun.com/docs/guides/install/trusted">Add a trusted dependency</a>」。</p>
<p>現在 npm 本家也進一步要處理這個問題了，npm v12 預設要關掉 post install script 了，因為這個行為可能會影響到相容性，所以有發通知出來：「<a href="https://github.blog/changelog/2026-06-09-upcoming-breaking-changes-for-npm-v12/">Upcoming breaking changes for npm v12</a> (<a href="https://news.ycombinator.com/item?id=48467705">via</a>)」。</p>
<p>查資料的時候發現 <a href="https://en.wikipedia.org/wiki/Yarn_(package_manager)">yarn</a> 看起來預設還是開的，在 npm 本家都關掉的情況下應該也會關... 吧？</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/13/13067/npm-v12-%e8%a6%81%e9%a0%90%e8%a8%ad%e9%97%9c%e6%8e%89-post-install-script-%e4%ba%86/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13067</post-id>	</item>
		<item>
		<title>Linux 上的 Firefox 要支援 Vulkan Video Decoding 了？</title>
		<link>https://blog.gslin.org/archives/2026/06/10/13066/linux-%e4%b8%8a%e7%9a%84-firefox-%e8%a6%81%e6%94%af%e6%8f%b4-vulkan-video-decoding-%e4%ba%86%ef%bc%9f/</link>
					<comments>https://blog.gslin.org/archives/2026/06/10/13066/linux-%e4%b8%8a%e7%9a%84-firefox-%e8%a6%81%e6%94%af%e6%8f%b4-vulkan-video-decoding-%e4%ba%86%ef%bc%9f/#respond</comments>
		
		<dc:creator><![CDATA[Gea-Suan Lin]]></dc:creator>
		<pubDate>Tue, 09 Jun 2026 22:47:03 +0000</pubDate>
				<category><![CDATA[Browser]]></category>
		<category><![CDATA[Computer]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Murmuring]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[decoder]]></category>
		<category><![CDATA[decoding]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[nvidia]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[vulkan]]></category>
		<guid isPermaLink="false">https://blog.gslin.org/?p=13066</guid>

					<description><![CDATA[前幾天看到「Firefox Merges Support For Vulkan Video Decoding (via)」這個，然後也有人到我 blog 之前的「Firefox 上 YouTube 的加速」這篇下面留言提到。 看「2021722 - Add Vulkan Video path to FFmpegVideoDecoder in Firefox」是三個月前開的票，然後順利實作完了： 看 milestone 是 153 Branch，應該是三個月後的版本？目前都是 CPU 硬幹啊，現在總算是有解了...]]></description>
										<content:encoded><![CDATA[<p>前幾天看到「<a href="https://www.phoronix.com/news/Firefox-Vulkan-Video-Merged">Firefox Merges Support For Vulkan Video Decoding</a> (<a href="https://news.ycombinator.com/item?id=48439348">via</a>)」這個，然後也有人到我 blog 之前的「<a href="https://blog.gslin.org/archives/2025/12/11/12780/firefox-%e4%b8%8a-youtube-%e7%9a%84%e5%8a%a0%e9%80%9f/">Firefox 上 YouTube 的加速</a>」這篇下面留言提到。</p>
<p>看「<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2021722">2021722 - Add Vulkan Video path to FFmpegVideoDecoder in Firefox</a>」是三個月前開的票，然後順利實作完了：</p>
<picture><source type="image/webp" srcset="https://i.gslin.com/s/1781045058-4cbc0b56.webp" /><img decoding="async" src="https://i.gslin.com/s/1781045058-4cbc0b56.png" alt="" /></picture>
<p>看 milestone 是 153 Branch，應該是三個月後的版本？目前都是 CPU 硬幹啊，現在總算是有解了...</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.gslin.org/archives/2026/06/10/13066/linux-%e4%b8%8a%e7%9a%84-firefox-%e8%a6%81%e6%94%af%e6%8f%b4-vulkan-video-decoding-%e4%ba%86%ef%bc%9f/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13066</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 33/39 objects using APC
Page Caching using APC (Page is feed) 
Minified using APC
Database Caching using APC

Served from: blog.gslin.org @ 2026-06-19 08:36:20 by W3 Total Cache
-->