Tag Archives: livejournal

During the December/January slowdown, Geek Feminism is re-publishing some of our highlights from last year. This post originally appeared on July 8, 2011.

I knew that someone posted on this blog discussing what requirements a feminist-informed social network would have. Turns out it was me. A year on, and due to discussions around Google+, I think I have some positive requirements. (I recommend reading the old comments thread too.)

Control over identifying information. Name, gender, age, who you are friends with, what you talk about, what events you are in, and what you look like: this is all varyingly sensitive information and should be able to be hidden.

As few restrictions as possible on identity. Allowing use of pseudonyms, not assuming that everyone has two, or two ‘important’, names, free specification of gender if specified at all. As little structured compulsory information as possible. Unstructured, free-form, and non-compulsory are key things here.

Accessibility. State of the art accessibility design including testing with screen readers, colour palettes suited to as many variants of vision as possible, collaborative transcripting and captioning of images, no flashing ads or autoplaying video.

You own your space and control entry. This means you should be able to moderate things. Being able to ignore people is good but is not enough: you likely don’t want to subject your friends to the conversation of a person who you dislike enough to ignore.

Rigorous site-level attention to spam and harassment. No one (much) wants spam, enough said. But harassment—continued interactions or attempts to interact after being told to stop, including ban evasion—should be a terms of service level violation, as should any threats (whether or not the person has been told to stop). Use of threats or hate speech in user names and default icons or other things that appear in directory listings or search results may also need to be considered. This all requires staffing and a complaints system.

Consistent access control. If you set something private, or it was private by default at the time, it should stay that way, probably to the extent where if it can’t remain private for technical reasons, it should be deleted/hidden by the site rather than made public.

Access to your work and ability to export it. The correct thing to do here is a little tricky (are other people’s comments in your space yours to export and republish, or not? what about co-owned spaces?) The autonomo.us community has had some inconclusive discussions.

Fine-grained access control. I don’t think something along the lines of that which Livejournal and its forks have had for years and which Facebook and Google+ have implemented to varying degrees, is required (public blogs have a strong presence in activist discussions) but it’s useful for more universal participation. Some people need it.

Clear limits on sharing. This is something that Google+ early testers are coming up against again and again: ‘Limited’ posts are or were shareable, a commenter using someone’s name with the + sign (eg ‘+Mary’) does or did actually invite them into private comment threads without the original poster’s input. If you offer access control, the software must make it clear what controls apply to any space, and if you have influence over that or not, so that you can control your own revelations in that space. Substantial user testing to make sure that people understand what your interface is trying to say is required.

No advertising. I guess it might be possible to show people ads in a way that has neither the problem of offensive or upsetting ads (“lose weight for your wedding today!”) nor the problem of the advertisers doing dodgy malware ads to harvest your info or worse. Maybe.

I knew that someone posted on this blog discussing what requirements a feminist-informed social network would have. Turns out it was me. A year on, and due to discussions around Google+, I think I have some positive requirements. (I recommend reading the old comments thread too.)

Control over identifying information. Name, gender, age, who you are friends with, what you talk about, what events you are in, and what you look like: this is all varyingly sensitive information and should be able to be hidden.

As few restrictions as possible on identity. Allowing use of pseudonyms, not assuming that everyone has two, or two ‘important’, names, free specification of gender if specified at all. As little structured compulsory information as possible. Unstructured, free-form, and non-compulsory are key things here.

Accessibility. State of the art accessibility design including testing with screen readers, colour palettes suited to as many variants of vision as possible, collaborative transcripting and captioning of images, no flashing ads or autoplaying video.

You own your space and control entry. This means you should be able to moderate things. Being able to ignore people is good but is not enough: you likely don’t want to subject your friends to the conversation of a person who you dislike enough to ignore.

Rigorous site-level attention to spam and harassment. No one (much) wants spam, enough said. But harassment—continued interactions or attempts to interact after being told to stop, including ban evasion—should be a terms of service level violation, as should any threats (whether or not the person has been told to stop). Use of threats or hate speech in user names and default icons or other things that appear in directory listings or search results may also need to be considered. This all requires staffing and a complaints system.

Consistent access control. If you set something private, or it was private by default at the time, it should stay that way, probably to the extent where if it can’t remain private for technical reasons, it should be deleted/hidden by the site rather than made public.

Access to your work and ability to export it. The correct thing to do here is a little tricky (are other people’s comments in your space yours to export and republish, or not? what about co-owned spaces?) The autonomo.us community has had some inconclusive discussions.

Fine-grained access control. I don’t think something along the lines of that which Livejournal and its forks have had for years and which Facebook and Google+ have implemented to varying degrees, is required (public blogs have a strong presence in activist discussions) but it’s useful for more universal participation. Some people need it.

