You shouldn't be. I saw you in there since I fixed it. There could still be a bug or two since the update. But I did see you in the chat.
The new code does do some blocking. But only in specific situations that shouldn't apply to you. And it should give you a system message if it does temporarily block. Basically, the new code is going to block people who have zero posts on the site from coming by and sliding the chat. And a few other odd things. I actually wanted to keep that more low-key and let someone who discovers those features discover them on their own. But if it is affecting you then there could be a bug. In any case it should say why.
So there was no indication of why it didn't go through? At least some did because it's there, and beenPoisoned also replied to you in chat. Was there a red disconnect warning on the chat when you hit send? Sometimes a WebSocket can break, and it takes half a second to reestablish the link. There is code to hold the message and send it after the re-connect, but you never know. From my own tests it seems everything should be working.
I'm going to plumb in some more diagnostic stuff into the new code.
Log in
You shouldn't be. I saw you in there since I fixed it. There could still be a bug or two since the update. But I did see you in the chat.
The new code does do some blocking. But only in specific situations that shouldn't apply to you. And it should give you a system message if it does temporarily block. Basically, the new code is going to block people who have zero posts on the site from coming by and sliding the chat. And a few other odd things. I actually wanted to keep that more low-key and let someone who discovers those features discover them on their own. But if it is affecting you then there could be a bug. In any case it should say why.
So there was no indication of why it didn't go through? At least some did because it's there, and beenPoisoned also replied to you in chat. Was there a red disconnect warning on the chat when you hit send? Sometimes a WebSocket can break, and it takes half a second to reestablish the link. There is code to hold the message and send it after the re-connect, but you never know. From my own tests it seems everything should be working.
I'm going to plumb in some more diagnostic stuff into the new code.
It's working fine now. It was yesterday when I posted this, and was typing stuff in chat and noticing it wasn't appearing.
Also, on https://cytu.be/r/matrixhub , the chat still isn't working in the same way.
youre banned bud. for crimes against the fatherland.