We definitely want eOS to use by default the Orchil client, but its unclear to me if it should be a submodule in this repo. I also presume that Orchil can't be served by DGD and must be served by the websocket-to-tcp tunnel node.js service.
It is likely that eOS doesn't need the full thin-auth, but it is pretty darn close to an MVP of what a chat theatre or a small game needs. Otherwise user admin has to be done in different ways. But don't know.
@noahgibbs What are your thoughts?
We definitely want eOS to use by default the Orchil client, but its unclear to me if it should be a submodule in this repo. I also presume that Orchil can't be served by DGD and must be served by the websocket-to-tcp tunnel node.js service.
It is likely that eOS doesn't need the full thin-auth, but it is pretty darn close to an MVP of what a chat theatre or a small game needs. Otherwise user admin has to be done in different ways. But don't know.
@noahgibbs What are your thoughts?