The only way I can think of is that he tried to sign into your account with a fake password and therefore locking it because of too many incorrect attempts. Having done that he knocked you offline with the s, and you were unable to log back on.
Also this would probably display a different error.
/ 
s, and you were unable to log back on.![[Image: Dr4g0n_.gif]](http://imagegen.last.fm/basicrt10/recenttracks/5/Dr4g0n_.gif)
