LJ screws up again...

[kengr]

This time they are going to force you to choose "male" or "female" in your user info by removing the "unspecified" option.

For more details:

http://rm.livejournal.com/1770434.html

And yes, it's virtually certain they want this to enable advertisers to better target ads.

Comments

[kengr]

If so, it's yet another example of *the* single most widespread database design error. You *always* should have an "other" option for a "radio button" type field. No exception.

Because the world will always come up with something you didn't think of.

Yep. you "get it" and elljay hopefully will too.

[capybyra.livejournal.com]

DO please post your above comments VERBATIM into their support etc thread! And, I have a stupid sounding "UI intersects DB communication" thought.

Can unpressed radio button fields be coded to somehow "go away" and stay gone- in response to a pre-entered button near a form's first button? Example:

Profile: choices= personal data shown button is pressed to indicate NONE. Then the "Save form" causes the impertinent buttons to be gone.

"Asking invasive questions is impertinent"