1
00:00:00,000 --> 00:00:01,920
All right, ready to go deep on something

2
00:00:01,920 --> 00:00:03,520
you might not expect.

3
00:00:03,520 --> 00:00:06,240
A Drupal bug.

4
00:00:06,240 --> 00:00:07,080
A what?

5
00:00:07,080 --> 00:00:07,900
Yeah, you heard that right.

6
00:00:07,900 --> 00:00:08,740
Drupal.

7
00:00:08,740 --> 00:00:09,580
Oh, okay.

8
00:00:09,580 --> 00:00:10,600
I know, I know, you're thinking website stuff.

9
00:00:10,600 --> 00:00:11,440
Well, yeah.

10
00:00:11,440 --> 00:00:13,560
But hold on, this isn't just some random glitch.

11
00:00:13,560 --> 00:00:14,400
Okay.

12
00:00:14,400 --> 00:00:16,560
This bug, this takes us down a rabbit hole,

13
00:00:16,560 --> 00:00:19,920
like how software gets made, how we experience tech,

14
00:00:19,920 --> 00:00:22,280
even security, the whole shebang.

15
00:00:22,280 --> 00:00:24,240
You're not wrong, it does sound kinda niche

16
00:00:24,240 --> 00:00:25,320
when you put it like that.

17
00:00:25,320 --> 00:00:29,080
Niche, maybe, but important, definitely.

18
00:00:29,080 --> 00:00:31,400
For sure, anyone using the internet, which is.

19
00:00:31,400 --> 00:00:32,280
Basically everyone.

20
00:00:32,280 --> 00:00:33,120
Pretty much.

21
00:00:33,120 --> 00:00:34,280
And that's what we do here, right?

22
00:00:34,280 --> 00:00:37,160
Shine a light on the systems we use every single day

23
00:00:37,160 --> 00:00:39,520
and see how even a tiny bug can spiral.

24
00:00:39,520 --> 00:00:40,440
Absolutely.

25
00:00:40,440 --> 00:00:41,680
So what is this bug?

26
00:00:41,680 --> 00:00:43,000
Picture this.

27
00:00:43,000 --> 00:00:43,880
You're on a website, right?

28
00:00:43,880 --> 00:00:44,720
Okay, got it.

29
00:00:44,720 --> 00:00:47,720
And you can see this unpublished page,

30
00:00:47,720 --> 00:00:50,120
you have permission and all.

31
00:00:50,120 --> 00:00:50,960
Makes sense.

32
00:00:50,960 --> 00:00:53,360
But here's the kicker, you can't link to it.

33
00:00:53,360 --> 00:00:56,800
You can see it, but you can't reference it.

34
00:00:56,800 --> 00:00:58,880
It's like some weird information paradox.

35
00:00:58,880 --> 00:01:00,240
You're right, that is weird.

36
00:01:00,240 --> 00:01:02,660
Logically, if you can see something,

37
00:01:02,660 --> 00:01:05,000
shouldn't you be able to link it?

38
00:01:05,000 --> 00:01:06,280
I can see why people are scratching

39
00:01:06,280 --> 00:01:07,200
their heads over this one.

40
00:01:07,200 --> 00:01:08,800
Oh, people are definitely scratching their heads.

41
00:01:08,800 --> 00:01:10,840
Trust me, it's causing some serious frustration.

42
00:01:10,840 --> 00:01:11,680
I bet.

43
00:01:11,680 --> 00:01:12,720
Think about it, you're an editor,

44
00:01:12,720 --> 00:01:14,440
you've got articles all over the place,

45
00:01:14,440 --> 00:01:16,640
some finished, some still drafts.

46
00:01:16,640 --> 00:01:17,800
Right, gotta have drafts.

47
00:01:17,800 --> 00:01:19,280
You wanna connect them, make a nice flow,

48
00:01:19,280 --> 00:01:22,600
but bam, this book throws a wrench in the works.

49
00:01:22,600 --> 00:01:23,440
Ouch.

50
00:01:23,440 --> 00:01:26,320
You can see those drafts, but linking them.

51
00:01:26,320 --> 00:01:27,920
Nope, not a chance.

52
00:01:27,920 --> 00:01:29,320
That just sounds so frustrating.

53
00:01:29,320 --> 00:01:31,680
And from a bigger picture perspective,

54
00:01:31,680 --> 00:01:33,880
doesn't this kind of go against

55
00:01:33,880 --> 00:01:35,800
how information should be organized?

56
00:01:35,800 --> 00:01:37,560
Like, if you can access it,

