Specify id/relay server as part of target id when connecting to another device

[vladimir-angelov-1337]

It would be cool if instead of "123 456 789" I could write "123 456 789@domain.com" when connecting to another device and that would use domain.com as the id/relay server for this specific connection. That way even with self-hosted setups we could connect cross-organization.

[AtanasDDimitrov]

Yes! This would be very useful!

[likedigital-slavik]

That sounds way more efficient and safety. Definitely will use it!

[ivanov-GSGroup]

Yes! This can be useful for us!

[vladimir-angelov-1337]

Come to think of it, would be best if we could somehow use emails instead of numbers. We're willing to help by contributing with an MR but need some help going through the source code.

[IliyanAng]

Up.

This will add great flexibility.

[animus95]

This would be an awesome feature.

[simeonovPavel]

Please implement this it would be great !!!

[PetyaPamukliyska]

It will be super helpful, think about it!

[borislavvelkov]

It will be really cool, yes!

[anojoyman]

This would be good addition. Also to expand on the idea there may be a special group when you use private id/relay server to use this server for that group and public/default for others. Or define id/relay server for each group to use, which I think would be great. This way you can use multiple id/relay servers with ease.

[HFord1234]

Please make it happen, so we can finally ditch anydesk

[marto7777777]

It would be very beneficial!

[Stanwolf157]

Definitely needed as soon as possible!

[rustdesk]

Make sense #2118

[pedjas]

This is necessity. As if you have several clients set to connect to several hosts and they all share the same configuration it becomes quite a mess. You have all remotes listed at the same place regardless they are not of the same server. There is no clue to which server one has to connect to be able to connect specific remote client.

[TorstenVo]

It would be very useful and ideally, the planned address book would be connected to the respective server/domain.
Appreciate your great work.

[rustdesk]

Then how do you specify key?

[pedjas]

Since key is already public (it is written in file name, openly visible, and all clients use the same key) then key also may be provided in target id.

Even better, it would be great that keys are not part of connection parameters. It would be much better if client connects to server, gets key from it and then switch to encrypted connection using provided key. HTTPS works that way.

[d3sync]

Indeed some kind of federation would be awesome for selfhosted relays / id servers