1
00:00:02,400 --> 00:00:05,000
Welcome back to the Elon Musk 
podcast where we explore the 

2
00:00:05,000 --> 00:00:07,900
latest news and updates on the 
companies associated with one of

3
00:00:07,908 --> 00:00:11,000
the most Visionary minds of our 
time, Elon Musk. 

4
00:00:11,100 --> 00:00:13,800
And in this episode, we'll be 
discussing the recent Twitter, 

5
00:00:13,800 --> 00:00:17,500
outage the left users unable to 
access links or images on the 

6
00:00:17,500 --> 00:00:21,100
platform and the implications of
the incident for the company and

7
00:00:21,100 --> 00:00:24,700
its stakeholders, the outage was
caused by a technical glitch 

8
00:00:24,800 --> 00:00:27,900
that brought down much of 
Twitter's internal tools, as 

9
00:00:27,900 --> 00:00:31,800
well as its public facing apis. 
It has raised concerns about the

10
00:00:31,800 --> 00:00:35,000
technical infrastructure and 
vulnerabilities on the platform 

11
00:00:35,200 --> 00:00:38,300
which have been compounded by 
recent layoffs and the shutdown 

12
00:00:38,300 --> 00:00:40,300
of free access to the Twitter 
API. 

13
00:00:40,700 --> 00:00:43,900
Now as we dive deeper into this,
incident will be exploring the 

14
00:00:43,900 --> 00:00:46,100
challenges and opportunities 
facing Twitter. 

15
00:00:46,300 --> 00:00:48,600
And we'll also discuss the 
potential Solutions and 

16
00:00:48,600 --> 00:00:52,100
Innovation that could help the 
company regain its footing and 

17
00:00:52,100 --> 00:00:55,700
re-establish itself as a 
reliable platform for real-time 

18
00:00:55,700 --> 00:00:58,200
communication. 
And social engagement Twitter's 

19
00:00:58,200 --> 00:01:00,300
website is breaking in novel, 
new ways. 

20
00:01:00,300 --> 00:01:03,100
And The company managed to 
recover from its latest outage 

21
00:01:03,100 --> 00:01:06,000
within a couple of hours, the 
story behind how it broke 

22
00:01:06,000 --> 00:01:07,900
suggest. 
There are likely to be similar 

23
00:01:07,900 --> 00:01:11,500
problems in the near future on 
Monday morning, Twitter, users 

24
00:01:11,500 --> 00:01:14,000
logged on to find a Thicket of 
connected issues. 

25
00:01:14,400 --> 00:01:16,300
Clicking on links with no longer
open them. 

26
00:01:16,600 --> 00:01:19,400
Instead users would see a 
mysterious error message. 

27
00:01:19,400 --> 00:01:23,700
Reporting that your current API 
plan does not include access to 

28
00:01:23,700 --> 00:01:26,500
this endpoint images, stop 
loading as well. 

29
00:01:26,900 --> 00:01:30,300
Other users reported that they 
could not access tweetdeck. 

30
00:01:30,400 --> 00:01:33,100
Check the Twitter own client for
professional users. 

31
00:01:33,500 --> 00:01:38,600
Now, everything went crazy KS 
took over the timeline is users 

32
00:01:38,600 --> 00:01:42,300
tweeted about the outage and 
often Illustrated their points 

33
00:01:42,300 --> 00:01:45,300
with images and memes that no 
one can see because they 

34
00:01:45,300 --> 00:01:48,800
wouldn't even load. 
Now, the Twitter API has been 

35
00:01:48,800 --> 00:01:52,700
shut down for outside sources 
for certain things and in a 

36
00:01:52,700 --> 00:01:56,100
tweet, the company offered the 
vaguest of explanations of what 

37
00:01:56,100 --> 00:01:59,400
was happening. 
During this time, they said some

38
00:01:59,400 --> 00:02:02,400
parts of Twitter May not be 
working as expected right now. 

39
00:02:02,900 --> 00:02:05,900
We made an internal change that 
had some unintended 

40
00:02:05,900 --> 00:02:09,300
consequences. 
Now, the changing question was 

41
00:02:09,300 --> 00:02:12,400
part of a project to shut down 
free access to the Twitter API 

42
00:02:12,700 --> 00:02:14,900
on February 1st. 
The company announced it will no

