Just like ZeroBin [1] does: verifiable Javascript file uploaded to client. It is far from perfect, but at least some control of what is sent to the server is given to the client.
I guess it relies on the HTTP referer field. You can do more resilient by adding parameters to the query string (look at the table at the third of the webpage).
It means that the user gets redirected to the website with pre-filled forms. It avoids loading additional Javascript.
I second https and history (I already commented on dynamic layout).
Offline would require some work I guess but it is still a good idea. However, I tend to dislike realtime webapp as they are always trying to sync sending HTTP/WebSocket and throwing errors around whenever one packet is lost.
Well, TCP certainly doesn't throw a fit if a single packet is lost, and this is a note taking app, right? Well, if I need a constant internet connection just to take notes then your app is far less useful to me and I probably won't use it.
22 comments
[ 3.7 ms ] story [ 55.8 ms ] threadRemove as much third party JS as possible (use direct links instead). Seven different domains is way too much.
Do you use (client-side) encryption for ensuring privacy?
Otherwise, I like the almost (share buttons) minimal design.
[1] http://sebsauvage.net/wiki/doku.php?id=php:zerobin
<a href="https://twitter.com/share" class="twitter-share-button" data-lang="en">Tweet</a>
I guess it relies on the HTTP referer field. You can do more resilient by adding parameters to the query string (look at the table at the third of the webpage).
It means that the user gets redirected to the website with pre-filled forms. It avoids loading additional Javascript.
[1] https://dev.twitter.com/docs/tweet-button
- should work offline
- realtime updates visible to other parties, so it would be usable as chat
- history
- align editor size to browser window size, so there are no two vertical scrolbars
- even better is to grow editor window as documents grow, use only browser vertical scrolab
- https, useless for me otherwise
Offline would require some work I guess but it is still a good idea. However, I tend to dislike realtime webapp as they are always trying to sync sending HTTP/WebSocket and throwing errors around whenever one packet is lost.
HN effect once more!