1
00:00:00,080 --> 00:00:02,560
Speaker 1: Okay, So, like, have you ever thought about, like what

2
00:00:02,680 --> 00:00:06,919
if there was you know, a secret code hidden inside

3
00:00:06,919 --> 00:00:08,359
a book, a book you thought you.

4
00:00:08,400 --> 00:00:10,480
Speaker 2: Knew, uh, like a hidden language or something.

5
00:00:10,519 --> 00:00:13,640
Speaker 1: Yeah, exactly, a language that get this, some people believe

6
00:00:13,679 --> 00:00:17,519
has been like whispering about the future for thousands of years.

7
00:00:17,559 --> 00:00:19,440
Speaker 2: Oh that's kind of freaking you know, right.

8
00:00:19,719 --> 00:00:22,640
Speaker 1: And we're not talking metaphors or you know, vague prophecies here.

9
00:00:22,679 --> 00:00:26,760
It's like straight up literal messages encoded in the text,

10
00:00:26,920 --> 00:00:31,920
like information deliberately planted there waiting to be unlocked. So

11
00:00:32,200 --> 00:00:35,159
like a code then, exactly, and not just any book.

12
00:00:35,159 --> 00:00:38,399
We're talking about the Bible, specifically the Old Testament and

13
00:00:38,520 --> 00:00:41,920
these alleged secret messages. While they're called Bible codes, we're

14
00:00:41,920 --> 00:00:43,799
doing a deep dive on this today.

15
00:00:44,159 --> 00:00:48,119
Speaker 2: Interesting, So we're ditching symbolism and deep interpretation and jumping

16
00:00:48,159 --> 00:00:51,200
straight into like deciphering literal messages.

17
00:00:51,479 --> 00:00:54,320
Speaker 1: You got it. It's a totally different way of looking

18
00:00:54,399 --> 00:00:57,119
at these ancient texts. I mean, for centuries people have

19
00:00:57,159 --> 00:01:00,799
been trying to understand the Bible through like context symbolism,

20
00:01:00,880 --> 00:01:04,000
the historical background, all that jazz. But the Bible codes

21
00:01:04,319 --> 00:01:07,200
they suggest there's a whole other layer underneath, like a

22
00:01:07,280 --> 00:01:11,879
deliberate encoding of information hidden within the actual words themselves.

23
00:01:12,000 --> 00:01:14,560
Speaker 2: And we're talking about the Hebrew text, right, the Old Testament,

24
00:01:14,599 --> 00:01:18,879
those twenty four books written over like thousands of years.

25
00:01:18,640 --> 00:01:22,120
Speaker 1: That's right. And here's the thing. Those ancient scribes, the

26
00:01:22,120 --> 00:01:25,599
guys who copied those texts, they were like obsessed with accuracy.

27
00:01:26,159 --> 00:01:28,959
They believed that even a single letter out of place

28
00:01:29,040 --> 00:01:32,920
could make the whole scroll like religiously unusable.

29
00:01:32,519 --> 00:01:34,120
Speaker 2: Right right, I mean you have to think about it,

30
00:01:34,120 --> 00:01:37,439
that kind of meticulousness, that level of precision. It wasn't

31
00:01:37,519 --> 00:01:40,159
just about preserving the words. It's like they were like

32
00:01:40,920 --> 00:01:45,280
safeguarding something, maybe even unintentionally, for future generations exactly.

33
00:01:45,439 --> 00:01:48,719
Speaker 1: And that leads to this crazy idea. What if that

34
00:01:48,840 --> 00:01:52,879
crazy level of accuracy was like totally necessary to preserve

35
00:01:52,920 --> 00:01:55,400
some kind of hidden code within the text.

36
00:01:55,120 --> 00:01:58,319
Speaker 2: Itself, because even a smell change, a single letter difference,

37
00:01:58,519 --> 00:02:02,799
could throw the whole thing off gramble the code. That's wild, totally.

38
00:02:03,079 --> 00:02:05,719
Speaker 1: And you know, this whole concept of hidden messages, it's

39
00:02:05,760 --> 00:02:08,840
not some new age digital thing. It actually goes way back.

40
00:02:08,919 --> 00:02:10,319
I mean way way back.

41
00:02:10,080 --> 00:02:11,759
Speaker 2: Really, Like how far back are we talking?

42
00:02:11,960 --> 00:02:15,879
Speaker 1: Like thirteenth century, there was this rabbi Bacia ben Asher.

43
00:02:15,960 --> 00:02:19,439
He lived way before computers, obviously, and he supposedly found

44
00:02:19,479 --> 00:02:21,599
something remarkable in the Book of Genesis.

45
00:02:21,719 --> 00:02:22,960
Speaker 2: Oh what did he find?

46
00:02:23,039 --> 00:02:26,039
Speaker 1: Okay? So he used this like early version of what

47
00:02:26,080 --> 00:02:28,840
we now call a skip code. Basically, you pick a letter,

48
00:02:28,879 --> 00:02:31,240
skip a set number of letters, pick another, and keep going.

49
00:02:31,240 --> 00:02:33,360
You know, kind of like connect the dots, but with letters.

50
00:02:33,439 --> 00:02:35,560
Speaker 2: Okay, I get it. So what did he find with

51
00:02:35,599 --> 00:02:36,479
this skip code thing?

52
00:02:36,680 --> 00:02:39,879
Speaker 1: Well, reportedly he found a reference to the creation of

53
00:02:39,919 --> 00:02:42,879
the moon. And not just that, it also like specified

