北北基桃竹高端疫苗地圖

北北基桃竹高端疫苗地圖（1/10 更新）

https://www.google.com/maps/d/edit?mid=1Kg9ivV-Mf6AImpkKJ5cff22FCrYyjWju&usp=sharing

 

資料來源： https://medigenvactw-my.sharepoint.com/personal/info_medigenvac_com/Documents/Forms/All.aspx?RootFolder=%2Fpersonal%2Finfo%5Fmedigenvac%5Fcom%2FDocuments%2F%E9%AB%98%E7%AB%AF%E6%96%B0%E5%86%A0%E8%82%BA%E7%82%8E%E7%96%AB%E8%8B%97%E5%85%A8%E5%8F%B0%E6%8E%A5%E7%A8%AE%E9%86%AB%E7%99%82%E9%99%A2%E6%89%80

美國運通 / HSBC 匯豐卡 2022 優惠地圖

在手機上打開地圖後，會自動存放到 Google Maps app 中「已儲存」內的「地圖」中。

美國運通 2022 餐飲優惠地圖

含年度優惠 & Live the World

地圖連結： https://www.google.com/maps/d/u/0/edit?mid=1GlYysvhYP2ieUHZRGWEwJ-WiOa_zYZpo&usp=sharing

HSBC 匯豐卡 2022 優惠地圖

地圖連結： https://www.google.com/maps/d/u/0/edit?mid=1WuI0Db5C0yAzkRT_OYDDze1Bz0j5iOk7&usp=sharing

---

美國運通簽帳白金卡 2021 優惠

2021 住宿優惠

（含年度優惠 & Live the World）

2021 餐飲優惠

（含年度優惠 & Live the World）

Tab Groups + Firefox Quantum (v57)

(Chinese below, Medium link)

Because Firefox will start removing XUL interface and it’s related codes, Firefox Quantum (v57) begin to disable extensions developed with legacy (non-WebExtension) API.

It’s been a significant impact on my working environment, with 400+ tabs organizing in 28 groups with Tab Groups (formally Panorama), which is a must for me.

So I will stay on Firefox 56 as long as possible…

Well… Im NOT staying in Firefox 56. There is actually a way to keep Tab Groups working in Firefox Quantum.

因為 Firefox Quantum (57) 開始陸續要移除 XUL 介面，因此正式把非 WebExtensions 的套件停用了。對我的整個瀏覽器環境，影響最大的是，用以組織 400 個以上分頁成為 28 個專案的 Tab Groups「分頁群組 / Panorama」即將無法使用。

所以我決定要死守 Firefox 56⋯⋯沒有啦，還是可以用啦，其實！

Here is how to make Tab Groups working in Firefox Quantum,

1. Download and install last Firefox 57 Beta (57.0b14) and open it .
2. Open about:config?filter=extensions.legacy.enabled In URL, double-click to set the value to true, restart Firefox 57 Beta.
3. Open Tab Groups page listed on AMO.
4. Youll notice [+Add to Firefox] button is unclickable. Right-click on the button, choose Save Link As… to download .xpi file.
5. Drag & drop the .xpi file into Firefox window and install it. After installed, check for Tab Group icon shows up on top-right, to make sure its enabled.
6. Shutdown Firefox Beta, and open Firefox Quantum (v57)
7. Youll notice Tab Groups working fine on Firefox Quantum!

經過這週的持續實驗，確認在 Firefox 57 釋出後，分頁群組仍然能（有條件的）運作。方法是：

1. 下載安裝 Firefox 57 最終 Beta (57.0b14) 。
2. 打開 about:config?filter=extensions.legacy.enabled，點兩下將其值設定為 true，關閉重開 Firefox 57 Beta。
3. 打開 Firefox 擴充套件網站的 Tab Groups 頁面。
4. 你會發現「+新增至 Firefox」按鈕無法點擊。在按鈕上按右鍵，選擇鏈結另存新檔。
5. 將下載後的 xpi 檔拖拉到 Firefox 視窗上，就能正常安裝。
6. 待安裝完成之後，關閉 Firefox Beta，再打開 Firefox Quantum (v57) 正式版
7. 你會看到持續正常運作中的分頁群組！

I assumed its a bug and not a Feature. The process will cease to function soon after Firefox 58 release. Thanks for it to enabling the upgrade of my working profile to Quantum anyway.

預期這個方法到 Firefox 58 應該就會失效（如果開啟 Firefox (v58) Beta，Tab Groups 會被再次停用）。雖然這應該是個 Bug 不是 Feature，不過還是感謝它能讓我的作業環境正式升級到 Quantum。

After testing for few days, I notice that sometimes Tab Group will randomly disappear (with all tabs in other groups).

Dont panic! You just need to close Firefox, reopen Firefox 57 Beta, go to AMO Tab Group page, and click [+Install to Firefox]. It will resume working after reinstalling addon, and your tabs will still there.

經過幾天測試，分頁群組偶而會失效。此時只要關閉 Firefox，重新開啟 Firefox 57 Beta，再到 AMO 上點選「+新增至 Firefox」即可恢復正常。

I’ll keep using Firefox Quantum (v57) until the most critical WebExtension API "Hiding & showing tabs" (Bug 1384515) landed, and successor of Tab Groups been giving birth.

The patch and proof of concept from Dietrich and :johannh had been uploaded for three months, but I’m not able to follow the long, long thread of comments on that bug recently.

接著應該會繼續用這個方式用 57.0 頂著，直到 WebExtension API 中最關鍵的「隱藏分頁」API 完成，並有人開發出分頁群組替代品吧。

