And we are wondering why guys on this forum keep coming back here, trying the same thing again and again while expecting different results.
This mentality of looking for "easy" women only leaves you with wretched 304's. What has led to this way of thinking is called "the fallacy of affirming consequent", which is the fallacy of thinking (A => B) implies (not A => no B), which is mathematically and logically incorrect.
In the scenario under discussion in this thread, the fallacy is this:
If she is giving it up for you, she is into you (probably a true statement); therefore, if she isn't giving it up for you, she isn't interested in you, or some variations of that conclusion (false statement).
This is incorrect.
The logically correct step-by-step analysis is this:
- Quick s*x: She easily has s*x with me. So she is into me. But also she is or will probably do the same with other men. So she probably is not a reliable woman for LTR.
- Wait for s*x: If she doesn't want to have s*x with me now, it is because one of the three:
- She is not heteros*xual.
- She is not that into me.
- She is the kind of woman who is saving for marriage, or at least first verifies the man and then has s*x.
Now 1. and 2.1. are easy. Discerning 2.2. and 2.3. is quite tricky however. To make sure you're in scenario 2.3. and not 2.2. you need to verify quite a few things, such as:
- She is religious or has strong traditional values.
- She introduces you to other people and ideally her family.
- She express her interest in you in other ways, such as cooking for you, trying to do things for you, etc.
- Her phone an open book. She allows you to see her messages and call history.
- She does not have an active social media account (for example an Instagram account with <200 followers, where most of her followers and followings are family and female friends is OK.)
- She does not have any close male friends (I don't mean acquaintance or colleague).
If she doesn't check
all of the boxes above, then you're in scenario 2.2. Otherwise, you're most likely in scenario 2.3.