54
00:02:42,879 --> 00:02:45,879
the exact length of the lunar month. Get this, twenty

55
00:02:45,960 --> 00:02:47,680
nine point five three days.

56
00:02:47,800 --> 00:02:49,080
Speaker 2: Wow, that's pretty specific.

57
00:02:49,240 --> 00:02:52,719
Speaker 1: And here's the kicker. NASA, with all its fancy technology,

58
00:02:53,199 --> 00:02:58,159
didn't confirm that precise figure until like nineteen ninety six.

59
00:02:58,560 --> 00:03:01,680
Speaker 2: So this rabbi back in the third teen hundreds figured

60
00:03:01,680 --> 00:03:05,280
out something that took NASA like centuries to confirm.

61
00:03:05,599 --> 00:03:08,240
Speaker 1: You got it. It's almost like he was tapping into

62
00:03:08,240 --> 00:03:10,240
some kind of hidden knowledge, right.

63
00:03:10,159 --> 00:03:13,439
Speaker 2: That's that's pretty mind blowing. Imagine trying to do that manually,

64
00:03:13,759 --> 00:03:17,120
I mean, using skip codes to search through the entire

65
00:03:17,120 --> 00:03:18,240
Old Testament by hand.

66
00:03:18,319 --> 00:03:21,520
Speaker 1: Oh, I know, it would be like insanely tedious. You'd

67
00:03:21,520 --> 00:03:25,159
probably do cross eyed before finding anything meaningful. It would

68
00:03:25,159 --> 00:03:27,680
be like finding a needle in a haystack, but the

69
00:03:27,719 --> 00:03:30,080
haystack is made of letters, and the needle is also

70
00:03:30,120 --> 00:03:30,840
made of letters.

71
00:03:30,919 --> 00:03:33,039
Speaker 2: It's like you'd need a lifetime to do it. But

72
00:03:33,080 --> 00:03:35,960
then boom, computers come along and change everything.

73
00:03:36,080 --> 00:03:38,520
Speaker 1: It's a total game changer, right. Suddenly you don't need

74
00:03:38,599 --> 00:03:42,400
years and years of painstaking manual work. You can run

75
00:03:42,520 --> 00:03:45,439
complex calculations in like seconds.

76
00:03:45,599 --> 00:03:50,039
Speaker 2: Yeah, computers basically took this like super niche almost impossible

77
00:03:50,080 --> 00:03:53,919
task and made it well possible. It's like, now you

78
00:03:53,919 --> 00:03:56,680
can search for these Bible codes systematically at a scale

79
00:03:56,719 --> 00:03:58,159
that was just unimaginable before.

80
00:03:58,479 --> 00:04:01,800
Speaker 1: Right, And it wasn't just about like finding words hidden

81
00:04:01,840 --> 00:04:05,080
in straight lines anymore. With computers, you could take those

82
00:04:05,159 --> 00:04:07,319
long strings of letters you get from the skip codes

83
00:04:07,360 --> 00:04:09,840
and you could arrange them into grids. Think of it

84
00:04:09,919 --> 00:04:13,280
like giant crossword puzzles filled with letters from the Bible.

85
00:04:13,560 --> 00:04:15,719
Speaker 2: Oh I see. So, Like instead of just looking for

86
00:04:15,759 --> 00:04:19,519
words in a straight line, now you can search horizontally,

87
00:04:19,959 --> 00:04:23,360
vertically diagonally, like a word search that opens up a

88
00:04:23,399 --> 00:04:25,199
whole lot of possibilities it does.

89
00:04:25,600 --> 00:04:28,480
Speaker 1: And that brings us to this pivotal experiment that happened

90
00:04:28,480 --> 00:04:32,120
back in nineteen eighty five. It's called the Great Rabbis Experiment.

91
00:04:32,279 --> 00:04:32,920
Have you heard of it?

92
00:04:33,040 --> 00:04:34,839
Speaker 2: Yeah, I've come across it in my research. It was

93
00:04:34,879 --> 00:04:37,199
a pretty big deal, right, because it tried to go

94
00:04:37,319 --> 00:04:41,360
beyond just anecdotal evidence and like apply a statistical framework

95
00:04:41,360 --> 00:04:42,199
to these Bible.

96
00:04:41,920 --> 00:04:44,079
Speaker 1: Codes exactly Like they wanted to see if there was

97
00:04:44,160 --> 00:04:47,800
any real provable evidence that these codes existed. And their

98
00:04:47,839 --> 00:04:51,199
focus was on, get this, the names of famous rabbis.

99
00:04:51,680 --> 00:04:55,879
Speaker 2: So these researchers Eleah who Rips, darn zdem and jol Rosenberg.

100
00:04:56,079 --> 00:04:58,000
They basically wanted to find out if the names of

101
00:04:58,040 --> 00:05:01,120
these prominent rabbis were like encoded within the.

102
00:05:01,040 --> 00:05:04,160
Speaker 1: Old Testament, right, and not just random names. They used

103
00:05:04,160 --> 00:05:08,519
a specific list of thirty four super influential rabbis from

104
00:05:08,560 --> 00:05:11,439
this book called the Encyclopedia of Great Men in Israel.

105
00:05:11,839 --> 00:05:15,240
They took these names, programmed them into a computer, and

106
00:05:15,319 --> 00:05:17,959
told the computer to search for them in the biblical text.

107
00:05:18,000 --> 00:05:20,279
Speaker 2: But they didn't stop there, right, They also looked for

108
00:05:20,319 --> 00:05:22,319
the rabbis as birth and death dates, yep.

