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?
既然 ChatGPT 已将机器人和人工智能领域推向中心舞台，人们开始提及使用 Discourse 论坛的数据作为训练数据。因此，这个主题似乎是两种可能性中的一种，另一种是 Discourse REST API。
我知道管理员有能力获取备份然后清理数据，最好有一个已知的标准。
我们能否获得此事的最新状态，即使只是“自上次以来没有变化”。 
这是我们人工智能团队的路线图。 
很高兴看到 Discourse 正朝着正确的方向发展，为那只小鸟感到难过。