The status of pseudonymity and privacy on Google+

This article originally appeared on Geek Feminism.

Here’s a separate thread for people most interested in keeping track of official, semi- and unofficial pronouncements about pseudonymity and/or privacy on Google+ in particular, in addition to the more general discussions taking place at Anti-pseudonym bingo and Social networking requirements. You can also discuss your feelings and reaction to various announcements here. warped-ellipsis, you can re-post your existing links in this thread if you like.

If you’re linking to a blog or Google+ discussion, please also include a summary or excerpt that explains why you’re linking to it. Is it a user test showing such-and-such a property of Google+? Is it a statement by Google or an employee? Is it a change or a clarification? That sort of thing. (No linking/quoting anything from G+ that isn’t marked “Public” please.)

Note: yes, Google+ is in beta/early launch/testing/something, and they’re actively seeking feedback. Please no nagging to people to send in their comments here as feedback, since they now know this for sure and presumably they have or will send it in if they want to, and if they haven’t they presumably have their reasons.

Social networking requirements

This article originally appeared on Geek Feminism.

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.

What else? How do your favourite sites do on these?

Anti-pseudonym bingo

This article originally appeared on Geek Feminism.

People testing the Google+ social network are discussing increasing evidence that, terms of service requirement or not, Google+ wants people to use their legal names much as Facebook does. Skud shares a heads-up from a user banned for using his initials. Then, for example, see discussion around it on Mark Cuban’s stream, Skud’s stream and Sarah Stokely’s blog.

Let’s recap really quickly: wanting to and being able to use your legal name everywhere is associated with privilege. Non-exhaustive list of reasons you might not want to use it on social networks: everyone knows you by a nickname; you want everyone to know you by a nickname; you’re experimenting with changing some aspect of your identity online before you do it elsewhere; online circles are the only place it’s safe to express some aspect of your identity, ever; your legal name marks you as a member of a group disproportionately targeted for harassment; you want to say things or make connections that you don’t want to share with colleagues, family or bosses; you hate your legal name because it is shared with an abusive family member; your legal name doesn’t match your gender identity; you want to participate in a social network as a fictional character; the mere thought of your stalker seeing even your locked down profile makes you sick; you want to create a special-purpose account; you’re an activist wanting to share information but will be in danger if identified; your legal name is imposed by a legal system that doesn’t match your culture… you know, stuff that only affects a really teeny minority numerically, and only a little bit, you know? (For more on the issue in general, see On refusing to tell you my name and previous posts on this site.)

Anyway, in honour of round one million of forgetting about all of this totally, I bring you anti-pseudonymity bingo!
5x5 bingo card with anti-pseudonymity arguments
Text version at bottom of post.

What squares would you add? Continue reading “Anti-pseudonym bingo”

From comments: this is what a computer scientist looks like

This article originally appeared on Geek Feminism.

From comments on Women in science: contrary to popular belief, some of us are actually alive!, Lindsey has started a Flickr group for “This is what a computer scientist looks like”. The group itself has this description:

This group collects photos of computer scientists, with a particular focus on women (may change later to include other underrepresented groups in CS).

If you are a woman in computer science, feel free to contribute a photo of yourself. If you’re contributing a photo of someone else, please make sure it’s a public photo that you have permission to share, preferably one taken at a public event such as a professional conference or workshop.

In the spirit of Photos of Mathematicians, we’re looking for modern, candid photos of currently active, not-necessarily-famous computer scientists. We’re not looking for historical photos.

So far, I am the only computer scientist. Fear me or displace me at the front of the queue!

Harassing photography and recording; ethics and policies

This article originally appeared on Geek Feminism.

