That and the packet leeching, you know, the problem with a constant stream
of con/discon packets being pointed at a connected 1.0 and it sends back
random packets. And of course an expanded aux-id array and recognition of
"recovered" chat spew, i.e. recovered aux packets are checked against the
aux-id array as well instead of just passing strait thru to the chat
window. Note I didn't make the recovered chat spew WP specific, tho I've
yet to see it from non-WP clients, but I have seen it from 2.1.1 2.1.2 and
3.1.* versions which leads me to believe this may be a historic problem
along the lines of the recovery bug. With the recovery bug fixed in the
Cornell client and by ERef's the spew bug is now showing up.
>
>Oh..and feel free to visit my reflector any time. :)
>
You were just *waiting* for Martyne to show up on the list for that one,
weren't you. :)