自 此提交 起，Discourse 工作人员现在可以锁定帖子。
锁定帖子会阻止其作者编辑该帖子。您为什么要这样做？有时用户发布了不当内容，工作人员会介入修改。在此提交之前，无法防止用户恶意将其改回。
要锁定帖子，请点击其下方的扳手图标并选择“锁定帖子”。
锁定后，帖子顶部将显示一个锁形图标，发帖人将无法编辑该帖子，直到解锁为止。
新增了一个站点设置 staff edit locks post（工作人员编辑锁定帖子）——如果启用，则每当工作人员编辑非工作人员用户的帖子时，该帖子将被自动锁定。这适用于大型论坛，以避免工作人员在每次编辑后手动锁定每个帖子的繁琐操作。
锁形图标仅对工作人员和帖子创建者可见。
工作人员始终可以编辑帖子，即使帖子已被锁定。
请尝试一下，并告诉我们您的想法！
I predict we’ll soon get moderators asking us what is the difference between “Closing a topic” and “Locking a post”. Couldn’t we at least spell the whole thing out as “Lock post editing”?
Maybe, I would wait to see if this actually happens before attempting to predict the future.
Hello from 11 months later. I was indeed confused by “lock” vs “closed” because “lock” is the terminology I am most familiar with from other forum software. I ended up having to go through all of my “locked” posts on my forum and change them to “closed” when the realization hit that “lock” here just means “lock from editing” not “lock from replies”. I agree with @erlend_sh here and urge you to reconsider the UX by being more explicit in the naming.
It’s a very rarely used function. To be honest we only implemented it because a certain very large, very important customer demanded that we have it. I’m not really a fan of it as a general feature, and I’m not even sure it makes sense as implemented.
Anyway, it sounds like you misunderstood “closed” first, and this wouldn’t have made any difference in that case.