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
Support for Enterprise slack instances? #273
Comments
Hey @yarikoptic, thanks for the suggestion! Right now it would prevent the export from working on the enterprise instances. I suspect, the workaround would be to "observe" the edge api and making a custom call to the edge APIs. |
It looks like we have the code here, but it is not being actively used in the codebase. |
I even know who wrote it 😂 It's just a stray one from one of the experimental branches that I did not want to lose. Did not go far with it. It will need to be revised. |
Known restrictions:
|
Experimented with this over the weekend - findings: Slack does not allow to seek past Page 100, when page > 100 requested, Slack I'll take a break from this, maybe some idea comes up. |
Hey @yarikoptic , with the great help of a slackdump user in Telegram, we were able to get it going, you can check the "v3" branch.
The only thing you need to do, is to use the In the examples I will use the "record" format which is a new way to save the Workspace information implemented in v3. It is already quite stable, so the plan is for future versions to support it unchanged. I'll show how to convert to export further, please keep reading. ExportingTo export full workspace (in the "chunk" format):
To export some conversations:
This will create "slackdump_" directory. I will refer to it as "slackdump_record_dir" further in this message. To get the chunk format spec:
EXPERIMENTAL: viewing the archive"View" allows to view the slackdump record archives, Slack and slackdump export ZIP files and directories, and Slackdump dump archives. It will detect the format automatically. To view the archive, run:
Then head to http://localhost:8080 Converting to Slack export formatIf you wish for some reason to convert to slack export format, run this command:
Any feedback is welcomed. |
Getting helpHelp is still in progress, but most of the commands will provide the flags and their description. To get the list of commands:
To get help for the command or read a help topic:
To get help on a subcommand:
for example
|
Thanks for your hard work on this @rusq ! Really appreciated it! I can confirm that it works on my side as well. I checked out |
Hey @xiaket, thank you for the feedback! Sorry about that, v3 is in heavy development, I have renamed "record" to "archive" to make the purpose more clear, I'll update my prev msg. |
@rusq I have also verified this works as advertised off the
To get past this I updated the regexp used in
Thanks for all you work on this. |
Hey @hutchiko thanks for letting me know, I'll update the code and tests, when able! Glad that you were able to make it work. |
Is your feature request related to a problem? Please describe.
Tried to auth against our dandiarchive instance which is on mit's enterprise slack instance.
after telling slackdump to dump list of conversations and going through authentication in a browser just getting
❯ ./slackdump -w dandiarchive Slackdump dev (commit: placeholder) built on: 2077 authenticated. 2024/02/29 23:41:53 > checking user cache... 2024/02/29 23:41:53 retrieving data... 2024/02/29 23:41:53 application error: callback error: enterprise_is_restricted
Previously successfully fetched a list for another slack workspace on a "regular" slack instance
The text was updated successfully, but these errors were encountered: