05:07 <spacekookie> Thanks!

05:08 <spacekookie> So regarding a tcp/ethernet netmod, realistically there's two things to do but they don't have to hap'en at the same time

05:08 <spacekookie> One is just keeping a routing table of local IPs (in whatever range and interface the netmod operates on) and map'ing those to ratman IDs

05:09 <spacekookie> The other is then actually a service that exposes this information via new routing IDs so that it would be possible to tunnel arbitrary protocols through qaul

05:10 <spacekookie> This requires IPs to be advertised somehow

05:10 <spacekookie> But also, it's much later down the road and okay if our beta doesn't do that

10:44 <lejonet> Advertising IP shouldn't be all too hard to fix, iirc you already had some type of discovery, just append the current IP to that phase

15:44 <spacekookie> We have a discovery but it's very low level and it doesn't really convey other payloads and propably shouldn't

15:44 <spacekookie> The external IP spce discovery should probably be handled via some service

15:47 <qyliss> Async/await is stable :)

15:47 <spacekookie> On the wire this won't look much different. I guess it just means not every node needs to run an IP space discovery :P

15:47 <spacekookie> Yaaay!