Skip to content

Resubmit PR#2908+2951 Bot self identification and bug fix. #3625

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 25, 2025

Conversation

Rider-Linden
Copy link
Contributor

#2908
Issue #2907

Process metadata sent along with chats of type `IM_NOTHING_SPECIAL', The metadata can contain information about the bot status of the sender. It may also contain a system-injected notification that is displayed to the agent as part of the 1:1 chat window.

Server PR https://github.com/secondlife/server/pull/1519


#2959
Adds optional parameters to addMessage which allow the function to override the icon and session name used for the chat while correctly naming and constructing the chat session.

See https://github.com/secondlife/server/pull/1519#issuecomment-2438596546 for issues addressed.

…G_SPECIAL, The metadata can contain information about the bot status of the sender. It may also contain a system-injected notification that is displayed to the agent as part of the 1:1 chat window.
…essage on behalf of the system, optionally specify the agent id and name that should be used.

(cherry picked from commit 7ff297e)
@Geenz
Copy link
Collaborator

Geenz commented Mar 1, 2025

This looks good, but I'm gonna give this one some pause here so we can better incorporate some feedback before we merge it. Here's a couple of questions that I think that someone on Product should jump in on (@kylelinden - can you forward this to the right person?):

  • Do we want bot interactions to be highlighted in a different text color?
  • Do we want to also include a toggle for the viewer to just ignore bot interactions?

@Geenz
Copy link
Collaborator

Geenz commented Mar 25, 2025

@Rider-Linden I'd say let's go ahead and get this merged into develop. Can you resolve the conflict on the message template?

@Rider-Linden
Copy link
Contributor Author

Sure thing. I've always thought we should remove that damn sha1 file from source control. It's generated as part of the build from message_template.msg.

@Rider-Linden Rider-Linden merged commit e452084 into develop Mar 25, 2025
13 checks passed
@Rider-Linden Rider-Linden deleted the rider/bot_tattle branch March 25, 2025 17:46
@github-actions github-actions bot locked and limited conversation to collaborators Mar 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants