Results from yesterday’s poll. I’m inclined to agree. And this is something I’m going to fix in my next move.

On December 25 Mr Pool retweeted August 16 message about the Phoenix and that the worst was still on the horizon to come. 1/*

Maybe now we can assume that November 3 message meant "FUD" nor "FUN". Putting the word in capital letters seems to indicate the aspect the word fud has in our space, FUD. 2/*

Brad started it on December 22 (1/3 posts (Don't say? Sure) = 13 = Plan B). 3/*

And immediately the SEC followed dropping the bomb (1.3 billions (Don't say? Sure) = 13 = Plan B). 4/*

FUD materializes, Bitstamp is one of the first that haltes XRP trading and so on. 5/*

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.

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...