Editors need a way to determine whether they are talking to an official TS Server

Otherwise, they will obliviously forward events from the server to our official telemetry system and we'll have confusing noise in our data (e.g. stacks that don't match our source or asserts that don't exist).

The most secure approach would be to cryptographically hash the official tsserver.js and have the editor only report telemetry for matching files. This would likely be impractical for, e.g., nightly builds. Edit: @minestarks pointed out that signing the files would be a smarter way to do this - no need for a big inclusion list.

An intermediate approach would be to only report telemetry from the in-box implementation (i.e. not if tsserver comes from npm or nuget). We might lose a lot of data.

Alternatively, our publication process could modify tsserver.js in some way that the editor could detect. A fork would have to be deliberately malicious to replicate the change (vs now, where they'd have to explicitly suppress events to be good citizens).

Inizia da tsserver.js e dal processo di pubblicazione; l’issue non indica test specifici né altri punti di ingresso. Confronta i meccanismi di identità proposti e determina come un editor possa riconoscere in modo affidabile i server ufficiali prima di inoltrare la telemetria, incluse le distribuzioni nightly o npm/nuget. Il lavoro è completato quando la telemetria viene segnalata solo per server verificabilmente ufficiali.