==> Downloading github.com/wabarc/wayback/cmd/wayback@master
==> Resolved version master to v0.12.1
==> Downloading binary for windows amd64
Error downloading, got 500 response from server
This does not help anyone since you can’t sideload an unreleased extension in Firefox anymore (except by manually installing it every time you start Firefox, via a “Debug Add-ons” menu).
I was curious about the IPFS archiving and it appears that it just inlines everything. This is a bit of a shame because with IPFS's content-addressing and deduplication it would be really cool if the assets were out-of-line so that they could be duplicated between webpages.
That being said there are problems with inlining IPFS URLs currently. Because few people support ipfs: URLs you essentially need to pick a gateway and embed that into the archived document which is unfortunate. That being said most people who run their own gateway intercept ipfs.io automatically so it is a sort of defacto IPFS scheme.
You could probably post-process this yourself if you wanted to to "pop out" the inline blobs.
I sometimes find that when I submit a link manually to Wayback or to archive.is, they may temporarily fail to save the link and I need to do it again. Other times they fail in a different way. In particular Wayback may say that a live version is not available even though it is.
Does this tool handle resubmitting the link for the kinds of failures that are temporary? And what do you do about permanent failures?
skraeling@moria ~ $ curl -sf https://gobinaries.com/wabarc/wayback/cmd/wayback > wayback
skraeling@moria ~ $ nano ./wayback
skraeling@moria ~ $ chmod 777 ./wayback
skraeling@moria ~ $ ./wayback
Am I doing something wrong here?