The discussion centers on implementing a public data export feature for Discourse, similar to Stack Exchange’s public dumps, which would sanitize private user data and offer exports in JSON and HTML formats. Proposed benefits include enabling CC-licensed content redistribution, increasing user trust by ensuring content longevity, and supporting data analysis. While some users like obvio171 and samwilson strongly support the idea, codinghorror suggests prioritizing the individual download button first. tobiaseigen proposes integrating filtering options (by user, topic, or keyword) into the export tool. EricGT highlights growing interest in using Discourse data for AI training, noting that while admins can manually sanitize backups, a standardized export tool would be preferable. As of Falco, this feature is now on the roadmap for Discourse’s AI team, signaling active development. EricGT expresses optimism about Discourse’s direction amid broader AI trends.
I’d like to propose a public data export feature similar to Stack Exchange’s. This is not the same as the backup feature, because it requires sanitizing all private user data first. Both JSON and HTML export formats would be great.
This is useful for:
Let me know what you think.
Sounds like a great idea, would you like to work on something like this?
I would rather see the individual download button on the user page working first.
Maybe these are related. E.g. the functionality provides filtering options during the export process. Export content from these users, these topics, these keywords etc.
This would be great!
Did this feature ever get built? What’s the best way to provide public exports of a site?
Now that ChatGPT has moved the world of bots and AI closer to center stage, starting to see mention of using the data from a Discourse forum as training data. As such this topic seemed like one of two possiblities for such, the other being the Discourse Rest API.
I know admins have the ability to grab a backup and then santize the data, having a known standard would be prefered.
Can we get a current status on this even it is only, no change since last time. 
This is in our roadmap for the AI team now. 
Glad to see Discourse is headed in the right direction, so sad for the little bird.