>>4672

>did something that made his super secure trip change, it may have also changed everybody's IP hash

Doubtful. IP bans are stored as bcrypt hashes.

The new super secure trips are/were based on SHA256 (now base64 encoded? [this being the likely change, along with new salt])

>>4696

I've looked at the sources. I can't find the changes from super secure trips (not committed to github yet?). Either way, it's extremely unlikely one would affect the other.

>>4706

"Insecure" trips only allow a maximum length of 8 characters, regardless of input length. Additional input is ignored.