Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I'm interested to test Chronicler for Ubuntu (currently I'm using Ubuntu 20.04 Desktop) #1

Open
raphael10-collab opened this issue Aug 25, 2022 · 2 comments

Comments

@raphael10-collab
Copy link

I'm interested to test Chronicler for Ubuntu (currently I'm using Ubuntu 20.04 Desktop)

@CGamesPlay
Copy link
Owner

Hey! Chronicler is woefully out of date at this point and likely won’t compile on newer versions of Electron without some modifications. If you use the outdated versions listed in the repository, only minor modifications should be necessary. Unfortunately, my development of the project stalled when I found that building the browser UI was actually going to be more work than building the core functionality of the project.

I don’t have the capacity to help you with this version of Chronicler, but you can do anything you like with this code. What follows is basically a brain dump of my thoughts about the future of the project.

I have thought about what it would take to make a new, production-grade version of Chronicler, and I think the right approach is to build a backend application that functions as an archiving proxy server, and combine it with browser extensions that allow the user to switch to the proxy server when they want to access offline content or archive new content. This allows users to take advantage of their existing browser settings, including extensions and preferences, and also means that Chronicler doesn’t have to build a browser interface that matches user expectations. So the ideal version of Chronicler would look like:

  • A system daemon that works as a MITM proxy server which can archive content that it sees. It is controlled via an HTTP API and also hosts the search engine application (which is accessed as though it was a normal website).
  • A browser extension that interacts with the daemon to enable/disable the proxying/archiving functionality.

@raphael10-collab
Copy link
Author

Thank you for your kind explanation

It looks that the second option, A browser extension that interacts with the daemon to enable/disable the proxying/archiving functionality, might be simpler to use

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants