Log in

No account? Create an account
No Opt In, No Ads
Fueling the resistance
Recent code changes require gender for sign up and profile edits, has only male/female options 
14th-Dec-2009 11:33 pm - Recent code changes require gender for sign up and profile edits, has only male/female options
Skittish Eclipse
So, as noted by [personal profile] synecdochic in this post, upcoming posts in changelog (http://community.livejournal.com/changelog/7932846.html and http://community.livejournal.com/changelog/7937189.html) suggests that the way LiveJournal treats gender information is changing:

* During the sign up process, gender will be on the first page, and required.
* The only options are male and female.
* You will no longer be able to save edits your profile without specifying a gender if you have not set it.

Unfortunately, not everyone fits into a gender binary, and not every one wants to specify their gender to their journaling service.

So, why is this post going into no_lj_ads? Because this decision is nearly certain to have been driven by the need for better ad targeting. (Despite this, paid users must also give their gender. This is an example of how site development done to increase ad revenue can affect paid users, even though they do not see ads.) I don't know how things are for others, but I know that being in a female demographic increases my receiving of ads irrelevant to my interests or downright offputting.

Now, I feel I must note that this change has not come to pass yet. It has opportunity to change or be revised. Other and unspecified could be added, and the information no longer required. However, given the new aggressive interstitial ads, LiveJournal appears to be strongly seeking ways to increase its advertising revenue. Better targeting could help them do that. Given this, it might be possible that they do not change this, although you may not personally see why they would need this information.

If this upcoming development is not changed, and you do not want to give LiveJournal your gender or be forced to choose a gender that does not fit you, you should edit your profile before the next site update to something you are willing to keep for the remainder of your use of the service. I suggest putting your bio into a post and linking to it from the profile, so you can change it without running into the restriction.

ETA: Response suggesting this might not make it live, thankfully:

hi Denise,

thank you for your feedback. This is all very informative, I received many email with this already.
However, the code update that you refer to is not live and did not have any chance to go live. That was a beta release, we always push code to beta to see if everything works correctly. In many cases it does not and we either fix bugs or pull the code from the final release plan.
We were going to add a gender field to the sign up user flow, which is fine, but by mistake it became a mandatory "female/male" field for everyone. This is why this is not going live. And this is what beta releases are for, to see problems and solve them before any user faces a problem.

I would appreciate if you share this information with your friends that are also concerned.

Best regards,
Anjelika Petrochenko
GM, LiveJournal US

However, the code to make the option mandatory on the profile was very much added on purpose (it's hard to write it on accident, so it's not a bug), so if there was a mistake in implemented, it was in miscommunication with programmers (or they'll decide not to do it after all). I'll be happy if it's true and she says this won't be going live--but I'm waiting until the next release at least before I'm entirely comfortable with the notion.

ETA2: We have rollback! And in unrelated news, apparently Nokia is going to be reskinning LiveJournal.
15th-Dec-2009 09:56 am (UTC)
No. Requiring existing users to specify one of two genders was at least as intentional as the new users signing up and part of the second code change. The following code involving the profile edit page (htdocs/manage/profile/index.bml
), setting up error checking and making an error message saying gender must be specified does not happen unintentionally by the programmer (although, like I said, it could happen by miscommunication):

+ # gender
+ unless ($POST{gender} =~ /^F|M$/){
+ push @errors => $ML{'.error.gender.not_specified'};
+ }
15th-Dec-2009 10:09 am (UTC)
Thanks for that. Yes, miscommunication is the most charitable explanation, but I'm sure there would have been plenty of opportunities to fix that before it got as far as public entries on changelog and beta testing.
This page was loaded Dec 11th 2018, 6:22 pm GMT.