| ▲ | simonw 18 hours ago | |||||||||||||||||||||||||
The telemetry they removed here isn't unique to uv, and it's not being sent back to Astral. Here's the equivalent code in pip itself: https://github.com/pypa/pip/blob/59555f49a0916c6459755d7686a... It's providing platform information to PyPI to help track which operating systems and platforms are being used by different packages. The result is useful graphs like these: https://pypistats.org/packages/sqlite-utils and https://pepy.tech/projects/sqlite-utils?timeRange=threeMonth... The field that guesses if something is running in a CI environment is particularly useful, because it helps package authors tell if their package is genuinely popular or if it's just being installed in CI thousands of times a day by one heavy user who doesn't cache their requirements. Honestly, stripping this data and then implying that it was collected by Astral/OpenAI in a creepy way is a bad look for this new fork. They should at least clarify in their documentation what the "telemetry" does so as not to make people think Astral were acting in a negative way. Personally I think stripping the telemetry damages the Python community's ability to understand the demographics of package consumption while not having any meaningful impact on end-user privacy at all. Here's the original issue against uv, where the feature was requested by a PyPI volunteer: https://github.com/astral-sh/uv/issues/1958 Update: I filed an issue against fyn suggesting they improve their documentation of this: https://github.com/duriantaco/fyn/issues/1 | ||||||||||||||||||||||||||
| ▲ | stackedinserter 17 hours ago | parent [-] | |||||||||||||||||||||||||
Now people on HN defend telemetry. How did we come to this point? Don't be surprised when you're asked to drink control bottle in order to continue living. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||