Sure, to use the TV you need to go past the EULA screen. And the button right in front of you, pre-selected - is agree to all terms. And after pressing OK, you now have ACR turned on. But you did that, it wasn't on by default.

Okay I can take my soul sucking corporate hat off now.

At least bringing up the underlying method (restrict to contributors) has spawned the discussion about how that's probably a bad idea on the security side.

The account was commenting on the satirical sysadmin subreddit yesterday, so they know what makes a engaging story.

LiveKit Cloud uses virtual compute and networking across multiple (USA based) cloud providers. DigitalOcean, Google and Oracle at minimum. They each have servers all of the world of course, but the controlling entity(s) parent companies are all based in the USA.

Latency shouldn’t be a problem, it's handled by a global CDN.

Proton including that part about geopolitical instability implies that Meet is does not fall under the USA's CLOUD Act - that would be wrong. The metadata of any Meet call could be handed to USA authorities, for example the participants date & time, source IP and useragent of each member. The call itself should be E2E encrypted.

I didn't immediately see a red flag that would make me discount all of their work. It's clear what the author's general opinions are. They're entitled to them of course.

They were required to change the way their systems worked, to no longer respect a user's chat deletion request. That means a non-chat-logging company can of course be forced to change the way their system works, to instead log chats.

In the same way Apple can not only be forced to hand over back-doored access to UK users iCloud data (when Apple also hold a copy of the keys), they can also be forced to change the way their OS works to prevent the scenario where Apple don't hold the keys (preventing Advanced Data Protection from being enabled). The USA could force the same thing via the CLOUD Act.

For example OpenAI were required by a US federal judge to log all chats, and make them discoverable to lawyers representing The New York Times last year. https://www.businessinsider.com/openai-new-york-times-copyri...

Additionally the company can be gagged by a court from disclosing that the chats are being logged, at least in the USA and the UK.

Both accounts are used to advertise their website.

Comments on issues use the format <[OrgName]/[RepoName]/issues/[IssueNumber]/[CommentID]@github.com>

A mitigation to this would be to take the combination of message ID and the sending domain and use that as the unique value, because message ID is not guaranteed to actually contain a domain label that's owned by the sender.

For example SendGrid's message IDs are <[RandomValue]@geopod-ismtpd-[Integer]>.

Of course every service will have outages, it's just funny to see it so soon after saying:

> We're nuts for studying failure at the company [...]

(albeit a different 'failure' context)