4 ms·
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 differe
by yoha 13y ago
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.
- obblekk 13y agoI'm curious, how do you securely implement client side encryption?
- deleted 13y ago[deleted]
- yoha 13y agoJust 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 http://sebsauvage.net/wiki/doku.php?id=php:zerobin
- altero 13y agoAdd 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
- napoleond 13y agoBut 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.
- drjake 13y agoCurrently, this isn't implemented.
- drjake 13y agoThanks! Could you explain what you mean by using direct links?
- yoha 13y agoLook at [1]. They suggest using this: <a href="https://twitter.com/share" 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 https://dev.twitter.com/docs/tweet-button