Thanks to @vgabruzzo, I think we have the problems with migration fixed and could try moving some content. @lspector asked a question, however, that I thought we wanted to address before I go and poop all over the world.
I should also say that we’re going to be disconnecting the Internet here at the house shortly, traveling tomorrow and Sunday, and getting things put back together in Morris at the beginning of the week (including re-establishing Internet at the house there), so nothing big will happen for most of a week regardless.
Continuing the discussion from Test topic created via the discourse_api gem:
I think the short answer is not really. The longer answer depends a lot on how we follow conversations on Discourse. In theory since none of us are following any of the conversations in “Slack Archives”, all that will go up without impacting things like what shows up in the little speech bubble at the top of the Discourse UI. It will, however, totally flood the “new posts” space
In looking at these few test posts, one thing that occurs to me is that if I include all the
@mcphee style user references, then we’ll all get included/notified about all those conversations, which will completely flood things for all of us that were using Slack. I’m now thinking that I should replace those with something like
@ mcphee (i.e., putting a space between the ‘@’ and the name) so Discourse doesn’t see them as user references, but they could still be searched for.
All this said, the question now stands – do we want to try this migration? I can do something small like migrate the first 10 messages across just to see what that does, or we can decide this was a Bad Idea and look for an alternative way to archive the Slack content if you’re worried about flooding Discourse.