57
00:01:37,560 --> 00:01:39,000
you should be able to link it, right?

58
00:01:39,000 --> 00:01:40,080
100%.

59
00:01:40,080 --> 00:01:42,960
And when systems act in ways we don't expect,

60
00:01:42,960 --> 00:01:44,920
it just creates friction.

61
00:01:44,920 --> 00:01:47,360
People get frustrated, they lose trust,

62
00:01:47,360 --> 00:01:48,600
and then they're less likely

63
00:01:48,600 --> 00:01:49,960
to use the platform effectively.

64
00:01:49,960 --> 00:01:50,800
Yeah, for sure.

65
00:01:50,800 --> 00:01:52,680
It's all about usability at the end of the day.

66
00:01:52,680 --> 00:01:55,460
And we're not talking about a minor inconvenience here.

67
00:01:55,460 --> 00:01:57,800
I mean, some users are patching their own systems.

68
00:01:57,800 --> 00:01:58,640
Yeah.

69
00:01:58,640 --> 00:02:01,100
Every single update.

70
00:02:01,100 --> 00:02:03,520
Just to get around this thing.

71
00:02:03,520 --> 00:02:06,600
Whoa, that's dedication.

72
00:02:06,600 --> 00:02:07,800
Or maybe desperation.

73
00:02:07,800 --> 00:02:09,620
Probably a bit of both.

74
00:02:09,620 --> 00:02:12,760
It's a huge time sink, all because of this one little bug.

75
00:02:12,760 --> 00:02:14,540
Wow, and I hate to say it,

76
00:02:14,540 --> 00:02:17,120
but it might be even worse than just being annoying.

77
00:02:17,120 --> 00:02:19,160
Think about the security implication.

78
00:02:19,160 --> 00:02:20,680
Oh, right, you mentioned that earlier.

79
00:02:20,680 --> 00:02:21,820
What are we talking about here?

80
00:02:21,820 --> 00:02:23,400
Well, if there's a way to reference

81
00:02:23,400 --> 00:02:24,920
that unpublished content,

82
00:02:24,920 --> 00:02:27,000
even if it's not supposed to be possible.

83
00:02:27,000 --> 00:02:28,160
Someone could exploit that.

84
00:02:28,160 --> 00:02:29,960
Exactly, it's like leaving a back door

85
00:02:29,960 --> 00:02:31,680
wide open to your website.

86
00:02:31,680 --> 00:02:33,920
Information that shouldn't be public suddenly is.

87
00:02:33,920 --> 00:02:35,960
Okay, so now we're talking workflow chaos

88
00:02:35,960 --> 00:02:37,600
and security breaches.

89
00:02:37,600 --> 00:02:39,400
You'd think someone would have fixed this by now, right?

90
00:02:39,400 --> 00:02:40,840
You'd think so, wouldn't you?

91
00:02:40,840 --> 00:02:43,200
But the thing is, software is rarely that simple.

92
00:02:43,200 --> 00:02:44,120
What's the catch?

93
00:02:44,120 --> 00:02:46,080
Backward compatibility.

94
00:02:46,080 --> 00:02:49,000
Any fix, any solution can't break the websites

95
00:02:49,000 --> 00:02:51,200
that rely on the old way of doing things.

96
00:02:51,200 --> 00:02:53,440
Ah, so it's like walking a tightrope.

97
00:02:53,440 --> 00:02:54,960
Basically, you fix it for one group,

98
00:02:54,960 --> 00:02:56,280
you might break it for another.

99
00:02:56,280 --> 00:02:58,320
Talk about a developer's nightmare.

100
00:02:58,320 --> 00:03:02,520
So how do you even begin to tackle a problem like that?

101
00:03:02,520 --> 00:03:04,760
It really is a tough nut to crack, isn't it?

102
00:03:04,760 --> 00:03:08,620
But hey, the Drupal community, they're a resourceful bunch.

103
00:03:08,620 --> 00:03:10,080
There are ideas out there.

104
00:03:10,080 --> 00:03:11,000
Oh, I bet.

105
00:03:11,000 --> 00:03:13,640
What are we talking, like crazy workarounds

106
00:03:13,640 --> 00:03:17,400
or some elegant solution just waiting to be discovered?

107
00:03:17,400 --> 00:03:19,440
Hopefully a little more elegant than that.

108
00:03:19,440 --> 00:03:22,160
Some people, they're all about getting their hands dirty

109
00:03:22,160 --> 00:03:25,760
with the code, you know, make those precise targeted fixes.

