Fixing the long time no see warning for AI personas

Support
, ,
1

That is the long-time-no-see warning when started a PM to an user that hasn’t visited over 30 days.

The image depicts a screenshot of a text box with a blue border, situated in a gray window, containing the text "Mika" and an icon representing a speech bubble. (Captioned by AI)
The image depicts a screenshot of a text box with a blue border, situated in a gray window, containing the text "Mika" and an icon representing a speech bubble. (Captioned by AI)2360×353 91.1 KB

But that user is an AI-persona. And that happens with only with this one.

I reckon this comes from one idiotic action I did some times ago. I added that as an user to private group chat. At that time my goal was give ability to mention AI if needed. Well, that wasn’t such good idea, because it answered to everyone all the time.

But an admin can’t kick out an user from group chats, but that user must do it, and an AI persona can’t. So, I impersonated it, say goodbye to group chat, logged out and everything was happy and sunny again, and the globe was even more rounded.

Three things happened, though.

I don’t think this would be a pure bug, because there is really big chance it was born because of me. But I know I’m not the only one, because the question of how to drop an AI from group chat has asked and I guided that impersonating trick :woozy_face:

So:

  • can I do something to fix that (other than deleting that pseudo-user and re-creating it)
  • is there something on code level that could stop this happening in the future

Not a major issue, sure. That warning is just annoying.

2 Likes
2

What happens if you post as the bot while impersonating it somewhere (the notice of welcoming back the bot appears), then delete that post so it is hidden, and then it will be fine?

3

But wouldn’t same happen again after 30 days (or what the limit now is)?

3 Likes
4

What happens if you hop into PSQL in the container and do UPDATE users SET last_seen_at=NULL WHERE id=bot-id-here;?

5

With ID no go. But changing to username worked.

Thanks!

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.