zlacker

[return to "Performance and telemetry analysis of Trae IDE, ByteDance's VSCode fork"]
1. Aurorn+lk[view] [source] 2025-07-27 20:30:49
>>segfau+(OP)
I see a lot of confused comments blaming Microsoft, so to clarify: This analysis is about TRAE, a ByteDance IDE that was forked from VSCode: https://www.trae.ai/
◧◩
2. userbi+xp[view] [source] 2025-07-27 21:14:44
>>Aurorn+lk
Arguably it was Microsoft who started the whole trend of calling spyware "telemetry" to obfuscate what they were doing.
◧◩◪
3. tempac+uq[view] [source] 2025-07-27 21:22:39
>>userbi+xp
Obfuscate? Telemetry arguably helps with deobfuscation.
◧◩◪◨
4. inetkn+Lq[view] [source] 2025-07-27 21:24:24
>>tempac+uq
> Telemetry arguably helps with deobfuscation.

Can you please expand on that? I have trouble understanding how telemetry helps me, as a user of the product, understand how the product works.

◧◩◪◨⬒
5. tempac+Jr[view] [source] 2025-07-27 21:31:48
>>inetkn+Lq
You can capture the telemetry data with a HTTPS MITM and read it yourself.

Or (if you're working lower level) you can see an obfuscated function is emitting telemetry, saying "User did X", then you can understand that the function is doing X.

[go to top]