110
00:03:25,760 --> 00:03:28,420
So it's like performing surgery on the software,

111
00:03:28,420 --> 00:03:31,560
trying to remove the bug without damaging anything else.

112
00:03:31,560 --> 00:03:32,640
That's a good way to put it.

113
00:03:32,640 --> 00:03:35,360
But remember that backward compatibility thing?

114
00:03:35,360 --> 00:03:37,640
Sometimes even the most precise fix

115
00:03:37,640 --> 00:03:40,040
can cause unexpected problems down the line.

116
00:03:40,040 --> 00:03:41,480
Right, like a domino effect.

117
00:03:41,480 --> 00:03:44,120
You fix one thing and it ends up breaking something else

118
00:03:44,120 --> 00:03:44,940
for someone else.

119
00:03:44,940 --> 00:03:47,340
Exactly, and that's why some folks are pushing

120
00:03:47,340 --> 00:03:49,520
for a different approach, something a bit more,

121
00:03:49,520 --> 00:03:50,440
well, universal.

122
00:03:50,440 --> 00:03:52,020
Okay, I'm intrigued.

123
00:03:52,020 --> 00:03:54,400
What kind of universal solution are we talking about?

124
00:03:54,400 --> 00:03:58,280
Imagine this, a simple little checkbox in the settings,

125
00:03:58,280 --> 00:03:59,600
right there for everyone to see,

126
00:03:59,600 --> 00:04:03,680
something like allow referencing of unpublished content.

127
00:04:03,680 --> 00:04:05,040
Oh, I see where you're going with this.

128
00:04:05,040 --> 00:04:07,760
Give people the choice, enable the function if they want it,

129
00:04:07,760 --> 00:04:09,400
leave it off if they don't, simple.

130
00:04:09,400 --> 00:04:12,420
You got it, but, and there's always a but, isn't there?

131
00:04:12,420 --> 00:04:15,000
This approach comes with its own set of challenges.

132
00:04:15,000 --> 00:04:18,440
It's that age-old trade-off control versus complexity.

133
00:04:18,440 --> 00:04:19,560
Okay, break that down for me.

134
00:04:19,560 --> 00:04:21,480
What makes a checkbox so complicated?

135
00:04:21,480 --> 00:04:25,740
Well, on the one hand, it gives website administrators more control.

136
00:04:25,740 --> 00:04:28,840
They get to decide if they want this functionality enabled or not.

137
00:04:28,840 --> 00:04:33,480
But on the other hand, it also introduces another decision they need to make.

138
00:04:33,480 --> 00:04:36,440
And more decisions usually mean more room for error.

139
00:04:36,440 --> 00:04:37,600
That's it, exactly.

140
00:04:37,600 --> 00:04:41,360
Now, suddenly they need to understand all the ins and outs of this checkbox.

141
00:04:41,360 --> 00:04:42,640
What happens if you check it?

142
00:04:42,640 --> 00:04:43,680
What breaks if you don't?

143
00:04:43,680 --> 00:04:48,520
It's a lot to put on someone's plate, especially if they're not a tech expert.

144
00:04:48,520 --> 00:04:54,600
It's a slippery slope from a simple checkbox to a full blown configuration nightmare.

145
00:04:54,600 --> 00:04:56,800
And it highlights something really important, doesn't it?

146
00:04:56,800 --> 00:05:00,320
This isn't just a technical problem with a technical solution.

147
00:05:00,320 --> 00:05:04,560
It's about finding that sweet spot between functionality,

148
00:05:04,560 --> 00:05:08,200
security, and making things easy for people to use.

149
00:05:08,200 --> 00:05:09,840
Couldn't have said it better myself.

150
00:05:09,840 --> 00:05:12,520
And speaking of making things easy to use,

151
00:05:12,520 --> 00:05:15,480
there's another angle to this whole thing we haven't even touched on yet.

152
00:05:15,480 --> 00:05:16,280
Do tell.

153
00:05:16,280 --> 00:05:19,240
So let's imagine for a second that the developers,

154
00:05:19,240 --> 00:05:22,600
they wave their magic wands and completely fix this bug.

155
00:05:22,600 --> 00:05:25,840
Everyone can reference unpublished content without a hitch.

156
00:05:25,840 --> 00:05:27,120
Problem solved, right.

157
00:05:27,120 --> 00:05:28,920
Sounds too good to be true.

158
00:05:28,920 --> 00:05:30,560
What's the catch this time?

