Run a separate websocket server reporting the transport as "snowflake"

Description

Also, maybe we also need to spin up a pretty much identical but separate websocket server, to more easily measure the number of snowflake proxies available?

If we wanted to purely count Snowflake users, does it make sense to spin up another websocket server and maybe label it as "snowflake" instead? Is there anything special we need to do to get it displayed on the metrics website?

This is what we should do. (I meant to do it already...) It will be a websocket server but will record users as snowflake.

Child Tickets

Oldest firstNewest firstThreaded

Show commentsShow property changes

Change History (3)

What I'm planning to do is just to import the existing websocket-server code into the snowflake repo, and make the necessary changes. The necessary changes are pretty trivial, but perhaps we'll want to make further changes independent of the upstream websocket.git repo, like #18628.

I added the server source code to the snowflake repo. I put it in the /server directory, moving the existing WebRTC server out of the way into /server-webrtc. Here are the commits related to the server source code:​c4cfc7f8 Move server to server-webrtc.​e5370551 Add a copy of websocket-server in the server directory.​cfca4767 Build the websocket-server.​a269053a Make Snowflake-specific changes to the websocket server.