Status report and new roadmap for the ICE adapter

Sheikah

@lord_asmodeus
The UI does not expose any ips or even any information not already available if you were to join the lobby of the game or open the client. It simply shows the connection status between players.

Brutus5000

There are 2 independent layers:

What the telemetry server collects
What the debug UI actually shows

The UI does not and probably will not show any ip addresses, even though as a participant of the game you are connected to all the players so you see their ip anyway
Even the telemetry server does not collect anything sensitive apart from user ids and user names so far, as it is a drop-in replacement for the current ICE adapter debug window.

NOC-

Yeah, although you can find the IP's already if you look in the correct places, putting it all in one place would make things easier for someone to find if they wanted to.
As Sheikah said only show the status of the connection.

So my personal recommendation would be to keep the IP's not displayed.

The telemetry server I like the idea of as well.

My Kotlin skills are a little rusty but if I get free time from work I will check the GitHub and see what's going on.
As far the ICE adapter coding wise my Java is not terrible but I will leave that alone for now rather than interfere.

Brutus5000

Progress Report

Release the Java17 ICE adapter to the world.

The Java 17 transition is done and already shipped with client pre-releases. So far we heard no complains, so it will come with the client update at the end of the month.

Finish the basic telemetry server and ice adapter logic and ship it for testing (keep the old debug ui for comparison)

The ICE telemetry server is actually running on production right now in a very basic version. It keeps no state and cleans up games after the last player left. So for now it only replaces the functionality of the debug UI window.

So here is how to trigger it (once released): Click on the tray icon and open the web ui.

And then you end up on the current ui:

Unfortunately not all features are supported yet (such as Coturn region or rtt), but some of these require more complex changes in combination with the clients.

We will release the first version with the client pre-release starting in November.

relentless

Awesome work on this Brutus! Takes a brave man to dive into legacy code.

Eternal-

Works like a charm

PaulWay

Is this available?

Brutus5000

speed2

Again?

Brutus5000

The previous non-java (I think c++ and nodejs) version were never fully working, so I wouldn't say that counts as a rewrite.