109
00:05:22,519 --> 00:05:25,279
Speaker 1: That was like the key to the whole experiment. The

110
00:05:25,399 --> 00:05:28,360
idea was if they could find the names and those

111
00:05:28,399 --> 00:05:32,160
specific dates intersecting within these coded grids, the chances of

112
00:05:32,199 --> 00:05:35,439
that happening randomly would be like astronomically small.

113
00:05:35,519 --> 00:05:38,040
Speaker 2: It's like finding your name in a crossword puzzle and

114
00:05:38,040 --> 00:05:40,839
then having your birth date and death date also spelled

115
00:05:40,839 --> 00:05:43,040
out in the same puzzle, all crossing your name. That

116
00:05:43,079 --> 00:05:44,920
would be pretty freaky totally.

117
00:05:45,000 --> 00:05:48,240
Speaker 1: And well, the results they reported were well, pretty mind blowing.

118
00:05:48,319 --> 00:05:50,800
They said they found all thirty four names.

119
00:05:50,839 --> 00:05:52,720
Speaker 2: Wow. And what about the dates?

120
00:05:52,959 --> 00:05:55,720
Speaker 1: They claimed that the birth and death dates often intersected

121
00:05:55,720 --> 00:05:57,920
with the names. And get this, They did another test,

122
00:05:58,000 --> 00:06:00,920
this time with thirty two different names, and they supposedly

123
00:06:00,959 --> 00:06:02,000
got similar results.

124
00:06:02,319 --> 00:06:05,519
Speaker 2: That's that's pretty compelling. But I mean, couldn't it still

125
00:06:05,560 --> 00:06:06,600
be just a coincidence.

126
00:06:06,879 --> 00:06:08,959
Speaker 1: That's what they wanted to rule out. So they did

127
00:06:08,959 --> 00:06:12,120
what's called a control experiment. They took other long texts

128
00:06:12,720 --> 00:06:16,000
like War and Peace and some religious writings that aren't

129
00:06:16,000 --> 00:06:18,920
supposed to have codes, and they ran the same program

130
00:06:18,959 --> 00:06:19,720
on those texts.

131
00:06:20,399 --> 00:06:24,000
Speaker 2: Oh, I see, So if they found similar patterns in

132
00:06:24,040 --> 00:06:26,560
those other books, then it would suggest that maybe it

133
00:06:26,600 --> 00:06:29,560
wasn't so special that maybe it was just random chance

134
00:06:29,600 --> 00:06:32,959
at play exactly. But guess what did they find anything?

135
00:06:33,079 --> 00:06:35,800
Speaker 1: They said, all they found were just random letters, no names,

136
00:06:35,879 --> 00:06:37,079
no dates, no patterns.

137
00:06:37,160 --> 00:06:39,920
Speaker 2: Okay, so that does seem to support their claim that

138
00:06:39,959 --> 00:06:41,839
there's something unique about the Old Testament.

139
00:06:42,120 --> 00:06:45,519
Speaker 1: It does, right, Doctor Rips one of the researchers, he

140
00:06:45,639 --> 00:06:47,959
did some calculations and said that the odds of this

141
00:06:48,040 --> 00:06:52,399
happening randomly were like one in ten million. That's that's

142
00:06:52,399 --> 00:06:53,319
a pretty huge name.

143
00:06:53,360 --> 00:06:56,000
Speaker 2: One in ten million. I mean, that's not just a fluke, right.

144
00:06:56,040 --> 00:06:58,759
Speaker 1: It doesn't seem like it. And because of this, their

145
00:06:58,839 --> 00:07:02,879
study actually got public in a pretty prestigious scientific journal

146
00:07:02,959 --> 00:07:04,480
called Statistical Science.

147
00:07:04,759 --> 00:07:07,800
Speaker 2: Wow, so it was peer reviewed by other scientists and

148
00:07:08,000 --> 00:07:10,680
deemed credible enough to be published. That's a big deal.

149
00:07:10,839 --> 00:07:13,480
Speaker 1: It was. Of course, it also created a huge controversy

150
00:07:13,519 --> 00:07:14,680
in the scientific community.

151
00:07:14,759 --> 00:07:17,319
Speaker 2: Oh I bet. I mean, if you believe their findings,

152
00:07:17,319 --> 00:07:19,319
it kind of turns our whole understanding of the Bible

153
00:07:19,399 --> 00:07:20,560
upside down right totally.

154
00:07:20,639 --> 00:07:23,160
Speaker 1: And one of the people who was super skeptical at

155
00:07:23,160 --> 00:07:26,040
first was this guy, Harold Dan's. He was like a

156
00:07:26,040 --> 00:07:29,199
big shot mathematician working for the NSA, you know, the

157
00:07:29,279 --> 00:07:32,240
National Security Agency whoa the NSSA.

158
00:07:32,279 --> 00:07:35,399
Speaker 2: So this guy, he basically dealt with codes for a

159
00:07:35,439 --> 00:07:36,399
living exactly.

160
00:07:36,439 --> 00:07:40,600
Speaker 1: He was a codebreaker, a cryptologist. If anyone could debunk

161
00:07:40,639 --> 00:07:42,160
these Bible codes, it would be him.

162
00:07:42,399 --> 00:07:43,240
Speaker 2: And what did he think?

163
00:07:43,639 --> 00:07:46,920
Speaker 1: He was, like totally dismissive at first. He even created

164
00:07:46,920 --> 00:07:50,759
his own computer program, like specifically designed to find flaws

165
00:07:50,879 --> 00:07:52,120
in the Bible code research.

