Target ID codes keep changing

Hi,

We will investigate to figure out why the Wayk ID has changed (we have had a few reports since Friday). We are sorry about the inconvenience.

Best regards,

Hi,

We did a brainstorming session and came up with a solution to alleviate the problem. We will keep working on reducing the probability of a Wayk ID reset, but it will always remain a possibility. Here is the simplest solution we came up with that we wish to implement quickly:

Each machine has a unique id in the form of a UUID, like this: 385930c7-8960-4906-b63f-f58081ced627. This ID is randomly generated by Wayk Now and persisted in a local file, but we are currently not using it. To solve the problem of a Wayk ID reset, we would expose this unique id in the UI such that it could be copy/pasted in a bookmark entry alongside the short id. Wayk Now would take care of updating an entry corresponding to its unique id with its current short id, such that a bookmark containing the unique id of the target would be able to fetch the new short id if it ever changes.

This would only be the first iteration of the feature, the second iteration would add further improvements to automate the process, such as automatically updating bookmark entries with the unique id using only the short id, etc. For usability, the short id is much easier to communicate, so we would try to find ways to fetch the unique id automatically from the short id to avoid having to manually copy/paste the unique id (much longer). The advantage is that with the unique id, we would always be able to find the target id, even if it has changed.

Let me know if this solution sounds reasonable to you,

Best regards,

Hello


The 3.1 release of Wayk Now is available now, and includes some new functionality to mitigate this issue.


As Marc-André wrote above, we are working hard to ensure that Wayk IDs remain static, but, however small the probability of an ID getting reset, it will remain a possibility.


In the new release, you can create a bookmark for a remote machine using a new field - "Target Unique ID". You can get the unique ID for another machine by running the Wayk Now client and choosing "About Wayk Now" from the Help menu (on Windows and Linux; on macOS, this is under the "Wayk Now" menu). The machine's unique ID is a regular UUID and can be copied to your clipboard.


This unique ID, while less convenient than the regular "short" Wayk ID, will be used by the bookmark to fetch the short ID of the remote machine at connection time - so even if does change, you will still be able to connect.


As Marc also wrote above, this is the first iteration of this feature and we recognize there are usability and ergonomic improvements to be made. However we wanted to get this into users' hands as quickly as possible. As such, we welcome any questions or feedback you might have on this.


Thanks and best regards,