43
00:02:14,900 --> 00:02:18,700
longer support free access to 
its API which effectively ended 

44
00:02:18,700 --> 00:02:22,100
the existence of third-party 
clients and dramatically limit. 

45
00:02:22,100 --> 00:02:25,500
The ability of outside research 
has to study the network. 

46
00:02:25,500 --> 00:02:28,700
In a sign of just how deep Elon 
musk's cuts to the company of 

47
00:02:28,700 --> 00:02:31,800
been, only one site. 
Reliability Engineers, been 

48
00:02:31,800 --> 00:02:35,500
staffed on the project and on 
Monday, then engineer meeting 

49
00:02:35,500 --> 00:02:38,800
bad configuration change. 
The basically broke the Twitter 

50
00:02:38,800 --> 00:02:42,900
API now the change had cascading
consequences inside the company 

51
00:02:42,900 --> 00:02:46,300
bringing down much of Twitter's 
internal tools along with the 

52
00:02:46,300 --> 00:02:50,000
public facing apis on slack. 
Engineer's responded with 

53
00:02:50,000 --> 00:02:55,500
variations of crap and Twitter 
is down the entire thing as they

54
00:02:55,500 --> 00:03:00,900
scrambled to fix the problem. 
And we think Elon Musk was mad 

55
00:03:00,900 --> 00:03:05,700
about this, a small Epi change 
had massive, ramifications musk 

56
00:03:05,700 --> 00:03:08,700
tweeted later in the day after 
Twitter investor, Mark Anderson 

57
00:03:08,900 --> 00:03:11,300
posted a screenshot showing the 
company's API. 

58
00:03:11,300 --> 00:03:13,200
Failures were trending on the 
site. 

59
00:03:13,400 --> 00:03:16,400
The code stack is extremely 
brittle For No Good Reason. 

60
00:03:16,500 --> 00:03:20,600
Ilan said, will ultimately need 
a complete rewrite. 

61
00:03:21,100 --> 00:03:24,500
Now, they've had non-stop 
layoffs for the company with 

62
00:03:24,900 --> 00:03:28,500
only 100 or 500 50. 
Full-time Engineers now now, 

63
00:03:28,800 --> 00:03:31,300
Current employees are 
sympathetic to that view, which 

64
00:03:31,300 --> 00:03:34,200
places, at least part of the 
blame for Twitter's problems on 

65
00:03:34,200 --> 00:03:37,100
technical failures. 
That predate musk's ownership of

66
00:03:37,108 --> 00:03:39,900
the company. 
And the fail whale became an 

67
00:03:39,900 --> 00:03:42,400
icon of the old Twitter for a 
reason. 

68
00:03:42,800 --> 00:03:46,500
There's so much Tech debt for 
Twitter 1.0 if you make a change

69
00:03:46,500 --> 00:03:49,600
right now, everything breaks, 
that's what a current employee 

70
00:03:49,600 --> 00:03:51,600
said. 
Still, when musk took over the 

71
00:03:51,600 --> 00:03:54,700
company, you promise to 
dramatically improve the speed 

72
00:03:54,700 --> 00:03:58,100
and stability of the site and is
associate screen, the existing 

73
00:03:58,100 --> 00:04:01,100
staff for their Technical 
prowess, ultimately cutting 

74
00:04:01,100 --> 00:04:05,400
thousands of people working who 
were deemed not technical enough

75
00:04:05,400 --> 00:04:09,400
to succeed under musk's 
leadership but non-stop layoffs,

76
00:04:09,400 --> 00:04:11,800
have left the company with under
five hundred and fifty 

77
00:04:11,800 --> 00:04:15,100
full-time, engineer's, and just 
as former employees had 

78
00:04:15,100 --> 00:04:18,399
predicted from the start, these 
losses have made Twitter 

79
00:04:18,399 --> 00:04:21,200
increasingly vulnerable to 
catastrophic. 

80
00:04:21,200 --> 00:04:25,700
Outages Monday's, configuration 
chains was at least the six 

81
00:04:25,700 --> 00:04:28,600
high-profile service outage at 
Twitter. 

82
00:04:28,600 --> 00:04:32,300
The Year in January, Twitter, 
suffered an outage that lasted 

83
00:04:32,300 --> 00:04:35,400
for more than two hours and 
affected the site's mobile app, 

