in the time i've spent looking at white supremacist violence, i've mostly focused on men. i think we as a society have only just started the examination of white supremacist women and di think this thread/article is a great start.

The best way to know if people like your product is NOT:

- Have a lot of emails in the waiting list
- Become #1 on PH
- Become #1 of HN or Reddit
- Have people that saing "I'll pay"
- Have a lot of free users

The best way to know if they're actually pay for it.

The only thing that matters is your product providing a value, and you can't know this until people will pay money for it.

We can have a first signal of a product/market fit after the launch by check how many sales we've got in the first 24h. Some scale:

200+ This has a high potential.
100+: This has a potential.
50+: Some people need it.
10+: People almost don't need it.
0+: People don't need it.

This is for a single time payment product. For a subscription probably it should be less because people hate subscription.

And obviously, you should have a lot of traffic like 3-5k+.

Here is a stat for my products (macOS apps) for the first 24h after the launch:

An interesting set of games that I've been vaguely interested in since I was a kid, after seeing one at a friend's house and never being able to find it again, was the BATTLES IN A DISTANT DESERT/BATTLES ON DISTANT PLANETS series.

These are turn-based wargames for windows 3.x, sharing the same engine.
Battles in a Distant Desert is from 1992, and is based on the first Iraq war (Desert Storm)

and Battles on Distant Planets is from 1991, and takes place in SPACE!
I'm pretty sure this is the one I played as a kid.

They've got 3 options to play with:
* Player vs. Player
* Player vs. Computer
* Computer vs. Computer

So it's a 0-2 player game!

They also did a DOS strategy game called "STARDATE 2140.2: GALACTIC CONQUEST" in 1990, but it seems to be lost.
All the games share an experimental AI system based on neural networks.

Singing the Blues:
Taking Down an Insider Threat

"I had all of the advantages. I was already inside the network. No one suspected me. But they found my hack, kicked me off the network...

...and physically hunted me down."

Many pentests start from the outside, wanting to see how the perimeter might be breached.

This pentest started from the inside. My client wanted to assume they had already been breached, and, if breached, how far could an attacker go.

Could they stop me once I was inside?

So they snuck me in. Disguised me as a new employee. Gave me a work computer, an ID badge, an account in their system... hell, I even had a cubicle w/my assumed name on it.

The only person who knew who I really was was their CISO. Everyone else thought I was Jeremy in Marketing.

During most of the first morning, I completed onboarding, made introductions, and completed menial tasks.

But I had to act quick. I only had a week onsite. I had to hack their network while not raising suspicion.

So I set about it.

You have to understand... most "Internal Pentests" are straight forward. The hard part is breaching the network, but once you're inside, it's a target rich environment. End of Life computers, default passwords, everyone a Local Administrator...