-
希伯来书 4
- 1 我们既蒙留下,有进入他安息的应许,就当畏惧,免得我们(原文是你们)中间或有人似乎是赶不上了。
- 2 因为有福音传给我们,像传给他们一样;只是所听见的道与他们无益,因为他们没有信心与所听见的道调和。
- 3 但我们已经相信的人得以进入那安息,正如 神所说:「我在怒中起誓说:『他们断不可进入我的安息!』」其实造物之工,从创世以来已经成全了。
- 4 论到第七日,有一处说:「到第七日, 神就歇了他一切的工。」
- 5 又有一处说:「他们断不可进入我的安息!」
- 6 既有必进安息的人,那先前听见福音的,因为不信从,不得进去。
- 7 所以过了多年,就在大卫的书上,又限定一日,如以上所引的说:「你们今日若听他的话,就不可硬着心。」
- 8 若是约书亚已叫他们享了安息,后来 神就不再提别的日子了。
- 9 这样看来,必另有一安息日的安息为 神的子民存留。
- 10 因为那进入安息的,乃是歇了自己的工,正如 神歇了他的工一样。
- 11 所以,我们务必竭力进入那安息,免得有人学那不信从的样子跌倒了。
- 12 神的道是活泼的,是有功效的,比一切两刃的剑更快,甚至魂与灵,骨节与骨髓,都能刺入、剖开,连心中的思念和主意都能辨明。
- 13 并且被造的没有一样在他面前不显然的;原来万物在那与我们有关系的主眼前,都是赤露敞开的。
- 14 我们既然有一位已经升入高天尊荣的大祭司,就是 神的儿子耶稣,便当持定所承认的道。
- 15 因我们的大祭司并非不能体恤我们的软弱。他也曾凡事受过试探,与我们一样,只是他没有犯罪。
- 16 所以,我们只管坦然无惧地来到施恩的宝座前,为要得怜恤,蒙恩惠,作随时的帮助。
-
-
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
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.