Guess what else was released in May 2015? RFC 7540, otherwise known as HTTP/2. In retrospect this seems highly poetic, as HTTP/2 kinda makes the compound document aspect of JSON-API a little bit pointless, and compound documents to me go hand in hand with what JSON-API is as a standard.
這次 iOS 11 的無線網路與藍芽需要到 Settings (設定) 裡面才能有效關掉的設計，讓 EFF 不爽寫了一篇文章：「iOS 11’s Misleading “Off-ish” Setting for Bluetooth and Wi-Fi is Bad for User Security」。
On an iPhone, users might instinctively swipe up to open Control Center and toggle Wi-Fi and Bluetooth off from the quick settings. Each icon switches from blue to gray, leading a user to reasonably believe they have been turned off—in other words, fully disabled. In iOS 10, that was true. However, in iOS 11, the same setting change no longer actually turns Wi-Fi or Bluetooth “off.”
在「Flat UI Elements Attract Less Attention and Cause Uncertainty」這邊透過追蹤眼球的技術，發表了研究結果：
Summary: Flat interfaces often use weak signifiers. In an eyetracking experiment comparing different kinds of clickability clues, UIs with weak signifiers required more user effort than strong ones.
其中最明顯的一個例子就是大家被訓練「有底線的文字應該可以按」，這也是最能馬上被想到的問題... 不過這算是 Flat UI 的問題嗎？
The popularity of flat design in digital interfaces has coincided with a scarcity of signifiers. Many modern UIs have ripped out the perceptible cues that users rely on to understand what is clickable.
Years ago I pursued my interest in InnoDB’s architecture and design, and became impressed with its sophistication. Another way to say it is that InnoDB is complicated, as are all MVCC databases. However, InnoDB manages to hide the bulk of its complexity entirely from most users.
I decided to at least outline a book on InnoDB. After researching it for a while, it became clear that it would need to be a series of books in multiple volumes, with somewhere between 1000 and 2000 pages total.
作者還沒開始寫，不過 outline 已經先列出來了：
I did not begin writing. Although it is incomplete, outdated, and in some cases wrong, I share the outline here in case anyone is interested. It might be of particular interest to someone who thinks it’s an easy task to write a new database.
這篇文章的重點在這些 outline，即使沒有寫成書，這些 outline 也讓你知道要可以朝什麼方向研究...
因颱風延期的「COSCUP 2015 Hands-on【妙生活】MySQL 入門」剛好可以 review 這邊的 outline 來修正一些主題。
總算有大頭把這個不安全的「安全問題」移除掉了：「Google Drops Support for Security Questions」。
Security questions weren't a great way to protect an account since many answers could be guessed or found using a Google search.
目前提供的機制是手機號碼，以及透過其他的 e-mail address 認證。
一樣是在 Zite 上看到在分享要如何設計 API 的文章與影片：「Parse Developer Day Video Series: How to Design Great APIs」。
算是觀念性的分享，很多觀念很有趣... 而不可避免的，講到 naming 的時候，PHP 又被拿出來婊... (沒辦法，這個程式語言的 naming 實在太經典 XD)
在 Hacker News 的摘要上看到的，對於政府提供數位服務，英國政府嘗試訂出設計原則 (雖然目前這份文件還是 alpha 版本)：「Government Digital Service Design Principles」。