看起來是透過不同的 encoder，轉到 vector space 後查詢：
ping REST api and return results」當作範例：
之後找範例與用法就不用只在 StackOverflow 上找了... (咦)
Amazon Polly 是 AWS 的文字發音的服務，現在支援中文了：「Amazon Polly Adds Mandarin Chinese Language Support」。
文章裡有 sample voice，跟 Google 小姐比起來中國腔有點重 XDDD
— Jeff Barr ☁️ (@jeffbarr) July 17, 2018
Amazon Translate is priced at $15 per million characters ($0.000015 per character).
Decompiler，也就是直接把 machine code 試著轉回高階語言的程式碼：
這對於分析工作來說簡化很多，尤其是在資安產業的人... 以往比較常見是轉成 assembly 再用人工分析，現在這樣有機會讓大腦輕鬆一些。
雖然目前有些限制 (像是 32 bits only)，不過 open source 出來後，可以預料會有不少人開始加功能進去：
目前還在 Preview，需要申請才能用，不過價目表「Amazon Translate Pricing」已經先出來了 (畢竟已經有競爭對手，可以參考他們的價錢)：
Sign up for the Amazon Translate preview today and try the translation service. Learn more about the service by checking out the preview product page or reviewing the technical guides provided in the AWS documentation.
At Preview, Amazon Translate supports translation between English and any of the following languages: Arabic, Chinese (Simplified), French, German, Portuguese, and Spanish. Support for more languages is coming soon.
* Usually more difficult than other languages in the same category.
We recently released a new interactive visualization of Wikipedia traffic by country and language. Called WiViVi, which stands for Wikipedia Views Visualized, the new visualization shows the geographic distribution of pageviews to any or all Wikipedias from two different perspectives[.]
不過翻牆 VPN 的不知道怎麼算...
Consequently, HHVM will not aim to target PHP7. The HHVM team believes that we have a clear path toward making Hack a fantastic language for web development, untethered from its PHP origins.
And because a few people have asked me this recently, while HHVM usage is not included above in the graph it is at 0.36% which is a third of PHP 5.3 usage and really hardly significant. I personally think it's fine to support it still in libraries if it just works, or if the fixes involved are minor. If not then it's probably not worth the time investment.
Comment 的地方有註明這是扣掉 CI 的量：
@ocramius: These numbers ignore Travis CI and other CI systems that set the "CI" env var in their workers. Without excluding those HHVM is around 0.95% so it's still low but those .36% is probably actual usage.
這樣就放心可以完全不用管 HHVM 了 XDDD
不過後續的更新這樣寫，所以看起來暫時會先恢復 BitTorrent 下載的方式：
After reading this discussion, my current conclusion is that we've totally misunderstood the impact of the attack, and that the security of our bittorrent downloads is still good enough. So I propose we revert to what we did before the 2.12 release, i.e. ship Torrents, for the foreseeable future when 2nd pre-image attacks are not realistic yet.
回到 Tails 3.0 本身，其中比較大的改變是放棄了 32bits 的支援：
Tails 3.0 works on 64-bit computers only and not on 32-bit computers anymore.
不過也不確定是不是愚人節消息就是了：「[tor-dev] Tor in a safer language: Network team update from Amsterdam」。
What has already been done:
- Rust in Tor build
- Putting together environment setup instructions and a (very small) initial draft for coding standards
- Initial work to identify good candidates for migration (not tightly interdependent)
What we think are next steps:
- Define conventions for the API boundary between Rust and C
- Add a non-trivial Rust API and deploy with a flag to optionally use (to test support with a safe fallback)
- Learn from similar projects
- Add automated tooling for Rust, such as linting and testing
目前看到後續的討論只有「[tor-dev] Tor in a safer language: Network team update from Amsterdam」這篇，也許等全世界的 4/1 都過了之後再回來確認吧...