As I mentioned on >>>/sudo/66101, I updated the code for super secure tripcodes because someone found it was excluding capital letters, thus making them less secure. I immediately changed the code on January 5, 2018. Because it wasn't really announced except on /sudo/, this might have caused some confusion. Sorry about that.

Regarding any Q posts that happened then, I can't verify anything because it seems the posts have been deleted. However, let's assume Q's post history wasn't the same. That does not necessarily mean his tripcode has been cracked. Q might have changed IPs, reset his connection, used cellular data, used a different VPN provider or even a different IP location from the same VPN provider - there are a number of reasons why a post history might start from scratch. Again, I cannot verify his posts because, well, they don't exist anymore.

Based on the access logs, which I had to carefully go through just for this - and this alone, I can confirm this is Q (>>>/thestorm/4706), using his verified tripcode.

>>6139

>(>>>/thestorm/4706)

Not sure why this didn't expand into a link, but it should be >>>/thestorm/4706

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/.

About creating a global board just for Calm Before the Storm-related happenings, I must decline the request. But why?

8chan tries to give anons all the tools they need to post as freely as they can provided this happens within the boundaries of the law. I created the tripcode whitelist and super secure tripcodes because I saw there was a need for it. As admin, I have other tasks, like understanding the code I inherited and implementing additional features our users want without breaking the website.

Creating and managing yet another global board would reduce the time I have to update and maintain the 8chan codebase and this wouldn't be fair to the 16,500+ boards 8chan currently has.

All of this reminds me a lot of the early GamerGate boards (not the later split). Try not to fall prey to board brands. The board name doesn't matter because you are mission-oriented, first and foremost. If board x falls, move to board y; if board y becomes compromised, move to board z and so on and so forth. This is the 8chan system.

Finally, I probably wouldn't be a good BO. I'm forgetful and quite busy. What if you need immediate action and I'm traveling or shoveling snow or walking the dog? You would do better with a mission-specific BO that is knowledgeable about these happenings.