Bible Codes Search Providers

These Bible codes became known to the public primarily due to the American journalist Michael Drosnin, whose book The Bible Code (Simon & Schuster, 1997) was a best-seller in many countries. Modern computers have been used to search for similar patterns and more complex variants, and it has been published as a challenging puzzle in a peer-reviewed academic journal in 1994. View the latest Bible Codes. Obama Anti-Messiah. The Rapture Verdict Rapture. Fire is the End Signs and Wonders. War is coming End Times. View the latest.

  • 47/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests

Click here to check amazing Biblecodewisdom content for Canada. Otherwise, check out these important facts you probably never knew about biblecodewisdom.com

We analyzed Biblecodewisdom.com page load time and found that the first response time was 373 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

  • HTML62.3 kB
    Images59.9 kB
    Javascripts961.7 kB
    CSS6.8 kB

    In fact, the total size of Biblecodewisdom.com main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 961.7 kB which makes up the majority of the site volume.

  • HTML optimization

    HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 42.7 kB or 69% of the original size.

  • Image optimization

    Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Biblecodewisdom images are well optimized though.

  • JavaScript optimization

    It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 652.5 kB or 68% of the original size.

  • CSS optimization

    CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Biblecodewisdom.com needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 82% of the original size.

Search

Network requests diagram

  • biblecodewisdom.com
  • WebResource.axd
  • WebResource.axd
  • WebResource.axd
  • biblebg.gif
  • show_ads.js
  • bibleHeader.jpg
  • adsbygoogle.js
  • widgets.js
  • button1-share.gif
  • addthis_widget.js
  • urchin.js
  • ca-pub-5610629605743825.js
  • zrt_lookup.html
  • show_ads_impl.js
  • ads
  • like.php
  • osd.js
  • ads
  • ads
  • __utm.gif
  • piwik.js
  • ads
  • Widget.aspx
  • metrics.js
  • qeKvIRsJabD.js
  • LVx-xkvaJ0b.png
  • adj
  • beacon
  • m_js_controller.js
  • abg.js
  • adj
  • beacon
  • favicon
  • favicon
  • googlelogo_color_112x36dp.png
  • nessie_icon_tiamat_white.png
  • s
  • x_button_blue2.png
  • button.0308b81ff1714e446f674b5b9793f2cd.js
  • 300lo.json
  • verify_selector.js
  • blank.gif
  • beacon.js
  • bapi
  • sh.8e5f85691f9aaa082472a194.html
  • verify_selector.js
  • blank.gif
  • Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
  • dt
  • tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
  • dt
  • dtc
  • dtc
  • antenna2.js
  • prWriteCode.js
  • verifyr.js
  • verifyr.js
  • jot
  • 0
  • pixel
  • dbapi
  • pixel
  • lidar.js
  • sbhK2lTE.js
  • dt
  • dt
  • cTrvNaRi.html
  • pixel
  • pixel
  • dt
  • adServer.bs
  • RAM_160x600.png
  • PRScript
  • adServer.bs
  • sd
  • prTrk.js
  • HTML_P3_2016_Ram_BT_Segment_160.css
  • TweenMax.min.js
  • HTML_P3_2016_Ram_BT_Segment_Event_160.js
  • m
  • m
  • activeview
  • activeview

Our browser made a total of 92 requests to load all elements on the main page. We found that 7% of them (6 requests) were addressed to the original Biblecodewisdom.com, 10% (9 requests) were made to Pagead2.googlesyndication.com and 9% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (464 ms) relates to the external source Piwik.webcontrolcenter.com.

Requests

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Biblecodewisdom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.

Free Bible Codes Search

Bible

Javascripts

Initial D Street Stage APK Android PPSSPP is a popular PlayStation PSP Video Game and you can play this game on android using PPSSPP emulator best settings. Initial D Street Stage APK Android PPSSPP is a racing game developed by Sega for the PlayStation 3. Initial D - Street Stage is a PSP game but you can play it through PPSSPP a PSP Emulator and this file is tested and really works. Now you can play it on your android phone or iOS Device. Corpse party ppsspp english. Download page for Initial D - Street Stage (Japan). Initial D: Street Stage is a PSP exclusive game based on the popular anim/manga of the same name. Aug 05, 2014  ~ Initial D Street Stage ~Driving Drifting ~Japan ~Cso ~0.7 build 21 ~Android 3.2 ~Playable ~OMG it started to work! It crashes when starting with fastmem but unchecked its runs and I dont notice any glitches in the menu BUT there is a semi harnessing glitch.

Images

CSS

AJAX

All

Possible request optimization

Javascripts

Images

CSS

AJAX

Optimized

All

IP address

Biblecodewisdom.com uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

biblecodewisdom.com

mogaznews.com

Bible Codes Search Pro

mcentre.lk

archnadzor.ru

anblogony.com

104.28.0.119

104.28.1.119

