So I think sockbot's exposed a bug with the following repro steps:
- Start a chat with someone
- Before they click the notification, change the title of the chat
- Expected: They observe one chat notification. Actual: they observe two chat notifications, with identical participants and text
The UI seems to have disabled the ability to rename chats?! It's still accepted by the websocket, or else sockbot wouldn't be able to cause this issue for me to try and repro in the first place.
The UI seems to have disabled the ability to rename chats?!
You can't rename a chat you aren't the starter of.
@ben_lubar Neither of the participants in the chat can rename it according to the UI though. Well. Hers went thorugh, but it she had to hack it into letting her.
ETA: upon further inquiry, a refresh enabled her ability to rename.
Hers went thorugh, but it she had to hack it into letting her.
clarification, they went through, but threw a boat load of "you have insufficient privileges for this action" toasters, when i refreshed to get the websocket appearing in dev tools 9they had been closed at the time) the issue went away entirely......
Have you tried repeating step 2 dozens of times?
Asking for a friend.