Rewriting binary WebSocket packets to text

[Jimbly]

Apologies in advance if I've arrived at the wrong place. I am the developer of Worlds FRVR (https://worlds.frvr.com/). It appears some users are trying to play it via what appears to be a proxy at https://artclass.site/ which brought me to their support, who said they use this project for their HTTP rewriting, so I thought I'd pass the error along here. Users are unable to play (and it's causing various errors we're noticing) due to the proxy turning binary WebSocket packets into text WebSocket packets (and losing information along the way). Feel free to close if there's nothing you can do about this, I'm just passing along the issue =).

[desplmfao]

that would probably be an ultraviolet issue, this is just the backend for it.
neither githubs host "artclass.site" though, so its just a general issue.

[desplmfao]

ultraviolet has been pretty shit lately so i would just recommend using some proxy blocking script tbh

[mdoryammilwalrus]

Probably Ultraviolet, the bare spec says it should keep binary / text data

You could set up a bare server and try using it to forward websockets:
https://github.com/tomphttp/specifications/blob/master/BareServerV3.md#create-a-websocket-tunnel-to-a-remote