166
00:07:52,199 --> 00:07:54,480
Speaker 2: So he was actively trying to prove it wrong, not

167
00:07:54,560 --> 00:07:56,079
just dismissing it exactly.

168
00:07:56,199 --> 00:07:59,680
Speaker 1: But here's where it gets crazy. When he ran his program,

169
00:08:00,079 --> 00:08:00,800
guess what happened?

170
00:08:00,839 --> 00:08:02,839
Speaker 2: Did it like crash or something.

171
00:08:02,920 --> 00:08:05,000
Speaker 1: It not only confirmed the names and dates from the

172
00:08:05,040 --> 00:08:09,399
Great Rabbis experiment, but it also started finding like places

173
00:08:09,439 --> 00:08:13,000
of birth and death for these Rabbis, all intersecting with

174
00:08:13,079 --> 00:08:14,360
their names within the grids.

175
00:08:14,639 --> 00:08:17,079
Speaker 2: So he set out to disprove it, but ended up

176
00:08:17,079 --> 00:08:19,759
proving it even further. That's a huge turnaround.

177
00:08:19,879 --> 00:08:22,160
Speaker 1: It is he basically became a believer all thanks to

178
00:08:22,199 --> 00:08:23,199
his own investigation.

179
00:08:23,480 --> 00:08:25,920
Speaker 2: That's pretty compelling, I have to admit. But so far

180
00:08:26,079 --> 00:08:28,839
we've just been talking about historical figures, right, Yeah, what

181
00:08:28,959 --> 00:08:32,159
about the future predictions that people talk about with Bible codes.

182
00:08:32,240 --> 00:08:36,039
Speaker 1: Oh yeah, that's where it gets even more well controversial.

183
00:08:36,080 --> 00:08:39,559
It goes beyond the past and into like predicting future events,

184
00:08:39,919 --> 00:08:42,279
even details about people who weren't even born yet.

185
00:08:42,440 --> 00:08:44,720
Speaker 2: Okay, I'm intrigued, tell me more so.

186
00:08:44,840 --> 00:08:48,600
Speaker 1: Take Saddam Hussein, for example. In nineteen ninety, Doctor Rips,

187
00:08:48,720 --> 00:08:51,320
the same guy from the Great Rabbis Experiment, said he

188
00:08:51,399 --> 00:08:54,960
found Hussein's name encoded in Bible along with the prediction

189
00:08:55,039 --> 00:08:57,039
that he'd attack Israel within three weeks.

190
00:08:57,360 --> 00:09:01,080
Speaker 2: So a specific person and a specific timeframe. That's a

191
00:09:01,159 --> 00:09:02,279
bold claim.

192
00:09:02,200 --> 00:09:04,759
Speaker 1: It is right. And what's really freaky is that while

193
00:09:04,759 --> 00:09:07,720
Saddam Hussein did actually launch a missile attack on Israel

194
00:09:07,799 --> 00:09:10,279
during the Gulf War, and it happened within that three

195
00:09:10,320 --> 00:09:10,919
week window.

196
00:09:11,039 --> 00:09:14,279
Speaker 2: Oh okay, So prediction and reality kind of lined up there.

197
00:09:14,399 --> 00:09:16,159
That's pretty hard to ignore, right.

198
00:09:16,399 --> 00:09:18,960
Speaker 1: It makes you wonder. And there are other examples too.

199
00:09:19,120 --> 00:09:22,559
People claim they've found President Kennedy's name encoded with the

200
00:09:22,559 --> 00:09:27,360
words to die and Dallas Shakespeare's name along with will

201
00:09:27,399 --> 00:09:30,200
present plays on stage crossing Hamlet and Macbeth.

202
00:09:30,559 --> 00:09:33,440
Speaker 2: Wow, I mean, if those are genuine encodies, it's like

203
00:09:33,480 --> 00:09:35,679
the Bible is some kind of ancient crystal ball.

204
00:09:35,799 --> 00:09:38,120
Speaker 1: It's almost like that, right. And then there's this other

205
00:09:38,200 --> 00:09:41,159
example with Saddam Hussein. Some people claim to have found

206
00:09:41,200 --> 00:09:44,960
the phrases Russian missile and fire on third Shabbat intersecting

207
00:09:45,000 --> 00:09:48,039
with his name. They say those phrases perfectly match the

208
00:09:48,080 --> 00:09:50,120
actual date and the type of attack that happened on

209
00:09:50,200 --> 00:09:51,879
January eighteenth, nineteen ninety.

210
00:09:52,200 --> 00:09:56,320
Speaker 2: Russian missile, but didn't a rock attack Israel not Russia.

211
00:09:56,559 --> 00:09:59,879
Speaker 1: Yeah, but remember back then Iraq was using Soviet may

212
00:10:00,159 --> 00:10:04,039
Scud missiles, so the phrase Russian missile could technically apply.

213
00:10:04,519 --> 00:10:07,399
Speaker 2: Oh right, Okay, that makes sense. It's all starting to

214
00:10:07,440 --> 00:10:09,080
sound a little too coincidental.

215
00:10:09,240 --> 00:10:12,200
Speaker 1: And that's exactly what this guy, Michael Drawsnen thought. He

216
00:10:12,240 --> 00:10:16,159
was an investigative journalist, super skeptical at first. He went

217
00:10:16,200 --> 00:10:19,039
to meet doctor Rips in the early nineties thinking he

218
00:10:19,159 --> 00:10:21,799
might write an article debunking the whole Bible code thing.

219
00:10:22,399 --> 00:10:24,120
But then he.

