invitations favor sparsely connected mesh

[igel-kun]

hi and thanks for this cool piece of software!

I am trying to set up a mesh between a couple of friends and I hoped that invites may help make this idea more sexy to the less tech-versed among them. However, the way I understood invitations is that the inviting node will always be the single connection point for the invitee (modulo manual tinkering with host-files). This goes totally against the mesh/peer-to-peer idea and, in my case, I cannot guarantee that the inviting node will always be online.
I did play around with the invitation-created script which allows to publish at least the currently known host-configurations (which, by the way, would be useless to the invitee if they themselves were created by the invitation process, because, if I understood correctly, the invitee has no means to communicate their address/port to the inviting node). However, when the mesh grows, older invitees are left with only few connections.

So, I would love to see a functionality allowing the invitee to publish address/port changes at least to the inviter, better yet, allow any node on the mesh to publish an address/port update (of their own host-config) to the mesh, in order to allow establishing connections to them. Or maybe anyone can think of a better way to keep well-informed and updated host-configurations spread in the network in an automated manner?

cheers & thanks

[gsliepen]

Actually, almost everything is in place for this, the only thing remaining is for peers to store address/port combinations they learned while running in the host configuration files, so they can be used when restarting. I will add this soon.

[gsliepen]

Support for updating known peer addresses has been added in 04543a5. This still requires some manual work to enable, it should be made fully automatic.