Also you’ll see in the photos that the pickup pole pieces were grounded. We’ve seen this once before, most likely to reduce hum. Quite a story! Fender stratocaster serial number mz 9. We also speculate it is possible that the neck & bridge pickups were rewound.

DNS records

TypeHostTarget/ipTTLOther
A

biblecodewisdom.com Arizona license plate fee calculator.

104.28.1.119278
A

biblecodewisdom.com

104.28.0.119278
NS

biblecodewisdom.com

rajeev.ns.cloudflare.com86395
NS

biblecodewisdom.com

adi.ns.cloudflare.com86395
SOA

biblecodewisdom.com

3600Mname: adi.ns.cloudflare.com
Rname: dns.cloudflare.com
Serial: 2031736462
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum-ttl: 3600

Language

N/A

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Biblecodewisdom.com can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Biblecodewisdom.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Similarly rated websites

HTTPS certificate

Biblecodewisdom.com has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Visitor World Map

Country of origin for 59.2% of all visits is Canada. It lies approximately 1130 miles away from the server location (United States) and such a distance cannot critically affect website speed, but moving the server closer to their user base in Canada can speed up Biblecodewisdom.com page load time anyway.

Ratings of similarly popular websites

Social Sharing Optimization

Open Graph description is not detected on the main page of Biblecodewisdom. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

biblecodewisdom.com

Genesis 1:1–4. Biblia Hebraica from Kittel's edition (BHK) 1909. Four letters, 50 letters apart, starting from the first taw on the first verse, form the word תורה (Torah).
Exodus 1:1–6. Biblia Hebraica from Kittel's edition (BHK) 1909. Four letters, 50 letters apart, starting from the first taw on the first verse, form the word תורה (Torah).

