It’s in DOWNLOAD button. How does it not work in EVERY browser?
A link would. A form submission would. Ultra simple JavaScript would.
It’s not a question of “why doesn’t chrome work“ but more a question of “how is this even an issue“.
A link would. A form submission would. Ultra simple JavaScript would.
It’s not a question of “why doesn’t chrome work“ but more a question of “how is this even an issue“.
In fact, they'd probably be perturbed by the bandwidth costs even if everyone who wanted the dataset was only downloading it once.
Maybe it uses WebTorrent?
(Not sure why it couldn't just fall back to giving you a .torrent file in that case, though.)
BitTorrent and related protocols handle this automatically by breaking the file into large (megabyte-range) chunks, and then putting the cryptographic hashes of all the chunks in the manifest. As long as you've received the manifest, you can protect against both passive corruption and active MITMing in the same way you resume broken downloads: by just discarding chunks that failed to complete to a state of "has all the bytes and hashes correctly", and trying those chunks again.
(Sadly, HTTP doesn't support a digest response header that applies to each chunk of a "Transfer-Encoding: chunked" response stream, or it could vaguely compete with this. The Content-MD5 header could have done this, but it was removed precisely because implementations were in conflict on whether it was for this, or for hashing the document as a whole.)
COCO (and friends) provide either cloud-backed rsync tools or curl snippets for this reason.
I’m really tired of people declaring other browsers “broken“ because they don’t implement the future-of-the-minute that chrome has already added.