lemonskate

Only if they aren't using customer provided encryption keys (is using blob/bucket storage) or an equivalent approach to encryption at rest, and make sure they're doing standard TLS for encryption in flight.

It's absolutely possible, and standard for any decent organization, to build their cloud architectures to fully account for the cloud provider potentially accessing your data without authorization. I've personally had such design conversations multiple times.

Yes, ICE, the 22 year old agency is definitely something the US can't do without. Certainly didn't manage fine without it for the vast majority of our history as a country. Fucking hell.

Brother Ali don't miss

crazy people need dick too

There are literally dozens of us!

I read it originally from a poster on a privacy/security reddit who was reporting their personal experiences. It isn't the most reliable source but in this context I consider it worth accounting for anyway, as what the person described experiencing is both possible and plausible. For anyone who is serious about preventing these sort of privacy breaches, the open wifi vector should absolutely be considered and guarded against if possible (easy but less comprehensive approach would be to see if there is an airplane mode on TV, harder but more reliable is to physically disable or shield the wifi module on the TV itself).

Some TVs have been found to continually scan for open wifi networks to connect to in order to ship back the telemetry they gather.

How does that logically follow? It seems obvious to me that if every choice is going to piss people off then you simply disregard that as a factor and then make the best choice possible. If that had been their decision process and status quo was the best choice on the merits then that would be perfectly reasonable. That was not, however, the process they described in their blog, instead they remained entirely focused on the one issue that they should have ignored.

They did pick a solution that pisses off a large portion of their user base, that's exactly what choosing to do nothing means when attempting to fix the most complained about issue with your language. Doing nothing is a choice too after all.

I see it as a pretty clear sign of dysfunction in the project unfortunately. Being unable to reach an actionable decision to improve on the most disliked part of the language (I'm personally ambivalent, I find that the repetitive error handling quickly fades into the background, but I also really love the ? operator in rust) is a bad sign.

after much deliberation, we've decided to do absolutely nothing

lol, lmao even

basedpyright includes some nice features that Microsoft has otherwise gated behind the closed source Pylance. There's also (in development) ty from Astral that I'm pretty excited for (ruff and uv have made writing python so much better for me).