The Bible code (Hebrew: הצופן התנ'כי‎, hatzofen hatanachi), also known as the Torah code, is a purported set of secret messages encoded within the Hebrew text of the Torah. This hidden code has been described as a method by which specific letters from the text can be selected to reveal an otherwise obscured message. Although Bible codes have been postulated and studied for centuries, the subject has been popularized in modern times by Michael Drosnin's book The Bible Code and the movie The Omega Code.

Many examples have been documented in the past. One cited example is that by taking every 50th letter of the Book of Genesis starting with the first taw, the Hebrew word 'torah' is spelled out. The same happens in the Book of Exodus. Modern computers have been used to search for similar patterns and more complex variants, as well as quantifying its statistical likelihood.

Some tests purportedly showing statistically significant codes in the Bible were published as a 'challenging puzzle' in a peer-reviewed academic journal in 1994, and later questioned.

  • 2Equidistant Letter Sequence method
  • 3History
  • 4Criticism
    • 4.2Replies to MBBK's criticisms
    • 4.3Criticism of Michael Drosnin

Overview[edit]

Contemporary discussion and controversy around one specific steganographic method became widespread in 1994 when Doron Witztum, Eliyahu Rips and Yoav Rosenberg published a paper, 'Equidistant Letter Sequences in the Book of Genesis', in the scientific journal Statistical Science.[1] The paper, which was presented by the journal as a 'challenging puzzle', presented strong statistical evidence that biographical information about famous rabbis was encoded in the text of the Book of Genesis, centuries before those rabbis lived.[citation needed]

Since then the term 'Bible codes' has been popularly used to refer specifically to information encrypted via this ELS method.

Since the Witztum, Rips, and Rosenberg (WRR) paper was published, two conflicting schools of thought[which?] regarding the 'codes' have emerged among proponents. The traditional (WRR) view of the codes is based strictly on their applicability to the Torah, and asserts that any attempt to study the codes outside of this context is invalid. This is based on a belief that the Torah is unique among biblical texts in that it was given directly to mankind (via Moses) in exact letter-by-letter sequence and in the original Hebrew language.

Equidistant Letter Sequence method[edit]

The primary method by which purportedly meaningful messages have been extracted is the Equidistant Letter Sequence (ELS). To obtain an ELS from a text, choose a starting point (in principle, any letter) and a skip number, also freely and possibly negative. Then, beginning at the starting point, select letters from the text at equal spacing as given by the skip number. For example, the bold letters in this sentence form an ELS. With a skip of −4 (that is, reading backwards every fourth letter), and ignoring the spaces and punctuation, the word safest is spelled out.

Arrange the letters from Genesis 26:5–10 in a 21-column grid and you get a word search with 'Bible' and 'code'. Myriad other arrangements can yield other words. (Alternate words are bolded for legibility.)

Often more than one ELS related to some topic can be displayed simultaneously in an ELS letter array. This is produced by writing out the text in a regular grid, with exactly the same number of letters in each line, then cutting out a rectangle. In the example below, part of the King James Version of Genesis (26:5–10) is shown with 21 letters per line. ELSs for 'Bible' and 'code' are shown. Normally only a smaller rectangle would be displayed, such as the rectangle drawn in the figure. In that case there would be letters missing between adjacent lines in the picture, but it is essential that the number of missing letters be the same for each line.[1]

Although the above examples are in English texts, Bible codes proponents usually use a Hebrew Bible text. For religious reasons, most Jewish proponents use only the Torah (Genesis–Deuteronomy).

ELS extensions[edit]

Once a specific word has been found as an ELS, it is natural to see if that word is part of a longer ELS consisting of multiple words.[2] Code proponents Haralick and Rips have published an example of a longer, extended ELS, which reads, 'Destruction I will call you; cursed is Bin Laden and revenge is to the Messiah'[3] (though the Hebrew, using appositives in place of to be, lacking helper verbs, and employing definite articles less frequently, would entail far fewer words than the English phrasing).

ELS extensions that form phrases or sentences are of interest. Proponents maintain that the longer the extended ELS, the less likely it is to be the result of chance.[4] Critics reply, as in the Skeptical Inquirer deconstruction of 1997,[5] that the longer ELS is in fact effectively nothing more than further increased number of permutations, employing a massive application of the Look-elsewhere effect.

History[edit]

Early history[edit]

Jewish culture has a long tradition of interpretation, annotation, and commentary regarding the Bible, leading to both exegesis and eisegesis (drawing meaning from and imposing meaning on the texts). The Bible code can be viewed as a part of this tradition, albeit one of the more controversial parts. Throughout history, many Jewish, and later Christian, scholars have attempted to find hidden or coded messages within the Bible's text, notably including Isaac Newton.[citation needed]

The 13th-century Spanish rabbiBachya ben Asher may have been the first[citation needed] to describe an ELS in the Bible. His four-letter example related to the traditional zero-point of the Hebrew calendar. Over the following centuries there are some hints that the ELS technique was known, but few definite examples have been found from before the middle of the 20th century. At this point many examples were found by the Michael Ber Weissmandl and published by his students after his death in 1957. Nevertheless, the practice remained known only to a few until the early 1980s, when some discoveries of an Israeli school teacher Avraham Oren came to the attention of the mathematician Eliyahu Rips at the Hebrew University of Jerusalem. Rips then took up the study together with his religious studies partners Doron Witztum and Alexander Rotenberg, among several others.

Rips and Witztum[edit]

Rips and Witztum designed computer software for the ELS technique and subsequently found many examples. About 1985, they decided to carry out a formal test, and the 'Great rabbis experiment' was born. This experiment tested the hypothesis that ELS's of the names of famous rabbinic personalities and their respective birth and death dates form a more compact arrangement than could be explained by chance. Their definition of 'compact' was complex but, roughly, two ELSs were compactly arranged if they can be displayed together in a small window. When Rips et al. carried out the experiment, the data was measured and found to be statistically significant, supporting their hypothesis.

The 'great rabbis experiment' went through several iterations, and was eventually published in 1994, in the peer-reviewed journalStatistical Science. Prior to publication, the journal's editor, Robert Kass, subjected the paper to three successive peer reviews by the journal's referees, who according to Kass were 'baffled'. Though still skeptical,[6] none of the reviewers had found any flaws. Understanding that the paper was certain to generate controversy, it was presented to readers in the context of a 'challenging puzzle.' Witztum and Rips also performed other experiments, most of them successful, though none were published in journals.

Other experiments[edit]

Another experiment, in which the names of the famous rabbis were matched against the places of their births and deaths (rather than the dates), was conducted in 1997 by Harold Gans, former Senior Cryptologic Mathematician for the United States National Security Agency.[7]Again, the results were interpreted as being meaningful and thus suggestive of a more than chance result.[8] These Bible codes became known to the public primarily due to the American journalist Michael Drosnin, whose book The Bible Code (Simon & Schuster, 1997) was a best-seller in many countries. Rips issued a public statement that he did not support Drosnin's work or conclusions;[9] even Gans has said that although the book states that the codes in the Torah can be used to predict future events: 'This is absolutely unfounded. There is no scientific or mathematical basis for such a statement, and the reasoning used to come to such a conclusion in the book is logically flawed.'[10]

In 2002, Drosnin published a second book on the same subject, called Bible Code II: the Countdown.The Jewish outreach group Aish-HaTorah employs Bible codes in their Discovery Seminars to persuade secular Jews of the divinity of the Torah, and to encourage them to trust in traditional Orthodox teachings. Use of Bible code techniques also spread into certain Christian circles, especially in the United States. The main early proponents were Yakov Rambsel, who is a Messianic Jew, and Grant Jeffrey. Another Bible code technique was developed in 1997 by Dean Coombs (also Christian). Various pictograms are claimed to be formed by words and sentences using ELS.[11]

Since 2000, physicist Nathan Jacobi, an agnostic Jew, and engineer Moshe Aharon Shak, an orthodox Jew, claim to have discovered hundreds of examples of lengthy, extended ELSs.[12] The number of extended ELSs at various lengths is compared with those expected from a non-encoded text, as determined by a formula from Markov chain theory.[13]

Criticism[edit]

The precise order of consonantal letters represented in the Hebrew Masoretic Text was only finalized in its current form in the first century, largely through the energies of Rabbi Akiva. However, it is known from earlier versions, such as the Dead Sea Scrolls, that the number of letters was not constant before this. The Bible code theory thus does not seem to account for these variations.[14]

The primary objection advanced against Bible codes is that information theory does not prohibit 'noise' from appearing to be sometimes meaningful. Thus, if data chosen for ELS experiments are intentionally or unintentionally 'cooked' before the experiment is defined, similar patterns can be found in texts other than the Torah. Although the probability of an ELS in a random place being a meaningful word is small, there are so many possible starting points and skip patterns that many such words can be expected to appear, depending on the details chosen for the experiment, and that it is possible to 'tune' an ELS experiment to achieve a result which appears to exhibit patterns that overcome the level of noise.

Others have criticized Drosnin by stating that Drosnin's example of 'Clinton' in his first book violated the basic Bible code concept of 'Minimality'; Drosnin's 'Clinton' was a completely invalid 'code'. In addition, McKay claimed that Drosnin had used the flexibility of Hebrew orthography to his advantage, freely mixing classic (no vowels, Y and W strictly consonant) and modern (Y and W used to indicate i and u vowels) modes, as well as variances in spelling of K and T, to reach the desired meaning.

Criticism of the original paper[edit]

In 1999, Australian mathematician Brendan McKay, Israeli mathematicians Dror Bar-Natan and Gil Kalai, and Israeli psychologist Maya Bar-Hillel (collectively known as 'MBBK') published a paper in Statistical Science, in which they argued that the case of Witztum, Rips and Rosenberg (WRR) was 'fatally defective, and that their result merely reflects on the choices made in designing their experiment and collecting the data for it.'[15] The MBBK paper was reviewed anonymously by four professional statisticians prior to publication. In the introduction to the paper, Robert Kass, the Editor of the Journal who previously had described the WRR paper as a 'challenging puzzle' wrote that 'considering the work of McKay, Bar-Natan, Kalai and Bar-Hillel as a whole it indeed appears, as they conclude, that the puzzle has been solved'.[6]

From their observations, MBBK created an alternative hypothesis to explain the 'puzzle' of how the codes were discovered. MBBK's argument was not strictly mathematical, rather it asserted that the WRR authors and contributors had intentionally or unintentionally (a) selected the names and/or dates in advance and (b) designed their experiments to match their selection, thereby achieving their 'desired' result. The MBBK paper argued that the ELS experiment is extraordinarily sensitive to very small changes in the spellings of appellations, and that the WRR result 'merely reflects on the choices made in designing their experiment and collecting the data for it.'

The MBBK paper demonstrated that this 'tuning', when combined with what MBBK asserted was available 'wiggle' room, was capable of generating a result similar to WRR's Genesis result in a Hebrew translation of War and Peace. Bar-Hillel subsequently summarized the MBBK view that the WRR paper was a hoax, an intentionally and carefully designed 'magic trick'.[16]

The Bible codes (together with similar arguments concerning hidden prophecies in the writings of Shakespeare) have been quoted as examples of the Texas sharpshooter fallacy.

Replies to MBBK's criticisms[edit]

Harold Gans[edit]

Harold Gans, a former Cryptanalyst at the National Security Agency, argued that MBBK's hypothesis implies a conspiracy between WRR and their co-contributors to fraudulently tune the appellations in advance. Gans argues that the conspiracy must include Doron Witztum, Eliyahu Rips, and S. Z. Havlin, because all of them say that Havlin compiled the appellations independently. Gans argues further that such a conspiracy must include the multiple rabbis who have written a letter confirming the accuracy of Havlin's list. Finally, argues Gans, such a conspiracy must also include the multiple participants of the cities experiment conducted by Gans (which includes Gans himself). Gans concludes that 'the number of people necessarily involved in [the conspiracy] will stretch the credulity of any reasonable person.'[17] Gans further argued that while 'the mathematical issues are difficult for non-mathematicians to comprehend, I can summarize as follows: Professor McKay and his colleagues never claimed to have discovered real codes in those non-Torah texts. Their only “successful” results were obtained by deliberately rigging the experiment in such a way that the layman wouldn't recognize the mathematical flaws.'[18]

Brendan McKay has replied that he and his colleagues have never accused Havlin or Gans of participating in a conspiracy. Instead, says McKay, Havlin likely did what WRR's early preprints said he did: he provided 'valuable advices'. Similarly, McKay accepts Gans' statements that Gans did not prepare the data for his cities experiment himself. McKay concludes that 'there is only ONE person who needs to have been involved in knowing fakery, and a handful of his disciples who must be involved in the cover-up (perhaps with good intent).'[19]

WRR authors[edit]

The WRR authors issued a series of responses regarding the claims of MBBK,[20] including the claim that no such tuning did or even could have taken place.[21] An earlier WRR response to a request by MBBK authors presented results from additional experiments that used the specific 'alternate' name and date formats which MBBK suggested had been intentionally avoided by WRR.[22] Using MBBK's alternates, the results WRR returned showed equivalent or better support for the existence of the codes, and so challenged the 'wiggle room' assertion of MBBK. In the wake of the WRR response, author Bar-Natan issued a formal statement of non-response.[23] After a series of exchanges with McKay and Bar-Hillel, WRR author Witztum responded in a new paper[24] claiming that McKay had used smoke screen tactics in creating several straw man arguments, and thereby avoided the points made by WRR authors refuting MBBK.[25] Witztum also claimed that, upon interviewing a key independent expert contracted by McKay for the MBBK paper, that some experiments performed for MBBK had validated, rather than refuted the original WRR findings, and questioned why MBBK had expunged these results from their paper.McKay replied to these claims.[26]

No publication in a peer reviewed scientific journal has appeared refuting MBBK's paper. In 2006, seven new Torah Codes papers were published at the 18th International Conference on Pattern Recognition (ICPR'06).

