Closed mr-flibble closed 2 years ago
Sure. Based on some quick testing of the official slack exporter, the output zip seems to have the following hierarchy:
users.json
integration_logs.json
channels.json
groups.json
dms.json
channels.json
, containing message json filesOnly users.json
and channels.json
seem to be required by slack-export-viewer
. Since I don't have a paid Slack plan, I can't test groups.json
and dms.json
via the official exporter myself.
Also, the official slack export splits up message jsons in channel directories by date (e.g., 2021-11-18.json
); fortunately slack-export-viewer
doesn't seem to care about this, so a single .json
inside each channel directory should work just fine.
To replicate this behavior with the slack-exporter
, try the following:
--lc --json
to a file called channels.json
at the root of this directory. Duplicate it to dms.json
. In the channels file, delete any entry where "id"
doesn't start with C
. In the dms file, delete any entry where "id"
doesn't start with D
."name"
param. Export history for each channel and/or DM with -c --ch ID_HERE --json
and put each json in its corresponding subdirectory.slack-export-viewer
to that directory.Hope this works! Feel free to close if so.
Thanks! I haven't succeeded yet, but I'll let you know if I do
Helo, any idea how can output be manipulated, to be compatible with https://github.com/hfaran/slack-export-viewer ? Thanks