-
Joshua 20
- 1 And the Lord spak to Josue, and seide, Spek thou to the sones of Israel, and seie thou to hem,
- 2 Departe ye the citees of fugytyues, `ether of men exilid for vnwilful schedyng of blood, of whiche citees Y spak to you bi the hond of Moises,
- 3 that whoeuer sleeth vnwytyngli a man, fle to tho citees;
- 4 that whanne he hath fled to oon of these citees, he may ascape the ire of the neiybore, which is veniere of blood. And he schal stonde bifor the yatis of the citee, and he schal speke to the eldre men of that citee tho thingis that schulen preue hym innocent; and so thei schulen reseyue hym, and schulen yyue to hym place to dwelle.
- 5 And whanne the vengere of blood pursueth hym, thei schulen not bitake hym in to the hondis of the vengere; for vnwityngli he killide his neiybore, and is not preued his enemy bifor the secounde dai ethir the thridde dai.
- 6 And he schal dwelle in that citee, til he stonde bifor the doom, and yelde cause of his dede. And he that killide a man, dwelle `in that citee, til the grete preest die, which is in that tyme; thanne the mansleere schal turne ayen, and he schal entre in to his citee and hows, `fro which he fledde.
- 7 And thei ordeyneden Cedes in Galilee, of the hil of Neptalym, and Sichem in the hil of Effraym, and Cariatharbe, thilke is Ebron, in the hil of Juda.
- 8 And biyende Jordan, ayens the eest coost of Jerico, thei ordeyneden Bosor, which is set in the feeldi wildirnesse of the lynage of Ruben, and Ramoth in Galaad, of the lynage of Gad, and Gaulon in Basan, of the lynage of Manasses.
- 9 These citees weren ordeyned to alle the sones of Israel, and to comelyngis that dwellen among hem, that he that killide vnwityngli a man, schulde fle to tho citees; and he schulde not die in the hond of neiybore, coueitynge to venge the blood sched out, til he stood bifor the puple, to declare his cause.
-
-
King James Version (kjv)
- Afrikaans
- Albanian
- Arabic
- Armenian
- Basque
- Breton
- Calo
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- Dari
- Dutch
-
English
American King James Version (akjv) American Standard Version (asv) Basic English Bible (basicenglish) Douay Rheims (douayrheims) John Wycliffe Bible (c.1395) (wycliffe) King James Version (kjv) King James Version (1769) with Strongs Numbers and Morphology and CatchWords, including Apocrypha (without glosses) (kjva) Webster's Bible (wb) Weymouth NT (weymouth) William Tyndale Bible (1525/1530) (tyndale) World English Bible (web) Young's Literal Translation (ylt)
- English and Klingon.
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malagasy
- Malayalam
- Manx Gaelic
- Maori
- Mongolian
- Myanmar Burmse
- Ndebele
- Norwegian bokmal
- Norwegian nynorsk
- Pohnpeian
- Polish
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Serbian
- Shona
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Tausug
- Thai
- Tok Pisin
- Turkish
- Ukrainian
- Uma
- Vietnamese
-
-
Active Persistent Session:
To use a different persistent session key, simply add it above, and click the button below.
How This All Works
Your persistent session key, together with your favourite verse, authenticates you. It links to all your notes and tags in the Bible. You can share it with loved ones so they can see your notes and tags.
However, to modify your notes and tags, you need both the persistent session key and your favourite verse.
Please Keep Your Favourite Verse Private
Your persistent session key and favourite verse provide you exclusive access to edit your notes and tags. Think of your persistent session key as a username and your favourite verse as a password. Therefore, ensure your favourite verse is kept private.
The persistent session key allows viewing, while editing is only possible when the correct favourite verse is provided.
-
Loading...
-
Basic Hash Usage Explained
At getBible, we've established a robust system to keep our API synchronized with the Crosswire project's modules. Let me explain how this integration works in simple terms.
We source our Bible text directly from the Crosswire modules. To monitor any updates, we generate "hash values" for each chapter, book, and translation. These hash values serve as unique identifiers that change only when the underlying content changes, thereby ensuring a tight integration between getBible and the Crosswire modules.
Every month, an automated process runs for approximately three hours. During this window, we fetch the latest Bible text from the Crosswire modules. Subsequently, we compare the new hash values and the text with the previous ones. Any detected changes trigger updates to both our official getBible hash repository and the Bible API for all affected translations. This system has been operating seamlessly for several years.
Once the updates are complete, any application utilizing our Bible API should monitor the hash values at the chapter, book, or translation level. Spotting a change in these values indicates that they should update their respective systems.
Hash values can change due to various reasons, including textual corrections like adding omitted verses, rectifying spelling errors, or addressing any discrepancies flagged by the publishers maintaining the modules at Crosswire.
The Crosswire initiative, also known as the SWORD Project, is the "source of truth" for getBible. Any modifications in the Crosswire modules get reflected in our API within days, ensuring our users access the most precise and current Bible text. We pledge to uphold this standard as long as getBible exists and our build scripts remain operational.
We're united in our mission to preserve the integrity and authenticity of the Bible text. If you have questions or require additional information, please use our support system. We're here to assist and will respond promptly.
Thank you for your understanding and for being an integral part of the getBible community.
Favourite Verse
You should select one of your favourite verses.
This verse in combination with your session key will be used to authenticate you in the future.
This is currently the active session key.
Should you have another session key from a previous session.
You can add it here to load your previous session.