Sawood Alam

Here is a sample output draft. ```json { "original_uri": "http://example.org/index.html", "total_mementos": 54, "archives": { "web.archive.org": { "count": 53, "first": { "datetime": "2002-10-16T10:13:37Z", "uri": "http://web.archive.org/web/20021016101337/http://example.org/index.html" }, "last": { "datetime": "2016-04-10T22:12:45Z", "uri":...

Thanks @machawk1, the point is taken. We can perhaps make it more coherent across the board. However, the primary goal of this sample output was to communicate the intended implementation...

> What are your thoughts on having that same sort of breakdown (optionally, additionally, and/or in lieu of the inter-archive) on a per-archive basis? That is certainly doable if it...

> Adding `period` information also increases the size of the response. It sure does, but the number of items are capped to a max of `number of archives + 12...

That would be a good idea. Also, in the root of the repo, you can have a `main.py` file that uses this package to build the CLI. This would be...

Holding until browsers implement it. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers

The simplest thing to do seems to have a response header `Cache-Control: public` in certain responses. From there the client or proxy may choose how long they want to keep...

YAML would certainly be a very friendly format. However, Go does not have YAML parser built-in, but there is a very good third-party package for that. I did not use...

Yes, that's the one I was referring to.

No, it's not too late @galsondor. However, there are a few arguments in favor of YAML. - JSON is almost a subset of YAML that means if someone chooses to...