Live data from Hacker News

Bible API

bible-api.com

51–60 of 308 posts

Re: Bible API

#52
post #42

Edit: my bad, I literally clicked on an example link provided in the page, which clearly shows the same URL format I used in my post, and edited the URL to have the strings for the Luke passage. I see that's the wrong syntax. Safari must be doing something funny… nope, that wasn't it. It was me, not noticing that %20 was an encoded + since it was mashed together with another number which threw me off. Earlier questio…

Nope you just have to get the URL right... http://bible-api.com/luke%2014:26

Re: Bible API

#53
post #42

Edit: my bad, I literally clicked on an example link provided in the page, which clearly shows the same URL format I used in my post, and edited the URL to have the strings for the Luke passage. I see that's the wrong syntax. Safari must be doing something funny… nope, that wasn't it. It was me, not noticing that %20 was an encoded + since it was mashed together with another number which threw me off. Earlier questio…

[deleted]

Re: Bible API

#54
post #38

Earlier quoted context omitted.

Apparently, the Bible is the Word of God. I'm not sure if copyright applies. Romans 13:1-2 says: "Obey the government, for God is the One who has put it there. There is no government anywhere that God has not placed in power. So those who refuse to obey the law of the land are refusing to obey God, and punishment will follow." Acts 5:29 says: "Peter and the other apostles replied: “We must obey God rather than human…

Additional edit: removing somewhat off-topic discussion that was replying to an example in the above comment, and discussion of whether a controversial passage was censored. And no, it was not censoring it (thanks to all of you who replied below pointing this out!). The issue was my incorrect editing of the URL without accounting for the fact that the URL contained URL-encoded characters, namely + as %20.

The documentation is pretty clear: http://bible-api.com/luke+14:26

Re: Bible API

#55
post #38

Earlier quoted context omitted.

Apparently, the Bible is the Word of God. I'm not sure if copyright applies. Romans 13:1-2 says: "Obey the government, for God is the One who has put it there. There is no government anywhere that God has not placed in power. So those who refuse to obey the law of the land are refusing to obey God, and punishment will follow." Acts 5:29 says: "Peter and the other apostles replied: “We must obey God rather than human…

Additional edit: removing somewhat off-topic discussion that was replying to an example in the above comment, and discussion of whether a controversial passage was censored. And no, it was not censoring it (thanks to all of you who replied below pointing this out!). The issue was my incorrect editing of the URL without accounting for the fact that the URL contained URL-encoded characters, namely + as %20.

It isn't censoring anything. Your url is incorrect.

Re: Bible API

#56
post #42

Edit: my bad, I literally clicked on an example link provided in the page, which clearly shows the same URL format I used in my post, and edited the URL to have the strings for the Luke passage. I see that's the wrong syntax. Safari must be doing something funny… nope, that wasn't it. It was me, not noticing that %20 was an encoded + since it was mashed together with another number which threw me off. Earlier questio…

I have the impression you purposefully messed the URL so you could leave that snarky comment.

Re: Bible API

#57
post #38

Earlier quoted context omitted.

Apparently, the Bible is the Word of God. I'm not sure if copyright applies. Romans 13:1-2 says: "Obey the government, for God is the One who has put it there. There is no government anywhere that God has not placed in power. So those who refuse to obey the law of the land are refusing to obey God, and punishment will follow." Acts 5:29 says: "Peter and the other apostles replied: “We must obey God rather than human…

Additional edit: removing somewhat off-topic discussion that was replying to an example in the above comment, and discussion of whether a controversial passage was censored. And no, it was not censoring it (thanks to all of you who replied below pointing this out!). The issue was my incorrect editing of the URL without accounting for the fact that the URL contained URL-encoded characters, namely + as %20.

It's not censored. You just have to use the correct URL.

https://bible-api.com/luke%2014:26

Re: Bible API

#58
One of the most interesting things to happen to the scriptures is their balkanization into verses. We generally don't atomize other writings that way, and when folks read the scriptures as a series of disconnected logical propositions all sorts of wackiness ensues. What would it look like to have an API for the collected works of Jane Austen that returned snippets (some of which are not even complete sentences)? How would that shape the way we read, say, Persuasion?

That hermeneutic - texts are collections of independent logical propositions - was essentially unknown in the ancient world, and cedes immense epistemological ground to the project of the enlightenment that is diametrically opposed to a Christian reading of the Scriptures, which emphasizes their unity and their role in liturgical worship.

Re: Bible API

#59

This is neat. This makes me curious about the licencing around popular translations, like the Jerusalem Bible or the NIV; is it not legal to post those translations??

Apparently, the Bible is the Word of God. I'm not sure if copyright applies. Romans 13:1-2 says: "Obey the government, for God is the One who has put it there. There is no government anywhere that God has not placed in power. So those who refuse to obey the law of the land are refusing to obey God, and punishment will follow." Acts 5:29 says: "Peter and the other apostles replied: “We must obey God rather than human…

Generally translations are subject to copyright and not considered inspired by Christians. There are a small minority of folks who consider the KJV an inspired translation, but that translation is too old for copyright law to speak to it.

Re: Bible API

#60
I wrote a bible desktop application and pulled in a bunch of translation and commentary from the swords project. I recommend looking into it if you're after the underlying data, nicely structured.
Post reply on HN