Clear limits on sharing. This is something that Google+ early testers are coming up against again and again: ‘Limited’ posts are or were shareable, a commenter using someone’s name with the + sign (eg ‘+Mary’) does or did actually invite them into private comment threads without the original poster’s input. If you offer access control, the software must make it clear what controls apply to any space, and if you have influence over that or not, so that you can control your own revelations in that space. Substantial user testing to make sure that people understand what your interface is trying to say is required.

No advertising. I guess it might be possible to show people ads in a way that has neither the problem of offensive or upsetting ads (“lose weight for your wedding today!”) nor the problem of the advertisers doing dodgy malware ads to harvest your info or worse. Maybe.

My intent in this project was to examine the labeling of female-oriented geek spaces on the internet. What I found was that self-labeling of geek women often defeats the potentially subversive act of creating a female-oriented geek community.

I would argue that the mere creation or and participation in geek communities labeled “for women” are aggressive acts towards male-dominated geek culture. One of the reasons we can see these communities as a challenge to mainstream geek culture is the still-prevailing myth of internet neutrality.

This myth argues that since we are “disembodied” on the internet, everyone begins on equal ground.

Bodies don’t matter in cyberspace. This is not how it works in real life, however, particularly in geek spaces. It is true that until you mark yourself as Other than the privileged class—male, heterosexual, cisgendered, abled, middle-class, and white—you will be assumed to be those things. However, this will not protect you from hate speech or sexist, racist, and homophobic “jokes,” since geek communities often engage in these forms of discourse. Even objecting to these discursive acts, without revealing the state of one’s own body, will immediately mark you as Other, and leave you vulnerable to harassment and denigration. By labeling their spaces as for women, female geeks challenge the neutrality myth, by making their female bodies conspicuous and by demonstrating a need for safe cyberspaces for women.

In a study of the language of male gamers playing within a Quake server, Natasha Christensen claims that

Even though the world of cyberspace allows for the possibility that gender can be transformed, men in Jeff’s Quake Server continue to relate to each other in ways which support male dominance and heterosexual male superiority. […] In the bodiless realm of cyberspace, it is fascinating to note that men who are able to create an alternate world where masculinity is defined differently do not take this opportunity. Instead, real life is mimicked not only by taking on the physical attributes of strength, but also by using ways of talk that emphasize aggression and sexual dominance.

[…]

Therefore, in the same way that sports and war help to perpetuate the concept of male dominance through physical strength, the Quake server also promotes the idea of success through aggression and violence. […] Sports and war games became a way for white middle class men to fight their fears of social feminization. At the turn of this century, online computer games are being used in the same manner. Computer geeks who are especially vulnerable to the accusations of being less than manly are able both through the actions and discourse on Quake to demonstrate the qualities required of hegemonic masculinity. Emphasis is placed on the strength of the masculine body while discourse sets the players apart from anything that is feminine.

The same patriarchal standards that put women at a disadvantage also disadvantage computer and other geeks. Often, geeks cite an experience of growing up with bullying and teasing, precisely because they do not live up to hegemonic masculinity. Instead of using cyberspace to fight against hegemonic masculinity, however, geek men often use it to buttress those standards and fulfill them discursively instead of physically. This is precisely why geek women find online geek spaces—necessarily discursive spaces—to be so unwelcoming and hostile. And it is through alternative discourse, whether blogging or forum writing or fanfiction, that women challenge this culture of hypermasculinity.

First up, the return of fannish scammer formerly known as Victoria Bitter, most recently appearing on LiveJournal as thanfiction. If you’re familiar with the back-story, you’ll know that the person in question has been identifying as male for some years now. Despite this, various people in the fandom_wank thread have been referring to him as “she” or “s/he” or the like. The fandom_wank post now comes with a “No more transfail!” warning.

It is never okay to disregard a transperson’s preferred gender identity. Not if he’s a compulsive liar, not if he’s a demonstrated con-artist, not if he’s dragging down the name of fandom, not if he’s the worst person on the internet.

Let me recontextualize, with a hypothetical: “It is never okay to slut-shame. Not if she’s a compulsive liar, a demonstrated con-artist, dragging down the good name of fandom…”

Clearer now?

Meanwhile, Livejournal has recently added code which will require (binary) gender disclosure, presumably to better target its advertising. Unlike, say, Facebook, LJ has never nagged you to disclose your gender or fit into the boxes marked “Male” or “Female”. This made it more trans-friendly than many social networking sites.

Denise’s letter to the LJ feedback folks reads, in part:

Transgender and genderqueer individuals experience discrimination every day when they are forced to identify themselves with the gender binary when it doesn’t apply to them. Please do not contribute to this oppression.

Please keep the “Unspecified” option for gender, and add an “Other” option, if you are making the gender field mandatory. Please do not contribute to the oppression of others. While I recognize that having a user’s gender makes advertisers happier, collecting revenue at the expense of human suffering is not the action of a company I want to do business with.

She suggests that LJ users go set their gender to “Unspecified” in protest, before the probable code-push on Thursday, and send a letter to LJ registering your disapproval.