The mysteriously matching filename hash is 256 bits long. If that is SHA256 it might be broken by Q/others but not publicly. Also I thought I read that was the hash used in Q's new/latest tripcode. If so might be wise to augment the tripcode with a digital signature in the text as an additional layer. Would burden anons a bit to verify it but Q doesn't post very often and it would just take a minute after setup. If the hash is broken it seems to mean they don't need anyone's password to spoof their tripcode, they can produce a different password/input that makes the same tripcode. It may be easier to match two less constrained strings like with pic name/hash than to find an input that matches a fixed tripcode. But it's unexpected enough to worry about. Can anyone look up in the code what the hash functions are for pic names and for tripcodes on this board/Q's board?
Nice numbers on these - confirms important so correct if I am wrong!