Awesome-Technologies
Has anyone got this working correctly?
Has anyone gotten this code to actually migrate a complete slackdump export?
Been refactoring this code over the last week to get it to properly import a "slackdump" export. Running Pylinter and PDB against this code points to all kinds of issues. It seems to be way more than just making a variable local --> global
I'll push the fork once its working for others to use/test
I'll share the fork url once it actually works fully. I've had to move to other work, but plan to get back to this fairly soon. I have ~15 Slack workgroups to move over to a hosted synapse server
Let me know if you make any headway with code or performing imports
While you're working on this... would it be possible to import the slack export into a Space? For example a Space Old Slack in the Matrix Server, under which all the rooms etc are created. I'm just asking because you seem to have familiarized yourself with this codebase now. But if I get time I can look at it myself.
RE Spaces:
Yup, its a room in a room. I initially have started down that path, but am thinking if there is a way to simplify everything by importing into a pre-built Space with all its Rooms. Then just import users and messages.
I suspect that the import would be a one time operation for most users, so inputting the needed information into a config file shouldn't be too arduous.
My use case is that I have bridged Matrix Spaces <==> Slack Workgroups to keep the users in a familiar space, yet provide an ability to access historical messages. We are a non-profit Federation of ~35 clubs, whose members are hard pressed to adopt another new technology. Many still only have a comfort with email, so to be able to bridge to our groups.io email digest is important, yet we need to keep everything in sync so we don't have conversations ending up only being available to a particular group of members.
Now I need to bring in the historical messages backed up with slackdump for organization legacy.
Ideas/input?
