After some time I have had enough, and deleted the conversation.
Bot didn’t get any clue about conversation was deleted on my end.
Bot keeps sending me messages, which my DC app sees as requests to setup conversation.
Expected behavior
After (4) (when user wants to delete conversation) DC app should automatically send /stop or equivalent, and maybe check for the answer before actual deletion of conversation.
Both bots and users should probably be noted on chat deletion.
this is not necessary, only sync the 1:1 chat deletion with the bot (on the bot side the bot should get an event that chat was deleted with the contact id, so bot can do cleanup in case some user data was stored in some external DB etc)
this is a privacy issue, if the user deletes the chat with the bot, they expect the chat/data to also be deleted in the bot side
don’t go so fast buddy, lets keep it for bots only for now, that was your original problem of the bot constantly sending you stuff
for a case of human ↔ human, it is more socially complicated because some people would say “but I don’t want others to delete the chat for me”, telegram also allows to delete 1:1 chat for both parties and I think we should do it that way as well, but to avoid endless discussions and move forward, let’s focus first on the bot problem that is easier to agree with
and I don’t agree with this, it would be annoying and in some cases awkward, it can be an old chat etc. and then user gets a notification, also this makes it more complicated to implement UI-wise, the bot thing is a small change in core (this is what I meant with keeping it simple for now so it is easy to move forward and not go asking for full-blown complex features)
It’ not about deleting chat. It’s about getting info of chat being deleted on other end.
I didn’t mean ‘Desktop notification’ (or their mobile analogy). It can be in the same way as change of disapearing messages timeout are handeled now - just specially styled mesage in chat log, not a ‘loud’ notification.
yo, you literally came to me complaining that you deleted the chat of PixelSocial bot but the bot keeps sending stuff, that was the problem you had and why I recommended you to open this post here, now you are diverging too much…
A way for the bot to fix this currently would be not to use 1:1 chat, but create a dedicated chat with just one user and send there. Then the user will be able to leave it without having to figure out which command should be sent.
the reason the bot can’t use groups is because webxdc API limitations, you don’t know to whom a webxdc status update belongs to, so you need the 1:1 chat as a way to warranty the identity of the sender
sure, this needs to be fixed/improved in core, but independently the feature to “stop a bot” by deleting its chat is the right approach and is how it works on Telegram which is “state of the art” wrt bots
also because creating an additional group is confusing for the user, when they scan the bot’s 1:1 QR they get the chat with the bot and then an additional group chat etc. a dynamic invite link that gives a command to the bot and the bot directly puts the user into a new group instead of creating 1:1 chat would also be nice
Sorry for late answer.
Yes, I literally came to you - because it’s your bot
But you told me it’s not the single bot problem, it’s common for all the DC bots, and method to handle such case should be added to DC. So my starting post here was more generic.
I can’t help to fix it, at least right now. But I can at least make this issue more visible.
But when some information is not available for human but in the same time available for bot - I see the discrimination of humans here