（Patch 以及驗證概念的測試套件都提出三個月了，最近吵了一長串，看不懂是什麼狀況⋯⋯）

Besides the above method, I’d also been tested Waterfox for last month. The current Waterfox is developed based on Firefox 55, and they planned to release ESR version based on Firefox 56 soon, with security patch backport from latest Firefox.

It may be another good choice, if you want to have Tab Groups, and not really care about the speed of Quantum.

在還未實驗出以上 Workaround 之前，我也測試了一個月的 Waterfox。該分支目前版本是 55.2.0，計畫近期要釋出基於 56 的長期版本，然後持續 backport 新版 Firefox 的安全性更新。如果不必然堅持要享受 57 的速度差異，也是一個可考慮的穩定選擇。

Please correct our country’s name from “Taiwan, Province of China” to “Taiwan” on Access Now’s website

An open letter to Access Now

Hi,

I’m Irvin, Mozilla contributor from Taiwan. I had contributing to internet Human Right policy advocacy for years and had joined last year’s RightsCon.

Recently I notice that Access Now wrongly list my country’s name as “Taiwan, Province of China” on the campaign page country drop-down list (eg., Take Action - Access Now ). Please correct it and listing our country as "Taiwan" or "Taiwan (Republic of China)" (our formal name).

I believe you had wrongly followed ISO 3166-2, this name list wrongly put Taiwan under "province of China", following UNs POV, we all know how bias it can be.

Taiwan had never been a province of current China Communist government, although they always claimed as it, and force other country to acknowledge it as "One-China Policy".

We are an independent island country, with 23M inhabitants. We had democracy government with elected presidents, no internet regulation, not behind the great firewall, and in no favor of totalitarianism.

We had strong civil society and diversity civil hacker communities such as g0v, famous civil hacker community. We even have legally gay marriage (start from 2019).

You can read the whole story in articles below. In short, we had been an independent political entity since 1949, when KMT party lose their civil war against Communist Party in China and retreat to this island.

• Taiwan country profile - BBC News
• Political status of Taiwan - Wikipedia
• Cross-Strait relations - Wikipedia

Some Best practice,

• Mozilla — Lists of Countries and Regions - MozillaWiki
• FreeBSD — Internationalization Policy

Please correct our name in Access Nows country list, just simply list it as Taiwan.

Very thanks,

Irvin Chen
Community Liaison,
MozTW (Mozilla Taiwan Community)

(Medium link)

Concerning about how add-on auto-reviewing process can hurt user’s trust to Firefox

(Cross-post from Mozilla Discourse and Medium)

What is the price for us to eliminating the reviewing queue with robots? (picture from Mozilla Wiki)

Most people don’t know that we’re now using an automatically-approval process on AMO for Firefox Add-on review (since mid. September)*, which means, our program will check for known problems and threats in new add-ons, and if not found, it will get published without any manual process.

* Extension review wait times are about to get much shorter (blog.mozilla.org)

The benefit is time. Some addon author already found that the reviewing process is incredibly quick, that it will get published in just a few minutes after uploaded new version.

However, the automatically approved system (which Chrome used for many years) had been considering harmful for general user, because it can be the routes for malware to get into user’s browser, and we can only stop and fix it after someone discovered and reported back, and cannot prevent in advance with current manual reviewing process.

And this bad part had ALREADY happened just in that week after the automatically review process up. Two weeks ago, we discover several add-ons had bound with mining codes on AMO. After some research, we found 7 add-ons with the same codes in the end.

• Mining codes been discovered in two reviewed add-ons from "Add-ons for Firefox" site. (r/firefox)

• /g/ - >bitcoin miner in firefox addons. >addons are aut - Technology - 4chan (boards.4chan.org)

Although the editor had banned them, the MALICIOUS ADD-ONs had already got into user’s computer. We didn’t know how many users were affected nor how many mal-addons left there in public.

Many people (including me) feel that AMO is not trustworthy anymore because of the potential threat. Without fully manual review, we need to assume that every add-on appears on AMO can be dangerous.

The manual review process had always been considering one of the better things Firefox’s eco-system over Chrome, that the reviewer will not only check for the malicious codes, but also help addon author to follow some best practice (eg., using the known version of libraries such as jQuery from official site).

And because of the manual reviewing process, we told general user that they need to be aware for Add-on installed from other sites, and they can trust the one listed on AMO.

With non-manual checking Add-ons (and the fact that dangerous code can be live there), we cannot trust any AMO add-ons now. Even for those been manual reviewed, because we just cannot tell which one had been check and which is not apart.

Even worst, some normal add-ons may be updated with malicious codes, been auto-approval and push into user’s browser with our auto-update mechanism anytime.

Many people are asking for purchasing the ownership of my add-ons from time to time in past, that they want to earn the profit by adding Ads to it. Guess what they want to do for now if they discover the change of reviewing process?

According to the discussion on AMO blog article, on IRC addon channel, Reddit, 4chan, Telegram and within above and below links, many contributors including volunteering reviewers, Add-on authors and users already raise the concern about safety and trust problem, before and after the change.

• Mozilla changes review process for Firefox WebExtensions - gHacks Tech News (www.ghacks.net)

• Mozilla needs to adjust new review process for Firefox add-ons - gHacks Tech News (www.ghacks.net)

They didn’t get the answers before the auto-approved enabling. And they saw the incidents happened. Besides removing those add-ons which been reported, there is still lack of any steps and strategies to prevent future incidents happening again.

My question is — How can we still convince users that Firefox eco-system is still TRUSTWORTHY? If even myself found it’s not trustful anymore.

Please join with me and represent your concern on the Discourse thread.