Socket recv erroneous behavior #15
Description
Although the main issue with #10 has been addressed by some socket changes, the behavior of the recv function is not correct as it pertains to how it should function.
Old data is oddly spilling back into the buffer even though it is nulled prior to the recv call, some research indicates that this is the behavior or the PEEK_MSG flag on sockets that is enabled by default and requires some further adjustments to change.
As this has no adverse effects on the bot that I have seen for now, I am simply marking this as a bug and leaving it in the to-do list for the time being.