Robert Aumann[edit]

https://ninpixel.netlify.app/sygic-maps-windows-ce-pocket.html. Robert Aumann, a game theorist and winner of the Nobel Prize in Economics in 2005, has followed the Bible code research and controversy for many years. He wrote:[27]

Though the basic thesis of the research seems wildly improbable, for many years I thought that an ironclad case had been made for the codes; I did not see how 'cheating' could have been possible. Then came the work of the 'opponents' (see, for example, McKay, Bar-Natan, Bar-Hillel and Kalai, Statistical Science 14 (1999), 149–173). Though this work did not convince me that the data had been manipulated, it did convince me that it could have been; that manipulation was technically possible.

After a long and interesting analysis of the experiment and the dynamics of the controversy, stating for example that 'almost everybody included [in the controversy] made up their mind early in the game' Aumann concluded:

A priori, the thesis of the Codes research seems wildly improbable.. Research conducted under my own supervision failed to confirm the existence of the codes – though it also did not establish their non-existence. So I must return to my a priori estimate, that the Codes phenomenon is improbable'.[28]

Robert Haralick[edit]

Internet Search Providers Lists

Robert Haralick, a Professor of Computer Science at the City University of New York, has checked the Bible Code for many years and became convinced of its validity. He contributed a new experiment : he checked whether besides the minimal ELS, in which it was known that WRR's list was successful in Genesis, and MBBK's list was successful in War and Peace, there are other, non-minimal ELSs where there is convergence between the rabbis' names and their respective dates. In other words, what convergence will be found at 2nd minimal ELSs, 3rd minimal ELSs and so on. According to him the results were impressive: WRR's list was successful until the 20th minimal ELS, whereas MBBK's list failed after the 2nd minimal ELS.[29] Haralick lectured on the subject in front of the participants of the international conference on pattern recognition in 2006.[30]

