4 ms·
Thanks for the heads-up! Working on a fix so you can't query a private room and send in Matrix events. We already block from Gitter -> Matrix side.
by MadLittleMods 6y ago
Thanks for the heads-up! Working on a fix so you can't query a private room and send in Matrix events. We already block from Gitter -> Matrix side.
- MadLittleMods 6y agoUpdate: Fix deployed -> https://gitlab.com/gitterHQ/webapp/-/blob/develop/CHANGELOG.md#21110-2020-12-7 https://gitlab.com/gitterHQ/webapp/-/blob/develop/CHANGELOG....
- Vinnl 6y agoThanks! I'm still in the room with no feedback that sending the message failed, but from the room's point of view it's now private. One other thing: my message was still posted by @matrixbot, rather than by my Matrix user. Is this another case of every client having to migrate (I'm using Fractal)?
- MadLittleMods 6y agoThe virtualUser messages are being shepherded by `@matrixbot` behind the scenes but you shouldn't really notice that part. `@matrixbot` does show in the browser notification but we do plan to fix that up: https://gitlab.com/gitterHQ/webapp/-/issues/2695 https://gitlab.com/gitterHQ/webapp/-/issues/2695 If you see messages directly from `@matrixbot` in the chat area, then that means that the room is still plumbed using the old Gitter bridge. We're working on a plan to migrate rooms using the old bridge over to the new one, https://gitlab.com/gitterHQ/webapp/-/issues/2674 https://gitlab.com/gitterHQ/webapp/-/issues/2674
- Vinnl 6y agoAre you sure it's a room issue? In the same room where my message was sent directly by @matrixbot, I can also see an earlier message from someone else from @theiraccount:matrix.org.