Here is another reason Pluto is aro: Pluto has a heart shaped region called the Tombaugh region:

[ID: an image of Pluto and it's heart shaped Tombaugh region, with the moon Charon in the background. End ID]

top 2 will move on, bottom 5 will be eliminated, ties will be broken by random chance

you are not too much

you are not hard to love

you are allowed to have bad days

you are allowed to fall apart

I went, "What. no. she/her."

"How does that work? With she/her/hers and they/them?"

I stared at her. "What are you talking about?"

"Well you came out as-" and I said, "I'm asexual."

She replied, "Like an amoeba, I know."

"Oh. My god. No. Mom. It doesn't- it's not the asexual you learned about in biology. I didn't come out as a single celled organism."

With heavy relief, she said "Oh, it has a different meaning?"

What is a hit?

According to AO3′s FAQ:

Hits are a counter of how many times a work has been accessed. A hit is registered every time a visitor navigates to a work’s page, with the following exceptions:

If two visits in a row come from the same IP address, only the first one is registered.

Moving between chapters in a work will only register one hit in total, not one hit per chapter.

If you’re logged in, hits are not counted when you visit your own works.

Note that hits only log the number of visits to a work, not the duration of the visit. The number of Hits in the Totals box on your Statistics page (refer to Where do I find Statistics? for instructions) is the total number of hits all your works have received.

Hold up.

Read that first bullet point again. 

If two visits in a row come from the same IP address, only the first one is registered.

What does this mean exactly? Here’s an example from AO3:

So if you visit a work, then leave the page and view it again (from the same device and internet connection) the following week, and no other user has visited it in the meantime, your second visit would not register as a new hit.

However, if I had visited the work after your first visit but before your second, then your second visit would count as a new hit.

Here is another example. Pretend that your AO3 fandom consists of only three people: You, your friend, and an author. The author posts a fic and never looks at it again. Being the loyal fanfic followers you are, you and your friend both strive to read the fic.

Scenario A: You open the fic first. Your friend is busy with real life and does not open the fic until the next day. You take your time and read the fic over the course of the day, refreshing the fic four times (from the same device and internet connection so that your IP address is the same).

Since you are the sole reader that day, even though you visited the fic five times (your first visit was when you first opened the fic + four times you refreshed), AO3 registers that all five consecutive visits were from the same IP address and therefore does not count the four times you refreshed the page as hits.

Visits: 5   |   Readers: 1   |   Hits: 1

You finish the fic today and close out of it. The next day, your friend opens the fic and begins reading. The first time they open the fic (visit 6 of the fic), AO3 registers that the IP address is different from the previous visit. The hits counter ticks up by one.

Visits: 6   |   Readers: 2   |   Hits: 2

Your friend also takes their time and refreshes the fic four times over the course of the day. Since they are the only reader that day, at the end of the day, the score is:

Visits: 10   |   Readers: 2   |   Hits: 2

Scenario B: You and your friend both open the fic on the same day. You open it first, and then they do. If each of you refresh the fic four time with you refreshing first, and interleaving both of your refreshes, at the end of the day, AO3 would have recorded thus:

Visits: 10   |   Readers: 2   |   Hits: 10

There are multiple variations on these scenarios but hopefully these two are enough to illustrate how the hit counter on AO3 works. AO3 has their reasons for coding the hit counter the way they do (mostly to do with privacy and storage of information issues), but that’s a hit, and that’s why hits should only be used to make a rough estimate of the number of readers — and why you shouldn’t put too much stock in the kudos/hits ratio (particularly for multichapter fics). 

I wanted to call particular attention to this point. Multi-chapter works often receive many more hits than audience members, especially if the chapters are posted over time. This typically drops the kudos/hits ratio dramatically.

Even if the chapters are all posted at once, or if a long work is published as a single chapter, long works often have the same person opening and closing them multiple times before they finish. Popular works experience the same effect through being re-opened by people who previously enjoyed them. This is one reason you’ll see kudos/hits ratios drop for a work over time, even for works that take only a short time to enjoy.