Thread by @_MG_

I like to read replies to posts like this just to remind myself how misinformed the general public is about “USB-C”
So here is a thread looking at a few of them…
🧵1

First, USB-C is a specification for the physical connector. NOT the protocol. And it intentionally supports multiple protocols like USB, USB-PD, Thunderbolt, DisplayPort, HDMI, PCIe, etc.

Some protocols exclusively use USB-c, like USB-4, Thunderbolt 3 & 4, USB-PD.
🧵2

Now, because a high quality C to C cable can support ALL of these protocols, people incorrectly think the protocols are the same thing.
🧵3

And a lot of it has a belief that USB-C is somehow anti-Apple.
Reality: Apple (& Intel) designed USB-C.
The USB-Implementers Forum is responsible for USB-4, USB-PD, and many others. There are a lot of companies on the USB-IF, including Apple!
🧵4

A lot of people celebrate the cable “standardization” & low cost availability. It’s becoming common knowledge that there are 8 types of compliant cables. But people don’t understand that quality matters. Else, you get perceptions like this:
🧵5

Most people with wired CarPlay that switched from a lighting cable to usb-c will notice how much more fragile the connection is if using cheap cables. That’s because the moving parts went from the socket (lightning) to the cable (USB-C). So cable quality matters more.
🧵6

It really is impressive how confidently wrong people are about this stuff. But also how it’s almost like it challenges their identity or something 😂

Anyway, if I left anything out, let me know.
🧵7

To reiterate, a lot of companies are involved in the USB-IF now.

One of the most inspirational & enlightening people in the USB-C space, for me, is @Laughing_Man. He opened my eyes to the complexity, beauty, & horrors of USB-C.

🧵8

Correction: The idea that Apple/Intel invented C & gave it to USB-IF is based on an industry rumor citation. It’s believable with the timing & numerous similarities with Lightning, but only rumor.

Apple is still on USB-IF, so trying to say C is anti-Apple is silly either way
🧵9

Lotta people getting defensive 😂

USB C (& even earlier USB) is a confusing mess, as my thread shows & tries to inform. Especially with all the protocols & cable types.

The screenshots of confident-but-wrong “correction” reply guys isn’t purely a spec problem though :p

🧵10

Yes, if you aren’t aware, there are 8 possible spec compliant C to C cables.
Lets not count the non-compliant ones 😂

USB-IF has a labeling proposal to “fix” this. But mfgs are also YOLOing it and making cables look like NASCAR logos
🧵11 people.kernel.org/bleung/

Here are the logos that USB-IF released in late 2021. Only cables that have been certified by USB-IF will be allowed to have the logos. And they must have the logo to get certified.
Yet somehow the Apple cable I bought yesterday doesn’t have any of them. 🤷‍♂️
🧵12

lmao, 12hrs later and people are acting like I personally designed these specs.

Quite the contrary. I make USB cables that abuse these specs, like the OMG Cable.



Anyway, there are some good questions too, so I’ll try to update this thread.

🧵13

For people asking for details on “moving parts”, here’s a graphic. This is NOT the only way a connector fails, but cheap metal loses its spring much faster.

Spec says the connectors should achieve 10k+ mating cycles. But bottom price cables generally aren’t to spec…

🧵14

For people asking how to pick a good cable… ehhh 🤷‍♂️

Figure out which of the 8 possible cables fits your need (post #11) and then find one that was certified by USB-IF with a logo (post #12) or some trusted brands.

Or YOLO it, test them, & don’t be sad when they die.

🧵15

Somehow this turned into an AMA about USB-C. So let’s go with it. Next most common question I’m seeing: “why doesn’t <device> charge from USB-C?”

Answer: cause the maker didn’t bother to read the spec. But there is usually a fix! (Next post).
I see the is failure a lot. Ex:
🧵16

So, if your poorly designed device won’t charge or power up with a C to C cable, try converting it to USB-A and back again. Adapter MUST be on the Charger/Host side!

Also, try flipping the connector on the device side, just incase they really screwed it up.
🧵17

@seb_mc2 Even if Apple’s only involvement was via USB-IF, it still makes the weird anti-Apple views pretty silly. I just want to know about the 2012 piece for personal curiosity.

@seb_mc2 Lighting: released in 2012, compact, reversible, orientation marker in cable, host/device responsible for reorienting, reconfigurable pins, etc

USB-C: same, but more pins and reversed mechanical. 2014

Could also be industry response to Lightning? 🤷‍♂️
I WANT TO KNOW!

@CinnamonComfy @calicodev There is no scenario that I can imagine where simply using a C to C cable what supports higher wattage will result in failure to power on when a lower wattage one works fine. So far more info is needed.

@CinnamonComfy But if we are making guesses with insufficient info, context clues suggest that @calicodev doesn’t actually have the theoretical 100w cable and is wondering why 100w is unsafe for a 60w device. (Which is not actually unsafe at all)

Sketchy cables aren’t just a risk of annoyance. Safety is an issue too, especially with the recent enhancements to USB-PD allowing up to 240w. Design considerations now include electrical arcing! ⚠️⚡️
Probably good if the mfg has read the specs!

(video unrelated)
🧵18