The Mastodon export feature is insufficient:

 * countless events can separate users from their data at any unannounced spontaneous moment
 * users can only request archives once every 7 days, thus ≥3½ days of dataloss is expected on avg.
 * the request is a cumbersome manual process (thus not done every 7 days)

There is a request to implement CLI-driven archival:

https://github.com/ihabunek/toot/issues/201

That feature would be useful, but it’s still only a partial
solution. In addition to periodic archivals it would be very useful
for individual messages to be stored locally to mitigate the loss of
data generated since the last fetched archival, just as an email
client would do.

Bonus points if those messages are formatted in mbox format or maildir
format, so we can simply use a mail user agent to browse recent
outbound msgs.

Optionally, it would be interesting if users had the /option/ of
having these cached msgs deleted upon the successful fetching of their
archive (assuming GH bug 201 is satisfied).