220
00:10:24,080 --> 00:10:28,919
Speaker 2: Got hooked, so another skeptic turn believer. What changed his mind?

221
00:10:29,120 --> 00:10:33,159
Speaker 1: Well, apparently doctor Rips showed him just how many potential

222
00:10:33,240 --> 00:10:36,320
encoding messages there could be, like billions of them hidden

223
00:10:36,399 --> 00:10:37,480
within the Old Testament.

224
00:10:37,559 --> 00:10:40,279
Speaker 2: Billions. That's like an unfathomable amount of information.

225
00:10:40,480 --> 00:10:44,519
Speaker 1: I know, imagine all the possibilities. Drawsenen ended up working

226
00:10:44,519 --> 00:10:46,840
with rips and they claimed to have found, get this,

227
00:10:47,000 --> 00:10:50,759
over a thousand instances of encoded predictions for all sorts

228
00:10:50,759 --> 00:10:53,600
of events. Some of the examples are like really specific,

229
00:10:53,720 --> 00:10:56,639
really like what okay? So they claim they found the

230
00:10:56,720 --> 00:11:00,519
Apollo eleven moon landing, like the date July twenty, nineteen

231
00:11:00,559 --> 00:11:03,679
sixty nine, and the words spaceship and Apollo eleven were

232
00:11:03,720 --> 00:11:07,000
found like intersecting in a passage about counting the stars.

233
00:11:07,080 --> 00:11:08,399
Speaker 2: That's incredible. What else?

234
00:11:08,559 --> 00:11:12,879
Speaker 1: Okay? So how about the nineteen twenty nine stock market crash?

235
00:11:13,440 --> 00:11:18,480
They found economic crisis crossing paths with depression stocks and

236
00:11:18,559 --> 00:11:19,919
the year nineteen twenty nine.

237
00:11:19,960 --> 00:11:23,639
Speaker 2: Wow? And what about events that really shook the world?

238
00:11:23,759 --> 00:11:26,440
Speaker 1: Oh, there are those two. They claimed they found encoded

239
00:11:26,480 --> 00:11:30,399
references to the Oklahoma City bombing, where Oklahoma supposedly crossed

240
00:11:30,440 --> 00:11:32,639
with Mura. The name of the building that was bombed

241
00:11:33,200 --> 00:11:36,120
and that intersected with his name was Timothy, referring to

242
00:11:36,120 --> 00:11:37,399
Timothy McVeigh, the bomber.

243
00:11:37,759 --> 00:11:40,000
Speaker 2: That's that's incredibly specific.

244
00:11:39,639 --> 00:11:41,960
Speaker 1: I know. And then there's the Shoemaker Lavy comet that

245
00:11:42,039 --> 00:11:44,799
crashed into Jupiter back in nineteen ninety four. They said

246
00:11:44,799 --> 00:11:48,000
they found the comet's name intersecting with will pound Jupiter

247
00:11:48,159 --> 00:11:49,840
and the exact date of the impact.

248
00:11:49,960 --> 00:11:52,480
Speaker 2: It's like they had a cosmic calendar encoded in the Bible.

249
00:11:52,600 --> 00:11:54,960
Speaker 1: And probably one of the most famous examples, they claimed

250
00:11:54,960 --> 00:11:58,120
to have found the assassination of Yetzac Rabin encoded in

251
00:11:58,159 --> 00:12:01,200
the text. Like they found Ribbon's name cross with assassin,

252
00:12:01,240 --> 00:12:03,279
will assassinate and the date and.

253
00:12:03,320 --> 00:12:06,879
Speaker 2: Hebrew didn't Drasnen claim he tried to warn Raven about it.

254
00:12:07,320 --> 00:12:09,840
Speaker 1: Yeah, he said that he saw the prediction, trying to

255
00:12:09,840 --> 00:12:13,440
warn Raven but was ignored. A truly tragic event. And

256
00:12:13,480 --> 00:12:15,960
those are just a few examples. They also claimed to

257
00:12:16,000 --> 00:12:18,720
have found the rise of Libya, the threat of nuclear war,

258
00:12:19,159 --> 00:12:23,000
Benjamin Netanyahu's victory in the nineteen ninety six Israeli election.

259
00:12:23,519 --> 00:12:26,159
Speaker 2: That's a lot of predictions. Did they talk about Princess

260
00:12:26,159 --> 00:12:27,679
Diana's death too, They did.

261
00:12:27,919 --> 00:12:32,320
Speaker 1: They said they found Princess Diana and Spencer, her maiden name,

262
00:12:32,600 --> 00:12:35,519
all with the same skip code, and these words intersected

263
00:12:35,559 --> 00:12:40,080
with Wales, Paris, France, tunnel, and river, along with the

264
00:12:40,120 --> 00:12:43,080
Hebrew date for August nineteen ninety seven, the month she died.

265
00:12:43,639 --> 00:12:46,279
Even the names of Dotie Fade and Honri Paul, who

266
00:12:46,279 --> 00:12:48,240
were with her, were supposedly found later.

267
00:12:48,399 --> 00:12:51,279
Speaker 2: It's like a never ending list, all these major events, tragedies,

268
00:12:51,320 --> 00:12:54,919
triumphs supposedly predicted in this ancient text. Drosenen wrote a

269
00:12:54,919 --> 00:12:55,519
whole book about it.

270
00:12:55,600 --> 00:12:58,320
Speaker 1: Right he did. It was called The Bible Code. That book,

271
00:12:58,360 --> 00:13:01,080
it became a huge bestseller, brought this whole idea into

272
00:13:01,080 --> 00:13:01,679
the mainstream.

273
00:13:01,799 --> 00:13:04,600
Speaker 2: I can imagine it must have really captured the public's imagination.

274
00:13:05,039 --> 00:13:08,279
Speaker 1: It totally did, and the claims just kept coming. People

275
00:13:08,279 --> 00:13:12,000
said they found encoded references to like everything, the fall

276
00:13:12,039 --> 00:13:15,399
of Saddam Hussein, the capture of Osama bin Laden, both

277
00:13:15,440 --> 00:13:19,080
Gulf Wars, the two thousand and eight financial crisis, swine

278
00:13:19,080 --> 00:13:21,639
flew all sorts of natural disasters.

279
00:13:21,759 --> 00:13:25,080
Speaker 2: So basically, if something major happen in recent history, someone

280
00:13:25,120 --> 00:13:27,399
probably claimed it was predicted in the Bible Code.

281
00:13:27,480 --> 00:13:31,240
Speaker 1: Pretty much. But Drasenen believed that like the real test

282
00:13:31,279 --> 00:13:34,080
of the Bible Code wasn't in explaining the past, it

283
00:13:34,120 --> 00:13:35,519
was in predicting the future.

284
00:13:35,879 --> 00:13:38,440
Speaker 2: Makes sense, I guess, But how do you predict the

285
00:13:38,440 --> 00:13:40,440
future with something written thousands of years ago.

286
00:13:40,559 --> 00:13:42,759
Speaker 1: Well, he believed there was a key, a literal key

287
00:13:43,039 --> 00:13:46,279
to unlocking future predictions. He thought it was hidden in

288
00:13:46,320 --> 00:13:49,480
a stone obelisk located in Jordan near the Red.

289
00:13:49,279 --> 00:13:52,120
Speaker 2: Sea, like an ancient art fact that unlocks the secrets

290
00:13:52,120 --> 00:13:52,879
of the Bible code.

291
00:13:53,000 --> 00:13:55,559
Speaker 1: That's pretty wild, I know, right, And get this, he

292
00:13:55,639 --> 00:13:59,240
actually got tremission from the Jordanian government to excavate the site.

293
00:13:59,279 --> 00:14:00,200
Speaker 2: Did they find any thing?

294
00:14:00,399 --> 00:14:03,799
Speaker 1: Nop. At the last minute, the permission was revoked, so

295
00:14:04,000 --> 00:14:06,399
that whole obelisk thing remains a mystery.

296
00:14:06,639 --> 00:14:11,080
Speaker 2: To talk about, a cliffhanger. So Drasenen spent years trying

297
00:14:11,080 --> 00:14:14,279
to decode the Bible predict the future. Did he ever

298
00:14:14,320 --> 00:14:16,639
come up with like a grand theory about where these

299
00:14:16,679 --> 00:14:17,559
codes came from? Oh?

300
00:14:17,600 --> 00:14:20,399
Speaker 1: He did, but it got a little out there. He

301
00:14:20,440 --> 00:14:24,120
started suggesting that Moses didn't actually meet God on Mount Sinai,

302
00:14:24,399 --> 00:14:25,799
but rather he met aliens.

303
00:14:26,120 --> 00:14:27,320
Speaker 2: Aliens really yep.

304
00:14:27,519 --> 00:14:30,000
Speaker 1: He thought these aliens were super advanced and used some

305
00:14:30,120 --> 00:14:33,840
kind of crazy computer technology to encode the Bible with

306
00:14:33,960 --> 00:14:35,679
all possible future timelines.

307
00:14:35,759 --> 00:14:38,440
Speaker 2: So the Bible code is actually an alien message.

308
00:14:38,840 --> 00:14:41,240
Speaker 1: That's what Drawsen came to believe, and even After one

309
00:14:41,279 --> 00:14:44,759
of his big predictions about a global catastrophe involving Jerusalem,

310
00:14:44,759 --> 00:14:46,799
New York and beIN Lauden in two thousand and six

311
00:14:46,960 --> 00:14:50,120
didn't happen, he was still convinced. He thought maybe he

312
00:14:50,240 --> 00:14:52,679
just got the timing wrong. He spent like twenty five

313
00:14:52,759 --> 00:14:56,080
years researching this, even learn Hebrew. But even some of

314
00:14:56,080 --> 00:14:59,200
the people who initially supported the Bible code, they started

315
00:14:59,200 --> 00:15:01,000
to have doubts about Drawsnen's prediction.

316
00:15:01,159 --> 00:15:02,960
Speaker 2: Wait so even doctor Rips, the one who did the

317
00:15:02,960 --> 00:15:05,360
Great Rabbis Experiment, he didn't agree with Drawsnen.

318
00:15:05,799 --> 00:15:10,720
Speaker 1: Yeah, Professor Rips became increasingly skeptical of Drawsnen's claims. He

319
00:15:10,840 --> 00:15:13,360
still believed in the results of the Great Rabbis Experiment,

320
00:15:13,759 --> 00:15:17,320
but he thought Drawsen was like seeing what he wanted to.

321
00:15:17,279 --> 00:15:21,000
Speaker 2: See, like cherry picking data to fit his own narrative exactly.

322
00:15:21,159 --> 00:15:24,440
Speaker 1: And you know rips work. Even the Great Rabbi's Experiment,

323
00:15:24,559 --> 00:15:27,960
it wasn't without its critics. Back in nineteen ninety nine,

324
00:15:28,000 --> 00:15:32,279
an Australian mathematician Brendan McKay published a whole critique of

325
00:15:32,360 --> 00:15:35,360
the experiment, pointing out flaws in the methodology.

326
00:15:35,519 --> 00:15:38,039
Speaker 2: Oh so, he was saying that maybe those results weren't

327
00:15:38,039 --> 00:15:40,879
as statistically significant as they seemed, right.

328
00:15:41,120 --> 00:15:43,679
Speaker 1: He said that the criteria for finding a match were

329
00:15:43,759 --> 00:15:46,440
way too loose. For example, they could count a name

330
00:15:46,480 --> 00:15:48,320
as a match even if the year of birth or

331
00:15:48,360 --> 00:15:50,879
death was wrong, as long as the month and day

332
00:15:50,919 --> 00:15:51,519
were correct.

333
00:15:51,639 --> 00:15:53,519
Speaker 2: Oh, so it wasn't a perfect match, just kind of

334
00:15:53,559 --> 00:15:54,120
close enough.

335
00:15:54,279 --> 00:15:57,159
Speaker 1: Yeah. And he also pointed out that they used nicknames, titles,

336
00:15:57,159 --> 00:16:00,440
even initials as matches and because ancient Hebrew doesn't have

337
00:16:00,559 --> 00:16:02,840
vowels to give them a lot of like wiggle room

338
00:16:03,039 --> 00:16:04,720
when searching for words, so you could.

339
00:16:04,639 --> 00:16:06,600
Speaker 2: Kind of make the letters fit the words you were.

340
00:16:06,480 --> 00:16:10,559
Speaker 1: Looking for exactly drawsnen. Of course, he dismissed all this criticism.

341
00:16:11,000 --> 00:16:14,759
He even challenges critics to find similar predictions in Get this.

342
00:16:14,879 --> 00:16:17,200
Speaker 2: Moby Dick, moby Dick the Whale book.

343
00:16:17,279 --> 00:16:20,440
Speaker 1: Yep. He basically said, if you think this is so easy,

344
00:16:20,639 --> 00:16:23,080
go find predictions in a random book.

345
00:16:23,240 --> 00:16:25,360
Speaker 2: And did anyone take him up on that challenge? Oh?

346
00:16:25,440 --> 00:16:29,399
Speaker 1: Yeah. Brenda McKay, the same mathematician who criticized the experiment,

347
00:16:29,879 --> 00:16:33,240
he took that challenge and ran with it. He supposedly

348
00:16:33,240 --> 00:16:37,519
found multiple predictions of Yitzak Rabin's assassination in Moby Dick,

349
00:16:37,879 --> 00:16:40,960
as well as the deaths of Princess Diana, Robert Kennedy,

350
00:16:41,000 --> 00:16:42,000
and a bunch of other events.

351
00:16:42,080 --> 00:16:44,639
Speaker 2: Wait, so he found those predictions in a book about

352
00:16:44,639 --> 00:16:45,039
a whale.

353
00:16:45,200 --> 00:16:48,120
Speaker 1: Yep. His point was, with a long enough text and

354
00:16:48,159 --> 00:16:51,120
a flexible enough program, you can find pretty much anything

355
00:16:51,120 --> 00:16:53,000
you want. It's like, if you look hard enough, you'll

356
00:16:53,000 --> 00:16:55,000
find patterns even in randomness.

357
00:16:55,120 --> 00:16:58,039
Speaker 2: That makes sense. So it's not necessarily the Bible especial.

358
00:16:58,120 --> 00:17:00,399
It's just that it's a long and complex techx and

359
00:17:00,440 --> 00:17:03,039
you can manipulate the search to find what you're looking

360
00:17:03,080 --> 00:17:03,919
for exactly.

361
00:17:04,119 --> 00:17:06,559
Speaker 1: Another point that krets brought up was that, well, the

362
00:17:06,559 --> 00:17:09,319
modern Hebrew text we use today, it's not exactly the

363
00:17:09,359 --> 00:17:11,279
same as the oldest ancient texts.

364
00:17:11,599 --> 00:17:12,960
Speaker 2: Oh right, like the Dead Sea scrolls.

365
00:17:13,039 --> 00:17:16,559
Speaker 1: Right, Yeah, those are some of the oldest surviving Biblical texts.

366
00:17:16,640 --> 00:17:18,960
And even though they're mostly the same as the modern text,

367
00:17:19,480 --> 00:17:23,240
there are small differences like spelling variations, maybe a letter

368
00:17:23,279 --> 00:17:25,599
added or missing here and there, and those.

369
00:17:25,400 --> 00:17:27,759
Speaker 2: Small differences they could totally mess.

370
00:17:27,640 --> 00:17:30,599
Speaker 1: Up the skip code, right exactly if the code relies

371
00:17:30,640 --> 00:17:33,680
on skipping a precise number of letters, even a single

372
00:17:33,759 --> 00:17:37,000
missing or added letter could throw off the whole thing,

373
00:17:37,119 --> 00:17:39,799
making the code like useless.

374
00:17:39,920 --> 00:17:41,480
Speaker 2: So it's a pretty fragile system.

375
00:17:41,240 --> 00:17:44,559
Speaker 1: Then it is. So after all this back and forth,

376
00:17:44,599 --> 00:17:47,960
the debate still continues. Are these patterns we see in

377
00:17:48,000 --> 00:17:51,440
the Bible are they really divine messages or maybe alien

378
00:17:51,480 --> 00:17:55,839
programming like Drasenen believed. Or are they just random noise

379
00:17:55,880 --> 00:17:57,519
that our brains are trying to make sense of.

