不能上传，就没法用他的云端词库了吧，只能用本地离线词库。而且要阻止的话，可以直接用防护墙阻止搜狗的进程上传数据吧。

@aut0man 我理解是低档位发动机转速太高 抖动厉害，所以发虚。

@gavindexu

第一条，出租车是不是很合适，应该指驾驶技术较好的汽车。比如知乎上面看到的这个晚上开车的方法，类似的。

我在晚上是这么开高速的（一个近十年驾龄的老司机，）：1，我的车灯不太亮，最好的办法等高级车（奥迪等灯比较亮的），让他们在前面跑，然后跟着他们走，距离 150-200 米，让他们先趟水，自己跟着，这样开车很轻松；有什么问题，观注他们的尾灯，这样跟车不太累。如果出现问题，他们都会亮刹车灯的，看到前面的刹车灯，你就知道怎么做了。如果对方紧急变线+刹车：无论你看没看到什么，跟着前车做：有一年驾车去成都，在贵州地，车速 100，突然前车紧急变线+急刹，我看不到前面发生了什么，右侧没车，于是跟着前车紧急变线+急刹，完全刹停后，车头已与路中间的故障车头平齐了，让同车的人都吓了一跳，如果我当时没有那么做，追尾是免不了的了。

我这刷新一下到后端的 app server 大概能 roll 出 7 8 台的样子。

@gabon 233333

侯捷的技术书籍排版都是用的 word。

其他出版社直接接受 pdf 的话 你自己使用 latex 也可以排出来的

tombkeeper: 2012 年，putty、WinSCP、SSH Secure 等软件的汉化版被植入后门。
2017 年，XShell、Xmanager 官方发布版被植入后门。
所以，TeamViewer 这事儿可不新鲜，未来一定还会发生。

对大多数人来说，面对远程访问软件的官方发布版被植入后门这种威胁，没有太好的办法。唯一可行的应对措施是：除非有严重漏洞，否则别随便升级。

是的，操作系统、办公软件之类都要及时升级，但远程访问软件的升级要谨慎。

如果你在使用 2009 年发布的远程访问软件，如果里面有后门，那这个后门必须能做到 10 年都不被发现才行。

楼主博客不错就是加载有点慢。建议搞个好点的 cdn

问下，去过朝鲜之后，米国签证会不会有影响啊

service ip 上配权重？

@aligo 赞啊

直接封号。

windows 就是不太开放的。特别还是图形界面。又是商业软件。

几个钟头。原来就是湾区日报的博主哈。

playbook 的话肯定是 ansible 吧。 salt 不叫这个名字。

The issues appear to be affecting Adobe ’ s services, Amazon ’ s Twitch, Atlassian ’ s Bitbucket and HipChat, Autodesk Live and Cloud Rendering, Buffer, Business Insider, Carto, Chef, Citrix, Clarifai, Codecademy, Coindesk, Convo, Coursera, Cracked, Docker, Elastic, Expedia, Expensify, FanDuel, FiftyThree, Flipboard, Flippa, Giphy, GitHub, GitLab, Google-owned Fabric, Greenhouse, Heroku, Home Chef, iFixit, IFTTT, Imgur, Ionic, isitdownrightnow.com, Jamf, JSTOR, Kickstarter, Lonely Planet, Mailchimp, Mapbox, Medium, Microsoft ’ s HockeyApp, the MIT Technology Review, MuckRock, New Relic, News Corp, OrderAhead, PagerDuty, Pantheon, Quora, Razer, Signal, Slack, Sprout Social, StatusPage (which Atlassian recently acquired), Travis CI, Trello, Twilio, Unbounce, the U.S. Securities and Exchange Commission (SEC), Vermont Public Radio, VSCO, Xero, and Zendesk, among other things. Airbnb, Down Detector, Freshdesk, Pinterest, SendGrid, Snapchat ’ s Bitmoji, and Time Inc. are currently working slowly.

http://venturebeat.com/2017/02/28/aws-is-investigating-s3-issues-affecting-quora-slack-trello/

影响服务： http://venturebeat.com/2017/02/28/aws-is-investigating-s3-issues-affecting-quora-slack-trello/

The issues appear to be affecting Adobe ’ s services, Amazon ’ s Twitch, Atlassian ’ s Bitbucket and HipChat, Autodesk Live and Cloud Rendering, Buffer, Business Insider, Carto, Chef, Citrix, Clarifai, Codecademy, Coindesk, Convo, Coursera, Cracked, Docker, Elastic, Expedia, Expensify, FanDuel, FiftyThree, Flipboard, Flippa, Giphy, GitHub, GitLab, Google-owned Fabric, Greenhouse, Heroku, Home Chef, iFixit, IFTTT, Imgur, Ionic, isitdownrightnow.com, Jamf, JSTOR, Kickstarter, Lonely Planet, Mailchimp, Mapbox, Medium, Microsoft ’ s HockeyApp, the MIT Technology Review, MuckRock, New Relic, News Corp, OrderAhead, PagerDuty, Pantheon, Quora, Razer, Signal, Slack, Sprout Social, StatusPage (which Atlassian recently acquired), Travis CI, Trello, Twilio, Unbounce, the U.S. Securities and Exchange Commission (SEC), Vermont Public Radio, VSCO, Xero, and Zendesk, among other things. Airbnb, Down Detector, Freshdesk, Pinterest, SendGrid, Snapchat ’ s Bitmoji, and Time Inc. are currently working slowly.

altrun windows 下的。还可以，占用很少。

todo list 不错

1. Sid: shared a public link to this document from @gitlabstatus, https://twitter.com/gitlabstatus/status/826591961444384768
2. Update sentry DSN to production as it ’ s updated for staging to point to a different project
3. Try to restore webhooks
4. Remove the users we removed earlier today due to spam/abuse.
5. Create outage issue
6. Create issue to change terminal PS1 format/colours to make it clear whether you ’ re using production or staging (red production, yellow staging)
7. Show the full hostname in the bash prompt for all users by default (e.g., “ db1.staging.gitlab.com ” instead of just “ db1 ”)
8. Somehow disallow rm -rf for the PostgreSQL data directory? Unsure if this is feasible, or necessary once we have proper backups
9. Add alerting for backups: check S3 storage etc.
10. Consider adding a last successful backup time in DB so admins can see this easily (suggested by customer in https://gitlab.zendesk.com/agent/tickets/58274)
11. Figure out why PostgreSQL suddenly had problems with max_connections being set to 8000, despite it having been set to that since 2016-05-13. A large portion of frustration arose because of this suddenly becoming a problem.
12. Upgrade dbX.cluster to PostgreSQL 9.6.1 as it ’ s still running the pinned 9.6.0 package (used for the Slony upgrade from 9.2 to 9.6.0)
13. Flush Redis cache once the DB has been restored
14. Add server hostname to bash PS1 (avoid running commands on the wrong host)