84
00:04:35,500 --> 00:04:37,700
as well as its web and API 
services. 

85
00:04:37,900 --> 00:04:41,300
In February Twitter, experience 
issues with posting tweets and 

86
00:04:41,300 --> 00:04:44,000
messages as well as 
notifications and likes. 

87
00:04:44,200 --> 00:04:48,100
And in March, a system 
irregularity, cause issues with 

88
00:04:48,100 --> 00:04:52,100
Twitter's ad platform in April, 
Twitter experience, a widespread

89
00:04:52,100 --> 00:04:55,400
outage that affected users, 
worldwide for over an hour. 

90
00:04:55,700 --> 00:04:59,000
And in July Twitter experience, 
an outage that caused it, Issues

91
00:04:59,000 --> 00:05:02,900
with notifications and finally 
the most out of recent outage on

92
00:05:02,900 --> 00:05:06,500
Monday and this type of outage 
has become so frequent that I 

93
00:05:06,500 --> 00:05:09,600
think we're all numb to. 
It said, one of the current 

94
00:05:09,600 --> 00:05:12,900
employees at Twitter and those 
are only the service outages. 

95
00:05:13,300 --> 00:05:16,200
There's other issues that are 
going on to such as the one that

96
00:05:16,200 --> 00:05:19,400
led musk's tweets to be made 
more visible on the timeline 

97
00:05:19,400 --> 00:05:22,700
than any other user which have 
also Royal the user base. 

98
00:05:22,700 --> 00:05:26,100
People got upset about that and 
in many ways, Monday's outage 

99
00:05:26,100 --> 00:05:28,600
represented, the culmination of 
musk's leadership at the 

100
00:05:28,800 --> 00:05:31,200
Japanese. 
So far the single-minded effort 

101
00:05:31,200 --> 00:05:33,800
to cut costs on his forty. 
Four billion dollar purchase. 

102
00:05:34,100 --> 00:05:36,900
He's been slashing the staff in 
a reducing Twitter's free 

103
00:05:36,900 --> 00:05:40,300
offerings and this paved a way 
for a single engineer to be 

104
00:05:40,300 --> 00:05:43,900
staffed on a huge project. 
One that is linked to several 

105
00:05:43,900 --> 00:05:47,400
critical interconnected systems 
that both users and employees 

106
00:05:47,400 --> 00:05:50,500
depend on and with few 
knowledgeable workers on hand to

107
00:05:50,500 --> 00:05:54,500
restore service, it took Twitter
all morning to fix the problem. 

108
00:05:54,700 --> 00:05:57,100
They were losing money during 
that time and this is what 

109
00:05:57,100 --> 00:06:00,400
happens when you fire 90. 
Percent of the company, one of 

110
00:06:00,400 --> 00:06:02,100
the current employees set as 
well. 

111
00:06:02,500 --> 00:06:05,700
Now, Twitter has technical debt 
to it's not just the recent 

112
00:06:05,700 --> 00:06:09,600
layoffs, the have left Twitter, 
vulnerable to these outages, the

113
00:06:09,600 --> 00:06:13,400
company's technical debt or the 
cost of maintaining outdated or 

114
00:06:13,400 --> 00:06:16,700
inefficient code. 
And hardware systems has been a 

115
00:06:16,700 --> 00:06:19,200
long-standing issue as one 
employee notes. 

116
00:06:19,500 --> 00:06:22,900
There is so much Tech debt from 
Twitter 1.0 that if you make a 

117
00:06:22,900 --> 00:06:26,600
change right now, everything 
breaks Twitter a struggle 

118
00:06:26,700 --> 00:06:28,400
struggle to keep up with its 
growth. 

119
00:06:28,800 --> 00:06:32,300
And the demand for its users 
resulting in a system that is 

120
00:06:32,308 --> 00:06:36,100
coupled together with Legacy and
spaghetti code, and outdated 

121
00:06:36,100 --> 00:06:38,800
technology, the company's 
internal systems and tools are 

122
00:06:38,800 --> 00:06:41,700
often unstable and unreliable as
well. 

123
00:06:42,000 --> 00:06:45,300
And there is a constant fear of 
things breaking down to make 

124
00:06:45,300 --> 00:06:47,600
matters, worse. 
Twitter has been slow to invest 

