Package: toot Version: 0.27.0-1 Severity: wishlist X-Debbugs-Cc: debbug.t...@sideload.33mail.com
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). -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'testing'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-19-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages toot depends on: ii python3 3.9.2-3 ii python3-bs4 4.9.3-1 ii python3-requests 2.25.1+dfsg-2 ii python3-urwid 2.1.2-1 ii python3-wcwidth 0.1.9+dfsg1-2 toot recommends no packages. toot suggests no packages. -- no debconf information