159
00:05:30,560 --> 00:05:32,560
Even if they fix the technical side of things,

160
00:05:32,560 --> 00:05:34,960
there's still the human factor to consider.

161
00:05:34,960 --> 00:05:37,040
Right now, visually, there's no way to tell

162
00:05:37,040 --> 00:05:39,440
the difference between a published article and a draft

163
00:05:39,440 --> 00:05:41,480
when you're looking at a list of potential links.

164
00:05:41,480 --> 00:05:42,920
Oh, I see where you're going with this.

165
00:05:42,920 --> 00:05:45,560
You could accidentally link to something that's not ready for prime time.

166
00:05:45,560 --> 00:05:46,600
Not exactly ideal.

167
00:05:46,600 --> 00:05:47,960
That's putting it mildly.

168
00:05:47,960 --> 00:05:52,600
It's like accidentally sending out a draft email to your entire contact list.

169
00:05:52,600 --> 00:05:54,440
Oof, I've been there.

170
00:05:54,440 --> 00:05:55,160
Not fun.

171
00:05:55,160 --> 00:06:00,320
And it goes to show how important a clear and intuitive user interface really is.

172
00:06:00,320 --> 00:06:02,200
It's not just about making things look pretty.

173
00:06:02,200 --> 00:06:04,520
It's about preventing mistakes and making sure

174
00:06:04,520 --> 00:06:08,160
people can actually use the software in the way it was intended.

175
00:06:08,160 --> 00:06:11,120
This is what blows my mind every time we do one of these deep dives.

176
00:06:11,120 --> 00:06:12,880
We started with this Drupal bug, right?

177
00:06:12,880 --> 00:06:14,440
Something so specific.

178
00:06:14,440 --> 00:06:17,600
But now we're talking about information architecture,

179
00:06:17,600 --> 00:06:19,880
user experience design, the whole nine yards.

180
00:06:19,880 --> 00:06:20,840
It's all connected.

181
00:06:20,840 --> 00:06:25,000
And it just goes to show you sometimes those seemingly small issues,

182
00:06:25,000 --> 00:06:27,200
they can open up a whole can of worms.

183
00:06:27,200 --> 00:06:29,040
Worms that need to be explored.

184
00:06:29,040 --> 00:06:31,000
But before we get too far down the rabbit hole,

185
00:06:31,000 --> 00:06:33,520
let's pause for a second and think about our listeners.

186
00:06:33,520 --> 00:06:37,240
We've thrown a lot of information at them, some pretty technical stuff too.

187
00:06:37,240 --> 00:06:39,920
So let's bring it back down to Earth for a moment.

188
00:06:39,920 --> 00:06:44,120
What does all this mean for someone who's not a coder or a designer?

189
00:06:44,120 --> 00:06:45,880
What's the takeaway message here?

190
00:06:45,880 --> 00:06:47,960
That's the million dollar question, isn't it?

191
00:06:47,960 --> 00:06:51,840
At the end of the day, I think the big takeaway here is this.

192
00:06:51,840 --> 00:06:55,160
We interact with digital systems all the time, right?

193
00:06:55,160 --> 00:06:57,880
Our phones, our computers, even our cars.

194
00:06:57,880 --> 00:07:00,320
And we just kind of assume they'll work the way they're supposed to.

195
00:07:00,320 --> 00:07:01,920
But they don't always work, do they?

196
00:07:01,920 --> 00:07:03,480
Oh, absolutely not.

197
00:07:03,480 --> 00:07:05,720
And this Drupal thing, it's a great example.

198
00:07:05,720 --> 00:07:08,120
It might seem like a small issue on the surface,

199
00:07:08,120 --> 00:07:12,160
but it shows just how complex these systems really are,

200
00:07:12,160 --> 00:07:13,400
even when we don't see it.

201
00:07:13,400 --> 00:07:13,920
Right.

202
00:07:13,920 --> 00:07:17,120
We just take it for granted, click a button, expect a result.

203
00:07:17,120 --> 00:07:19,160
But behind that click, there's a whole lot

204
00:07:19,160 --> 00:07:22,160
of code, a whole lot of decisions that went into making that happen,

205
00:07:22,160 --> 00:07:24,400
or in this case, not happen.

206
00:07:24,400 --> 00:07:26,920
So where do things stand now?

207
00:07:26,920 --> 00:07:31,040
Has someone, anyone, found the holy grail solution to this bug?

208
00:07:31,040 --> 00:07:34,160
Well, not quite a holy grail, but they are working on it.