125
00:06:47,600 --> 00:06:51,500
in upgrading infrastructure and 
modernizing its code base. 

126
00:06:51,800 --> 00:06:54,400
The company has been criticized 
for prioritizing new features 

127
00:06:54,400 --> 00:06:57,100
and products over stability and 
reliability. 

128
00:06:57,500 --> 00:07:00,600
And, as a result Twitter's been 
Plagued by outages and technical

129
00:07:00,600 --> 00:07:03,700
issues for years in 2019. 
The company experienced a 

130
00:07:03,707 --> 00:07:07,300
massive outage less it for 
several hours, and affected 

131
00:07:07,300 --> 00:07:10,200
users around the world. 
The outage was caused by a 

132
00:07:10,200 --> 00:07:12,400
server. 
Configuration change that went 

133
00:07:12,400 --> 00:07:15,200
wrong according to the company 
and last year, Twitter suffered,

134
00:07:15,200 --> 00:07:18,300
several outages that cause 
issues with tweets, direct 

135
00:07:18,300 --> 00:07:22,100
messages and notifications. 
The company blamed the issues on

136
00:07:22,100 --> 00:07:25,400
an inadvertent change. 
We made to our internal systems.

137
00:07:25,900 --> 00:07:29,400
And now with the recent layoffs 
in the shutdown, The free access

138
00:07:29,400 --> 00:07:32,800
to the API. 
The company is facing serious. 

139
00:07:32,800 --> 00:07:36,600
Technical challenges again. 
Now Twitter said Ilan, said that

140
00:07:36,700 --> 00:07:40,300
the code stack is extremely 
brittle for no good reason and 

141
00:07:40,300 --> 00:07:43,500
will require a full rewrite. 
And we're not sure what 

142
00:07:43,500 --> 00:07:46,400
language, they're going to use 
for this new rewrite, but it 

143
00:07:46,400 --> 00:07:49,900
will be a modern rewrite not 
using the Legacy code will 

144
00:07:49,900 --> 00:07:51,400
probably rewrite it from 
scratch. 

145
00:07:51,700 --> 00:07:53,200
So, where does Twitter go from 
here? 

146
00:07:54,100 --> 00:07:55,700
Have a companies clearly facing 
seven. 

147
00:07:55,700 --> 00:07:58,900
Dictated to get challenges both 
in terms of his technical 

148
00:07:58,900 --> 00:08:02,100
infrastructure and its business 
model, must cost, cutting 

149
00:08:02,100 --> 00:08:04,700
measures have helped the 
company's bottom line, make more

150
00:08:04,700 --> 00:08:09,300
money, but they have also left 
Twitter, vulnerable to outages 

151
00:08:09,300 --> 00:08:10,700
and technical issues throughout 
the time. 

152
00:08:10,700 --> 00:08:12,800
He's been there. 
Now, at the same time, Twitter's

153
00:08:12,800 --> 00:08:16,100
facing intense competition, from
other social media platforms, 

154
00:08:16,500 --> 00:08:19,400
Tick-Tock Facebook. 
And the company's user base has 

155
00:08:19,400 --> 00:08:22,900
been stagnant for years in a 
struggle, to attract new users. 

156
00:08:22,900 --> 00:08:25,800
And An existing ones except 
Woody Allen. 

157
00:08:25,800 --> 00:08:29,400
Took the helm more users started
joining up to see what the whole

158
00:08:29,400 --> 00:08:32,600
parade was about, and what the 
drama was about over on Twitter.

159
00:08:32,900 --> 00:08:35,700
Now address these challenges 
Twitter's will need to make 

160
00:08:35,700 --> 00:08:39,500
significant investments in 
technical infrastructure and 

161
00:08:39,500 --> 00:08:43,200
modernize its code base. 
The company will also need to 

162
00:08:43,200 --> 00:08:46,400
develop new features and 
products that will attract users

163
00:08:46,400 --> 00:08:48,500
and keep them at gauge for 
future times. 

164
00:08:48,900 --> 00:08:50,800
Now. 
And perhaps, more importantly, 

165
00:08:51,100 --> 00:08:54,200
Twitter will need to re-evaluate
its business model in Find new 

166
00:08:54,200 --> 00:08:57,400
ways to generate money. 
The company is reliance and 

167
00:08:57,400 --> 00:09:00,800
advertising has proven to be a 
double-edged sword as it has 