Criticism of Michael Drosnin[edit]

Journalist Drosnin's books have been criticized by some who believe that the Bible code is real but that it cannot predict the future.[31]On Drosnin's claim of Rabin's death, Drosnin wrote in his book 'The Bible Code' (published in 1997) on page 120; 'Yigal Amir could not be found in advance'. This is very telling in that dangerous period of Israeli politics from the Oslo Accords of 1993 to the assassination of Yitzhak Rabin on November 4, 1995.[32] Critics have noted a huge error in the 'code' Drosnin claimed to have found: Drosnin misused the Biblical verse Deuteronomy 4:42. Scholars note; 'For example, citing again the passage intersecting with Rabin: that passage is from Deuteronomy 4:42, but Drosnin ignores the words immediately following 'a murderer who will murder.' What comes next is the phrase 'unwittingly' (biveli da'at). This is because the verse deals with the cities of refuge where accidental killers can find asylum. In this case, then, the message would refer to an accidental killing of (or by) Rabin and it would therefore be wrong. Another message (p. 71) supposedly contains a 'complete' description of the terrorist bombing of a bus in Jerusalem on February 25, 1996. It includes the phrase 'fire, great noise,' but overlooks the fact that the letters which make up those two words are actually part of a larger phrase from Genesis 35:4 which says: 'under the terebinth that was near Shechem.' If the phrase does tell of a bus bombing, why not take it to indicate that it would be in Nablus, the site of ancient Shechem?' [33]

Drosnin also made a number of claims and alleged predictions that have since failed. Among the most important, Drosnin clearly states in his book 'The Bible Code II', published on December 2, 2002, that there was to be a World War involving an 'Atomic Holocaust' that would allegedly be the end of the world.[34] Another claim Drosnin makes in 'The Bible Code II' is that the nation of Libya would develop weapons of mass destruction that they would then be given to terrorists who would then use them to attack the West (specifically the United States).[35] In reality Libya improved relations with the West in 2003 and gave up all their existing weapons of mass destruction programs.[36] A final claim Drosnin made in 'The Bible Code II' was that Palestinian Authority leader Yasser Arafat would allegedly be assassinated by being shot to death by gunmen which Drosnin specifically stated would be from the Palestinian Hamas movement.[37] This prediction by Drosnin also failed, as Yasser Arafat died on November 11, 2004[38] of what was later declared to be natural causes (specifically a stroke brought on by an unknown infection).[39][40] The only conspiracy theories about Yasser Arafat allegedly being murdered have been made by a few Palestinian figures, and have involved alleged poisoning that was supposed to have been on the orders of Israeli officials. The only alleged Palestinian collaboration in this conspiracy theory involve two leading Palestinian figures from the Palestinian Fatah movement; those are current Palestinian Authority and Fatah leader Mahmoud Abbas and Mohammed Dahlan the former head of Fatah in Gaza.[41] Writer Randy Ingermanson criticized Drosnin by stating that; 'And that's all they are, even for Drosnin – possibilities. He believes that the future is not fixed, and that the Bible code predicts all possible outcomes. Which makes it not much of a predictive tool, but again, he seems not to mind this very much. If you are laying bets based on Drosnin, you had better be willing to bet on all possible outcomes.'[42]

Some accuse him of factual errors, claiming that he has much support in the scientific community,[43] mistranslating Hebrew words[44] to make his point more convincing, and using the Bible without proving that other books do not have similar codes.[45]

Bible Code Search Engine

Criticism using ELS in other texts[edit]

Bible Code Search Yourself

Equidistant letter sequences 'wiki' and 'Pedia' found in the King James Version of Genesis (10:7-14)

Responding to an explicit challenge from Drosnin, who claimed that other texts such as Moby-Dick would not yield ELS results comparable to the Torah, McKay created a new experiment that was tuned to find many ELS letter arrays in Moby-Dick that relate to modern events, including the assassination of Martin Luther King, Jr. He also found a code relating to the Rabin assassination, containing the assassin's first and last name and the university he attended, as well as the motive ('Oslo', relating to the Oslo accords).[46] Drosnin and others have responded to these claims, saying the tuning tactics employed by McKay were simply 'nonsense', and providing analyses[47] to support their argument that the tables, data and methodologies McKay used to produce the Moby Dick results 'simply do not qualify as code tables'.[48] Skeptic Dave Thomas claimed to find other examples in many texts. While Thomas' methodology was alleged to have been rebutted by Robert Haralick[49] and others, his broader arguments about the law of large numbers stood essentially unchallenged. Also, Thomas's criticisms were aimed at Drosnin, whose methodology is considered even worse. (In fact, Drosnin's example of 'Clinton' in his first book violated the basic Bible code concept of 'Minimality'; Drosnin's 'Clinton' was a completely invalid 'code'). In addition, McKay claimed that Drosnin had used the flexibility of Hebrew orthography to his advantage, freely mixing classic (no vowels, Y and W strictly consonant) and modern (Y and W used to indicate i and u vowels) modes, as well as variances in spelling of K and T, to reach the desired meaning.

In his television series John Safran vs God, Australian television personality John Safran and McKay again demonstrated the 'tuning' technique, demonstrating that these techniques could produce 'evidence' of the September 11 terrorist attacks on New York in the lyrics of Vanilla Ice's repertoire. And the influence and consequences of scribal errors (e.g., misspellings, additions, deletions, misreadings, ..) are hard to account for in claims for a Bible coded message left secretly in the text. McKay and others claim that in the absence of an objective measure of quality and an objective way to select test subjects (though that remains an objection as equally against Drosnin), it is not possible positively to determine whether any particular observation is significant or not. For that reason, outside of Davis' mathematical arguments, much or most of the serious effort of the skeptics has been focused on the scientific claims of Witztum, Rips, and Gans.

Search Providers List

See also[edit]

  • Alignment of random points, for another phenomenon of apparently mysterious coincidences
  • Ramsey theory, for a notion of 'unavoidable coincidences'

References[edit]

  1. ^ abDoron Witztum; Eliyahu Rips; Yoav Rosenberg (1994). 'Equidistant letter sequences in the Book of Genesis'. Statistical Science. 9 (3): 429–38. CiteSeerX10.1.1.495.9620. doi:10.1214/ss/1177010393.
  2. ^Shak, Moshe Aharon. 2004. Bible Codes Breakthrough. Montreal: Green Shoelace Books. 38
  3. ^Haralick, Rips, and Glazerson. 2005. Torah Codes: A Glimpse into the Infinite. New York: Mazal & Bracha. 125
  4. ^Sherman, R. Edwin, with Jacobi and Swaney. 2005. Bible Code Bombshell Green Forest, Ar.: New Leaf Press. 95–109
  5. ^Thomas, Dave (November 1, 1997), 'Hidden Messages and The Bible Code', Skeptical Inquirer, CSICOP, retrieved April 19, 2015
  6. ^ abKass, R. E. (1999). Introduction to 'Solving the Bible Code Puzzle' by Brendan McKay, Dror Bar-Natan, Maya Bar-Hillel and Gil Kalai Statistical Science, 14. projecteuclid.org. p. 149.
  7. ^'Kabbalah, Torah, and Torah Codes -- People'. www.torahcode.net.
  8. ^'PUBLIC STATEMENT BY HAROLD GANS'(PDF).
  9. ^'Public Statement by Dr. Rips on Michael Drosnin's theories'. despatch.cth.com.au.
  10. ^'Bible Code - The Skeptic's Dictionary - Skepdic.com'. www.skepdic.com.
  11. ^'Bible Code Pictograms Bible Codes that form images that predict the future'. bible-codes.org. Retrieved October 6, 2010.
  12. ^'Find what you are looking for'. biblecodedigest.com. Archived from the original on October 26, 2010. Retrieved October 6, 2010.
  13. ^Sherman, R. Edwin, with Jacobi and Swaney. 2005. Bible Code Bombshell Green Forest, Ar.: New Leaf Press. 281–286
  14. ^J. Scott Duvall, J. Daniel Hays, 2012, Grasping God's Word: A Hands-On Approach to Reading, Interpreting, and Applying the Bible, p. 337. 'The scholarly rebuttals to Bible codes have been devastating. These rebuttals have provided strong evidence that there is nothing mystical or divine about ELS. The arguments leveled against this method of finding secret messages fall into two basic categories: that relating to probability, and that relating to textual variations.. Textual variations: Another flaw in the ELS approach is that its proponents seem unaware of variations in the text of the Old Testament..'
  15. ^B. McKay; D. Bar-Natan; M. Bar-Hillel & G. Kalai (1999). Solving the Bible Code Puzzle. Statistical Science 14. projecteuclid.org. pp. 150–73.
  16. ^Maya Bar-Hillel & Avishai Margali (December 1999). 'Madness in the Method'. dartmouth.edu. Retrieved October 6, 2010.
  17. ^H. J. Gans. 'A Primer on the Torah Codes Controversy for Laymen (part 1)'. aish.com. Archived from the original on March 18, 2008. Retrieved April 7, 2008.
  18. ^'Up Close with Harold Gans'. Jewish Action. September 2, 2007.
  19. ^B. McKay (2003). 'Brief notes on Gans Primer'. cs.anu.edu.au. Retrieved April 7, 2008.
  20. ^'Refutations'. Archived from the original on March 9, 2001.
  21. ^'No such tuning'. Archived from the original on October 13, 2007.
  22. ^'Response'. Archived from the original on July 1, 1998.
  23. ^'Non-response'. Retrieved May 2, 2010.
  24. ^'New Statistical Evidence for a Genuine Code in Genesis'. www.torahcodes.co.il. Archived from the original on February 5, 2007.
  25. ^'Smoke Screen'. www.torahcodes.co.il. Archived from the original on February 9, 2007.
  26. ^'Concerning Witztum's response to our article 'Codes in War and Peace – a reply to Doron Witztum''. Cs.anu.edu.au. June 15, 2001. Retrieved May 2, 2010.
  27. ^'Analysis of the 'Gans' Committee Report'(PDF). Archived from the original(PDF) on June 25, 2006. Retrieved May 2, 2010.
  28. ^^ Aumann, R.H., H. Furstenberg, I. Lapides, and D. Witztum (July 2004) (PDF). Analyses of the 'Gans' Committee Report (#365). Center for the Study of Rationality, The Hebrew University of Jerusalem. 'Archived copy'(PDF). Archived from the original(PDF) on June 25, 2006. Retrieved May 2, 2010.CS1 maint: Archived copy as title (link). Retrieved 2006-06-20.
  29. ^'Torah Codes: Redundant Encoding'.
  30. ^'Testing The Torah Code Hypothesis: The Experimental Protocol'(PDF).
  31. ^'The Bible Code'. Leaderu.com. Retrieved May 2, 2010.
  32. ^'Context of 'October 1995: Right-Wingers Call for Israeli Prime Minister Rabin's Death, Compare Israeli Government to Nazis''. Historycommons.org. Retrieved May 2, 2010.
  33. ^'The Bible 'Codes' – A Textual Perspective'. Sas.upenn.edu. Archived from the original on May 15, 2010. Retrieved May 2, 2010.
  34. ^Drosnin, Michael (September 11, 2001). Bible Code II: The Countdown. Google Books. ISBN978-0-14-200350-3. Retrieved May 2, 2010.
  35. ^Drosnin, Michael (September 11, 2001). Bible Code II: The Countdown. Google Books. ISBN978-0-14-200350-3. Retrieved May 2, 2010.
  36. ^'Libya Gives Up Nuclear and Chemical Weapons'. Commondreams.org. December 20, 2003. Archived from the original on June 28, 2010. Retrieved May 2, 2010.
  37. ^Drosnin, Michael (September 11, 2001). Bible Code II: The Countdown. Google Books. ISBN978-0-14-200350-3. Retrieved May 2, 2010.
  38. ^'Palestinian leader Arafat dies at 75'. CNN. November 11, 2004. Archived from the original on June 1, 2010. Retrieved April 26, 2010.
  39. ^Erlanger, Steven; Altman, Lawrence K. (December 14, 2003). 'Arafat died from stroke linked to infection, records show / Review finds poisoning unlikely, rebuts rumor that Palestinian leader had AIDS – SFGate'. San Francisco Chronicle. Retrieved May 2, 2010.
  40. ^Erlanger, Steven; Altman, Lawrence K. (September 8, 2005). 'Medical Records Say Arafat Died From a Stroke'. The New York Times. Retrieved April 26, 2010.
  41. ^'The Muslim Brotherhood Official English Website'. Ikhwanweb. Archived from the original on September 29, 2011. Retrieved May 2, 2010.
  42. ^'The Bible Code and Terrorism'. Ingermanson.com. Archived from the original on September 24, 2010. Retrieved May 2, 2010.
  43. ^'Torah Codes'. Cs.anu.edu.au. December 13, 2004. Archived from the original on April 18, 2010. Retrieved May 2, 2010.
  44. ^'Review of Michael Drosnin's Bible Code'. Rsingermanson.com. Retrieved May 2, 2010.
  45. ^'Barry Simon on Torah Codes'. Wopr.com. September 8, 1998. Archived from the original on January 30, 2009. Retrieved 2010-05-02.
  46. ^'Assassinations Foretold in Moby Dick'. Cs.anu.edu.au. Archived from the original on May 5, 2010. Retrieved May 2, 2010.
  47. ^Robert M. Haralick. 'Skeptical About the Reasoning of the Bible Code Skeptic'(PDF). torah-code.org. Retrieved October 6, 2010.
  48. ^'Can Anyone Beat George W. Bush in 2004?'. CNN. Retrieved April 26, 2010.
  49. ^Robert M. 'Skeptical About the Reasoning of the Bible Code Skeptic'(PDF). torah-code.org. Retrieved October 6, 2010.

Notes[edit]

  • Drosnin, Michael (1997). The Bible Code. USA: Simon & Schuster. ISBN0-684-81079-4.
  • Satinover, Jeffrey (1997). Cracking the Bible Code. New York: W. Morrow. ISBN0-688-15463-8.
  • Drosnin, Michael (1997). The Bible Code. UK: Weidenfeld & Nicolson. ISBN0-297-81995-X.
  • Drosnin, Michael (2002). The Bible Code II: The Countdown. USA: Viking Books. ISBN0-670-03210-7.
  • Drosnin, Michael (2002). The Bible Code II: The Countdown. UK: Weidenfeld & Nicolson. ISBN0-297-84249-8.
  • Drosnin, Michael (2006). The Bible Code III: The Quest. UK: Weidenfeld & Nicolson. ISBN0-297-84784-8.
  • Drosnin, Michael (2010). The Bible Code III: Saving the World. Worldmedia. ISBN0-615-39963-0.
  • Stanton, Phil (1998). The Bible Code – Fact or Fake?. Wheaton, IL: Crossway Books. ISBN0-89107-925-4.
  • Haralick, Robert M.; Rips, Eliyahu & Glazerson, Matiyahu (2005). Torah Codes: A Glimpse into the Infinite. Mazal & Bracha Publishing. ISBN0-9740493-9-5.

External links[edit]

  • Dunning, Brian. 'Skeptoid #408: The Bible Code: Enigmas for Dummies'. Skeptoid.
  • The Bible Code, transcript of a story which aired on BBC Two, Thursday November 20, 2003, featuring comments by Drosnin, Rips, and McKay.
  • Doron Witztum's codes page from Doron Witzum, a coauthor of the Statistical Sciences paper
  • Tutorial Website from Professor Robert Haralick
  • 'Scientific Refutation of the Bible Codes' by Brendan McKay (Computer Science, Australian National University) and others
  • The Bible Code: A Book Review by Allyn Jackson, plus Comments on the Bible Code by Shlomo Sternberg, Notices of the AMS September 1997 (see the American Mathematical Society)
  • The Bible 'Codes': a Textual Perspective, by Jeffrey H. Tigay (Near Eastern Languages and Civilizations, University of Pennsylvania)
  • Madness in the Method, by Maya Bar-Hillel and Avishai Margalit, Chance, Dartmouth College
  • Hidden Messages and The Bible Code from Committee for the Scientific Investigation of Claims of the Paranormal, publisher of Skeptical Inquirer Magazine
  • Trying to stay objective, by Remy Wilders (Computer Science, France)

Top Search Providers

Retrieved from 'https://en.wikipedia.org/w/index.php?title=Bible_code&oldid=912998243'