It is possible to send messages even if a room is archived. The client shows a 'This room is read only' message but via the api it is still possible to send messages because there is no backend check. Even some of the clients were still able to write messages because they did not receive an update for the room(?)/did not reload.
The backend should check for the archived-flag and reject the message
The message is saved as if the room was not archived
this also happens with readonly rooms or rooms you've been muted in
:cold_sweat: don't let the vandals know...
How did you manage to get this to work with readonly rooms and rooms you've been muted in?
For a room were I have been muted, I get something like this:
ddp_asyncio.exceptions.RemoteMethodError: [You can't send messages because you have been muted]
And when I set a room to readonly all users get automatically muted, even the owner. Only with admin privileges I'm still able to write.
try the other API? theres 2 @smoehrle
I just found this too on my side. The channels I archived which were still appearing to my other users (since I'm not updating the data about archived channels yet in realtime) allowed the messages that were sent after archive.
In my case I'm using chat.postMessage to send the messages and channels.archive to archive a channel
@MarcosSpessatto fyi
@MarcosSpessatto any news on this?
Would, too, like to hear a status update. This is a bomb waiting to blow for every team.. (especially factoring in the readonly/muted)
Sorry for the long delay, I'll fix it for the next release. Thanks for let us know. :+1:
Most helpful comment
Sorry for the long delay, I'll fix it for the next release. Thanks for let us know. :+1: