Sounds interesting. What's your precise expectation of the server behavior in this case? Does the local instance have exactly one (or at most one) open session, so when you enter the IP address of that instance you automatically enter that singleton session?

Other idea: combine both the server address and the invitation code in one URI, e.g. as a hash or query parameter.

I think it would be nice if the host person could choose whether to share over the Internet or run a server.

Considering the case of sharing with both near and far people at the same time

• Share over the Internet
• Run a server
• Both
  I guess there are three choices.
  But then, when collaborating with an offline computer, you can't use an online account, so the question would be what to do about that.

I suddenly found another idea and will share it with you.

I am in Japan and often host on a local computer because it is slow from Japan to the shared server., but I am finding it difficult to have the other party rewrite the “oct.serverUrl” each time.

So, if it temporarily ignore “oct.serverUrl” when we enter the format “invitation code@domain” in the invitation code input field, it would be a generic solusion to changing servers.

For example, if we enter ooolahCeK3w@http://192.168.1.5/, it will be connected with the invitation code ooolahCeK3w while temporarily overwriting oct.serverUrl with http://192.168.1.5/

If it make https:// optional and http:// @ twice
ooolahCeK3w@@192.168.1.5/

That sounds good!

I can't say when our current team will have time for it, but contributions are welcome! 🙂