3 ms·

So yes, that tool is intended for one-off archives. And I'm not surprised that the archives are large, given Matrix rooms live forever by default, so if you're

So yes, that tool is intended for one-off archives. And I'm not surprised that the archives are large, given Matrix rooms live forever by default, so if you're in some room like #matrix:matrix.org the full history goes back to Aug 2014 will be millions of messages by now. The 'right' solution is presumably to give Element a button to maintain ongoing archives on desktop (it already archives your encrypted rooms into an encrypted sqlite DB for indexing) - with a control to limit how far back in time it goes. Separately, having a "save the last N days/msgs of this room" button would be useful in Element Web. But both simply haven't got to the top of the todo list yet.

guerby 6y ago
Hopefully I checked and I'm not subscribed to matrix:matrix.org via my local ISP matrix+element :). I noticed the archive json files have timestamps, so may be 'archive since previous archive timestamp' would do the trick (if there's a way in the matrix protocol to do that, and if matrix software is efficient in ressources in this timestamp to timestamp case). And having a starting timestamp being channel join time minus a user specified number of days to go backward a bit in your archive.