Open dchao19 opened 8 years ago
I think we should save a static page, but on reloading it, it reloads from the server, becoming dynamic.
For storage, I don't see the need for a separate encryption server, especially if people want to access stored tabs offline. Also, nedb is a great database that provides a mongo like api, but is purely javascript, and can run in memory in a browser.
I am a little concerned about the legitimacy of this project. What happens if the website gets updated and the DOM is changed? Do we forcefully change the content of the live webpage visible to the user? This could be misleading.
I think we should serve up a static page that is only a cached copy, but clicked links would still reference the real website. This way, the data can be saved/reloaded safely and we don't risk user confusion.
Also, how do we want to save the data? Storing it on a database that is network-accessible seems intriguing, but insecure. The same problem will occur if we use HTML5/Chrome local storage. I was thinking of encrypting the data using an encryption server (per se) and store then store the encrypted data in Local Storage. This obfuscates the data so people with a data analyzer cannot see it and it keeps it local (only the public key is stored on the server).
Does this threaten the concept of the project?