Ask HN: How can I improve my note-taking web app?(scrib.in)
scrib.in
Ask HN: How can I improve my note-taking web app?
http://scrib.in
22 comments
I have a few ideas:
- 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
- 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
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.
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.
How does realtime actually work? Can you shed light on that, please?
Love the idea of realtime updates. Thanks!
"Text Messaging Communications Suite for Businesses." tell me something more than this
Don't use a static layout. I hate unnecessary scrollbars (like most users).
Remove 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.
Remove 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.
I'm curious, how do you securely implement client side encryption?
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.
[1] http://sebsauvage.net/wiki/doku.php?id=php:zerobin
[1] http://sebsauvage.net/wiki/doku.php?id=php:zerobin
[deleted]
Currently, this isn't implemented.
Thanks! Could you explain what you mean by using direct links?
Look at [1]. They suggest using this:
<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
<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
i dont get it. nothing but "deskrove We're building cool things."
Sorry - hosting messed up.
doesn't work