Live data from Hacker News

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

scrib.in

1–10 of 23 posts

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

#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.

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

#3
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.

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

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

#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

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

#5
post #3
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.

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

[deleted]

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

#6
post #3
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.

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

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

#7
post #3
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.

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

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

#8
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?

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

#9
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

Love the idea of realtime updates. Thanks!

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

#10
post #3
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.

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

Currently, this isn't implemented.
Post reply on HN