Telemetry in Zed
Zed is an editor which seems to be gaining lots of momentum. Looking at the features which are already in there it seems fairly complete. For me to start testing it I'll wait for remote development support. I also do not necessarily agree with the need for "AI" to be added to the editor, but to their credit I can configure a local Ollama instance making this actually usable, even when working under restrictive terms.
What really stood out to me is their approach to telemetry. But to Zeds credit they are not only very clear what data they collect and where they send the data, but also mention that the data is proxied through their servers.
If you absolutely insist on collection telemetry for whatever reason, this is in my opinion the example to follow. Especially because you can choose how much telemetry you are willing to share. Want to help improving the product by sending stack traces, but don't fancy sending more metrics than necessary? That is doable! And you can configure it from the welcome screen. To be very clear, my general stance on data collection did not change: if you want to collect telemetry it should always be opt-in. No discussion, no questions asked.
posted on Aug. 21, 2024, 3:38 p.m. in app, software engineering
This entry was posted as a "note" and did not undergo the same editing and review as regular posts.