Image: jDrew Angerer / Getty Images / Protocol
Lessons for Jack from the big Twitter hack

Good morning! This Thursday, lessons from the epic hack that took over Twitter, the fight in streaming shifts to distribution and everybody wants to be the only work app you need.
(Was this email forwarded to you? Sign up here to get Source Code every day.)
On Protocol: Bill Tai says he has a big new project in the works:
On Protocol: Facebook's trying to help the government regulate Facebook, and deputy chief privacy officer Rob Sherman wants your thoughts, too:
The U.S. is restricting visas for Huawei employees, and Mike Pompeo said there's more to come:
On Protocol: Fixing climate change is about to become really big business, Mayfield's Arvind Gupta thinks:
Satya Nadella had some strong words about America's connectivity gap, as he announced a plan to help close it:
Here's what we know. As Protocol's Emily Birnbaum, Tom Krazit and Issie Lapowsky wrote, a bunch of high-profile Twitter users — from Elon Musk to Bill Gates to Joe Biden to Uber to Apple to Kanye West — were all hacked as part of a crypto scam yesterday.
We also know that people are mad: Josh Hawley, never one to miss an opportunity to yell at tech companies, quickly demanded information and answers. "I am concerned that this event may represent not merely a coordinated set of separate hacking incidents but rather a successful attack on the security of Twitter itself," he wrote.
Jack Dorsey certainly has some explaining to do. Last night he tweeted an apology. And then @TwitterSupport started to describe what happened: "We detected what we believe to be a coordinated social engineering attack by people who successfully targeted some of our employees with access to internal systems and tools." The company promised more information soon.
So what's the lesson for Jack? Well, it's one as old as the internet: Your company's weakest security link is the people who work there. You can turn on two-factor authentication (and you should), you can have clear security policies (and you should), but there are always risks. And there's a bigger point here about reducing that risk: The tech industry favors flat hierarchies and open cultures, but Twitter's not the first to run into trouble for giving too many people too much access. Maybe it's time for Twitter, and everyone, to rethink permissions.
After years of planning, prelaunches, delays, and relaunches, it appears we have all the streaming services we're going to have for a while. The newest entrant: Peacock, from NBCUniversal.
Now that Peacock's out, here's where we are: a landscape with four rough categories.
Going forward, the real streaming war is now over distribution, as Amazon and Roku in particular try to impose their will as powerful platforms (and the owner of customer data, and seller of ads) while the services try to go as direct as possible to viewers.
If you're thinking about where to advertise or where to put your content, the situation's more complicated than it was when everything was available everywhere. We're shifting now from questions about what people watch, to how and where they watch it. And that's going to be just as messy.
In the face of COVID-19, many healthcare providers turned to remote patient monitoring and virtual visits to continue caring for vulnerable patients while minimizing risk of virus transmissions and reducing the strain on scarce hospital resources. At Philips, we're pioneering stronger care networks with technologies we've spent decade innovating - and we believe our homes are destined to play a central role in the healthcare system of the future.
At some point, every business-software company seems to have the same idea: "There are too many apps. What if all the apps … were our app? That would be a much better user experience!" At least, until they realize every other company also wants to be everything to everyone.
Just yesterday, three big enterprise software makers had the thought, and announced their intentions to own the future of work. (Not to be confused with the enterprise software makers who have already made that announcement.)
So, for those of you who run a business-software company: In addition to building your own apps, are you going to build a deep and beautiful integration for Asana, one for Trello, one for Gmail, and one for every other work-home people have? Really good APIs solve part of your problem, but we're entering a phase a bit like the early smartphone market, with a zillion operating systems and no way to work with them all.
Which means, more likely than not, we'll get the iOS and Android of enterprise software pretty soon. And there's a lot of money to be made for whichever of you builds them.
If you do run a business-software company, I'm curious to hear what you think: david@protocol.com.
Taylor Bennett is DoorDash's new head of public affairs. He comes from the same job at Lime, where he's been since 2018.
Brad Parscale is out as Trump's campaign manager, and will go back to running the campaign's digital and data strategies. Bill Stepien is now running the campaign.
Catherine Powell is Airbnb's new global head of hosting. Hiroki Asai is also joining the company to run marketing, and head of homes Greg Greeley is leaving the company.
OK, last thing on the Twitter stuff: The most fun part of the whole ordeal was watching all the people gleefully roast the verified users, who suddenly couldn't tweet for hours on end. If you wanted a blue check, and never got one? Yesterday was your day in the sun. Mashable has a good roundup of some of the funniest tweets, as proof that maybe half the people on Twitter should be kicked off the platform … every day.
In the face of COVID-19, many healthcare providers turned to remote patient monitoring and virtual visits to continue caring for vulnerable patients while minimizing risk of virus transmissions and reducing the strain on scarce hospital resources. At Philips, we're pioneering stronger care networks with technologies we've spent decade innovating - and we believe our homes are destined to play a central role in the healthcare system of the future.
Today's Source Code was written by David Pierce, with help from Shakeel Hashim. Thoughts, questions, tips? Send them to david@protocol.com, or our tips line, tips@protocol.com. Enjoy your day, see you tomorrow.
To give you the best possible experience, this site uses cookies. If you continue browsing. you accept our use of cookies. You can review our privacy policy to find out more about the cookies we use.