Discobot flag step requires any flag except "Something Else"

[outofthebox (Carson)]

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!”

[codinghorror (Jeff Atwood)]

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.)

[tshenry (Taylor)]

@codinghorror

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

[outofthebox (Carson)]

@tshenry

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.

[tgxworld (Alan Tan)]

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.

[tshenry (Taylor)]

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.

[codinghorror (Jeff Atwood)]

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.

[notriddle (Michael Howell)]

@codinghorror

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.

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

[codinghorror (Jeff Atwood)]

@notriddle

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.

Shouldn’t be the case – the bot will post a “hey, haven’t seen you in a while, want to continue?” message eventually.

[riking (Kane York)]

Yeah, but that’s still a soft lock and requires a “skip” command to keep going.

[outofthebox (Carson)]

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.

[simon]

@codinghorror

그렇게 되어서는 안 됩니다 – 봇이 “오랜만이다, 계속 진행할래?”라고 게시물을 올릴 것입니다.

방금 https://try.discourse.org에서 이 문제를 테스트했습니다. “기타” 플래그가 선택되면 튜토리얼이 재개되지 않으며, 사용자에게 어떤 안내도 주어지지 않습니다. @discobot resume tutorial을 게시하면 튜토리얼을 재개할 수 있습니다.

튜토리얼이 재개될 때 주어지는 응답은 명확하지 않습니다:

아, 내 거슬리는 게시물이 아직 플래그가 지정되지 않았네요. flag(아이콘)를 사용하여 부적절하게 플래그를 지정해 주시겠어요?

이 응답은 사용자가 최신 discobot 게시물을 플래그로 지정해야 한다는 것을 알 수 있도록 해야 합니다. discobot이 언급하는 “거슬리는” 게시물을 플래그로 지정하는 것은 불가능합니다.

수정: 플래그 지정 단계가 실패한 후 튜토리얼이 재개되기를 충분히 오래 기다리지 못했을 수도 있습니다. 몇 분 정도 기다렸지만, try에서는 discobot의 “오랜만에 안부를 묻고 있습니다” 게시물이 생성되는 데 10분이 걸리는 것으로 보입니다.

[adamengst (Adam C. Engst)]

여기서 한마디만 보태자면, 방금 한 사용자가 이 부분 때문에 혼란을 겪었습니다. 물론 사용자는 지시를 정확히 따르지 않았지만, 튜토리얼이 더 관대하고 빠르게 재개될 수 있도록 개선될 수 있을 것 같습니다.

[meiadeleite (ana)]

저희도 같은 문제를 겪고 있습니다. 회원 중 몇 명이 Discobot 메시지를 "기타"로 신고했는데, 그게 해야 할 일인 줄 알고 그렇게 했다가 튜토리얼에서 막혀버렸습니다. 잘못된 신고가 접수된 후, 초보자가 다시 돌아가서 게시물을 다시 신고할 수 있는 명확한 방법이 없어 보이는 것 같아서, 회원들이 혼란을 느끼고 좌절하는 것 같습니다.

이러한 교착 상태를 피하기 위해, “기타” 신고도 튜토리얼 진행에 포함시켜 주시면 어떨까요?

[blake (Blake Erickson)]

"기타"를 선택해도 Discobot이 여기서 더 이상 멈추지 않아야 합니다.

‘기타’ 플래그 유형을 선택하면 Discobot 튜토리얼이 멈춥니다

이 문제를 해결하기 위해 수정 사항을 만들었습니다. 이제 discobot은 올바른 플래그 유형을 확인합니다. 잘못된 플래그가 사용되면, 사용자가 올바르게 하지 못했다는 것을 알리는 응답을 보내고, 잘못된 플래그를 제거하여 사용자가 다시 시도할 수 있도록 합니다. 현재 동작 방식 데모는 다음과 같습니다: [unicorn]