209
00:07:34,160 --> 00:07:36,120
The Drupal community is on the case.

210
00:07:36,120 --> 00:07:37,680
That's something, at least.

211
00:07:37,680 --> 00:07:40,400
So it's not just going to be ignored, brushed under the rug.

212
00:07:40,400 --> 00:07:41,200
No, not at all.

213
00:07:41,200 --> 00:07:44,360
And that's one of the things I find so fascinating about this case.

214
00:07:44,360 --> 00:07:48,080
It really highlights the power of open source software.

215
00:07:48,080 --> 00:07:51,600
Here, you have a community of developers, users, everyone

216
00:07:51,600 --> 00:07:53,760
coming together to try to solve a problem.

217
00:07:53,760 --> 00:07:55,760
I'm like global brainstorming session.

218
00:07:55,760 --> 00:07:56,440
Yeah.

219
00:07:56,440 --> 00:07:58,360
And all because of this one little bug.

220
00:07:58,360 --> 00:07:59,320
You've got it.

221
00:07:59,320 --> 00:08:02,400
Though I think little might be a bit of an understatement by now.

222
00:08:02,400 --> 00:08:05,600
The more we dig into this, the more we realize it's not so little,

223
00:08:05,600 --> 00:08:06,480
after all, is it?

224
00:08:06,480 --> 00:08:07,000
Not at all.

225
00:08:07,000 --> 00:08:09,040
It's a whole rabbit hole of complexity.

226
00:08:09,040 --> 00:08:10,360
But isn't that always the way?

227
00:08:10,360 --> 00:08:13,000
It's like the more you learn, the more you realize you don't know.

228
00:08:13,000 --> 00:08:13,680
Truth.

229
00:08:13,680 --> 00:08:14,440
But that's OK.

230
00:08:14,440 --> 00:08:15,600
That's where the excitement is.

231
00:08:15,600 --> 00:08:15,960
Right.

232
00:08:15,960 --> 00:08:17,240
It keeps things interesting.

233
00:08:17,240 --> 00:08:21,480
So for our listeners who are still with us, still absorbing all of this,

234
00:08:21,480 --> 00:08:24,520
what's the one thing you want them to remember?

235
00:08:24,520 --> 00:08:26,560
The call to action, if you will.

236
00:08:26,560 --> 00:08:27,080
Let's see.

237
00:08:27,080 --> 00:08:29,880
I think the most important thing is this.

238
00:08:29,880 --> 00:08:32,120
The next time you run into something online,

239
00:08:32,120 --> 00:08:35,360
maybe it's a weird bug, a frustrating design, anything

240
00:08:35,360 --> 00:08:36,960
that just doesn't seem quite right.

241
00:08:36,960 --> 00:08:38,160
Don't just accept it.

242
00:08:38,160 --> 00:08:39,120
Exactly.

243
00:08:39,120 --> 00:08:40,840
Don't just shrug and move on.

244
00:08:40,840 --> 00:08:41,600
Get curious.

245
00:08:41,600 --> 00:08:44,080
Ask yourself, why is this like this?

246
00:08:44,080 --> 00:08:46,080
What went into making it this way?

247
00:08:46,080 --> 00:08:47,080
Because you never know.

248
00:08:47,080 --> 00:08:48,800
You might just uncover a whole world

249
00:08:48,800 --> 00:08:51,080
of fascinating complexity hiding right there

250
00:08:51,080 --> 00:08:52,040
beneath the surface.

251
00:08:52,040 --> 00:08:54,080
Or maybe, just maybe, you'll come up

252
00:08:54,080 --> 00:08:56,600
with a brilliant solution that no one else has thought of.

253
00:08:56,600 --> 00:08:57,720
That's the dream, isn't it?

254
00:08:57,720 --> 00:09:01,080
To go from passive user to active innovator.

255
00:09:01,080 --> 00:09:03,080
And on that note, I think we've explored just

256
00:09:03,080 --> 00:09:05,920
about every nook and cranny of this Drupal bug.

257
00:09:05,920 --> 00:09:09,240
We've talked about information architecture, user experience,

258
00:09:09,240 --> 00:09:11,400
even a little bit of philosophy along the way.

259
00:09:11,400 --> 00:09:13,920
And a good dose of cautionary tale, too.

260
00:09:13,920 --> 00:09:15,200
Can't forget that.

261
00:09:15,200 --> 00:09:18,560
So until next time, keep exploring, keep questioning,

262
00:09:18,560 --> 00:09:20,960
and keep diving deep into the fascinating world