I have seen some demos online such as WebVM [1] that use ephemeral devices to enable networking within the browser. It sounds like there is now a limit on the total length of ephemeral sessions on an account that last less than 240 minutes. While I'm not currently affected by this limit, it does seem rather arbitrary.
Hi, lead dev of WebVM here. Can you link to the specific change that affects ephemeral devices? I cannot find this reference in the article.
Keep in mind that we also plan to offer builtin networking in the near future, we are developing the infrastructure to do so as part of our newest product (In-browser sandboxes): https://browserpod.io
Thanks for sharing. I see how this could impact heavy user, but there is always the option of authenticating via a non-ephemeral auth key as a potential workaround. It's not integrated in the public WebVM UI, but it is supported by the underlying engine (CheerpX).
Comments
I have seen some demos online such as WebVM [1] that use ephemeral devices to enable networking within the browser. It sounds like there is now a limit on the total length of ephemeral sessions on an account that last less than 240 minutes. While I'm not currently affected by this limit, it does seem rather arbitrary.
[1]: https://labs.leaningtech.com/blog/webvm-virtual-machine-with...
Hi, lead dev of WebVM here. Can you link to the specific change that affects ephemeral devices? I cannot find this reference in the article.
Keep in mind that we also plan to offer builtin networking in the near future, we are developing the infrastructure to do so as part of our newest product (In-browser sandboxes): https://browserpod.io
https://tailscale.com/pricing says "1,000 mins per month for ephemeral resources"
Thanks for sharing. I see how this could impact heavy user, but there is always the option of authenticating via a non-ephemeral auth key as a potential workaround. It's not integrated in the public WebVM UI, but it is supported by the underlying engine (CheerpX).