Hi, when running through the discobot new user tutorial, there is a prompt to flag a very mean message. However, if the kind of flag chosen is not “inappropriate” but one of the other options, the tutorial hangs. I don’t see a way to add another flag to the post once it has been flagged for another reason besides “inappropriate.” Is there a way for discobot to say, “You flagged my post, but not for being inappropriate. Let’s try again!”
That isn’t a bug; the instructions indicate which flag type to use. So at best this would be an enhancement.
(also @tgxworld I’d expect any flag type to work, really… except contact staff which is a different thing.)
I agree with this 100%. If I had an instance where I wanted some of the flag options (including the inappropriate one) hidden via CSS, discobot would essentially be broken aside from overriding the step completely and telling the user to skip. Edge case of course, but it would be nice to allow all types of flags for that step ![]()
Yea, especially because it is designed to help a new user feel comfortable flagging a post. Setting them up for success = winning.
I’m comfortable calling this a feature rather than a bug - I see the point.
This is strange because I made the bot respond to all none custom flag types when the tutorial was added.
Are there any specific steps you took when you got stucked? Currently I’m unable to reproduce this locally or on your site.
I tried here on Meta with the “Something Else” flag and it does break the flagging step. Based on flag_types_without_custom.values, I’m assuming selecting the “Something Else” option doesn’t work since there is a custom value involved.
I really like that flag given its versatility. While I can’t think of a true downside to having all of the flag options visible, I have considered hiding all but “Something Else” and modifying the text to further convey a general usage. Just a simpler UI presentation to users.
If allowing the “Something Else” flag to continue the step is not an option (it would be nice if it was
), I guess another idea would be to hide it or disable it specifically for the discobot tutorial.
So @outofthebox I dispute the premise of this topic; almost any flag type will work except “something else” which is a PM to staff and requires typing in a custom reason.
Also in the discobot narrative, the user is explicitly told to use the “offensive” flag type, on top of that.
The problem isn’t that something-else doesn’t work (it’d be fine if Discobot replied back with “Oh no! You didn’t use the right flag type!” the same way it does when you reply without flagging the post). The problem is that, when the user takes this ill-advised action, the tutorial becomes deadlocked instead of giving them a chance to try again.
By the way, I’m actually able to un-deadlock the tutorial by posting a reply and then flagging Discobot’s “oh no, my nasty post hasn’t been flagged yet” response ![]()
Shouldn’t be the case – the bot will post a “hey, haven’t seen you in a while, want to continue?” message eventually.
Yeah, but that’s still a soft lock and requires a “skip” command to keep going.
The bot is designed for a new user who feels uncomfortable with forum software so they try discobot to learn the ropes, right? I think if there are ways the new user can make discobot fail, that is an area worth improving, if the resources required to do it aren’t unreasonably high.
我刚刚在 https://try.discourse.org 上测试了这一点。如果选中了“其他情况”标志,教程不会恢复——用户不会收到任何指示。用户可以通过发布 @discobot resume tutorial 来恢复教程。
当教程恢复时给出的回复并不清晰:
哦不,我那篇讨厌的帖子还没被标记。你能用 标记(图标)将其标记为不合适吗?
这条回复应该让用户知道他们需要标记最新的 discobot 帖子。用户无法标记 discobot 所提到的那篇“讨厌”的帖子。
编辑:也许我在失败的标记步骤后没有等待足够长的时间让教程恢复。我等了几分钟,但在 try 网站上,discobot 发布“刚来检查一下,因为有一段时间没收到你的消息”这条帖子似乎需要 10 分钟。
我想插一句——我刚才就遇到一个用户因此感到困惑。当然,他没有完全按照说明操作,但这个教程本可以更具容错性,并能更快恢复。
我们遇到了同样的问题。我们的一些成员将 Discobot 的消息标记为“其他”,因为他们认为应该这样做,结果卡在了教程中。
似乎没有明显的方法让新手在错误标记后返回并重新标记该帖子,这让他们感到困惑和沮丧。
或许可以将“其他”标记视为教程的一部分,以避免这种僵局?
4 篇帖子已移至新主题:Discobot 教程在选择“其他”标志类型时会卡住
当选择“其他”类型时,Discobot 不应再在此处卡住。