幹壞事是進步最大的原動力
好幾個禮拜前的東西，這幾天才上 Hacker News：「Introducing the CSS coding style guide」。
18F 是美國政府的官方單位，取名自辦公室所在的地址：(取自 Wikipedia 的「18F」說明)
Its name refers to its office location in northwest Washington, D.C., on 18th and F Streets.
不只是定義了 CSS Coding Style Guide，還給了 SCSS Lint 工具使用：
The styleguide provides a method of linting Sass (SCSS) code to ensure it conforms to the rules in the styleguide.
Linode 這陣子一直被 DDoS 攻擊，前幾天放出報告：「The Twelve Days of Crisis – A Retrospective on Linode’s Holiday DDoS Attacks」。
其中這段提到了一些數字，Linode 有個小機房有 40Gbps 的能力，但以現在的 DDoS 規模會馬上爆掉：
Linode’s capacity management strategy for IP transit has been simple: when our peak daily utilization starts approaching 50% of our overall capacity, then it’s time to get more links.
This strategy is standard for carrier networks, but we now understand that it is inadequate for content networks like ours. To put some real numbers on this, our smaller datacenter networks have a total IP transit capacity of 40Gbps. This may seem like a lot of capacity to many of you, but in the context of an 80Gbps DDoS that can’t be blackholed, having only 20Gbps worth of headroom leaves us with crippling packet loss for the duration of the attack.
另外把 DNS 整個放上 CloudFlare 讓他們來擋：
Our nameservers are now protected by Cloudflare, and our websites are now protected by powerful commercial traffic scrubbing appliances.
後續的改善應該還要幾個月？完成後應該會再看到 blog post...
Firefox 46 的開發版本將會對非 HTTPS 頁面加上警示：「Login Forms over HTTPS, Please」。
技術上來說，是當偵測到頁面上有 input type="password" 的元素時會加上不安全的 icon：
When a page with a password field is not delivered securely, Firefox displays a lock with a red strikethrough in the address bar[.]
不過看起來是在試水溫，沒有打算在正式版本開起來：
There are no current plans to show these warnings to users of Beta and general release Firefox.
這樣就有點可惜了...
Mark Callaghan 在「MyRocks vs InnoDB with Linkbench over 7 days」這邊分析了 MySQL 上的兩個 engine 的差異，總結是大獲全勝：
但 InnoDB 的 engine 是 2000 年的設計 (16 年前)，MyRocks 的 engine (RocksDB) 則是 2013 年的設計，不屬於同一個世代。
相較於與 InnoDB 對打，我更想看到的是與 TokuDB (2012 年的設計) 對打的結果。
兩個新的 engine 都有針對 SSD 的特性發展，可以看出資料結構與寫入的方式就很不一樣，而且一開始就是在多 CPU 多核環境下開發，相較於 InnoDB 是一路改的包袱來的輕鬆許多。
在 Twitter 上看到如標題所說的，從 Google Chrome 50 開始 (現在正式版本是 48)，HTTP 網頁將禁用 Geolocation API：
Starting in Chrome 50, geolocation will not be available in insecure contexts (i.e. only HTTPS embedded in HTTPS): https://t.co/2L6hlzkXnw
— Joel Weinberger (@metromoxie) January 21, 2016
對隱私保護的加強。
昨天先看到 Mark Zuckerberg 丟出來的資訊，比較完整的資料可以在「Better Computer Go Player with Neural Network and Long-term Prediction」這邊看到。
Facebook 這邊的成就在於用 DCNN-based model 改善效率，可以用一台電腦 (包括 GPU) 維持在 KGS 5d (業餘五段)，跟 Zen19 差不多的棋力，跟目前最好的電腦圍棋軟體棋力差不多：
darkfmcts3now holds a stable KGS 5d level, on par with the top Go AIs, has beaten Zen19 onceand hold 1win/1lose against a Korean 6p professional player with 4 handicaps.
The distributed version, named darkfmcts3in KGS Go Server, use darkfores2 as the underlying DCNN model, runs 75,000 rollouts on 2048 threads and produces a move every 13 seconds with one Intel Xeon E5-2680 v2 at 2.80GHz and 44 NVidia K40m GPUs.
In this paper, we have substantially improved the performance of DCNN-based Go AI, extensively evaluated it against both open source engines and strong amateur human players, and shown its potentials if combined with Monte-Carlo Tree Search (MCTS).
而隔壁棚的 Google 也丟出對應的研究成果「AlphaGo: Mastering the ancient game of Go with Machine Learning」，直接往 Nature 上丟：「Mastering the game of Go with deep neural networks and tree search」。
Google 不是跑在單機上，而是跑在 Google Cloud Platform 上，分散式的版本大約是職業五段的水準：
Of course, all of this requires a huge amount of compute power, so we made extensive use of Google Cloud Platform, which enables researchers working on AI and Machine Learning to access elastic compute, storage and networking capacity on demand.
實際對樊麾 (職業二段) 的成績也是五比零的大獲全勝：
So we invited the reigning 3-time European Go champion Fan Hui — an elite professional player who has devoted his life to Go since the age of 12 — to our London office for a challenge match. The match was played behind closed doors between October 5-9 last year. AlphaGo won by 5 games to 0 -- the first time a computer program has ever beaten a professional Go player.
而今年預定要去打大魔王，目前韓國圍棋第一人李世乭：
AlphaGo’s next challenge will be to play the top Go player in the world over the last decade, Lee Sedol. The match will take place this March in Seoul, South Korea. Lee Sedol is excited to take on the challenge saying, "I am privileged to be the one to play, but I am confident that I can win." It should prove to be a fascinating contest!
到時候中國那邊的圍棋節目應該會有網路直播可以看吧，再來盯...
從 Hacker News Daily 上看到的，在 Sun-2 的 bootloader 裡可以看到「Love your country, but never trust its government」這樣的字串：「Why the Sun 2 has the message "Love your country, but never trust its government"」。
這段字串是由 John Gilmore 當時在 Sun 開發時所放入的，John Gilmore 同時也是後來 EFF 創辦人之一，不過當初放入這段字串的目的是為了抓到盜版：
Yes. Vinod Khosla, first President of Sun, came to me at one point and said to put something hidden, triggered in an unexpected way, into the ROM Monitor, so that if somebody cloned the Sun Workstation (violating our software’s copyright), we could do that unexpected thing to the competitor’s demo workstation at a trade show and thereby prove that they had cloned it.
過了三十年後 John Gilmore 被挖出來問的回應也是蠻有趣的... (可以參考原文附上的信件)
而這句話現在回頭看也很經典，尤其是最近各國政府想要在 crypto system 裡面放後門的各種反應。
在「YouTube Loop」這邊看到 YouTube 支援 Loop 了，在影片上按右鍵：
而且作者也有提到，在外嵌的影片也支援：
It also works for embedded videos.
以前要找外掛或是某些網站幫你，官方支援後省不少事 XD
之前也有遇到，結果 Lorna Jane Mitchell 寫了一篇「Handling Composer "lock file out of date" Warning」給了不少解法。
第一種是 composer upgrade，直接全部升級。
第二種是先用 composer update --dry-run 看看是不是有人加到 composer.json 後忘記更新，如果是的話再用 composer update [package] 處理。
第三種是用 composer update nothing 閉上眼睛更新 hash 值，當作什麼都沒看到 XDDD
Sometimes this is the right answer so it's a handy trick to know!. I seem to see these kinds of issues in people's projects quite often (I'm a consultant, I see a lot of projects) so I thought I'd share my usual tactics for getting things sorted - if you have any tricks of your own to share, I'd love to hear them :)
該說很「實用」嗎 XDDD
Adobe Typekit 是個收費的網頁字型服務，為了讓變更可以儘快生效，用了比較短的 cache time：
We use a short cache time for the kit JavaScript so that you can update your kit (for example, adding fonts, or changing the list of allowed domains) and have your changes live in a reasonable amount of time.
但這也造成了不少人抱怨 Google PageSpeed Tools 會扣分，而實際上也的確降低效率 (因為你不需要天天改設定)：
Adobe 給了妥協的方案，你可以選擇使用更長的 cache time，從本來的 10 mins 變成 1 week：「Improved caching for kits: Opt for longer cache timeout」。
這個選項使得 Google PageSpeed Tools 不會扣分，也讓效能再更好一些。