Dear @MayorLungoKoehn (cc @Morell4Medford@zacbears):
This will be a bit long, but it’ll be a series of tweets, not just a picture, so it’s accessible to more humans.
I think I can see your effort here, but this semi-apology is highly problematic. 1/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears Let’s start with your language. An apology should always start with “I,” not “We.” “I” owns. “We” deflects. Who is “We”? There are some exceptions, but “I” is more powerful, and, actually, helpful as you write the rest of the apology. 2/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears Why are you apologizing? You need to reiterate the action. Are you apologizing for the harm? No, you *regret* the harm. You need to apologize for the action. *How* did your office fail this spectacularly? What specific things did your team do or not do? 3/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears Why are you apologizing to the community at large? By the way, this is a dog whistle; almost every time that a public official apologies or notes an antisemitic action, it’s “all forms of hate” or “community at large.” Can’t you just apologize to us? 4/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears Now let’s talk about “used in error.” The *error* is the entire point of your apology, but it’s glossed over. This should be where you really go. Maybe: “We did not reach out to faith leaders in the community, despite a long tradition of doing so.” 5/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears Really, I want to understand precisely how an image associated with a fringe messianic Christian movement came into play here. How did your staff find this image? How did no one have enough knowledge to even question it? This is the meat of the failure. 6/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears The optics from over here, which I’d like to think is wrong based on past history, is that City Hall communicates more with antisemitic eliminationists than with Jews, and doesn’t have enough in-house awareness to detect awful rhetoric. 7/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears “attributed with Christian symbolism.” First, copyediting should have been done here; but let’s not tarnish all of our Christian siblings with this one. I’m pretty sure that most of them would find this image offensive (my sample today agrees). 8/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears The problem is language that calls for Jews to “atone for Israel”, be “clean from sin,” mixed in with the Christian language. How disconnected is your office that *no one* questioned this? 9/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears In short, I am disappointed in the lack of general process here, and it probably applies elsewhere: how did no one second-guess and triple-check this? I hate recommending sensitivity training, but Judaism 101 might be a good idea. 11/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears I don’t know how many Christians were discomfited by the use of a tree, versus a nativity scene, to represent their holiday, and whether that’s tied up in First Amendment jurisprudence, which might be a better educational display! 12/ #MedfordAntiSemitism
@MayorLungoKoehn@Morell4Medford@zacbears That’s it. I hope this was helpful, so you can better understand what it feels like over here. I’m off to go welcome Shabbat (that’s our weekly celebration of the day Adonai rested after creating the world). May you find peace and joy. 13/ #MedfordAntiSemitism
The first time I crossed paths with @dakami, let’s just say I wasn’t pleased. But it’s a little bit of a long story, and we did share a laugh at the end of it, so bear with me. #InMemoryOfDakami
The story starts in 2007, maybe. One of my biggest worries at Akamai was hardening our DNS infrastructure. If you take out a CDN’s top level DNS, that’s … pretty much it. 2/ #InMemoryOfDakami
You’re limited in how many top level name servers you can use for a given domain (by convention, 8 IPs, although really, 13). That’s gives you a weak spot that an attacker can go after, and I really wanted to solve it. 3/ #InMemoryOfDakami
I see a variant of this almost weekly. If you ever find yourself denigrating humanity’s risk management, recognize that we got this far, and consider how your model could use updating. 1/
Humans take risk in everything we do. It’s really important to *not* be paralyzed by known risks. So you internalize the risks you live with, and generally ignore them. 2/
But the new and novel risks - even if they don’t *yet* rise to levels you stably tolerate - capture your attention because they *might* go catastrophic. 3/
First: kudos to @Cloudflare for transparency here and throughout their incident.
Next: some thoughts on safety in distributed systems like this. (I don’t know how CF does it, so don’t take this as criticism of their practices, merely some musings from similar experiences) 1/
While test and QA is important, massive distributed systems with unconstrained user inputs are hard to simulate, so deployment to production is *always* risky. Call it “operational field testing,” but there is always the chance you’re going to find new failure modes there. 2/
There are several areas to scale safety: staged rollout, rapid rollback, error detection, edge failure rejection. 3/
Dear $VENDOR,
Starting your pitch – especially in a social setting – with “What are you doing about problem X?” is a pretty clear setup. You’re putting your target on the defensive even before they open their mouth. 1/
Yes, you’re trying to get your target to commit to doing something that isn’t as “good” as your solution. And of course, that sets you up to close an improvement deal, right?
Wrong. 2/
Here’s the secret about IT security: it’s imperfect. There are a thousand problems, and there is room for improvement on just about every single one.
And every CIO and CSO knows this, but probably doesn’t want to tell you this. 3/