No I actually cannot play back yet. But it's not hard to implement, it even would be relatively easy to selectively play back only certain edits.
I believe in the worst case a few thousand edits would suffice (though it would be rather tedious on the keyboard to do: type - then go back one with the arrow keys and type again).
Collabedit looks nice and solid! (Hadn't been aware of it.) Did you roll your own editor or did you use something like ACE or CodeMirror?
If 99% of your value is in the base product and 1% is in the advanced features, most people will chooses the cheapest plan available.
My customers don't care about ssl or extra storage so they'll always choose the cheaper plan. But if the basic plan was +$10 what percentage would still buy it?
He is not saying you should offer a second basic plan next to the primary basic plan. He is saying that you should AB-test two different basic plans, only one of them is visible for any given customer.
In order to maintain the usability of the URL in a heavily AJAX application.
For example, with movielandmarks I designed it so that you don't use back/forward at all. But I wanted to provide a useful URL for bookmarking and sharing with friends. So I used the hash for this because changing the actual URL of the page forces a refresh.
To save some state of your JS application which can be saved to bookmarks (or copy-pasted to someone else). For example, Gmail adds "#sent/12aa04feebaac50e" when I open an e-mail I just sent. Also, to get the "back" button to work properly in JS applications.
It was pretty tough to implement (for me at least). Especially when I got to using the "Bridger" and "Buffer" to transform.
Your approach seems much simpler. Do you retain the ability to "play back" the edits like etherpad did?
How big can a document get before you run into the precision issue you mentioned?