You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was made aware that this langserver uses telemetry with a unique identifier (log/token). I don't mind that much, but the way it's written now (always on, not mentioned in the Readme, or upon starting the langserver), it's a GDPR violation.
Which means I'm not allowed to use the langserver at work. Which is a shame because I like it :(
I understand telemetry uses a lot of its usefulness if it's opt-in by default, so I'm not suggesting to make it opt-in—but could you at least clearly, obviously mention, preferably in multiple places, that you log telemetry data?
In the readme
Upon installation, right at the end, so it's in the face of the user
Upon startup (maybe even every time, until the user sets a config like i_know_god_stop_yelling_about_telemetry)
The text was updated successfully, but these errors were encountered:
Hey,
I was made aware that this langserver uses telemetry with a unique identifier (
log/token
). I don't mind that much, but the way it's written now (always on, not mentioned in the Readme, or upon starting the langserver), it's a GDPR violation.Which means I'm not allowed to use the langserver at work. Which is a shame because I like it :(
I understand telemetry uses a lot of its usefulness if it's opt-in by default, so I'm not suggesting to make it opt-in—but could you at least clearly, obviously mention, preferably in multiple places, that you log telemetry data?
i_know_god_stop_yelling_about_telemetry
)The text was updated successfully, but these errors were encountered: