Remote browser and general initial user experience

[deliciouslytyped]

I started using conifer yesterday and at least for my use case so far, archiving a specific site, it seems to be working very nicely.

However I've run into the following rather irritating / time-waste causing issues:

• remote browsers seem to crash rather often
• the above makes it a problem to wait for starting a new remote browser, which also seems to take a while, or may in fact be unreliable? (the browser starts but the connection doesn't work?)
• I'm archiving a lot of a site, and I have to log in every time i start a new session, this is a problem coupled with the above;
  • a large amount of logins may be suspicious?
  • if I somehow load a page where I'm not yet logged in, I fail to archive it's content, and then I have to redo the whole session; this seems to happen when the remote browser crashes or I lose the connection, and I have to reload the conifer page.

It would be nice if some sort of session template could be specified when loading a remote browser.

[luckdam]

Completely agree. We need a --save-cookies and cookies.txt option to save log in details or equivalent. I also need to look into why the remote chrome browser crashes so much. nothing in the docker-compose logs that I can see.

[KaineRecycler]

Another general user experience was allowing conifer to accept warcs from third party cloud services like Dropbox Google drive or Microsoft OneDrive which I am currently trying to do but it’s not working so it needs to be resolved please.