Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: How can I improve my note-taking web app?

scrib.in

Post reply on HN
Print view View original

11–20 of 23 posts

Re: Ask HN: How can I improve my note-taking web app?

#11

Post by yoha »

altero wrote: post #4

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

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.

Re: Ask HN: How can I improve my note-taking web app?

#13

Post by yoha »

drjake wrote: post #8
yoha wrote: post #2

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.

Thanks! Could you explain what you mean by using direct links?

Look at [1]. They suggest using this:

https://twitter.com/share" class="twitter-share-button" data-lang="en">Tweet

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

Re: Ask HN: How can I improve my note-taking web app?

#18

Post by napoleond »

altero wrote: post #7
obblekk wrote: post #3

Earlier quoted context omitted.

I'm curious, how do you securely implement client side encryption?

Add encryption key to URL after hash tag. This is not send to webserver, but can be decripted by js. You can not read text without full URL

But the Javascript that's doing the encryption comes from the same server that you're trying to hide the data from. Browser crypto does not work.
Post reply on HN