>>67193448The server automatically sends the room's entire chatlog when you connect, so there isn't a way to keep a massive log from hitting you. But maybe there's a way to block specific websocket messages from being read by scripts, so they never propagate as chat messages, so it doesn't crash your browser/phone. I'm not as well-versed in that as I should be.
Alternatively, maybe a script could use the timestamp to immediately cull any message older than 5 minutes, so even if the initial load can't be stopped, it never runs out of RAM.
And yes, I am doing this instead of just asking the dev to give us a button for it because that would require talking to people.