> Is that really relevant here, though?

It is. That anecdote reminds us there are different kinds of demand:

1. apparent demand
2. latent demand

You are asking why we aren't meeting apparent demand. Part of my answer is that we are meeting latent demand at the cost of not meeting apparent demand.

> It implies that you think the features I mentioned shouldn't be built.

Taken literally, I can see how that is implied. It's not what I meant.

> isn't growth also about churn

It is and churn is about two things:

1. retention
2. attracting new people

On a relative basis, we are very good at retention and bad at attracting new people. So we should bias toward attracting new people.

> Surely easier than trying to use the internet in a way it's fighting you?

I don't understand this one.

k00b

I figured you'd say that. Is that really relevant here, though? It implies that you think the features I mentioned shouldn't be built.

I think such phrases need to be used in the appropriate context. It makes more sense when asking people on the street what they want, rather than when long-term users are repeatedly requesting a feature in an existing product without being prompted.

That I can agree with, but isn't growth also about churn? You don't grow if more people are leaving than coming in. I don't know if (enough) stackers are leaving for this to be important, though.

Yes. I'm basically asking why these general territory improvements, that 

 would have spent your time on, are less important than custom domains.

Surely easier than trying to use the internet in a way it's fighting you?

Anyway. You don't need to reply to this, I know you're busy. Just wanted to let you know my thoughts

Stacker Saloon

saloon

> 1. faster horses were in high demand when automobiles were invented

I figured you'd say that. Is that really relevant here, though? It implies that you think the features I mentioned shouldn't be built.

I think such phrases need to be used in the appropriate context. It makes more sense when asking people on the street what they want, rather than when long-term users are repeatedly requesting a feature in an existing product without being prompted.

> 2. custom domains are related to downstream work and getting them done will improve that work

Ok I did not know about this, thanks

> 3. custom domains are about growth and growth (having more people posting about and discussing stuff) is in high demand

That I can agree with, but isn't growth also about churn? You don't grow if more people are leaving than coming in. I don't know if (enough) stackers are leaving for this to be important, though.

> 4. i was supposed to be working on general territory improvements after my payment engine refactor but have had to work on wallets instead

Yes. I'm basically asking why these general territory improvements, that *you* would have spent your time on, are less important than custom domains.

> 5. territory pools are highly interactive/require coordination, so it's not as trivial as it seems

Surely easier than trying to use the internet in a way it's fighting you?

---

Anyway. You don't need to reply to this, I know you're busy. Just wanted to let you know my thoughts