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).

tsserver.js と公開プロセスから始めます。issue では、具体的なテストやその他のエントリーポイントは指定されていません。提案されている識別メカニズムを比較し、nightly または npm/nuget ディストリビューションを含め、テレメトリを転送する前にエディターが公式サーバーを確実に認識できる方法を決定します。公式であることを検証できるサーバーについてのみテレメトリが報告されれば完了です。