We’re starting to collect some examples of photography/recording harassment experiences (still open , and some of the kinds of problems people mention there and elsewhere are:

  • photography/recording conducted in a way that is designed to hide the fact of the photography/recording from the subject both before and after the shot/recording happens
  • photography/recording that is indifferent to or careless of the subject’s feelings about being photographed/recorded
  • photography/recording that is othering: “wow, women! *click click*” or “hey, babe, smile for the camera!” or later posted with othering, sexist or creepy commentary
  • failing or refusing to stop photographing/recording on an explicit request or appearance of discomfort (eg turning away or frowning or covering one’s face, etc)
  • publishing photographs without the subject’s consent, or after the subject’s explicit refusal of consent
  • use of photographs to implicitly or explicitly endorse an event or community, eg, using pics of smiling participants from the previous year in publicity materials, without consent

Now most of these things are legal in my region (see NSW Photographer’s Rights, which as you will guess from the title is not focussed on subject’s concerns, but which is informative) and in many others. I believe the only exception (in NSW) may be the last, because the use of someone’s image to promote a product requires a model release, that is, consent from the subject. Whether/when using someone’s photo on a website is considered promotion I don’t know but that’s a side point.

For that matter, I’m not even arguing that they should be illegal or actionable (in this piece anyway, perhaps some of them are arguable). I’m sympathetic to many of the uses of non-consensual photography, even (art, journalism, historical documentation). I’m arguing more narrowly that in the context of geek events, which are usually private and which can therefore impose additional restrictions on behaviour as a condition of entry, that restrictions on photography could prevent some harassment. (As a short and possibly sloppy definition for people who haven’t seen many harassment discussions, I would define harassment as “unwelcome interpersonal interactions, which either a reasonable person would know are unwelcome, or which were stated to be unwelcome but continued after that.”)

I’m arguing that this collection of behaviours around photographs makes geek events hostile to some participants, especially women. After all, even though it’s (I think) legal to sneak-photograph a woman’s face, write a little essay about how attractive you find her and try and get it on Flickr Explore even as she emails you to say that she’s upset and repeatedly request that you take it down, that doesn’t mean it’s ethical.

Now, obviously it would be nice not to have to spell ethical behaviour out to people, but the need for anti-harassment policies (and, for that matter, law) makes it clear that geek events do need to do so.

There’s quite a range of possible policies that could be adopted around photography:

  • the status quo, obviously, which at many geek events is that any photography/recording that would be legally allowed in public spaces is allowed there;
  • photography/recording should be treated like other potentially harassing interpersonal interactions at an event, that is, when one person in the interaction says “stop” or “leave me alone” (etc), the interaction must end;
  • photography/recording shouldn’t be done in such a way as to hide from the subject that it’s happening, and upon the subject’s request the photo/footage/etc must be deleted;
  • subjects cannot be photographed/recorded without prior explicit consent; and/or
  • the above combined with some kind of explicit opt-in or opt-out marking so that one doesn’t need to necessarily ask every time if one can see the marking (in various conversations on this I have to say my main concern tends to be the need to peer closely at people’s chests to see their “PHOTOS/VIDEOS OK” or “NO PHOTOS/VIDEOS” marking on their badge, however, Skud says it works well at Wiscon).

There might be certain additional freedoms or restrictions regarding crowd photography/recording and/or photography/recording of organisers, scheduled speakers and people actively highlighted in similar formal events.

What do you think? Whether a photographer/videographer/recorder or subject of same, what do you think appropriate ethics are when photographing/recording at private geek events, and what do you think could/should be codified as policy?

Note to commenters: there are a couple of things that tend to come up a lot in these sorts of discussions, which are:

  1. “but this is perfectly legal [in my jurisdiction]”
  2. some geeks, including geek photographers, are shy and asking strangers for permission to photograph them is a confronting interaction, and thus very hard on shy people

I’m not saying that you need to totally avoid discussion of these points in comments here, but you can safely assume that everyone knows these points and has to some degree taken them into account and go from there. (My own perspective on the last one is that it’s odd at best to pay an enormous amount of heed to the social comfort of photographers at the expense of their subjects. You could, of course, consider both together.) Also if talking about legal aspects, do specify which jurisdiction(s) you are talking about: this is an area where laws vary substantially.

Confession: I’ve been a girlfriend

This article originally appeared on Geek Feminism.

True story! I’m a wife now. I’ve moved up in the WAG acronym.

There’s been a lot of pushback on Cate’s guest post and with good reason, because it can be easily read as positing that geek woman are mutually exclusive from women who have a geek partner dichotomy:

  • She’s not a techie, she’s a girlfriend
  • the girlfriend… the lead user… the commenter
  • a girlfriend… rather than a genuine tech woman
  • the girlfriend, or another woman near tech
  • Sorry girlfriend, you’re not a geek.

Here’s another thing: there’s a lot of geek my then-boyfriend-now-husband introduced me to. Linux was a big one. A great deal of the C programming language. Digital music, both ripping and listening. Actual other living geeks, as opposed to Eric Raymond’s J Random Hacker. Suffice to say that his influence on the nature of my geekdom has been substantial (and vice versa, which needs to be said).

And frankly while a lot of people are introduced to geekdom or new geekdoms by partners, it’s considered rather a shameful thing in my experience, especially if it was a male partner. If a man taught a woman to do something, or a man remains better at that thing than the woman he taught is at it, it’s as if the woman doesn’t have that interest or skill at all. She is assumed to be the man’s puppet.

There is something real, in my experience, about less involved women being asked to give “the woman’s perspective” on geekdom, as if their experience is “more woman” than that of heavily involved geek women, as if very geeky women have forfeited “the woman’s perspective”. But there’s also equally difficult experiences:

  1. the assumption by geeks that a woman geek with a partner, especially a male one, is not geeky, or only geeky because of internal relationship dynamics, rather than being ‘really’ geeky (whatever that means)
  2. the experience some non-geek women or newly geek women report, of experiencing hostility from geek women for “making them look bad” and from geeks in general for being too mainstream or feminine (and hence boring or thoughtless)

We’re not going to get anywhere with the above by talking about girlfriends as if they aren’t us, or as if they can’t become us or we them. I think that adopting girlfriend as a metaphor is harmful: the primary meaning is (some subset of) women who have a partner. Anything said about metaphorical girlfriends will quickly be taken to apply to literal girlfriends, as in women who have partners, and used against them, even if it was supposed to be a metaphor for women who are granted some credibility as more woman because they are less geek (which is, I think, what Cate is using the term “girlfriend” to mean, although it isn’t totally clear to me).

We have to not feed the “femininity is mainstream and therefore not geek” beast.

Additional concerns about Cate’s post that were raised in her comments and which I share:

  • the geekiness hierarchy in which people who build things trump people who comment, use, or analyse in geekiness. If nothing else, I personally spend a lot of time writing feminist stuff on the Internet, as well as coding, and I’m not accustomed to thinking of one as the less geeky activity than the other
  • the conflation of “geek” with “programmer” or “computer geek”, which as several commenters noted we’re rightly committed to not doing around here

By the way, a little bit of background on our process: guest posts here tend to be selected by one author and put up here, we all have access to the “Guest Poster” account. So that accounts for the appearance of a guest post with a message/metaphor that I at least don’t especially like, if you are wondering! There’s no cabal, etc.

On feeling less safe

This article originally appeared on Geek Feminism.

Over at Hoyden About Town, Wildly Parenthetical considers Tackling Misogyny: Procedures or Social Sanctions?:

But more interesting has been the discussion about formal and informal mechanisms for dealing with sexual harassment. There are lots of reasons that formal mechanisms don’t work for lots of people… So we have the suggestion of informal “shunning’. Some have, with more and less hyperbole, suggested that without the formality of systems of justice and the “certainty’ they’re meant to bring, individuals could wind up excluded on heresay; this is the “OMG WITCHHUNT!’ objection. And others have pointed out that social sanctions are applied to all kinds of behaviours that are disapproved of in our society, and why should this particular behaviour be any different? I am pretty much with the latter group, although I understand those who think that we should be putting our energies towards fixing the formal systems rather than developing shun-lists…

I left a comment that I want to re-post here, since it captures neatly a lot of my more negative feelings about discussions around anti-harassment policies and such, which a lot of people in the geek community consider informal since geeks themselves will enforce them.

My response (very slightly edited here) was as follows:

I am a fan of social sanctions in an ideal world. There tend to be two problems with introducing it in practice:

  1. Some people at either the level of instinct or the level of rational analysis find it almost impossible to distinguish from bullying (see the Geek Social Fallacies, especially ) and refuse to participate or actively attempt to defend the person sanctioned or decide to sanction the sanctioners, causing a lot of internal community conflict.
  2. It often turns out (at least in communities that I’m a part of) that not as many people are opposed to sexual harassment as one might hope. So a substantial fraction of participants oppose social sanctions or vow to not enforce them because it turns out they like sexual harassment just fine.

Option 2 is always a really distressing conversation to have in a community you felt safe in; you seldom feel safe after it turns out that a loud minority feel that sexual harassment is the effective/normal/desirable (at least, but not exclusively) heterosexual mating strategy.

How is everyone else feeling about the geek community after whatever their latest local round of feminist discussion was? I’m far from entirely negative, but there are definitely whole new places I don’t feel safe from harassment and indeed assault now.

Open thread: parthenogenesis in Komodo dragons

This article originally appeared on Geek Feminism.

A baby Komodo dragon born by parthenogenesis, photographed at Chester Zoo (CC BY-SA 3.0, Wikipedia user Neil)
A baby Komodo dragon born by parthenogenesis, photographed at Chester Zoo (CC BY-SA 3.0, Wikipedia user Neil)

What the hell. It’s geeky. And this is a fairly new (published 2006) finding about komodo dragons. To quote from Wikipedia:

On December 20, 2006, it was reported that Flora, a captive Komodo dragon living in the Chester Zoo in England, was the second known Komodo dragon to have laid unfertilized eggs: she laid 11 eggs, and 7 of them hatched, all of them male. Scientists at Liverpool University in England performed genetic tests on three eggs that collapsed after being moved to an incubator, and verified that Flora had never been in physical contact with a male dragon. After Flora’s eggs’ condition had been discovered, testing showed that [London Zoo dragon] Sungai’s eggs were also produced without outside fertilization…

Komodo dragons have the ZW chromosomal sex-determination system, as opposed to the mammalian XY system. Male progeny prove that Flora’s unfertilized eggs were haploid (n) and doubled their chromosomes later to become diploid (2n) (by being fertilized by a polar body, or by chromosome duplication without cell division), rather than by her laying diploid eggs by one of the meiosis reduction-divisions in her ovaries failing. When a female Komodo dragon (with ZW sex chromosomes) reproduces in this manner, she provides her progeny with only one chromosome from each of her pairs of chromosomes, including only one of her two sex chromosomes. This single set of chromosomes is duplicated in the egg, which develops parthenogenetically. Eggs receiving a Z chromosome become ZZ (male); those receiving a W chromosome become WW and fail to develop.

The Nature article is Phillip C. Watts et al (2006) Parthenogenesis in Komodo dragons, Nature 444, 1021–1022 (21 December 2006), doi:10.1038/4441021a.

This is an open thread, for a discussion of biology geeking, great nerdy events and, of course, anything else you want to discuss!

Impostor syndrome and hiring power

This article originally appeared on Geek Feminism.

This is an Ask a Geek Feminist question:

What are some ways in which I can avoid rejecting people who suffer from impostor syndrome when they apply for a job?

I’ve recently been promoted to a position where I’m somewhat responsible for hiring people. I would like to increase the diversity of new hires, and so I’m more likely to put applications from women through to the interview stage.

Following that though I don’t want to lose out on quality applicants as they are modest about their achievements and abilities, due to impostor syndrome or otherwise.

Giving an automatic “+10 kickass” to every female applicant as they may suffer from impostor syndrome seems to be a strategy without much merit. Getting everyone to exhibit their full potential is clearly the better solution.

Can you suggest interview strategies that would create the environment in which women (and indeed anyone) will be better able to convince me of their suitability for the role?

I don’t have so many specific interview strategies, but I’ve got plenty of ideas for hiring strategies in general, I hope you can adopt some of them and perhaps our commenters can talk about the interview.

First, a should be obvious: a +10 kickass bonus may be illegal discrimination in your geographic area. If it is, definitely don’t do that.

With that out of the way, let’s talk about soliciting applications. Now, there’s a couple of things that stop some women at this point. First, there’s a tendency to regard themselves as underqualified for perfectly suitable jobs. Next, there’s concern that they needn’t bother, as a woman’s name will cause you to discount their resume. Some suggestions:

  1. get your signalling right. You want to say “women friendly employer” in your advertisements without discriminatory pro-women statements. This at least gets you past the “I’m not a man” part of impostor syndrome. Here’s some things you should be doing:
    • advertising all relevant open positions on a women’s job list such as, say, LinuxChix’s jobposts for open source jobs. This at least shows that you aren’t actively avoiding women applicants.
    • including on your full ads the “equal opportunity” boilerplate you might be able to find on other local job ads
    • including information on the “Careers” section of your website about your carer leave, your retirement contributions, your shared sick leave pool, your friendliness to part-time employees if any of these hold

    Not only are these things attractive to many women (and yes, some men as well) in and of themselves, they also signal in various ways that when you picture your new hire, the picture isn’t young, white, able-bodied, male, etc etc.

  2. if your employer has recently had a similar (especially perhaps slightly more junior) position available, get the resumes of the people who were considered the better applicants from the hiring manager, HR person or recruiter, and re-consider them for the new position (probably there would need to be some kind of process of tracking and perhaps re-application here, but I’ll handwave that problem to you).
  3. consider internal employees in more junior positions as potential applicants. Depending on the size of the company, other managers might be able to recommend people to you who are overqualified for their position (or possibly not, if they are getting good work from them)
  4. consider whether you really need experience that skews very very male. For example, does someone have to have open source development experience? Are there alternative ways that someone could have learned the skills you need?

And now for considering applications prior to interview:

  1. you may not be able to say you’re doing this, but in order to avoid bias on the basis of gender or other demographic characteristics, for as long as possible in the process keep names off resumes. Have names and addresses scraped from resumes by someone before you see them, and do as much ranking as you can prior to finding out the names and details of the applicants.
  2. avoid judgements about cultural fit at this stage.
  3. there are reasons companies rely on the recommendations of existing employees, but for each open position, try and select some applicants for interview who didn’t come in via the company networks in order to avoid duplicating your company’s present demographic by hiring all their friends

In the interview itself here is a strategy for getting people to talk about their successes when they are susceptible to impostor syndrome (note that any candidate might be part of an oppressed group, so don’t limit these to women candidates): ask about something the candidate did that benefited someone else. How did they save their company money or helped a team member learn what they needed to know? Present them with cooperative scenarios where they need to help you or your employer do something as well as or instead of competitive scenarios where they need to prove they are the single right person for the position. If anyone can flesh this out to specific example questions in the comments, that would be useful.

I strongly recommend reading Women Don’t Ask by Linda Babcock and Sara Laschever for good solid information both about women’s negotiation and self-promotion strategies and why they use those strategies, namely, that competitive and aggressive interpersonal strategies are simply not effective for most women because of negative responses to perceived aggression in women.

Quick hit: getting too close to power

This article originally appeared on Geek Feminism.

Trigger warning: this post describes and discusses harassment and threats.

Sady Doyle writes on Tiger Beatdown:

When feminist women reach a certain critical mass of readership or influence, then mass negative exposure and harassment invariably comes their way. Sooner or later, there are just too many people who know about you, and the threats become credible: Blacklisting, hacking, smear campaigns, invasion of private property, maybe even straight-up bodily harm. At a certain point it goes beyond grudges or trolling or sarcastic comments or even just isolated scary dudes; it becomes a large-scale Thing, and it attracts its fair share of people who operate without anything even vaguely resembling a conscience.

I mean, let’s review just a few of the more famous cases. They often have something to do with women approaching positions of power: As we all know, when Amanda Marcotte and Melissa McEwan were hired for the John Edwards campaign, there was a national and frequently televised campaign aimed not only at getting them fired, but at making them functionally unemployable. It went on for a long while, it was vicious, and it involved Bill O’Reilly, which is never fun. Furthermore, Jessica Valenti was accused of slutting it up with Bill Clinton because she was in a room with him along with some other people… In each case, this happened because the women were getting too close to power: A President, a presidential candidate. The idea that these women might be doing politics, not “just” gender politics. That was enough to set it off.

If it’s not power, it’s geek stuff. Because we are on the Internet, and the geeks are powerful. Kathy Sierra was subject to one of the most vicious, frightening campaigns of harassment and death threats that anyone has ever seen, because she spoke about software development. And being a lady, but mostly: Being a lady as it related to software development. “I am afraid to leave my yard, I will never feel the same. I will never be the same,” she wrote, to explain why she had to quit working and earning money as a speaker for a while… Then there was Harriet J and her criticism of Google Buzz — no, not Google Buzz!!!! — or McEwan, again, who got one of the biggest pile-ups of her career on a post about a video game called “Fat Princess.” Video games, tech, Google, basic Internet geek stuff: These are the things you’re not allowed to approach, for fear of harassment…

Other people are allowed to seek popularity. Other people are allowed to think it is a good thing. And yet, over here, we know that popularity is not good, but BAD. Feminists often RUN THE HELL AWAY FROM POPULARITY. At least, we do if we’ve got any darn sense in our heads or have seen this happen often enough. (I have a little sense. Not a lot, or enough.) Or if we don’t run away from it, our first instinct is to disavow basic things to which all writers should be entitled, like pride in our work, or a hope that our work might be read and respected. And the reason is this:

Because you cannot so much as mention “not deserving to be raped,” in a blog post about freaking GOOGLE PRIVACY SETTINGS, without getting hundreds of comments about how you should go get raped immediately, because you deserve to be raped so very much.

It is, as I hope is obvious from the quote, worth reading the whole thing.

But I wanted to highlight the relevance of this for this blog and the people who write for it or are in its community. None of this is news, and it is fairly obvious what I mean: we are critiquing geekdom, and geekdom is powerful here on the Internet.

And consequences like these have in fact of course already happened to us and near us. This blog itself doesn’t right at this moment undergo persistent trolling in moderation, it has in the past and undoubtedly will in the future. To give the best known example, MikeeUSA has been reappearing periodically since 2005, and that’s just in communities that I personally follow, and making threats of violence or death all that time, including explicitly invoking and praising the actions of murderer Hans Reiser and mass murderer Marc Lépine.

People who describe themselves as geek feminists and geek feminist activists regularly burn out or take planned breaks in various ways: they go back to technical blogging and technical work, they stop giving unicorn talks, they move their commentary partially or entirely to locked networks rather than public spaces. They may or may not come back to public activity.

I myself have not been a target of sustained personalised harassment campaigns—and even saying that is indicative of the problem, that someone who has “merely” experienced one-off incidents, or harassment aimed at women geeks in general rather than her in particular doesn’t feel like she’s experienced the “real” problem—but I have seen the weapons that are being used against my friends.

I want to, here, acknowledge these people and the work that they did, are doing, and will do. As firecat wrote a long time ago now:

Let’s say that fighting sexism is like a chorus of people singing a continuous tone. If enough people sing, the tone will be continuous even though each of the singers will be stopping singing to take a breath every now and then. The way to change things is for more people to sing rather than for the same small group of people to try to sing louder and never breathe.