Rendered at 15:10:10 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
pdpi 1 minutes ago [-]
I literally spent more than an hour yesterday debugging issues with USB-C cables that I wasn't aware were charging only, and this shows up today... Better late than never, I suppose, and definitely worth my ten quid.
lxgr 16 minutes ago [-]
Great utility.
The only wrinkles for me are that Macs apparently don't interrogate cables when they don't have to, i.e., when the power adapter supplies <= 60W (not sure if that's a USB-C protocol or an Apple implementation limitation) and that the website copy is full of GPT-isms, which makes me suspect that some of the output might be assumed instead of empirically validated as well.
bestouff 56 minutes ago [-]
I'm using the hardware tester from Treedix in which you have to plug both ends of the cable and which tests a lot of things, I'm quite fond of it.
I have a basket with a lot of USB-c cables and without the tester I can't remember (nor guess) which one does what.
callumprentice 7 minutes ago [-]
Would this tell me if a cable is close to the end of it's life? I like to travel light and I've had cables (mostly phone/pad power) go out on trips after working as expected when I packed.
blightful 46 minutes ago [-]
Nice. You just got them a sale from me. I have a crap ton of cables so this will come in handy.
robot_jesus 11 minutes ago [-]
I'm curious if this also works for USB-A to USB-C. The use case: My Suburu has USB-A inputs and only allows wired Carplay. When I upgraded my iPhone and ditched Lightning, I had to try 6 different cables from my cable drawer to find one that supported data transfer.
I have so many cables I've accumulated over the years, I should either purge or at least categorize the functionality of each.
extinctLizard 9 minutes ago [-]
Small question: did anybody succeed to pay via Apple Pay?
I came here to ask the same thing. I did find a Linux tool with the same name and purpose but that seems to be an entirely different codebase: https://github.com/nedrichards/whatcable-linux
I have a handful of wireless keyboards that just absolutely refuse to negotiate for charging with certain cables at all, so I'm hoping this will help me at least figure out what those keyboards are looking for in terms of cable.
The only wrinkles for me are that Macs apparently don't interrogate cables when they don't have to, i.e., when the power adapter supplies <= 60W (not sure if that's a USB-C protocol or an Apple implementation limitation) and that the website copy is full of GPT-isms, which makes me suspect that some of the output might be assumed instead of empirically validated as well.
I have a basket with a lot of USB-c cables and without the tester I can't remember (nor guess) which one does what.
I have so many cables I've accumulated over the years, I should either purge or at least categorize the functionality of each.
https://github.com/nedrichards/whatcable-linux
But (hazard guess) it comes with a headless CLI binary (no GUI libraries needed) so probably could be ported to Linux (easily with an LLM?)
https://github.com/darrylmorley/whatcable
As I understand it, Windows doesn't expose the necessary low-level hardware information for something like this to be possible.
I have a handful of wireless keyboards that just absolutely refuse to negotiate for charging with certain cables at all, so I'm hoping this will help me at least figure out what those keyboards are looking for in terms of cable.