380
00:17:57,839 --> 00:18:00,720
Speaker 2: That's million dollar question right looking it's some kind of

381
00:18:00,759 --> 00:18:03,319
hidden code? Or are we just really good at finding

382
00:18:03,359 --> 00:18:05,079
patterns even where they don't exist?

383
00:18:05,359 --> 00:18:08,000
Speaker 1: I mean, we humans, We love to find patterns. It's

384
00:18:08,039 --> 00:18:12,359
like hardwired into our brains. We see faces in clouds, animals,

385
00:18:12,359 --> 00:18:15,599
and star constellations. Maybe the Bible code is just another

386
00:18:15,640 --> 00:18:16,319
example of that.

387
00:18:16,759 --> 00:18:20,799
Speaker 2: Yeah, like peridolia, our tendency to perceive a specific, often

388
00:18:20,880 --> 00:18:25,079
meaningful image in a random or ambiguous visual pattern. Maybe

389
00:18:25,079 --> 00:18:25,799
that's a play here.

390
00:18:26,160 --> 00:18:29,440
Speaker 1: But even with all the criticism and skepticism, the idea

391
00:18:29,480 --> 00:18:32,720
of a hitting code it's just so alluring. It's like,

392
00:18:33,240 --> 00:18:35,720
what if there are secrets hidden in plain sight, secrets

393
00:18:35,720 --> 00:18:39,640
about our past, our future waiting to be unlocked. It's

394
00:18:39,680 --> 00:18:43,319
hard to resist that kind of mystery. There's even that quote,

395
00:18:43,440 --> 00:18:45,559
it is the glory of God to conceal a matter,

396
00:18:45,880 --> 00:18:48,279
and it is the honor of kings to search it out.

397
00:18:48,440 --> 00:18:51,240
Speaker 2: That's from Proverbs, right. It really captures that human desire

398
00:18:51,279 --> 00:18:54,400
to discover, to uncover the truth, no matter how hidden

399
00:18:54,400 --> 00:18:54,839
it might be.

400
00:18:54,920 --> 00:18:57,200
Speaker 1: It does, And you have to give Michael Drawsen credit.

401
00:18:57,240 --> 00:19:00,319
He was dedicated, even learned Hebrew to pursue this reas search.

402
00:19:00,559 --> 00:19:02,200
He spent a big chunk of his life trying to

403
00:19:02,240 --> 00:19:03,039
crack this code.

404
00:19:03,440 --> 00:19:05,720
Speaker 2: It's hard to argue with that level of commitment. And

405
00:19:05,759 --> 00:19:09,079
who knows, Maybe somewhere out there that stone obelisk is

406
00:19:09,079 --> 00:19:11,400
still waiting to be found, holding the key to everything.

407
00:19:11,839 --> 00:19:15,079
Speaker 1: Maybe. But what if instead of thinking about the Bible

408
00:19:15,119 --> 00:19:18,279
Code as like a fixed bluefrit of the future, we

409
00:19:18,400 --> 00:19:21,079
see it as a collection of possibilities, like not a

410
00:19:21,119 --> 00:19:24,559
definite prediction, but more like a weather forecast. It tells

411
00:19:24,559 --> 00:19:27,440
you what might happen, but you can still choose to prepare,

412
00:19:27,920 --> 00:19:29,400
maybe even change the outcome.

413
00:19:29,799 --> 00:19:33,039
Speaker 2: So instead of a set destiny, it's more like a warning,

414
00:19:33,079 --> 00:19:37,960
a heads up about potential dangerous challenges, maybe even opportunities.

415
00:19:37,359 --> 00:19:40,839
Speaker 1: Exactly, and even if those predictions aren't like divinely inspired

416
00:19:40,920 --> 00:19:43,079
or whatever. Maybe just being aware of them can help

417
00:19:43,160 --> 00:19:44,079
us make better choices.

418
00:19:44,359 --> 00:19:47,240
Speaker 2: It's like having a glimpse into a range of possible

419
00:19:47,279 --> 00:19:50,640
futures and then trying to steer towards the best one.

420
00:19:50,720 --> 00:19:52,960
It's a pretty empowering way to look at it. It is.

421
00:19:53,160 --> 00:19:56,039
Speaker 1: It makes you wonder, what if everything is connected in

422
00:19:56,079 --> 00:19:59,359
ways we don't even understand. What if those connections are

423
00:19:59,559 --> 00:20:03,359
like subtly reflected in these ancient texts The Bible cog

424
00:20:03,480 --> 00:20:05,680
might not give us all the answers, but it definitely

425
00:20:05,720 --> 00:20:07,799
makes you think about the nature of information and the

426
00:20:07,839 --> 00:20:10,119
power of belief, and just how much we still don't

427
00:20:10,119 --> 00:20:14,519
know about well everything. It's definitely a mystery worth pondering.

428
00:20:15,799 --> 00:20:17,440
What do you think? Is there something to this or

429
00:20:17,519 --> 00:20:19,000
is it all just a coincidence.

430
00:20:19,480 --> 00:20:22,359
Speaker 2: It's a fascinating puzzle, that's for sure. And even if

431
00:20:22,359 --> 00:20:24,119
it turns out to be nothing more than our brains

432
00:20:24,160 --> 00:20:27,160
trying to make sense of random patterns, it still makes

433
00:20:27,160 --> 00:20:28,000
you think, doesn't it.

434
00:20:28,000 --> 00:20:30,200
Speaker 1: It totally does, And that's what we're all about here,

435
00:20:30,279 --> 00:20:34,200
making you think, exploring the unknown and keeping you curious.

