3 ms·
1) saving is automatic 2) privacy-first architecture (e.g., plaintext is never uploaded, plaintext URLs are never uploaded etc)
by purplerails 12y ago
1) saving is automatic
2) privacy-first architecture (e.g., plaintext is never uploaded, plaintext URLs are never uploaded etc)
- lingben 12y agoah, so it saves... everything? wow! that's nuts. I mean, where the heck are you going to store all of that? and it is terribly inefficient to store say, 30,000 examples of the exact same article. or do you have a way to check and not store duplicates? if so, what if a blog post is saved today and has 10 comments and it is saved tomorrow by another person and it has 11 comments. technically the page is different so it would be saved again I think you need to explain exactly how it works a bit better or maybe I'm just not getting it :)
- purplerails 12y ago> ah, so it saves... everything? wow! that's nuts. I mean, where the heck are you going to store all of that? Please see my reply to idlewords. It isn't literally everything; there are some heuristics to detect what was interesting to you. I understand you might find this excessive. I routinely find that useful. :) See also "As We May Think" by Vannevar Bush. > and it is terribly inefficient to store say, 30,000 examples of the exact same article ... You're right: no deduping is and can be done across users (HMACs chained up the user's password are used create dedup hashes). Storage is sufficiently cheap that I feel it's a acceptable tradeoff vs. privacy (i.e., server being unable to confirm that two users have saved the same page).