訂閱

上次更新

July 16, 2018 08:00 AM

所有時間皆為協調世界時(UTC)。

Powered By

Planet

摩茲星球 | MozTW Planet

這邊是工作人員碎碎念的地方,您可獲得最新出爐的資訊以及最不成形的想法 :P

April 08, 2018

Irvin

Run for Mozilla Rep Council

Vote for Irvin

https://medium.com/media/b786ba2853b95da7bb4e4e2e3fdb1f08/href

Hi Rep,

I’m Irvin, volunteer and rep mentor, from East Asia, Taipei, Taiwan.

I’d join Rep since spring 2013, the very beginning of the program. I’d been Mozilla volunteers even longer, as early as 2004, since my first year in college.

We all feel that the internet is so important to keep healthy, and Mozilla plays a significant role. We all want Mozilla to be strong and great. We dedicate our time for it, and Rep program can help us to do our best.

That’s why I’d like to run for Rep council.

There are no perfect projects, and I believe sometimes you also feel as difficult as I do on rep program, and on Mozilla. I feel less motivated, unclear directions, helpless issues, and we’re losing so many people, recently.

I believe that, we can fix the problem, by making Rep not only Representative of Mozilla, but also the representative of Mozillians.

My first proposal, is to start a quarterly periodic survey for Rep, to understanding our ideas of Rep program, and our feelings of Mozilla projects.

As the core contributors, we can be the funnel for Mozilla to understanding our volunteer, more and deeply. We can become the bridge between the volunteers and paid-staff.

We can help volunteers to be heard and understood, we can start a more frequent communication, help engage each other, reduce problems, and strengthen the whole community.

Please vote for me on Rep council elections. If you have any questions, please ping me on Telegram Mozillians and Rep channel, or directly reply to the video.

Thanks.

Please do also check my answers to the nominee’s QA — 
https://discourse.mozilla.org/t/important-council-elections-spring-2018-nominee-q-a/27331/4

Run for Mozilla Rep Council was originally published in Mozilla related on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at April 08, 2018 05:52 PM

February 24, 2018

Mozilla 外電聯播

Mozilla 透過開源碼支援專案投資支持 Python 生態圈

MOSS Q4: Supporting the Python Ecosystem - The Mozilla Blog

2017 年 Q4 的 Mozilla 開放原始碼支援專案(Mozilla Open Source Support program, MOSS)獲選者包含 Python 生態圈中重要的 Buildbot 與 PyPI。其他獲選則包含 HarfbuzzZappaTatoeba、Tor 專案的 Open Observatory of Network InterferenceCommento 等專案獲得資助。

MOSS 專案仍持續接受提名中,另外也正接受開源碼專案申請安全檢核服務,詳情請查閱: https://www.mozilla.org/en-US/moss/


Mozilla 透過開源碼支援專案投資支持 Python 生態圈 was originally published in moznewszh on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at February 24, 2018 08:52 AM

January 05, 2018

Mozilla 外電聯播

Activity Stream 的 Test Pilot 畢業報告

Activity Stream 的目標是為 Firefox 使用者創造與歷史紀錄及書籤互動的全新方式,「假如用戶能更容易地回到最近觀看、儲存的頁面,使用者會更開心」。

經過數次的迭代,這個新分頁的新體驗,成功從 Test Pilot 畢業進入 Firefox Quantum (v57) 了。最終的新分頁體驗,包含可調整行數的常用網站、Pocket 推薦內容(目前為美、加、德國限定),以及來自書籤及瀏覽歷史的精選網站。

Firefox Quantum 的新分頁包含常用網站、推薦與精選內容

詳細的開發與測試過程歡迎閱讀下文

Graduation Report: Activity Stream


Activity Stream 的 Test Pilot 畢業報告 was originally published in moznewszh on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at January 05, 2018 12:33 PM

December 04, 2017

Mozilla 外電聯播

為什麼只是維護一個瀏覽器,一年需要三億美元。

Mozilla 到底為什麼會用到一千兩百個員工還需要志工?

Mozilla 1200 名員工包含工程師(引擎、安全、可及性、在地化、基礎建設、雲端服務)、開發環境與開源工具(CI、測試、分析、資料收集⋯⋯)、新技術研發(例如 Rust/Servo);設計師;網頁標準工作者;行銷、發布、使用者支援;企業營運(PR、法務、財務、經理)等等。

Maintaining An Independent Browser Is Incredibly Expensive


為什麼只是維護一個瀏覽器,一年需要三億美元。 was originally published in moznewszh on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at December 04, 2017 01:14 PM

November 18, 2017

Irvin

Tab Groups + Firefox Quantum (v57)

(Chinese below, blogger link)

Updated: This method only works on Firefox 57.0 and died after 57.0.1

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… I’m NOT staying in Firefox 56. There is actually a way to keep Tab Groups working in Firefox Quantum.

更新:本方法只適用於 Firefox 57.0,57.0.1 就失效嘍。

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

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

