K3 hacked

[RonF]

Originally Posted by Tiersten

Meh. Delete the thread if you wish. Its not immediately clear from the posts in the developer forum unless you read some preexisting threads that the K3 has been hacked so I thought it'd be helpful to inform people.

Yes, there is that. You can go into the developers forum and you still wouldn't know that the K3 has been hacked unless you read through to the end of the 2.5 thread.

So +1 to letting this stay

[Pushka]

Originally Posted by Tiersten

Meh. Delete the thread if you wish. Its not immediately clear from the posts in the developer forum unless you read some preexisting threads that the K3 has been hacked so I thought it'd be helpful to inform people.

I agree, most people wouldnt think of looking 'up there' at 2.5 hack for a Kindle 3 one. You did the right thing. I read about the hack for the K3 on kindleboards, and even then, couldnt find it for a while here until I clicked on the old thread. Had I not seen KB, then I would have seen your post and explored further. So

[pshrynk]

Well, my magical moderator powers seem to have failed, so th ghods must want it open. I never argue with the ghods. I like remaining on the other side of the celestial BBQ equation.

[HarryT]

Originally Posted by daffy4u

Before you close, note that this is pointing to a thread in the Kindle Developer's Forum which some folks might tend to overlook.

Please let it be.

Closing a thread doesn't make it disappear; it simply prevents people from posting new messages to it.

[93terp]

Originally Posted by RonF

I for one am glad that this was here. I have not looked into the developers forum and would not have known about this if not for this thread here.

Considering the many duplicate threads on lighted covers, slow page turns, and many others in this forum, I don't see a major breakdown if this thread were allowed to point people to what many consider a major improvement for the K3.

I completely agree! I would not have known about the hack had it not been for this thread.

[93terp]

Originally Posted by JSWolf

We do not need this thread. All it was created for was to point to another thread. Please mods, lets get this thread deleted.

Speak for yourself. Do not include me in your collective "we".

[93terp]

Originally Posted by daffy4u

There really is no need to be so regimental all of the time. This is not the military. This is a mostly social board. If we all acted as nit-picky as you're being right not, now much would get posted.

Your best bet would be to put this thread and maybe the whole Kindle forum on ignore.

We should be so lucky!

[JSWolf]

So let's get threads posted all over the place linking to other threads just because maybe somebody may not have seen yet because it's not int he same forum section where we posted the thread to link to the other thread and see how annoying it will be in the long run. Let's make sure every thread has a companion thread in other forum section linking to it.

[Ajax]

If the linked thread had any indication in the title about K3 being hacked I might understand your viewpoint. All that it mentions is the 2.5 hack, so anyone looking at the various threads in developer's corner wouldn't have any idea that the K3 was now hacked unless they decided to read threads that don't mention anything about it.

[Bill Lumburgh]

I don't think I would have found out about this, if it wasn't for this thread (thanks, Tiersten!).

I understand the concern about duplicate threads in different parts of the forum but I must say, I don't really see the problem here. It's not like everybody is going around the forum and posting random pointers to a bunch of threads for the fun of it.

The K3 is only going to get jailbroken (is that even a word?) once, unless Amazon go out of their way to fix the "exploit". And, the way I see it, this really isn't so much a duplicate thread as it is a newsflash of sorts. In any case, I thought it was useful and I just wanted to say thanks.

[JSWolf]

Originally Posted by Ajax

If the linked thread had any indication in the title about K3 being hacked I might understand your viewpoint. All that it mentions is the 2.5 hack, so anyone looking at the various threads in developer's corner wouldn't have any idea that the K3 was now hacked unless they decided to read threads that don't mention anything about it.

To be honest, a new thread about the K3 should have been created and not tacked onto one about the K2.

[NiLuJe]

Er, why don't we all take a deep breath?

I didn't create a new thread because it's essentially the same hack, so I didn't see the need to create a different, potentially confusing second thread. The point of the thread in the first place was to host a majority of the hacks in the same place. It already takes a good amount of time to maintain one thread, I don't really need to add to that burden...

The only issue I see with this choice is the inabilty to update one's own thread title, which explains why it's still only referencing K 2.5.

(And I'm talking about the dev subforum here, because I don't really see why everyone's got their panties in a bunch about this one here...)

[DiapDealer]

because I don't really see why everyone's got their panties in a bunch about this one here...

Because some apparently think that playing the role of "Forum Thread Integrity Gestapo" will help them land a Moderator gig someday.

[TallMomof2]

I usually check the Developer's Sub-forum but I'm still very glad to see an announcement in the general forum. (Good-bye creepy author pictures!)

[daffy4u]

Originally Posted by HarryT

Closing a thread doesn't make it disappear; it simply prevents people from posting new messages to it.

I familiar with that but the need to close a thread this not apparent to me. It's not a repeat thread (Like multiple people posting the same news item). So what if people want to post in this thread. It doesn't take away from the thread that is being pointed to. Threads are made to be posted in.