

vscodium isn’t immune to the problem tbh - put it behind a gating proxy (mitmproxy or something is probably easiest) and watch just how chatty it still is (for plugin mechanism etc)
the entire design of how the vscode ecocystem is put together is in service of their telemetry aims, imo. they may argue it’s “for safety” or whatever, but it’s just control and surveillance. alternative options that don’t do this shit exist and operate just fine


(Posting this at 01:41 after a very, very full week and with flubrain: take considered potentially faulty on delivery)
I’ve often thought about this specific problem part, and i gotta admit I’m pre-conflicted. Due aforementioned note I haven’t read the license yet (I’ll do in the week and post a reply with thoughts) but from what I’ve observed to date:
And ito a policy having defensive teeth, those are two load bearing pillars that turn out to not even be moth eaten wooden beams but instead rice crispies held together in a sugar glaze
Consider: what if some popular projects had a “if you’re using this in something making >= $thresholdOrPortionCalc, you must support the project with $percentageOfRevenue” clause in licensing? Modulo the payment distribution admit (lol @ modern aml nightmare), would help a ton with the open source funding squeeze. But can you imagine the bleeting (and probably parasitic forking) if that started happening?
Put another way: without copyright and IP reform (into what shape I have only vague suggestions), how far do licenses get us?
(I’m sorry if this sounds extremely negative -afaict with current regulatory climates and where-IP-is-at, it’s the broadstrokes view. Icbw in detail (I expect I am at least in some detail). But I want to be wrong because god this all fucking sucks)