>>121
Is it really, though?
Look, there are 64
8 candidates for tripcode's fixed points (
[a-zA-Z0-9./]{8}). Each of those can produce 64
9 ✕ 16 possible outputs, 64 ✕ 16 of which can be used to construct a fixed point input. That means that the chance of at least one fixed point existing is 63.21%.
Those odds are good enough that you should be looking for plain fixed points instead of cycles
first, and it's been pointed out that you can do an exhaustive search in under a day.
Exploring for the sake of exploring is one thing, but don't outright waste your time.