Does the issue also happened with bostr (JS) or only happened with bostr2? I think we use same Websocket (ws) library in NodeJS so i wonder about it
Discussion
It seems like the chances of this similar problem happening is also the same as like how bostr2 version 1.0.0 (before fixed by 1.0.1) did. It's also using permessage-deflate.
I would say, Maybe.
Because one thai user that is used to host bot here is using Damus & that also reconnects crazy like the current issue did.