Hacker News new | past | comments | ask | show | jobs | submit
Not to be that guy but I don't think this is the gotcha y'all think it is. I didn't know that ONNX had telemetry.

edit: I seem to have misunderstood the intent of the parent comments. Apologies

Top-level comment said "no way to opt out other than building it from source with telemetry disabled", so if that's not true then this is important to know. See https://www.astralcodexten.com/p/if-its-worth-your-time-to-l...
I don’t understand what you mean. I’ve maintained a decently popular ONNX wrapper for years, had 0 idea there was telemetry, and this is quite useful info to have, particularly because it would be a PITA to rebuild binaries right now.
Previous developer here. To clarify, ONNX and ONNX Runtime are two different things. ONNX Runtime is a Microsoft project while ONNX is community owned. Previously ONNX Runtime collected telemetry for their Windows users that use the prebuilt binaries from Microsoft. No data collection for non-Windows cases.
I only found out ONNX had telemetry because one time my program (that uses it) out of nowhere started hanging on closing. Looking at the command line output I realised it was because ONNX telemetry couldn't connect to their server and it just kept retrying the connection.
Good lord.

I was doing a Dart wrapper for MXC* this week, and found it was doing telemetry, though IIRC it was forthrightly/clearly documented.

Been on this planet long enough that I've seen plenty of MBAs saying "hoover every piece of data every time we can" and eng going along without thinking or saying anything.

I'm still somewhat surprised Microsoft would do that in SDKs.

* tl;dr: MS' CLI sandbox a la bubblewrap

I'm just passing information for anyone who wants to disable it without recompiling anything.
Yeah I read your tone wrong, that's on me. Sorry