TODO.org

V3.1

Database backend

Add database backend support to Dump converter, it relies on the files

Check if the thread export works as intended.

Conversion to and from.

Files and avatars support during conversion.

Tests for dbproc and related packages.

repository

control

dbproc

Resume will choke on export->database converted workspaces due to

missing “workspace” information. Find another way to verify the workspace name, possibly by team ID on the messages/users.

Info command, prints out the database sessions, workspaces and message stats.

Source detection

detect standard file storage

Removed the source storage flags in favour of Type method on Storage interface.

Universal search controller + tests

Export in db format missing “members”.

Converter from export and dump to database, where possible.

Boils down to reading the input and feeding through a Recorder with a database backend.

FIX double files in ZIP export

Verify that consequent calls of conversation.replies don’t have the first thread message as the item with 0-index.

Yes it does: #128 (comment)

Only participating users #287.

Attachment filter, use the same terms as channel filter, -filter-files=[public,private,dm] (#233)

Channel filter (private/public/DMs) -filter-channel=[public,private,dm] (controller already supports this)

Resume

user_not_found error when running with -channel-users

when resuming with -channel-users, and there are no new messages, the resume crashes with “no users collected”

V3.2

Starred items and bookmarks.

Connection pooling

load emojis alongside the messages during archive.

Static viewer output #416

Thumbnail download (#111)

Custom fields for users (#62)

Future

Aliasing users in the viewer, click on the username, assign a name, save.

detect external users and fetch them individually

even if running without -channel-users.

export compatibility (?)

/canvases.json is the list of all channel canvases (just slack files, files are not included).

/file_conversations.json contains list of all file conversations, conversations are presented as special directories. FC:<FILE_ID>:File_name, and contains date-files.

/users.json are formatted one json per line, comma at the end of each line, and it’s an array.

message JSON has empty fields omitted, while file JSON does not.

channel directories have a special “canvases_in_conversation.json” file that contains canvases in the channel as an array of files.

archived channels are included in the export.