A summary of events.
>January 2
I added super secure tripcodes. /cbts/ BO secures one.
>January 5 (Japan time)
Someone on /sudo/ pointed out that super secure tripcodes excluded capital letters, a big oversight which I fixed. I changed the code and announced it just on /sudo/. /cbts/ BO doesn't know about it and continues using the tripcode he secured, but because the code changed, his tripcode also changed - this led to confusion.
Q comes back and posts on /cbts/ normally. Post history is not the same, IP hash is not the same. /cbts/ BO assumes, incorrectly, that this is not Q, even though there are a number of reasons why a post history may start from zero, including changing VPN providers, changing VPN IP locations, using cellular data, resetting your modem, posting from a different location, using a different IP (hotel, restaurant etc.).
/cbts/ BO deletes those posts.
Then, Q goes to /pol/, where he is banned, and then /thestorm/, where he asks for verification.
Around 12 hours later, I confirm it is actually Q using his verified tripcode (still uncracked) on /thestorm/.