# WhatCable: Know what your USB-C cable can really do > [!question] Lingering Questions > - Does the crowdsourced cable database get moderated or deduplicated, given no verification process is detailed on the page? > - How does WhatCable's e-marker validation logic stay current as the USB-IF vendor ID list and PD spec evolve? > - Will Windows ever get equivalent diagnostics if Microsoft exposes the needed API, given the page frames the gap as platform-API, not prioritization? > [!tip] Article Ideas > - Honest hedging as a product-trust signal ("worth checking" vs. "proof of fake") — pairs with the vault's existing AI-uncertainty-expression notes. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Diagnostic Confidence Cannot Exceed Sensor Honesty]] — already captures the sensor-honesty claim from this exact source (created 2026-08-11) > - [[3. Resources/Literature Notes/This Free Mac App Can Help You Root Out Your Slow USB-C Charging Cables]] — the secondary CNET coverage of the same product > [!quote] Vocabulary > - *e-marker* — identification chip embedded in higher-power/higher-speed USB-C cables that reports rated current, supported speed, vendor ID, and PD capability flags to the host device. > - *PDO (Power Data Object)* — one negotiated USB Power Delivery voltage/current profile. ## Author's thesis (as stated by the source) Identical-looking USB-C connectors can carry categorically different underlying capability (speed, wattage, protocol support). A diagnostic tool that translates existing OS-level data into plain-English verdicts — while staying honest about the limits of its own inference — earns more trust than one that overclaims certainty. ## Key arguments (≤3) 1. A single connector shape (USB-C) hides wildly different real capability — USB 2.0 vs. USB4 vs. Thunderbolt 4 look identical but perform nothing alike. 2. WhatCable's "fake cable" detection is explicitly framed as a flag ("worth checking"), not proof — a more honest framing than typical counterfeit-detection marketing. 3. Missing e-marker data doesn't mean the cable lacks a chip — macOS only queries the chip when the connection needs it, so absence can be a false negative. ## Claim atoms ### Identical-looking USB-C cables have wildly different real capability > [!quote] ID:rw_whatcable_h1 > Every USB-C cable looks the same. They are not. **Context & use**: Section header framing "The problem," immediately followed by a three-tier comparison (USB 2.0 / USB4 / Thunderbolt 4) with concrete speed/wattage figures. This is the entire premise the product is built to solve. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> ### A cable can develop a fault after it's already plugged in > [!quote] ID:rw_whatcable_h2 > If a cable develops trouble while it is plugged in (an overcurrent or the connection dropping and reconnecting), a banner appears on the port. **Context & use**: Describes "Mid-session fault warnings" — a monitoring claim, not just a diagnostic-at-a-point-in-time claim. Implies WhatCable polls connection state continuously. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### Trust-signal flags mean "worth checking," not "definitely counterfeit" > [!quote] ID:rw_whatcable_h3 > It is not a guarantee the cable is fake, but it tells you where to look. **Context & use**: From "Cable trust signals" — the e-marker validation heuristic (vendor ID checks, PD spec range validation, reserved-bit flags). The clearest example of the page hedging appropriately rather than overselling. **Tags**: #xref #addendum <!-- atomicity: 1 idea ✓ --> ### Missing e-marker data doesn't mean the cable lacks a chip > [!quote] ID:rw_whatcable_h4 > macOS only asks a cable to identify itself when the connection needs it... Plug a marked cable into a low-power charger or a plain data connection and macOS may never query it, so there's nothing for WhatCable to show. **Context & use**: FAQ answer to "Why does my cable show no e-marker data?" Explains a specific, non-obvious false-negative scenario a less careful FAQ would gloss over. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> ## Permanent candidates - **Already captured** — the "hedged claims earn more trust" reading of atom H3 is functionally the same claim as the existing [[3. Resources/Permanent Notes/Diagnostic Confidence Cannot Exceed Sensor Honesty]] (same origin document, created 2026-08-11). Not re-promoted. - **Promoted** → [[3. Resources/Permanent Notes/Identical Connectors Can Hide Categorically Different Capability]] — atom H1, generalized past this one source; distinct from the sensor-honesty claim (this one is about standardized interfaces masking implementation variance, not about self-reported data trustworthiness). ## Processing checklist - [x] Ported claim atoms from the existing deep-read appendix - [x] Checked existing Permanent Notes first — found one true duplicate (skipped), promoted one genuinely new claim - [ ] Confirm the press-logo claims (Lifehacker, MakeUseOf, Adafruit, Boing Boing) resolve to findable coverage before citing elsewhere - [x] Connect into the relevant MOC ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — because applies-in; recognizing where a shared standard hides implementation variance is a product-design pattern, alongside the existing sensor-honesty note already synthesized under this MOC. - [[3. Resources/Readwise/Articles/WhatCable Know What Your USB-C Cable Can Really Do]] — source document.