168
00:09:00,800 --> 00:09:04,300
both fueled the company's growth
and left it vulnerable to 

169
00:09:04,300 --> 00:09:06,700
fluctuations in the advertising 
Market. 

170
00:09:06,700 --> 00:09:11,000
One possible solution is for 
Twitter to develop new revenue 

171
00:09:11,000 --> 00:09:13,200
streams such as paid 
subscriptions or premium 

172
00:09:13,200 --> 00:09:16,000
features for users. 
And the company is already begun

173
00:09:16,000 --> 00:09:17,600
experimenting with paid 
features. 

174
00:09:17,600 --> 00:09:21,400
The new check marks of course, 
exclusive content from different

175
00:09:21,400 --> 00:09:25,800
creators with a pay wall another
Possibility for Twitter is to 

176
00:09:25,800 --> 00:09:29,200
embrace its role as a platform 
for real-time communication to 

177
00:09:29,200 --> 00:09:32,200
develop new products and 
features that cater to that 

178
00:09:32,200 --> 00:09:34,600
role. 
For example, the company can 

179
00:09:34,600 --> 00:09:36,800
develop new tools for live 
streaming or real-time 

180
00:09:36,800 --> 00:09:40,100
collaboration, or could focus on
building a stronger Community 

181
00:09:40,300 --> 00:09:42,300
around certain topics or 
interests. 

182
00:09:42,700 --> 00:09:45,800
Ultimately the future of Twitter
will depend on its ability to 

183
00:09:45,800 --> 00:09:49,400
adapt to changing needs of its 
users in the broader social 

184
00:09:49,400 --> 00:09:52,300
media landscape and the company 
will need to strike a balance 

185
00:09:52,300 --> 00:09:56,600
between Innovation and Ability 
between growth and reliability. 

186
00:09:57,000 --> 00:09:59,400
And perhaps more importantly, 
Twitter will need to 

187
00:09:59,400 --> 00:10:03,100
re-establish itself as a 
platform that people trust and 

188
00:10:03,100 --> 00:10:06,500
rely on and is stable the 
company's recent outages and 

189
00:10:06,500 --> 00:10:10,100
technical issues have eroded 
user confidence in this platform

190
00:10:10,300 --> 00:10:15,000
and it will take a lot of time 
and effort to regain some of 

191
00:10:15,000 --> 00:10:18,100
those users trust as one current
employee notes. 

192
00:10:18,500 --> 00:10:21,100
There's so much potential here, 
Twitter could be an amazing 

193
00:10:21,100 --> 00:10:23,600
platform, but it needs to invest
in a sense. 

194
00:10:23,800 --> 00:10:27,700
Structure and its people if it's
going to realize its potential. 

195
00:10:28,000 --> 00:10:30,600
So in the end, the fate of 
Twitter will be decided by the 

196
00:10:30,600 --> 00:10:33,800
company's ability to overcome 
its technical debt. 

197
00:10:34,200 --> 00:10:37,600
Adapt to changing needs of its 
users and regain the trust of 

198
00:10:37,600 --> 00:10:40,500
its Community. 
It's a tall order, but a Twitter

199
00:10:40,500 --> 00:10:42,800
can rise to the challenge. 
It has the potential to be a 

200
00:10:42,800 --> 00:10:46,200
powerful force for real-time 
communication and social 

201
00:10:46,200 --> 00:10:52,300
engagement in the years to come.
Thank you for tuning in to the 

202
00:10:52,300 --> 00:10:55,800
Elon Musk podcast brought to you
by stage. 0 Productions, and 

203
00:10:55,800 --> 00:10:58,900
hosted by me will Walden. 
We hope you've enjoyed today's 

204
00:10:58,900 --> 00:11:01,100
episode and gained some valuable
insights. 

205
00:11:01,300 --> 00:11:04,100
If you haven't already, be sure 
to subscribe on your favorite 

206
00:11:04,100 --> 00:11:08,600
podcast app so you never miss an
episode and for exclusive ad 

207
00:11:08,600 --> 00:11:11,100
free content. 
Check out our patreon at 

208
00:11:11,100 --> 00:11:15,600
patreon.com slash stage Zero. 
Thanks for listening and we'll 

209
00:11:15,600 --> 00:11:16,400
see you next time.