Sean DuBois

Fantastic, that is really exciting! Those wireframes look great. thanks for the inside scoop @dmitshur that information is super helpful for everyone here :)

Just a design mistake! I am up for fixing this in the next major release. Maybe we could provide a nice helper to make `net.Conn` users migration easy. This also...

@ernado I think you can just resolve this one! but feel free to throw any info you want in here :)

Hey @MaxBosse I think it makes sense to add support for it! Would you be interested in contributing this? I would be happy to help. In the short/medium time I...

Great fix @mschexnaydre Do you think it would be possible to write a test that validates that this is respected? A test that would break (but now works) with this...

This is really exciting! Some random thoughts I had. ### We should join the IETF list and see if we can help. Would be so exciting if Pion DTLS could...

Hey @PieerePi, so excited to get you involved. Not a lot of devs get this deep :) I see what you are talking about. So the issue is CipherSuite priority/who...

Oh that is perfect, thanks for calling that out @daenney `crypto/tls` has [PreferServerCipherSuites](https://github.com/golang/go/blob/520f3b72db7befab2028d9a47376267cf2d274a9/src/crypto/tls/common.go#L633) we just need to add that to pion/dtls @PieerePi Are you interested in taking this on? I...

The issue is [here](https://github.com/pion/dtls/blob/master/listener.go#L65). Every time we get a new inbound stream we block until the handshake is complete. This behavior also isn't a regression f7a68a36523bf733b1c4139f88e109b4b31e02f8 We should look at...

https://gist.github.com/Sean-Der/a3a6abbe9b78ced613590312a18dc8a4 @jkralik @boaks @jdbruijn this worked^ If one Server process hangs the other 4 work just fine. If I remove the change in the example one client hanging hurts everything....