I'm not seeing the contradiction here.

If I buy a tool and damage your property with it, you can sue me, not the tool manufacturer. If I think the tool malfunctioned and led to that damage, I can sue the tool company to try and recoup the damages I had to pay to you. Both parties can be liable for different things.

The poster I initially replied to at least failed to acknowledge that it may be the tool itself malfunctioning, and therefore the liability of the AI company. The implication of their post was that it is always the end user who should be liable.

I'm not at all familiar with the Xbox One, but this is a feature that's generally available if you're designing "closed" hardware like a console. Most SoC these days have some sort of security processor that runs in its own little sandbox and can monitor different things that suggest tampering (e.g. temperatures, rail voltages, discrete tamper I/O) and take a corrective action. That might be as simple as resetting the chip, but often you can do more dramatic things like wiping security keys.

But this exploit shows that it's still almost impossible to protect yourself from motivated attackers with local access. All of that security stuff needs to get initialized by code that the SoC vendor puts in ROM, and if there's an exploit in that, you're hooped.

Your chances of running into trouble are pretty close to zero unless you're wearing a 51st State t-shirt or something.

I work with a a decent number of Americans who either moved here or are here temporarily, and I can't say there has been any tension. I think most Canadians who are staunchly anti-US are also aware that plenty of Americans aren't happy with their government. I can't say I've seen any vitriol towards the average American person.

There's a pretty stark contrast between an MLB player making $50M per year and a bobsledder who's promised $100K 20 years after reaching the pinnacle of their sport. Given the total amount of training that an Olympian puts in over their life, even if that $100K is adjusted for inflation it probably works out to less than minimum wage in many states. That's a pretty bad profession IMO.

I'm not an expert here, but I this is pretty unlikely at this point.

Google has been working on Fuschia for a decade, and far as I can tell, the only place it was ever deployed was to a Google smart home hub 5 years ago. The only Fuschia news I've heard since then was about layoffs and killing projects related to it (e.g. Chrome on Fuschia).

If Google isn't moving any of their own phones over to Fuschia after a decade of work, it's hard to imagine them unilaterally flipping Android to it and forcing the hand of every Android OEM to follow suit.

Yeah, this immediately made me think of DAF.

My wife is a speech pathologist and hooked me up to a DAF machine for some research, and the effect was totally shocking to me as a layperson. I think I did worse than average, but I was basically unable to speak with delayed sidetone.

I think you're misunderstanding their point.

Your API is constrained by the actual TCP protocol. Even if the sender uses this message-oriented TCP API, the receiver can't make any guarantees that a packet they receive lines up with a message boundary, contains N messages, etc etc, due to how TCP actually works in the event of dropped packets and retransmissions. The receiver literally doesn't have the information needed to do that, and it's impossible for the receiver to reconstruct the original message sequence from the sender. You could probably re-implement TCP with retransmission behaviour that gives you what you're looking for, but that's not really TCP anymore.

This is part of the motivation for protocols like QUIC. Most people agree that some hybrid of TCP and UDP with stateful connections, guaranteed delivery and discrete messages is very useful. But no matter how much you fiddle with your code, neither TCP or UDP are going to give you this, which is why we end up with new protocols that add TCP-ish behaviour on top of UDP.

Fair enough - I didn’t really fully consider the effect of retransmission and segmentation on the receiver view.

> but with the expectation that only openai has access to it

You can argue about "the expectation" of privacy all you want, but this is completely detached from reality. My assumption is that almost no third parties I share information with have magic immunity that prevents the information from being used in a legal action involving them.

Maybe my doctor? Maybe my lawyer? IANAL but I'm not even confident in those. If I text my friend saying their party last night was great and they're in court later and need to prove their whereabouts that night, I understand that my text is going to be used as evidence. That might be a private conversation, but it's not my data when I send it to someone else and give them permission to store it forever.

I haven't used it in a few years, but I always found it to be very flexible and useful for non-Qt projects.

I last used it for an embedded project, which are sometimes a pain to set up in an IDE (cross-compiler, sysroot, debug server, etc.), and I was shocked by how easy it was to get going and how smooth it felt compared to most IDEs.

This also stuck out to me, but in defense of Amazon (yuck), I don't see that language directly from anyone at Amazon. They use the regular "reduction in corporate workforce" BS that every big company on earth uses. It just seems like an editorial choice unless I'm missing something.