#dat

RangerMauve: anything you need re: multicast stuff?

(RangerMauve) konobi_: I haven't had a chance to really get into it yet. Sadly my day job and my partner have been taking most of my time this week. 😅

RangerMauve: ah... no worries. was just wondering because it's fresh in mind and multicast info always seems to have an odd half-life in terms of recall ^_^

(RangerMauve) I might have some time this Sunday evening (est) to read over what y'all were talking about in more detail, then I'll try to see how it relates to the code before I start bugging people about it. :P

(RangerMauve) Thank you for the help BTW! MDNS is pretty new to me so I'm not super familiar with the details 😅

yeah... multicast was slapped onto the socket api after the fact (at the spec level) and it doesn't quite fit the original model, so it's overly complex and confusing (and why each OS and OS version has varying quirks and alternate interfaces that all _sorta_ work... *le sigh*)

I was wondering of there were c, or c++, C#, or even python bindings for dat as a p2p networked application.

boogle: there's a rust effort in progress

to bind to other native platforms

noffle: hi

noffle: the put api is public yea. i should document it. used if you impl your own non stream based repl scheme

mafintosh: do you know of any examples of repls that use the hypercore stream directly?

Thanks, nofffle.