Hot take, #P2P protocols shouldn't use MDNS for peer discovery if they don't plan to use the OS provided APIs for it. Only one process can reliably bind the UDP port necessary for it and it quickly leads to conflicts. At the very least you should use a custom port to avoid conflicting with the OS.
@jgkawell I've been leaning to just doing bespoke multicast UDP stuff personally :o
@smallcircles @mauve @jgkawell Yes, well we do have some thoughts about multicast @librecast ☺️
@onepict @smallcircles @mauve @librecast librecast looks cool! Looking at the README and it says soon there will be tunneling added to the library so it can function as an overlay network. Is there more information on that effort? I'm working on a Wireguard based overlay network to enable remote peering between home LANs so I'm curious how librecast is solving that.
@jgkawell @onepict @smallcircles @mauve Multicast overlay tunneling using WebRTC will be in the next major release.
It didn't quite make it into 0.9 but will make it into 0.10.
Other tunnel types such as wireguard may be added later.
We're on IRC, plus we also have a mailing list you can join where we tend to post announcements.
@jgkawell Is your code published somewhere I may read BTW?
@mauve Yes it is! Here's the relevant code but feel free to look around at the whole repo for context: https://github.com/home-cloud-io/core/blob/main/services/platform/daemon/host/mdns.go
@mauve I tend to agree. I'm working on a project that uses mDNS and after ending up with issues with certain OS's failing to work with my Go module implementation I shifted to just doing it through Avahi on the host. It's been rock solid since.