-all-manifests parameter

[FatalBulletHit]

As mentioned in #148 and #205, an -all-manifests parameter would be a nice addition.

[azuisleet]

There is no such hypothetical "-all-manifests". Steam only provides the current manifest for a given app and its depots.

[psychonic]

No.

[FatalBulletHit]

Even if we keep calls to a minimum, e.g. by only requesting the entire manifest history if there was an update and caching the result?
Updates to a depot could be detected by comparing the latest manifest (which we get directly from Steam) with the latest cached one.

Ideally uploading the cached history rather than only saving it locally.

[psychonic]

Caching history of what DepotDownloader sees from Steam is a possibility. Scraping SteamDB is not.

[FatalBulletHit]

Obviously, I understand why we don't want any additional traffic on SteamDB, but I've probably caused more traffic by manually opening depot histories in my browser (which is allowed) than if I had scraped SteamDB on depot updates (which isn't allowed).
So, I think it'd also be in SteamDB's interest to allow minimum scraping as it would reduce traffic overall.

[psychonic]

Sure, if they say that scraping is allowed or provide an API, it can be considered.