(My daily environment) Tab Groups is still working on Firefox Quantum

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. You’ll 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 it’s enabled.
  6. Shutdown Firefox Beta, and open Firefox Quantum (v57).
  7. You’ll 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 it’s 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.

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

Don’t 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 58 應該就會失效(如果開啟 Firefox (v58) Beta,Tab Groups 會被再次停用)。雖然這應該是個 Bug 不是 Feature,不過還是感謝它能讓我的作業環境正式升級到 Quantum。

經過幾天測試,分頁群組偶而會失效。此時只要關閉 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 以及驗證概念的測試套件都提出三個月了,最近吵了一長串,看不懂是什麼狀況⋯⋯)

1384515 - Provide an API for hiding and showing individual tabs

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 的速度差異,也是一個可考慮的穩定選擇。

Waterfox - The free, open and private browser


Tab Groups + Firefox Quantum (v57) was originally published in Mozilla related on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at November 18, 2017 12:50 PM

October 10, 2017

Irvin

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

(Cross-post from Mozilla Discourse and blogger)

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

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.

https://medium.com/media/4d2ce868d658e01b408eb3c26197c8ad/href

/g/ - >bitcoin miner in firefox addons. >addons are aut - Technology - 4chan

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.

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.

Concern about how add-on auto-review can hurt user's trust to Firefox


Concerning about how add-on auto-reviewing process can hurt user’s trust to Firefox was originally published in Mozilla related on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at October 10, 2017 12:00 PM

Mozilla 外電聯播

Firefox Screenshots 的 Test Pilot 畢業報告

Page Shot 是最受歡迎的 Test Pilot 實驗項目,每日使用率高過其他功能兩倍以上;分享的流量持續成長,且也吸引非 Firefox 的用戶觀看。

Screenshots is Shipping in Firefox 56

經過 Test Pilot 測試的 Firefox 網頁抓圖分享功能「Page Shot」,正式在 Firefox 56 中以「Firefox Screenshots」名稱釋出。本文說明了 Test Pilot 時期的研究成果,與其在正式版中的功能差異。


Firefox Screenshots 的 Test Pilot 畢業報告 was originally published in moznewszh on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at October 10, 2017 11:37 AM

September 02, 2017

Mozilla 外電聯播

研究顯示 0 元上網方案無法有效引領新用戶接觸網路

Mozilla releases research results: Zero rating is not serving as an on-ramp to the internet

Mozilla 在印度、緬甸、秘魯、肯亞、奈及利亞、盧安達與南非所做的研究發現,0元上網方案(Zero-rating) 只是用戶省錢的其中一個途徑,而無法達到「讓更多人連上網際網路」的目的。除基礎建設與可負擔性外,數位素養是影響用戶充分利用網路的三大重要因素之一。

Credit: Peter Cihon

研究顯示 0 元上網方案無法有效引領新用戶接觸網路 was originally published in moznewszh on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at September 02, 2017 12:45 PM

August 12, 2017

Mozilla 外電聯播

Mozilla、創用 CC 與維基百科共同創立獎勵艱困地區致力於開放社群文化的 Bassel Khartabil 自由文化獎助金

為了紀念被敘利亞政府於 2015 年處決,於日前傳出死訊的開放網路與自由文化倡議者 Bassel (Safadi) Khartabil,Mozilla、創用 CC、維基媒體基金會、Jimmy Wales 基金會、#NEWPALMAYRA 與其他組織,於 8 月 11 日宣布共同創立 Bassel Khartabil 自由文化獎助金(Bassel Khartabil Free Culture Fellowship),用以資助在艱困環境中仍持續建立社群文化的傑出者,並提倡開放文化、激進共享(Radical Sharing)、知識自由、混搭、合作、勇氣、理想主義與人性等價值。

Honoring Our Friend Bassel: Announcing the Bassel Khartabil Free Culture Fellowship - The Mozilla Blog


Mozilla、創用 CC 與維基百科共同創立獎勵艱困地區致力於開放社群文化的 Bassel Khartabil 自由文化獎助金 was originally published in moznewszh on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at August 12, 2017 05:24 PM

May 09, 2017

Mozilla 外電聯播

Thunderbird 將繼續寄居於 Mozilla 基金會

經過一年的研究與商討,Thunderbird 議會與 Mozilla 達成協議,將繼續以 Mozilla 基金會作為財務跟法律的根據地,短期以自 Mozilla 公司的技術基礎設施獨立為開發方向,中期則以自 Gecko 平台轉移向 Web 為基礎的平台作為目標。

Thunderbird's Future Home

若你願意支持非商業性,獨立且更安全先進的 Email 軟體,請捐款支持 Thunderbird 專案(請務必考慮定期定額)。

Support Mozilla


Thunderbird 將繼續寄居於 Mozilla 基金會 was originally published in moznewszh on Medium, where people are continuing the conversation by highlighting and responding to this story.

by Irvin Chen at May 09, 2017 06:35 PM