WolverinDEV

I'm not sure, actually not really thought about it. I think it will be more work then it would be usefull.

Hey, i already gave you my option about that idea. But for all others I'll write it down too: I really like the idea, but its not so easy to...

> TeaSpeak sends the notifypermissionlist before the initserver, which caused the weird error message. Yes that's right, but except here it does not causes any issues at all ;) >...

@Flakebi As addition would you mind to implement the parsing of the "root" key attribute in `initivexpand2` command? This would allow to join TeaSpeak ignoring of the config settings. (The...

If you need any assistance, feel free to join my TS ;) Yes the `root` approach is an interesting one. BTW does your library support the "old" handshake? Since that's...

> No, I threw that out a few weeks ago Uff that's quite bad especially since the new handshake isn't enabled by default since its "experimental_31"

#179 seems pretty interesting but I'm not having the time to join the conversation. But after #173 I wanted to focus on performance (I'm into bug hunting) and encryption. I'll...

@sourcefrog any thoughts on this one? Turned out logging got into a more complex thing to do.

Ahh yeah all right. I got some spare time yesterday so I thought I would give it a shot. After some fiddling I came up with the concept of extracting...

> This would be easier to review as a few PRs, but I understand how you might need to write the whole thing first to understand the code or what...