Quote:
Originally Posted by nausica
Why not just "Kindlet Kit"...  |
Quote:
Originally Posted by GoSharks
From a strictly 'user' side, something simple like "Kindlet Keys (KK)" or 'Kindlet Skeleton Keys (KSK)" would make intuitive sense to me especially when paired with the Dev's Certificates. Or a shorter version of your favorite- "Kindlet Restrictions Kit (KRK)"?
(on second thought, would KK be confused for Kindle Keyboard? would the context make the difference obvious?
|
Thanks for the answers so far!
"Kindlet Kit" doesn't sound bad... but it "loses" the semantics of what the KJB is - namely, *only* a way to escape the standard restrictions imposed on a Kindlet (hence the original name "Kindlet Jailbreak", and the "Kindlet Restrictions Removal Kit"). These make the purpose clear (IMO), and after a second thought, are probably preferrable to "esoteric" names like liberator, escalator, savior etc.
Conceptually, the dev keys and the KJB are two completely separate things. To take KUAL or CM as an example: they require both of these as prerequisites, but both of them can actually "break" independently.
1. The dev keys are required *before* the app is even started, when the Kindle verifies if the app is signed with a key known to the device. If it is not, you get the message "You are not authorized by the developer to execute the app" or something along these lines.
Every time you unregister the Kindle, the dev certificates get deleted, and you'll get this error until you re-install the certs.
2. The "actual" Kindlet jailbreak is required once the app is running and doing stuff that would normally not be allowed for Kindlets. It's the application's responsibility to check whether the KJB is available or not, which is usually done right when the app starts. The KJB will generally get deleted on firmware updates.
As said, these are -- in principle -- two separate issues, which can -- in principle -- be resolved separately. Then again, I also find myself using NiLuJe's all-in-one files whenever I run into one of these problems, because that all-in-one file fixes both of them at the same time.
So, here's yet another proposal:
Let's call it "
Mobileread Kindlet Kit" and have it include the MR certificates, and the KJB. So in fact, it would be NiLuJe's all-in-one kit, just with a different name.
From a user perspective, that's only one thing to install when any problem occurs. From a developer perspective (or rather: from the paedagogic perspective for would-be-developers), it would also make sense, because it will encourage people to sign their applications with our well-known "standard" MR keypair, instead of creating their own vanity keys. And, as a side effect, it also mentions that all of this stuff comes from the MR community.
Looks like a win-win-win situation to me