Quota, DOS protection, or verification for the game relay server

It strikes me as a little dangerous to be running an open websocket relay server with no verification of its intended uses. Scenarios to think about:
1. Kid writes a cool game, shares on YouTube or something, it "goes viral", suddenly we have millions of connections.
2. Someone finds the protocol documentation, and decides to use it for their own unrelated shady commercial service, and suddenly we're handling millions of connections that aren't even about CodeWorld at all.
3. Someone thinks it's funny to take the system down, creates a session with 2000 players (because the work grows quadratically with the number of clients), and floods it with traffic from malware-infested systems.

It would be good to think about some of these issues. They are not pressing yet, but I'd rather they don't become pressing in the middle of the night!

オープンな websocket リレーサーバーとそのプロトコルドキュメントを確認し、未検証の利用、接続数、大規模なセッション、クライアント側の二次的な処理量について記載されたリスクに重点を置きます。実装前に、具体的な保護方針と測定可能な上限を定義します。リレーに予期しない負荷や悪用された負荷に対する合意済みの保護策があり、検証またはクォータの動作が文書化されていれば完了です。

索引モデルが issue の本文から書いたものです。