Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When exporting conversations, only export participating users #125

Open
mootari opened this issue Aug 31, 2022 · 1 comment
Open

When exporting conversations, only export participating users #125

mootari opened this issue Aug 31, 2022 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@mootari
Copy link

mootari commented Aug 31, 2022

Is your feature request related to a problem? Please describe.

When a specific conversation is exported via the -c argument, the users.json file will still contain the entire members directory. In popular Slacks this can easily be megabytes of data even when only a conversation between two members gets exported. This data may also contain PII that I'm not allowed to store outside of Slack.

Describe the solution you'd like

When exporting conversations, allow the export of users to be limited to participating members.

Describe alternatives you've considered

  • I tried to export with the -no-user-cacheargument, but it will fail with application error: failed to create an index: empty users data base.
  • I could manually read and purge the users.json, but this feels error prone.

Additional context

  • I've deliberately left out mentions, because for archival purposes their user data shouldn't be relevant (I think?).
  • Restricting to participants may also speed up the export, as fetching the entire user directory can take a minute. I realize though the current architecture may not support this boost.
@mootari mootari changed the title Only export participating users when exporting conversations When exporting conversations, only export participating users Aug 31, 2022
@rusq rusq added the enhancement New feature or request label Aug 31, 2022
@rusq rusq added this to the v2.3.0 milestone Oct 17, 2022
@rusq
Copy link
Owner

rusq commented Nov 3, 2022

TODO:

@rusq rusq modified the milestones: v2.3.0, v2.3.1 Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants