WARC'in the Crawler
marginalia.nu
marginalia.nu
My favorite capability of the WARC format borrows from the fact that most compression formats can be written to allow random access. Compression formats such as `gzip` and `zstandard` allow multiple compressed streams to be stuck together and act during decompression as if it's one contiguous file.
Hence you can create multiple compressions and literally stick them together:
$ echo cat > cat.txt
$ echo dog > dog.txt
$ zstd cat.txt dog.txt
$ cat cat.txt.zst dog.txt.zst > catdog.zst
$ zstdcat catdog.zst
cat
dog
For files composed of only a textual / clearly delimited format that means you can fairly trivially leap to a different offset assuming each of the inputs is compressed individually. You lose out on some amount of compression but random lookup seems a fairly reasonable tradeoff.
Common Crawl was able to use this to allow entirely random lookups into web crawl datasets dozens / hundreds of terabytes in size without any change in file format for example and utilizing Amazon S3's support for HTTP Range requests[1].Trading compression for random lookup is even more forgiving if you create a separate compression dictionary tailored toward your dataset. For web crawling you'd likely get you the majority of the compression gains back unless pages from the same website are sequentially written which is unlikely in most situations. The website's shared template/s would result in very high compression gains across files which you'd lose by allowing random lookup but most crawlers don't don't operate sequentially so local compression gains are likely smaller than larger.
[1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requ...
WARC as a format essentially states that unless you have good reason "record at a time" compression is the preferred[1]. The mixture of "technically possible" and "part of spec" is what makes it so useful - any generic WARC tool can support random access, there are explicit fields to index over (URL), and even non-conforming WARC files can be easily rewritten to add such a capability.
[1]: https://iipc.github.io/warc-specifications/specifications/wa...
Kind of a pity since it has the effect of making things that could be very easy, such as reading and writing parquet files, much harder than it needs to be in Java.
Nothing beats the user experience: Cmd-S in Safari and select “Web Archive”. It’s downloaded in permanent copy, indexed by Spotlight and accessible on all your devices.
I use it for collecting recipes around the web. However, I’m a bit concerned about data longevity. I’ve tried other more open formats (loved Singlefile) but none have the UX and support that this has. It’s so simple (as it should be).
Most browsers support MHTML: IE5's format, which is based on the .eml format. I think Firefox and Safari are the only major browsers that don't.
There's also the Mozilla Archive Format, which never really got popular for some reason: https://www.amadzone.org/mozilla-archive-format/ .
> I wish Apple would’ve open sourced the .webarchive format.
I mean… it's not like it's a secret. It's just very Apple-specific: binary plist and some other stuff.
Note: no affiliation, just in a deep rabbit hole on data
The WARC (Web ARChive) file format offers a convention for concatenating multiple
resource records (data objects), each consisting of a set of simple text headers
and an arbitrary data block into one long file. The WARC format is an extension
of the ARC file format (ARC) that has
traditionally been used to store “web crawls” as sequences of content blocks
harvested from the World Wide Web. Each capture in an ARC file is preceded by a
one-line header that very briefly describes the harvested content and its length.
This is directly followed by the retrieval protocol response messages and content.
The original ARC format file has been used by the Internet Archive (IA) since 1996
for managing billions of objects, and by several national libraries.