I would wait for actual use-cases to come up to bother
with this,
though. We should just make sure that nothing in the basic framework
really strictly assumes a male/female/unknown trichotomy.
What are the cascading implications of user
gender on localization
(adjective agreement in Romance languages, verb agreement in Semitic
languages) and what technical requirements would be imposed?
You'd likely need to write messages like "Automatically block the last
IP address used by this user, and any subsequent IPs {{#gender:$1|he
tries|she tries|they try}} to edit from", where $1 is the *username*
I think you're assuming on the syntax the male/female/unknown trichotomy
you wanted to avoid.
IMHO it should be: "block any subsequent IPs {{#gender:$1|male=he
tries|female=she tries|default=they try}} to edit from"
Now, the order isn't hardcoding the Zulitutsi gender.