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.
Acabei de testar isso em https://try.discourse.org. Se a opção “Algo mais” for selecionada, o tutorial não é retomado — nenhuma instrução é fornecida ao usuário. O tutorial pode ser retomado publicando @discobot resume tutorial.
A resposta fornecida quando o tutorial é retomado não está muito clara:
Oh não, minha postagem desagradável ainda não foi sinalizada. Você pode sinalizá-la como inadequada usando o sinalizador (ícone).
Essa resposta deveria informar ao usuário que ele precisa sinalizar a última postagem do discobot. Não é possível sinalizar a postagem “desagradável” à qual o discobot está se referindo.
Edição: é possível que eu não tenha esperado tempo suficiente para o tutorial ser retomado após a etapa de sinalização falhar. Esperei alguns minutos, mas no try, parece levar 10 minutos para que a postagem do discobot “só passando para ver, já que não recebi notícias de você há um tempo” seja criada.
Só para dar minha opinião aqui — acabei de ter um usuário confuso por causa disso. Claro, ele não seguiu as instruções exatamente como deveria, mas o tutorial poderia ser mais tolerante e retomar rapidamente.
Estamos enfrentando o mesmo problema. Alguns de nossos membros marcaram a mensagem do Discobot como “Outra coisa” porque acharam que era isso que deveriam fazer, e ficaram presos no tutorial.
Não parece haver uma maneira óbvia para um novato voltar e marcar a postagem novamente depois que a marcação “errada” foi feita, o que os confunde e frustra.
Talvez as marcações “Outra coisa” pudessem ser contadas como parte do tutorial, para evitar esse impasse?
4 postagens foram movidas para um novo tópico: O tutorial do Discobot trava se o tipo de flag ‘algo mais’ for selecionado
O Discobot não deve mais travar aqui quando “outra coisa” for selecionada.