Unfortunately a core technology we use for immediate feedback on <script> changes without sending user input to our servers was getting caught in the mess.
We have made significant frontend changes to ensure our output frame will continue to work, while still delivering
true infinite loop protection
true privacy, without servers
βΉοΈ
We are also working on proposals to improve the relevant web standards by creating ways to clearly signal and opt out of the persistent storage capabilities of the affected APIs.
Sign in with Google
We use <pwa-auth> by Microsoft for federated user logins.
Establishing connections could take up to 40 seconds with Chrome and Edge.
We have addressed the underlying issue and these browsers now establish remote output connections blazingly fast!
Multi-region signaling
While the vast majority of our users eventually get to enjoy a direct, peer-to-peer connection, all sessions initially go through a signaling system which facilitates route discovery between remote browsers.
We have invested heavily in our signaling infrastructure and now run in multiple regions/clouds with IPv6 support:
us.rt.htaws π
kr.rt.htoci π
eu.rt.htscaleway
βΉοΈ
All of our HTTPS services supported both IPv4 and IPv6 from day one.
UI improvements
Remote output β¦
now uses random short links which also support early cancellation.
Random links with Cancel option.
Active remote connections are now displayed with more detail.
New active remote connection elementsOld active remote connection element
Community Work
Shoelace (web components)
Upgraded to 2.0.0-beta.82, contributed to the following fixes:
shoelace-style
