Notice: You have been identified as a bot, so no internal UID will be assigned to you. If you are a real person messing with your useragent, you should change it back to something normal.
Anonymous C joined in and replied with this 14 years ago, 1 minute later, 24 minutes after the original post[^][v]#328,571
+ or - 10%
The technical explanation for this error is that MC server has tried to read (or write) from a TCP socket but that socket has been closed by the client at the other end with no notification given to MC server. Normally, as part of gracefully closing down a TCP connection, both the client and the server exchange TCP packets and agree to close both ends of their pipe. If something unexpected occurs at the remote end, such as the client being reset or the remote application crashing, then any open TCP connections may not be closed down properly.
Anonymous A (OP) replied with this 14 years ago, 1 hour later, 1 hour after the original post[^][v]#328,591
@previous (C)
it only happens with twitter and google+
Anonymous C replied with this 14 years ago, 2 minutes later, 1 hour after the original post[^][v]#328,592