gavinwahl / websocket-channel-server Goto Github PK

Seems like there should be some. @rockymeza what do you think should be logged?

I think we can just print stuff to stdout and let systemd or whatever handle the rest.

Something like

websocket-channel-server [bindaddr [port]] [-v|--verbose]

Use libsodium signatures to allow the channel creator to give invitations with authenticated data in them, like a username. By putting a public key in the channel name, only the room creator will be able to sign data (assuming they keep the private key private).

/anything/<public-signing-key>?<key>=<signed-value>[&<key-2>=<signed-value-2>...]

The URL before the ? is the room name, after are signed key-value pairs that are broadcast to the rest of the channel members if their signature validates.

I'm thinking that keys starting with an underscore should be reserved for future use.

I want numbers about how many concurrent clients are possible etc