We are leaking challenge page status in the URL

[markwhiting]

Challenge survey URLs at least sometimes show that they are challenges, which is not great, because workers may attend to them more if they think we are trying to trick them or check if they are paying attention.

Here's an example:

The main option would be to obfuscate this information in the URL, which could happen either by doing challenges as a state change with no URL change, or by using something like our encrypted URL scheme, or by just using abbreviations, e.g., URL/c.

This is not urgent but something to think about at some point if we are worried about the quality of our challenge signals.

This issue should be closed when...

• A plan of action has been made to deal with (or ignore) this problem
• That plan has been vetted, executed, and tested