>>16513801

I have verified the Board Owner of /project comms/ deleted the B post about 14 hours ago.

I am in Southern California and do not have access to SSH into the machines to do anything any deeper than that.

I can tell you that this past week, I fixed the TOR posting issues, which may have affected the trip codes.

I will give a complete report by Tuesday, if not Monday.

In either case, it would not have affected Q’s trip code which is wholly whitelisted.

The probability of a faked post is improbable.

I would show you the log, but the BO of projectdcomms has the log set to private. I don’t do that for other people. I won’t do it for this BO either.

from BO on Q posting

>>16510717

ty baker.

Am usually on duty much of every day, today IRL intervened. Have been preoccupied with other matters much of the day.

First, very glad to see Q on the board.

Second, TOR posting was enabled a few days ago for purposes of testing, anons who check the practice thread can check that out. There have been glitches, which is why it was not announced. TOR was turned off by previous BO, have been exploring turning it back on if glitches could be worked out. Useful during some kinds of attacks.

Third, to my knowledge, no one but Q has access to Q's tripcode. Will consider Q posts made under that trip as from Q unless there is a clear and definitive reason to believe otherwise.

>>16511125

Suggest BV confer with 8kun admin rather than speculate about the reason for tripcode changes involving archiving. Can verify that no tripcode setting was changed on the board level.