Mark all as read

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Importing StackExchange dumps


Users of StackExchange use the platform with the understanding that questions and answers are available under a CC licence and SE makes a dump of its content available under This gives some control back into the hands of the community, since in the case of disagreement a community can take the data and host its own side, essentially forking the community.

Would it be desirable for codidact to import some of these dumps for its own community, so users can refer to old answers instead of having to recreate already existing content.

Why should this post be closed?

1 comment

Thanks for the link to the dump on . I didn't know that maintains a dump in a form that's easy to grab. It may come handy some day. Nick Alexeev‭ 30 days ago

1 answer


We've tried something pretty much like that.

Specifically, both Writing Codidact and Scientific Speculation Codidact were seeded with content from Writing SE and Worldbuilding SE, respectively. (The former with what essentially amounted to a full copy; the latter with a subset of posts.)

It sounds good in theory, and I was actually in favor of it at first, but it does have one huge drawback that has become obvious to me in retrospect.

It makes the new site basically indistinguishable from the old one at the time of the import.

It thus gets difficult to answer the obvious question of "why should I go to X Codidact, instead of X SE, which is where everyone else is actually, you know, adding new content?". The Codidact site simply lacks any kind of a unique selling point other than the fact that it isn't Stack Exchange. Which is a major point for many SE refugees, but let's face it, for most people it doesn't really matter which entity is hosting the content.

Thus, without a reasonably large user base who are basically just waiting for the new site to pop up before they post additional content (questions and answers alike), differentiating the Codidact site from the corresponding SE site becomes very difficult. It then makes more sense to do something similar to what the folks behind the Electrical Engineering Codidact did: have a plan for seeding the new site with some content, and then draw in subject matter experts who can both answer questions that get posted and help spread the word.

Now, if a SE site is in actual danger of being shut down and the community wants to preserve the content in an easily browsable form, or maybe even set up a new community elsewhere and migrate the content, that's a different matter. However, a discussion would still be needed on the reason why the site in question is in danger of being shut down. The reason why Stack Exchange might want to shut down a site might not apply to a Codidact site, but without a frank discussion about the specific case, it would be difficult to know.

1 comment

Thanks for the elaborate answer. I agree important old data is not enough to create a community. Maybe this should only be done for communities that have enough momentum to create a sustainable group on this site. Peter‭ about 1 month ago

Sign up to answer this question »