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

[netdancer.livejournal.com]

Fuckers.

Male, then, and they can suck my...

Not that I've ever looked at any ads here. :>

I'm giving a condtional "time to get a clue" wait period. to them,

[capybyra.livejournal.com]

From my readings, the "plausible deniability" centers on the code push process and an "alleged" block of code never intended to be released. IIRC that's what we made "Lorem Ipsit.." pages for. So my Tar&Feathers are to hand if needed, but I won't waste propane firing up the tar kettle til it's proved as claimed.

If it is as claimed, though? We may consider buying into Dreamwidth:)

Re: I'm giving a condtional "time to get a clue" wait period. to them,

[kengr]

Oh, like incompetence is better than malice?

And I can't afford to buy into anything, alas. I got a permanent account here back when I still had lots of money.

Oh, like incompetence is better than malice?

[capybyra.livejournal.com]

Good point:) My point's a tiny long- forgive that- but it may help.

NO ONE has need-to know of anything related to Gender and us. Oh, we can decide that a friend,lover medical caregiver etc has that need. But even then -it's by OUR CHOICE. Anyone presuming to say otherwise is risking a rain of Truly Bad Karma coupled with a flood of EARNED hate. I just want to be sure if it's malice, greed, innocent code glitch- or something worse than all of the three combined.

If it's malice or related?- Not even a #deity has much chance of saving the perp from all our revenges:>

Re: I'm giving a condtional "time to get a clue" wait period. to them,

[acelightning.livejournal.com]

[acelightning.livejournal.com]

[xander-opal.livejournal.com]

Ugh. Hate being forced to choose; none o' their business.


If you choose not to decide, you still have made a choice...

[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"