I rather suspect we need a web-scale archiver: I -do not want- to be
running sqlite or whoosh at the scales of data we're looking at,
particularly with cross-list searches.
As far as this bug is concerned, I would say that yes, the mbox should
be obtained by a backend API call to get the mbox from the archive
server, and that it has nothing in common with the browsable archive &
search aspects.
I rather suspect we need a web-scale archiver: I -do not want- to be
running sqlite or whoosh at the scales of data we're looking at,
particularly with cross-list searches.
As far as this bug is concerned, I would say that yes, the mbox should
be obtained by a backend API call to get the mbox from the archive
server, and that it has nothing in common with the browsable archive &
search aspects.