Room Server response slow and they go to the room not the requester.

[RecklessRewards]

I found that when I have the bot respond in a room server I have two issues.

1: the response from the bot in a room server can take up to a minute to respond, sometimes it doesn't respond. Response in a channel are almost immediate. See video.
https://github.com/user-attachments/assets/d15d066a-0a48-4d26-a183-34d38be098ec

2: when the bot is responding to a request it ack the room not the person requesting. See image.

[agessaman]

Hi, sorry for the slow response. This is a totally novel use of the bot that I hadn't anticipated. It opens up some cool opportunities for persistence, but it also has some limitations when it comes to timliness.

The summary of the room server message sending process:

1. Someone posts "ping" → the server saves it. The server waits 6 seconds before sending to anyone. It wants messages to "settle" so it doesn't send too many at once.
2. After the wait, it sends to one client at a time (round-robin). If other people are also waiting, the bot may wait for its turn.
3. Once the bot receives "ping", it processes and replies.
4. That reply will also sit for 6+ seconds.

Because of the build-in delays, for the bot to respond to "ping" there will always be a 6+ second delay from when "ping" is posted until the bot receives it, and another 6+ seconds for the return message. This pretty closely matches the 15 second delay in your video.

I think there's a possibility that the bot could be modified the bot to identify when it is interacting with a room server and respond accordingly. The room server message includes the timestamp, message type, and the original sender's identity as the first 4 bytes of the author's public key, along with the message.