sudo @sd@qoto.org
sudo
boosted
Zoom iOS App Sends Data to Facebook Even if You Don’t Have a Facebook Account
https://www.vice.com/en_us/article/k7e599/zoom-ios-app-sends-data-to-facebook-even-if-you-dont-have-a-facebook-account
多加星多加星多加星多加星多加星多加星多加星多加星
sudo
boosted
Monument Valley 2（纪念碑谷 2）在 Google Play 限免。
https://play.google.com/store/apps/details?id=com.ustwo.monumentvalley2
sudo
boosted
Firefox 目前逐渐的被边缘化了，Google Chrome 已然成了浏览器的标准。当我用 Firefox 打开 Gmail 的时候，感觉有些卡顿。当我再用 Firefox 访问 web.skype.com 时候，网页告诉我浏览器不被支持。Google Chrome 由于隐私的问题我早已没在使用了，目前是 Brave + Firefox + Tor Browser。
sudo
boosted
No wonder #zoom can be used in China when they are such an American company--they have been fitting themselves into the GFW. My account registered abroad need to be verified by ID when used in China. They even redirect me to zoom.com.cn
I have NO BEEF with #zoom tho, except that it doesn't support #firefox. Just sentiments against the GFW.
我就说 zoom.us 这么美式的东西还能在大陆用，原来tm是送了中的。我在国外注册的帐号在国内用还要实名登记，还直接跳转到 zoom.com.cn
sudo
boosted
Apparently The Great Firewall came back to experiment MITM attack again. I won't be surprised if all HTTPS websites become broken one day when the operator presses the wrong button.
sudo
boosted
不要买 61 键。
sudo
boosted
RT @wanquribao: 【Oh God, It's Raining Newsletters】美国通过邮件订阅最为主要推送渠道的自媒体越来越多，为啥？你直接拥有所有读者的电子信箱，直接与读者对话，不用受制于平台，不用担心被屏蔽/被砍账号/被禁言。 https://t.co/8DebcRTkWq
sudo
boosted
GitHub Pages 被中间人劫持了
新闻源： https://www.v2ex.com/t/656367
总结一下：
- 全国范围内的劫持
- 只劫持了 TCP 443 端口到 AS4808（北京联通），其他端口正常
- 劫持证书里面有一个邮箱：346608453@qq.com
- 社工结果是一个黑龙江姓张的，不少人认为是接锅侠
- 看证书里面的各种数据像是从网上抄的教程
- 不少人声称劫持方式是 PBR（policy-based routing，基于策略路由）
- 内部人士称此人是 360 公司员工[1]
现在是这样的时代，打开网址之后常常只有一张右下角是二维码的宣传图。
中国银行是不是想把客户发展成雇员？
小米手环会震动并显示来自 iPhone 的达到时间限制的 app 的通知，以及因勿扰模式而被静音的通知（（
本来要写博客但是咕了的 GitHub 支持邮件部分内容
> GitHub Pages doesn't support external SSL certificates directly. We only officially support certificates that are generated and manged by GitHub itself.
> While it is possible to set up your own certificate service using 3rd parties like Cloudflare, these won't link in with the "Enforce HTTPS" option in the repository settings, and this will remain disabled even when you've manually set up HTTPS.
> Cloudflare enables their HTTP/DNS proxy feature by default, meaning GitHub isn't able to see the DNS records required to generate an HTTPS certificate. You'll need to disable this for any DNS records that point towards GitHub.
> ... for GitHub to handle the renewal of HTTPS certificates automatically you need your DNS records to point to GitHub IPs.
> If you do use GitHub's service and enforce HTTPS, it means you would also be using our CDN as well! If you are determined to use an external service, then yes, you would need to manage the renewal yourself.
