Page Requirements

• ability to add a single page to the archive (like echo <url> | archivebox add)
• ability to import a list of pages / feed of URLs into the archive (like archivebox add <url>)
• link to the homepage of the index /
• link to the django admin list of URLs for editing the archive /admin/
• link to the archivebox github repo & documentati

Please forgive me if there is an issue already or document anywhere, but I have tried to google, but no luck at the moment.

I would like to know what is the change between Backstop js 3 and Backstop js 4? Is there something deprecated or no longer used in v4 based from v3?

If you click a link from your Aquatone report, and your viewing it from a VPS http server, it sends referrer links with the location of the report along with the request.

Could you add rel="noreferrer" to the links that are generated so this doesn't happen?

Thanks

Steps to repro:

Run the command from documentation
docker run --net=host -v ./CONFIG_FILE.yaml:/etc/rendora/config.yaml rendora/rendora

What I have tried:

1. git clone repo && cd to config_examples && run with docker run --net=host -v ./CONFIG_FILE.yaml:/etc/rendora/config.yaml rendora/rendora
   Return value is
   docker: Error response from daemon: create ./CONFIG_FILE.yaml: "./CONFIG_

setCookie documentation in README.md says:

Parameters

• name string The name of the cookie.
• value string The value of the cookie.
• options (optional, default {})
• url string The request-URI to associate with the setting of the cookie.

So this should work:
await mainTab.setCookie("cookie", "1", {}, "http://example.com")

It does not. Right syntax seems to be:
`await mainTab.setC

New Edge browser is officially out and it is based on Chromium now, offering the Chrome Devtools Protocol - same one as in Chrome or Chromium headless.

Here are some ressources on this new version:

• [Edge Devtools on Chromium](https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide

Are you submitting a bug report or a feature request?

Feature request/documentation enhancement

What is the current behavior?

The requirements for a user to get up and running are insufficient with regard to the requirements and dependencies. I encountered this experience when trying to resolve #31 on a fresh Win