Quote:
|
Originally Posted by ixtab
Thanks to Amazon's "fuck independent developers, let's screw them over again and again" policy, CM has to needlessly be adapted to every firmware.
|
That is indeed getting more than a bit wearing to put up with.
My own answer to the problem:
"Find a manufacturer willing to cooperate with owner's after-market development - then pick the hobby device."
The progress to date (and why readers are seeing less of twobob and myself here for awhile):
The good news:
A manufacturer has been found, and is convinced this type of relationship with the owners of their products is an advantage to themselves. (Yeah! Big win!)
Work is underway to make this idea a reality, with the active support of the company.
The bad (?) news:
This manufacturer does not make e-ink display devices.
(What can I say? I tried, but none of the e-ink device manufacturers I contacted want to be first.)
When will the world know more about this?
Probably sometime next spring, it's a big project.
Just what is it all about
:
To keep the open source software Open (even after modification for the device) ;
To keep company proprietary software Private ;
And the big, catch-22 sounding goal:
Keeping the device and firmware security system in-place that protects against malicious code at the same time as meeting the GPLv3 requirement that the owner can install code of their own choosing (including updates to the GPLv3 items).
Leaving firms that are stuck with aging GPLv2 code due to their corporate policies in the dust of history.
One possible side-effect - -
The death of the Amazon Kindle Fire product line.
But hey - it was Amazon's own policies that brought this all about.
(Talk about shooting one's self in the foot.
)