Earlier quoted context omitted.
Plenty of times I've come back to my computer, typed my OS password expecting that it was locked, waited for my display's turn-on lag, and found that it wasn't locked (grace period). I type the password blind, but reserve the enter until I have visual feedback. At least typical IRC clients don't transmit until hitting enter. Browser omnibars and Javascript can send away every keystroke as it happens. Now I want to se…
Is it me or is your userid ironically apropos to this discussion?
How I reverse-engineered Google Docs to play back any document's keystrokes
81–90 of 121 posts
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#82I remember reading an article about how it's a shame that authors don't use pen/paper anymore, since we can't see their crossouts and things for rough drafts. I'd argue that this would be infinitely superior if authors would give us access to some revision history.
You do still miss out on doodles in the margins however
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#83Didn't Google Docs used to have this "playback" feature built in? I clearly remember there being a slider at the top of the page that you could scrub back and forth through a document's revision history.
I remember that from Google Wave at least.
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#84Great article, fascinating. The author mentions that his system doesn't handle rich text, which is fine, but I'd just like to comment on how difficult of a problem handling rich text is. If anyone is interested in having a personal text-only replay editor, check out http://sharejs.org/ by an ex-Google Wave engineer. As far as handling rich text, I've talked to the original co-founders of Writely (which became Google…
ShareJS and Quill have actually been making some great progress on this though: https://github.com/share/ShareJS/issues/1
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#85Is this really a privacy breach? It's been obvious that Google stores revision history since it launched—you've always been able to access a thorough revision history in the UI itself...
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#86Earlier quoted context omitted.
My browser URL bar has received a few passwords, usually just a local computer password but occasionally something more sensitive. Makes me wonder about the permissions my collection of browser addons has. I've also chucked a few passwords into IRC in times past. Fortunately non-essential stuff but really motivated me to sort out some better solutions (SSH keypairs, etc).
Plenty of times I've come back to my computer, typed my OS password expecting that it was locked, waited for my display's turn-on lag, and found that it wasn't locked (grace period). I type the password blind, but reserve the enter until I have visual feedback. At least typical IRC clients don't transmit until hitting enter. Browser omnibars and Javascript can send away every keystroke as it happens. Now I want to se…
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#87I broke out in to a cold sweat watching this as I remembered all the times I've inadvertently pasted sensitive stuff in to a document. It's still very cool though, I'll just need to remember to be careful when sharing documents.
I wonder how much sensitive information is inadvertently pasted into a browser location bar or autofill text box that's silently captured by web apps like Google Docs? I know I've accidentally done the "paste password" into those places accidentally at times.
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#88When can we get an IDE that can do this, and track copy / paste across source files :)
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#89Great article, fascinating. The author mentions that his system doesn't handle rich text, which is fine, but I'd just like to comment on how difficult of a problem handling rich text is. If anyone is interested in having a personal text-only replay editor, check out http://sharejs.org/ by an ex-Google Wave engineer. As far as handling rich text, I've talked to the original co-founders of Writely (which became Google…
Yup, collaborative rich text editing is a surprisingly thorny problem. ShareJS and Quill have actually been making some great progress on this though: https://github.com/share/ShareJS/issues/1
Re: How I reverse-engineered Google Docs to play back any document's keystrokes
#90A suggestion for further evolution would be an option to color text by the author that wrote it (for collaborated documents).