Mikołaj Hołysz on Nostr: nprofile1q…targs I haven't thought of this before, but this will cause so much IT ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqzdp33shl69xr0uq3x8n5gsjykq9upycwh6nqm02c3f6x0frrn0dqftargs (nprofile…args) I haven't thought of this before, but this will cause so much IT chaos.
Many people in the US have non-US-issued documents that have a gender on them, and the US government needs to have accurate knowledge of what those documents say (regardless of whether it considers what they say to accurately reflect reality).
Meanwhile, those same people may also have US-issued documents, and those documents will also have a "gender-looking thing" on them. The US government also needs accurate knowledge of what those documents say.
For some people, the value on the US-issued documents will no longer be allowed to match the value on the non-US-issued documents, therefore the question of "but should I expect 'male' or 'female' when this person shows us their ID" will no longer be answerable by a single database field.
Private organizations will also be affected by this, as many will need to separate "gender, as in what the person is expected to have when showing us ID" versus "what this person actually wants to get addressed by."
European organizations already have this problem (this is compounded here by the lack of a 'title' concept and European burreaucracies that makes gender changes extremely difficult for many).
Many people in the US have non-US-issued documents that have a gender on them, and the US government needs to have accurate knowledge of what those documents say (regardless of whether it considers what they say to accurately reflect reality).
Meanwhile, those same people may also have US-issued documents, and those documents will also have a "gender-looking thing" on them. The US government also needs accurate knowledge of what those documents say.
For some people, the value on the US-issued documents will no longer be allowed to match the value on the non-US-issued documents, therefore the question of "but should I expect 'male' or 'female' when this person shows us their ID" will no longer be answerable by a single database field.
Private organizations will also be affected by this, as many will need to separate "gender, as in what the person is expected to have when showing us ID" versus "what this person actually wants to get addressed by."
European organizations already have this problem (this is compounded here by the lack of a 'title' concept and European burreaucracies that makes gender changes extremely difficult for many).