<?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>gogoro s &#8211; 3C 達人廖阿輝</title>
	<atom:link href="https://ahui3c.com/tag/gogoro-s/feed" rel="self" type="application/rss+xml" />
	<link>https://ahui3c.com</link>
	<description>Liao A-hui&#039;s 3C &#38; Geek news</description>
	<lastBuildDate>Fri, 21 Apr 2017 18:50:52 +0000</lastBuildDate>
	<language>zh-TW</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<atom:link rel='hub' href='https://ahui3c.com/?pushpress=hub'/>
<site xmlns="com-wordpress:feed-additions:1">126135271</site><ins class="adsbygoogle"
     style="display:block"
     data-ad-format="fluid"
     data-ad-layout-key="-f9+4w+7x-eg+3a"
     data-ad-client="ca-pub-0181345587710654"
     data-ad-slot="8394749592"></ins>
<script>
     (adsbygoogle = window.adsbygoogle || []).push({});
</script>	<item>
		<title>應不應該升級到-gogoro-s-老屁股的自說自話 [轉]</title>
		<link>https://ahui3c.com/1423/%e6%87%89%e4%b8%8d%e6%87%89%e8%a9%b2%e5%8d%87%e7%b4%9a%e5%88%b0-gogoro-s-%e8%80%81%e5%b1%81%e8%82%a1%e7%9a%84%e8%87%aa%e8%aa%aa%e8%87%aa%e8%a9%b1-%e8%bd%89</link>
		
		<dc:creator><![CDATA[廖阿輝]]></dc:creator>
		<pubDate>Mon, 28 Nov 2016 00:47:32 +0000</pubDate>
				<category><![CDATA[Gogoro 與週邊]]></category>
		<category><![CDATA[gogoro s]]></category>
		<guid isPermaLink="false">http://ahui3c.com/wp/1423</guid>

					<description><![CDATA[ Gogoro S 的上市，毫無疑問地為穩健成長中的 Gogoro 市場注射一劑強心針，當然也騷動了老屁股們的心弦，好幾位車主朋友心猿意馬，準備來個華麗變身。身為 Gogoro Plus 的第一批預購車的車主，我想客觀的探討一下這個議題。 （阿輝：本文作者為好友彭明義，感謝授權全文分享）   Gogoro S（官方圖檔） 如果經濟實力不是問題，或是尚未購車的準 Gogoro Plus 車主，我是強&#46;&#46;&#46;]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1423</post-id>	</item>
	</channel>
</rss>
