logoalt Hacker News

jonhohleyesterday at 3:18 PM1 replyview on HN

That’s why I said, at what level should this disclosure be required? Obviously a small open source utility shouldn’t have to document everything. What about a $20 electric screwdriver with an unpopulated JTAG header? a $200 door buster TV? A $2,0000 OLED TV? A Kickstarter device that unexpectedly takes off? A small ICE engine? A house?

If you’re starting up a small business, selling at-a-loss widgets to gain market share do you want to be forced to publish a diagnostic manual that not only increases your work, but may also increase your liability?

Seatbelts and airbags are safety, but if you talk to anyone at a body shop, they will tell you there are significant regulation changes in the past decade that have made cars more expensive to fix while not necessarily safer.

I just don’t think it’s as cut and dry as everything must be forced to be documented. What is everything, at what size or industry is this documentation required, why this industry and not that one, is it just OBD or _everything_ including all CAN bus communication, etc. Minimally the end result is increased cost for everyone.

If it’s already published, perhaps libraries should start collecting the service manuals.


Replies

BenjiWiebeyesterday at 7:26 PM

How about; if it's already documented, make it available to the end user.

The right to repair cases that bother me most is where the company goes out of their way to prevent end-user repair (cryptographic pairing of modules!?), or where service manuals/information exist but are only available to dealers.

show 1 reply