Gitlab ‘rethinking’ third-party telemetry (gitlab.com)

Article summary

The article discusses GitLab's decision to implement third-party telemetry, which has sparked controversy among users. GitLab has since rolled back its ToS changes and is reconsidering its approach. The company has opened an issue for gathering feedback on the topic. Users are concerned about the use of third-party telemetry and its potential impact on their privacy.

Main themes

• GitLab telemetry
• user privacy
• third-party tracking
• community feedback
• GDPR compliance

What commenters say

• GitLab's decision to implement third-party telemetry is a violation of user privacy and trust.
• The use of third-party telemetry is not necessary and can be replaced with self-hosted solutions.
• GitLab's rollback of its ToS changes and reconsideration of its approach is a positive step towards addressing user concerns.
• The company's handling of the situation, including its communication with users, has been inadequate and dismissive of their concerns.
• The implementation of telemetry without explicit user consent is a violation of GDPR and other privacy regulations.
• Some users believe that GitLab's actions are driven by the interests of its VC backers rather than the needs of its community.
• Others argue that the use of telemetry can be beneficial for improving the platform, but it should be done in a transparent and opt-in manner.
• The effectiveness of GDPR enforcement is questioned, with some arguing that large companies are not taking the regulations seriously enough.