Currently, AF uses 3 external vars that are supposed to be booleans but are actually integers (0 and 1), and their documentation (copied & pasted below) is pretty cryptic:
|user_blocked||1 for blocked registered users; null for unregistered users.||should be true if the user is blocked, false otherwise, without registered/anonymous distinction. If this isn't possible, then true-false-null|
|user_mobile||1 for mobile users.||True for mobile users, false otherwise|
|tor_exit_node||0, 1 (only available if TorBlock is installed)||True for mobile users, false otherwise|
This shouldn't be too hard to do, however I'm leaving it here for two reasons: first, there are several variable-related patches around and I don't want too many of them. Second, as usual, this would require a query to ensure that we won't break any use case. The only breakable ones that I see are:
- Triple-comparing the variable.
- Almost any use of user_blocked due to the value change.
Since I don't think these variables are widely used, a query for user_blocked|user_mobile|tor_exit_node should provide a relatively tiny amount of data to analyse.