>>31
>You can't "whitelist" a trip so that it doesn't change when the SALT rotates. Which is why CMZ
Can't is a pretty big word when talking about computer code. While what you say IS true that given a generic piece of code that uses a function utilizing a salt, that you cannot cause "magically" different handling of similar inputs, UNLESS, you're written specific code that handles certain SPECIFIC inputs in a different manner.
For example, if the Q group had access to a specific fixed IP address, that would be ONE way used to "whitelist" that tripcode. Another would be a specially whitelisted passphrase that would be parsed through different code and not using the salt. Given a long enough passphrase, (with sufficient keyspace) a very secure tripcode can be made that DOES NOT require a salt for cryptographic security.

TLDR; there are ways of allowing a SPECIFIC tripcode to bypass the salt function, if one has SPECIFICALLY coded for such.
>t.former director of Systems Administration for a game developer many here would recognize.