Derek Atkins

@jonathancross > Please consider making this PR to https://github.com/libusb/hidapi > See #373 Sorry, while I know git pretty well, I'm not a github expert, so I'm not sure how to...

@Youw -- I figured that. I don't think my system is actually *using* libusb/hidapi, so I have no way to actually test that the change would work. I can certainly...

@Youw > Do you mind sharing what "your system" is? Fedora 29 (although it was FC25 when I did the work). The libhid they provide is the signal11 version, not...

@Youw -- Yes, I saw #373 and will try to migrate my PR over there, but like I said above, someone else is welcome to port my changes over if...

HI, > You may find that if you recompile `hidapi` to use the `libusb` driver instead of the `hidraw` driver, the `path` property you get back could be constant enough...

I know that the kernel has the information about what port the device is plugged into. It's printed clearly in the dmesg log, so the information is available -- it's...

@todbot -- it looks like `libusb_get_port_numbers()`, possibly combined with `libusb_get_bus_number()`, will get me a stable identifier. I modified the libusb hid_enumerate to print out the bus/portnum-list and the results are...

For the record, if I use the linux/hidraw version I could easily combine it with a udev rule to stabilize the path. I think the problem here is hidapi using...

C.f. https://github.com/signal11/hidapi/pull/406

Thanks, but I do often get real messages from people not in my roster. I can block those users, but I still wind up getting error messages when they try...