logoalt Hacker News

Liftyeeyesterday at 1:10 AM2 repliesview on HN

As other comments have pointed out, this statement (one I 100% support, BTW) is a little naive. I can see how it might be unreasonable to expect companies to publish documentation, build infrastructure, etc. to support running your own code on the hardware you own (which 99% of people will never need to do).

However, I strongly believe that - should one choose to do so - you should not be stopped from jailbreaking, cracking, etc. manufacturer restrictions on the hardware you own. Companies aren't obligated to support me doing this - but why should legislation stop me if I want to try? (You can easily guess my thoughts on the DMCA.)


Replies

inetknghtyesterday at 6:08 PM

> I can see how it might be unreasonable to expect companies to publish documentation, build infrastructure, etc. to support running your own code on the hardware you own (which 99% of people will never need to do).

Did you know that television schematics used to come with the documentation for the TV? Discussed not-too-recently on HN: https://news.ycombinator.com/item?id=26996413

danpalmeryesterday at 1:17 AM

> Companies aren't obligated to support me doing this

Where does one draw the line on support? If I jailbreak an iPhone, should I still get Apple customer support for the apps on it, even though they may have been manipulated by some aspect of the jailbreak? (Very real problem, easy to cause crashes in other apps when you mess around with root access) Should I still get a battery replacement within warranty from Apple even though I've used software that runs the battery hotter and faster than it would on average on a non-jailbroken iPhone?

I feel like changing the software shouldn't void your warranty, but I can see arguments against that. I probably fall on the side of losing all software support if you make changes like this, but even then it's not clear cut.

show 4 replies