Live data from Hacker News

Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

arstechnica.co.uk

91–93 of 93 posts

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#91

I'm not an electrical engineer, but wiring something other than ground to the ground pin is...well, I suspect it's straight-up malicious, although why you'd want to do something like this, I don't know.

> I suspect it's straight-up malicious Hanlon's razor: "never assume malice when stupidity will suffice." It doesn't even make rational sense for a business creating cables to intentionally damage equipment. They'd just get sued, tons of bad PR/reviews, and gain nothing obvious. More likely they just had production line issues, lack of QA, and poor training for staff. Resulted in malfunctioning equipment being sold.…

My point is that it may be more complicated to assume stupidity, because the process of getting someone that incredibly dumb into a position where he's dictating the wiring pattern of the cable, with nobody telling him he's an idiot in the process, is far more complex than most forms of stupidity. Hanlon and Occam may be at odds here.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#92
post #54

Earlier quoted context omitted.

Is that really true? (I have no idea just asking). Is there nothing you could put in the device to prevent bad inputs from damaging the internals? (for some definition of bad) Is it a question of impossibility? Or cost? Or bulk? or something else?

I t http://www.fiftythree.org/etherkiller/ttp://www.fiftythree.o... it's a matter of foreseeing the potential failure modes and correctly deciding which ones are so remote as to be not worth the cost and complexity to protect against. For instance, I don't think there's a consumer device out there that wouldn't fry if connected directly to mains AC through any peripheral port at all. But that doesn't stop someone fro…

Sorry about the weird url problem. I typed this on my phone in the HN app and had tried pasting in a URL at the end of my text. After being seemingly unable to get the URL to show up after two tries I gave up and cut down my post to not talk about the URL. I seem to have somehow inadvertently double pasted said URL to the beginning of my post in the process of all that.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#93

Earlier quoted context omitted.

>This is pretty disgusting because engineer man is a good guy and main guy has an underage girlfriend living in a plywood loft built inside a storage unit. One day engineer man says "fuck this I'm going to be a fucking farmer now". If engineer man does that, then he is not a good guy. If engineer man does that, then he is a scummy asshole.

You've mis-parsed the parent. His ...story contains an 'engineering man' and a 'main man.'

Ah, yes, I see that now. Thanks for pointing that out.
Post reply on HN