The pity of it all is:

"in some contexts it's not a problem to treat TW *as if* they are women, and in others it's a *huge* problem, so let's talk about specifics"

is all that a lot of people been saying.

TWAW was always absolutist, and always false.

So, you’re a writer and you’re worried about writing outside your immediate experiences and identities.

Here is the thread of practical advice for you.

EXAMINE YOUR MOTIVES. Why do you want to write this?

Are you trying to solve racism/sexism/colonialism with your work?

As writers we love stories about heroic writers whose work has changed the world. And as such we like to look to our own writing to solve societal problems.

And I understand this completely, not the least because I’ve felt the pull.

But if you’re looking to play saviour with your words, it is unlikely that you will do the marginalised people you are trying to save justice.

And I understand this very often comes from place of good intentions, but there is a reason that most of the moralising plays written by white abolitionists are deeply uncomfortable to read.

It is incredibly easy for works looking to play saviour to become patronising or traffic in simplistic stereotypes that ultimately hurt the people they are looking to rescue.

So there's a class of puzzles called "river crossing puzzles" which involve having to cross a river on a boat/bridge containing some set of individuals/items with restrictions on which ones can be on the boat/left on each shore, right?

and the most common subclass of these problems is the one where you have 3 items/animals to cross with.
This is alternatively called the "fox, goose, and bag of beans" or "wolf, goat, and cabbage" puzzle.

the idea is that your boat can only carry one item at a time, but if you leave the wolf/fox unattended with the goat/goose, the wolf/fox will eat the goat/goose.
and similarly, the goose/goat will eat the beans/cabbage if left alone

so you have to set up a set of actions that never leaves either side of the river in one of the lose-states.

the solution to this variant being:
1. take the goat/goose over
2. return empty
3. take the wolf/fox over
4. return with the goat/goose
5. take the cabbage/beans over
6. return empty
7. take the goat/goose over

So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

Wired first reported on how bad Keystone was 11 years ago when they put it into Google Earth (they seem to put it in all their popular

The fact that Keystone hides itself in Activity Monitor is bizarre. (The only sign of it was excessive CPU usage of WindowServer which is a system process).

I don’t know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about). But either way, I’m not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome)...

...since it's been a decade+ and this still hasn't been "fixed".

There is no reason for auto-update software to need to do what Chrome/Keystone was doing. It also has a long history of crashing Macs.