2019/11活动 仅供参考 随时编辑
站免：
OpenCD 11/01-11/10,FREE
MoeCat 11/01-11/03,FREE
HDDolby 11/01-11/05 08:00,FREE
HDSky 10/28-11/01,FREE
开药：
OpenCD 11/01-11/03
HDSky 11/01 ,Ultimate User+ ,limit all 200
HDDolby 10/22-12/01 00:00 ,User+ ,3 temporary invitation
开注：
MoeCat 11/01-11/03
https://moecat.best/signup.php
52pt 11/01-11/05
https://52pt.site/signup.php
PTHome 11/01
https://pthome.net/signup.php
消息来源: https://t.me/privatetrackernews/952
站免：
OpenCD 11/01-11/10,FREE
MoeCat 11/01-11/03,FREE
HDDolby 11/01-11/05 08:00,FREE
HDSky 10/28-11/01,FREE
开药：
OpenCD 11/01-11/03
HDSky 11/01 ,Ultimate User+ ,limit all 200
HDDolby 10/22-12/01 00:00 ,User+ ,3 temporary invitation
开注：
MoeCat 11/01-11/03
https://moecat.best/signup.php
52pt 11/01-11/05
https://52pt.site/signup.php
PTHome 11/01
https://pthome.net/signup.php
消息来源: https://t.me/privatetrackernews/952
Chrome 78 的 flags 页面中去掉了
但是经测试，可以在 chrome://flags 页面控制台执行
消息来源: https://t.me/yscschan/6675
omnibox-ui-hide-steady-state-url 相关的选项。但是经测试，可以在 chrome://flags 页面控制台执行
[
'omnibox-ui-hide-steady-state-url-path-query-and-ref',
'omnibox-ui-hide-steady-state-url-scheme',
'omnibox-ui-hide-steady-state-url-trivial-subdomains'
].forEach(function(f) {
chrome.send('enableExperimentalFeature', [f + '@2', 'true']);
})
@2 对应的是 Disabled。 @0 和 @1 分别对应 Default 和 Enabled。消息来源: https://t.me/yscschan/6675
升级到最新版之后url栏如上图所示，默认只显示一个顶级域名和path
不习惯的话浏览器输入
chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains·默认为Deafult
·选择Disabled即可恢复到原来的样子，如上图底部所示
·输入Enabled，强制隐藏https及域名前缀，如上图顶部所示
GitLab 发送邮件宣布正式撤回23日有关遥测服务隐私条款的更改
邮件原文：
We apologize and have rolled back the changes announced in our October 23 email
邮件原文：
We apologize and have rolled back the changes announced in our October 23 email
Dear GitLab users and customers,
On October 23, we sent an email entitled “Important Updates to our Terms of Service and Telemetry Services” announcing upcoming changes. Based on considerable feedback from our customers, users, and the broader community, we reversed course the next day and removed those changes before they went into effect. Further, GitLab will commit to not implementing telemetry in our products that sends usage data to a third-party product analytics service. This clearly struck a nerve with our community and I apologize for this mistake.
So, what happened? In an effort to improve our user experience, we decided to implement user behavior tracking with both first and third-party technology. Clearly, our evaluation and communication processes for rolling out a change like this were lacking and we need to improve those processes. But that’s not the main thing we did wrong.
Our main mistake was that we did not live up to our own core value of collaboration by including our users, contributors, and customers in the strategy discussion and, for that, I am truly sorry. It shouldn’t have surprised us that you have strong feelings about opt-in/opt-out decisions, first versus third-party tracking, data protection, security, deployment flexibility and many other topics, and we should have listened first.
So, where do we go from here? The first step is a retrospective that is happening on October 29 to document what went wrong. We are reaching out to customers who expressed concerns and collecting feedback from users and the wider community. We will put together a new proposal for improving the user experience and share it for feedback. We made a mistake by not collaborating, so now we will take as much time as needed to make sure we get this right. You can be part of the collaboration by posting comments in this issue: https://gitlab.com/gitlab-com/www-gitlab-com/issues/5672. If you are a customer, you may also reach out to your GitLab representative if you have additional feedback.
I am glad you hold GitLab to a higher standard. If we are going to be transparent and collaborative, we need to do it consistently and learn from our mistakes.
Sincerely,
Sid Sijbrandij
Co-Founder and CEO
GitLab