Category: Company Insights

Posted on

PocketBible for Windows Progress Update #14

Seriously, this should have been our first clue, right?

The last 3 months have been interesting. One of our ticking time-bombs exploded and we’re working hard to rebuild. Let me explain…

As we explained in the video that launched this project, when we originally designed PocketBible we put a lot of intelligence about specific Bibles into the program itself. This was done so that PocketBible could handle differences in versification between Bibles. A simple example is 3 John 14-15. These are two separate verses in some Bibles and are combined into verse 14 in other Bibles. As a result, if you highlight 3 John 15 in a Bible that has that verse but are reading a Bible that does not have that verse, we apply the 3 John 15 highlight to 3 John 14 (if it isn’t already highlighted), not because it’s the last verse of the chapter and there isn’t a verse 15, but because, in a 14-verse version of 3 John, verse 14 contains the contents of verse 15 and therefore is verse 15 (and verse 14).

3 John 13-14 (King James Version)3 John 13-15 (New American Standard Bible)
13I had many things to write, but I will not with ink and pen write unto thee:
14But I trust I shall shortly see thee, and we shall speak face to face. Peace be to thee. Our friends salute thee. Greet the friends by name.		13I had many things to write to you, but I do not want to write to you with pen and ink; 14but I hope to see you shortly, and we will speak face to face.
15Peace be to you. The friends greet you. Greet the friends by name.
Some Bibles split 3 John 14 into two verses (or, if you prefer, some Bibles combine verses 14 and 15 into one verse and call it 14).

Solving issues like this was originally done in the code. So there’d be a whole sequence of steps like, “If this Bible references is in 3 John and the verse number is 15 but the Bible you want to map it to has a version of 3 John that only has 14 verses, then set the verse number to 14.” This was fine when the number of these cases was relatively small. But as we added more and more Bibles, there turned out to be hundreds of these.

The solution was to describe all the mappings in a table containing the “from” book, chapter, and verse, and the “to” book, chapter, and verse for each weird situation. The data tables that describe this mapping are huge and complicated. There are between 1500 and 2000 of these “special cases” in PocketBible. And this is just one of the required data tables. There is another table that tell us which version of each book of the Bible is in each of the Bibles (so we can tell if a particular Bible has the version of 3 John with 14 or 15 verses, for example). Another table maps each of these different versions of the books of the Bible to their names. (So that we can tell that both versions of 3 John should be called “3 John”.) A variety of other data tables help us deal with these issues.

The problem with putting this information into PocketBible (whether directly in the code in a series of “if this then do this” statements or in tables that can be iterated and processed by code) is that anytime we release a new Bible with a new versification scheme for one or more of its books, we have to update every version of PocketBible. Currently that list would include PocketBible for iOS, Android, macOS, Windows Store, Windows Desktop, and the new Windows Version — six different apps would have to be modified. Three of those six share the code that contains these tables. That is, they all use the same code in the same language to process Bible references, and it is written in C++. So once we add a new Bible to the C++ code, the iOS, macOS, and Windows Desktop products are done. But the Android app is in Java, the Windows Store app is in C#, and the new Windows app is in JavaScript. So that means the same changes have to be made in 4 different languages, then 6 different apps have to be rebuilt.

Building the app for every platform is tedious, error-prone, and time-consuming. On top of that, over time it gets to where it can’t be done. We were still supporting PocketBible for Palm OS long after it got to where it was impractical to build a new version of the app. Ditto PocketBible for Windows CE and Pocket PC. And then there was PocketBible for webOS and Blackberry that were created by outside developers. In other words, this was just a bad design.

So in 2015 we decided to redesign our LBK files so that these tasks were not performed in the code, but were all described in tables that could be packaged with each Bible. That way, the app could look at each Bible as it was installed and if it contained a more recent version of these tables than what the app already knew about, it would update its tables with those contained in the LBK file. This would allow a new Bible completely unknown to PocketBible to be released and it would function as if PocketBible knew about it all along.

When we contacted the developer of the Windows Store app about these changes, he wasn’t excited about making them because of the time involved. And when we started digging into the old (old at that time; older still now) Windows Desktop code, we realized it would be all but impossible to update that app to include compatibility with these new Bibles. (Remember also that at this time it was unclear whether the Windows Desktop app was even going to continue to be used because supposedly the world was transitioning to the awful Modern User Interface paradigm of Windows 8. So it was unclear whether or not it would be worth the time to update it.)

We decided to go ahead with the new LBK Bible format anyway. It would just mean that new Bibles wouldn’t work on the Windows platform — at least not until the Windows Store version was updated. What we didn’t know at the time was that it never would be.

As you know, this became one of the primary motivations to re-write PocketBible for Windows. The new version already implements compatibility with the new LBK format for Bibles.

Psalm 68:11-14 NASBPsalm 68:12a-15 NAB
11The Lord gives the command;
The women who proclaim good news are a great army:
12“Kings of armies flee, they flee,
And she who remains at home will divide the spoils!”
13When you lie down among the sheepfolds,
You are like the wings of a dove covered with silver,
And its pinions with glistening gold.
14When the Almighty scattered the kings there,
It was snowing in Zalmon.		12aThe Lord announced the news of victory:
13a“The kings and their armies are in desperate flight.
12bAll you people so numerous,
14awill you stay by the sheepfolds?
13bEvery household will share the booty,
14bperhaps a dove sheathed with silver,
14cits wings covered with yellow gold.”
15When the Almighty routed the kings there, the spoils were scattered like snow on Zalmon.
This is the same passage in two different Bibles. Verse division is completely different and involves the rearranging of the text and suffixes on the verse numbers.

What we didn’t realize is that we had been lying to ourselves about no longer needing to update the code in PocketBible when a new Bible was released. There were conditions under which that lie was definitely true. But there were still small, special cases scattered throughout the code and not handled by a data table in the LBK file. For example, some Bibles contain verses with suffixes, like Isaiah 14:25b and Psalm 68:12a, 12b, 13a, 13b, 14a, 14b, and 14c. In the apocrypha, Sirach has a chapter called “Prologue” that is called “Forward” in some Bibles. Esther has chapters A-F in addition to its numbered chapters. While we could map all of these verses to their corresponding verses in other Bibles using the tables that we had moved into the LBK file, when we wanted to print out the Bible reference “Psalm 68:12b” there was a piece of code that got called to look at the stored verse number (which was 14 in this case — 12a was 12, 13a was 13, and 12b was 14) and return the correct “spelling” of that verse number (the 14th verse in Psalm 68 is “12b”).

This all came to the boiling point with the pending release of several new and updated Bibles. While updating the data tables that would make these new Bibles work on any version of PocketBible including the new Windows app, I realized I would also have to deal with some of the special cases in the code itself. And that meant doing the very thing that we had told ourselves we’d never need to do again — simultaneously updating the iOS, Android, macOS, and new Windows versions of PocketBible.

The only reasonable plan forward is to finish what we started back in 2015. So for the last couple of months I’ve been working in both our BookBuilder app and the macOS version of PocketBible (since its code is easiest to work with while working on BookBuilder) to move special cases out of the code and into data tables, then adding code to write those data tables into the LBK file, then adding code to read them into PocketBible when necessary. For each special case in the code, the code has to be rewritten to use the data tables instead. All of this has to be tested and will have to be tested on each platform into which we roll this new code.

What this means is that once I finish doing this in the macOS version, I need to do the same in the iOS version (should be quick since it’s the same code that is used in both the macOS and iOS versions), then re-write it in Java for Android, then release all those new versions to their respective stores, then update the new Windows version (re-write for a third time, this time in JavaScript) and test it there.

So that’s what I’ve been doing so far this year. How’s your 2023 going?

Meanwhile…

In the meantime, we’re moving on to Advanced Feature Set features in the Windows version.

The ability to create saved layouts has been implemented similar to how it exists in the macOS version. You can create a new layout, give it a name, and it will appear as a tab across the top of the screen. These tabs can be dragged around to re-order them, and they can be renamed. This will get awkward if you have more than a handful of layouts, but should work for most people who would like to dedicate a screen layout to devotional reading and another to study.

Screenshot showing 3 layout tabs: “Default Layout”, “Greek and Hebrew”, and “Today”. When “Today’s Reading” is selected on the toolbar, we’re taken to the “Today” tab and our devotional goes to the reading for today (which was March 17, 2023). Note that the date at the top of the pane (January 1) is incorrect; this is a debug build with some diagnostic code in place.

Related to the above, we’ve added a toolbar button labelled “Today” that will activate a devotional and take you to today’s reading. If you have a layout named “Today”, this button will activate your layout named “Today” and show today’s reading in the active devotional. This is not unlike the same feature in the macOS version of PocketBible.

Setting voice preferences. Note that we’re running on a Mac here, so the available voices are those from macOS. They would be different on Windows.

Quite a bit of progress has been made on implementing a “Speak” feature. The app uses the synthesized speech voices built into Windows to read to you. You can read the selected text, the selected verse(s), or start reading at the top of the page and continue until you tell it to stop. Toolbar buttons have been added to control this feature. You’ll be able to choose your voice and the rate at which it is speaking. Different voices will be available for English, Spanish, and Greek, assuming you have them installed. This will all be similar to the macOS version, which uses the synthesized voices built into macOS.

Some smaller tasks have also been accomplished:

  • Ability to remove an installed book.
  • Solved some very tricky issues related to date calculations in devotionals.
  • More tricky issues related to going to a particular place in a book (say the reading for today in a devotional) and the program getting confused about where it was at.
  • Better detection of AFS subscription changes and how that affects options you may have selected that require an active subscription.
Posted on

No, Not That Apple

Adam and Eve in the Garden of Eden by Wenzel Peter

Because we’re a Bible software company and because we produce software for Apple devices (iOS and macOS), we sometimes hear from people who are concerned because of Apple’s deep connections to evil and the influences of Satan. The most frequent evidence cited is the Apple logo, which is clearly the same apple from which Eve took a bite before handing it off to her husband, thus condemning all of humanity.

First of all, the fruit of the Tree of the Knowledge of Good and Evil was not an apple. Apples grow on apple trees. You’ve never seen a Tree of the Knowledge of Good and Evil, so you don’t know what its fruit looks like. Or tastes like. And the Bible just says “the fruit”, not “the apple”.

So we could stop there and move on to a more useful topic. But let’s continue.

The Original Logo

Ignoring for a moment that there was no apple in the story of the fall in Genesis 3, and therefore the Apple apple could not refer to the Eden “apple”, it’s reasonable to ask, “Then where did the Apple logo come from?”

The original logo of Apple Computer Co. was this woodcut. In it, we see Sir Isaac Newton about to “discover” gravity when an apple falls on his head. The story is undoubtedly apocryphal, but, just like we imagine naked Adam and Eve gorging themselves on apples behind conveniently arranged foliage, the image of Sir Isaac Newton sitting under an apple tree in his Sunday best while reading a book is how we imagine gravity being discovered.

The falling apple inspired Newton to think about gravity. The name “Apple Computer Co.” stands for inspiration and discovery. That’s what the company wanted to be identified with. Hence the incorporation of the apple (and Isaac Newton — a God-fearing Christian, by the way) into Apple’s logo.

The Modern Logo

Very early in their history, the folks at Apple discovered it was difficult to reproduce this complex image on their products. So they reduced it to the essential image of the silhouette of an apple with a bite taken out of it.

“Aha!” you might exclaim. “That’s the bite by which Eve disobeyed God!” You would exclaim that right before I smacked you upside the head and reminded you that the fruit of the Tree of the Knowledge of Good and Evil was not an apple, but rather was the fruit of the Tree of the Knowledge of Good and Evil.

No, the bite out of the Apple logo apple serves three purposes. First, it distinguishes the silhouetted apple from the similar-looking cherry (which is also not the fruit of the Tree of the Knowledge of Good and Evil, by the way). Second, it is a play on the word “byte”, the technical term for 8 bits of computer memory*. Finally, it is an homage to famed computer science pioneer Alan Turing, who died by his own hand and was found with a half-eaten apple at his bedside.

As tempting as it is to don my tinfoil hat and go looking for conspiracies behind every (apple) tree, I’m not biting. Not on this one. Sorry.

* A byte is 8 bits of memory. A half-byte (4 bits) is called a nybble. Yes, we computer nerds are a witty lot.

Posted on

PocketBible 2022 User Survey Results

We just completed a survey of our PocketBible users and I thought I’d share a few results with you. This isn’t everything and it’s not even every important thing. But some of this is interesting and might help you understand who your fellow PocketBible users are, and in some cases, why we might make the choices we do when it comes to the products we create for PocketBible.

Demographics

The majority of you are male, and are 55 or older. To some peoples’ surprise, you are not preachers — though most of you have some kind of teaching ministry.

This is consistent with what we’ve come to know about our PocketBible users. I believe that our age (yes, I’m in that “over 55” group, too) puts us in a generation that trusts the authority of the Bible and therefore wants to know more about it. We also believe there are people smarter than us who have things to say about the Bible from whom we can learn. Younger people tend to value the experience of God. They learn about God through their community experiences with their fellow believers. As a result they have less dependence on the kind of commentary and research tools at which PocketBible excels. Not all of them, of course; we continue to add new users of all ages to the PocketBible family.

Beliefs

Half of you choose the label “Bible-believing” to describe your Christian beliefs. One-third use the term “evangelical”. About a quarter of you are comfortable with “nondenominational” or “Baptist”. These terms aren’t mutually exclusive so the totals add up to more than 100% with a lot of overlap. Terms that mention specific denominations score in the single digits: “Methodist”, “Presbyterian”, “Anglican”, “Lutheran”, and “Catholic”, for example.

This is consistent with what we know from being in the Christian publishing business for over 30 years now. People who purchase Bibles and Bible study materials tend to be on the more theologically “conservative” end of the spectrum and they tend to describe themselves as neither Catholic nor Protestant. That “Bible-believing” term sums up who they are. This has been true the entire time I’ve been in this business.

And it makes sense. These are the kind of people who are encouraged by the churches they attend to study the Bible for themselves and not to depend on a formal member of the clergy to answer their questions. Even the least leadership-oriented person in this group has a small but useful Bible library, which may or may not be entirely digital.

Bible Reading

80% of you spend time reading the Bible every day (or nearly every day). The majority of those are either using PocketBible’s devotional features or following an external plan but using PocketBible to read the Bible. They spend about 12 minutes per day just reading the Bible.

I find that encouraging. I believe it’s important for Christians to read and understand the Bible. It’s our most direct way of getting instruction from God.

Online Habits

Most of you are still using Google for searches even though it puts your privacy at risk. The next most popular choice is arguably the right one: Duck Duck Go.

A few of you, when asked what search engine you use, told us you use Edge or Firefox. Please — Edge and Firefox are browsers. A browser is how you access the Web. A search engine is a website you use to perform searches. Most browsers allow you to choose a default search engine. This allows you to type some search words into the address line in your browser and it will automatically invoke your chosen search engine to perform the search.

More depressing than this is that a few of you reported that Edge and Safari are the websites you most frequently visit. Edge and Safari are browsers. A browser is an app you use to access the Web. You view a website in a browser, but the browser is not the website.

Use of PocketBible

Most of you use PocketBible every day and almost 90% use it more than just in church on Sunday.

Over 80% of you use PocketBible most of the time on either a phone or tablet. This is consistent with how we target our marketing of what we do — we are a mobile app developer and always have been. That less-than-20% who use it primarily on a desktop or laptop will argue with us about that and point out that Windows is the most popular operating system. Until we point out that Windows is the most popular desktop operating system. If you expand your scope to all computing devices, then Android OS is actually installed on more devices than Windows.

Hey, I don’t make these things up. I just write the code. 🙂

Satisfaction

Over 90% of you are somewhat or very satisfied with PocketBible. You are most interested in the same kinds of resources that we are already producing — commentaries, dictionaries, Bibles, and atlases. You have some very specific recommendations in some cases, and we’ve made a note of those.

We also are pouring over your criticisms. We can’t always respond to these but they help us understand where you all are coming from.

This is just a quick overview of the portions of the survey that I thought might be of general interest. There are 37 pages of 8-point text with your comments, suggestions, and complaints. Those are tough to summarize but are arguably the most helpful.

Thanks to those of you who participated and claimed your $10 coupon. The rest of you — we’ll do this again next year. 🙂

Posted on

Let’s Keep the “X” in “Xmas”

From time to time, PocketBible users will complain about our use of XMAS in a promotional priority code in one of our marketing emails — hence this article.

Christians and Christian values are under attack in America today. It’s nothing like what’s happening elsewhere in the world, of course, but given that this country was founded on biblical principles by people who held Christian beliefs, it is especially troubling to see those principles and beliefs under direct attack.

Because of the constant bullying we all face from people who claim to be “open minded” and “tolerant of differences”, we are sometimes quick to see offense where none really exists. The concern that some Christians have over the use of the abbreviation Xmas for Christmas is one such situation.

The X in Xmas is actually the Greek letter chi, which is the first letter in the Greek word Χριστος (christos), from which we get “Christ”. Its counterpart “X” has been used as an abbreviation for Christ for as many as 1000 years — maybe more. The abbreviations X, Xt, and Xr can be found in Early Modern English texts written by Christians from the 1700’s. In no case was it used to “remove Christ” from the text, but rather as a simple shorthand. It may also have been a recognition of the sacred nature of the name — in the same way that speaking the name of God was prohibited among the Jews, resulting in the unpronounceable 4-letter name (יהוה) that we sometimes see as YHWH in English. The substitution of chi for “Christ” was never meant as an insult but was used by Christians as a way of writing Jesus’ name.

Christianity is full of symbols. The cross in its various forms (the simple ✞ and many variations, including ⳩ and ⳨) is one. The dove that we use in our PocketBible icon is another. Then there’s the “fish” symbol. None of these are intended to denigrate the name of Jesus nor are they some kind of blasphemy. Instead, they are just easily recognized shorthand for the concepts they represent.

To the Christian, the X or chi in Xmas honors Jesus, while at the same time connecting us across time to our ancient brothers and sisters in Christ. It is the “secret handshake” that communicates deep spiritual truths that are evident to the believer but hidden from the world. So well hidden, in fact, that some well-meaning believers actually resist its use, arguing that it removes “Christ” from “Christmas”. But they are ignorant of the long history of Christian symbolism. “Xmas” is a Christian term, invented by Christians, with a long history of use in Christian literature, based on the ancient practice of abbreviating the title “Christ” with the Greek letter ​chi​. It is not the invention of modern political progressives to remove Jesus from the name of the holiday that celebrates his birth.

Ironically, when a modern-day enemy of Christianity tries to remove Christ from Christmas by replacing it with an X, they are actually acknowledging him. 🙂

There are plenty of reasons to be concerned about the animosity that exists in our society between Christians and non-Christians. But the use of Xmas as shorthand for Christmas is not one of them.

Posted on

“I heard that the author of that book eats babies. Are you going to drop their titles?”

From time to time, some controversy will arise over something an author publishes with which some faction of Christianity disagrees. We’ll get emails from users requesting that we drop that author’s work from our product line. Often they point out that this author has previously been associated with some other Christian leader, whose work we also publish, and that we should drop that person’s work, too. Our response has always been the same.

We are a book store, not your pastor or spiritual mentor. We stock a wide variety of doctrinal perspectives. We base our publishing decisions a lot on what our customers request. We don’t want to waste our time creating a book nobody wants.

We trust you to choose material based on your own research. We don’t select books for you; we merely provide them for you to select from. If you don’t like the doctrinal positions of a particular author, don’t buy their books. There are plenty of others.

No author is perfect. No reader is perfect. We’re not perfect. If we refused to distribute books from authors with whom we disagreed on a minor point of interpretation, and if we refused to sell to people who have ever sinned, we would have to shut down and go live in the woods. We’re not going to do that. We’re not going to compel everyone around us to comply with our standard of belief and behavior; we have trouble enough following it ourselves.

So thanks for thinking of us, but we don’t participate in this type of debate and character assassination. Never have.

Photo by Fred Kearney on Unsplash

Posted on

PocketBible is on MeWe

With more PocketBible users making the move from Facebook to MeWe, we thought we should be there, too. We’re not leaving Facebook, just adding a MeWe page. You can click here or search for PocketBible on MeWe. When you find us, follow us.

For those of you who have never heard of MeWe, it’s like Facebook except without the ads and the censorship of certain points of view. It’s free like Facebook, but you can get access to premium features for a small fee. The free version seems to work great, though.

We’ve been happily posting on Facebook since March 2008 and have no plans to leave. We have, however, left Twitter and have no plans to return. It didn’t really fit our needs, nor, apparently, the needs of the majority of PocketBible users.

Posted on

To What Are You Blind?

Photo by Josh Calabrese on Unsplash

I used to spend two or three days per week working from various coffee shops around town. Most of them open at 6AM. I’d be there right as the doors open and stay through the entire day. It wasn’t unusual to have to wait in line at 6AM as everyone stopped by to get a coffee and pastry on their way to work.

There’s a coffee shop right next door to my office. It opens at 7AM. I asked the owner why she didn’t open earlier. After all, her competitors are already open. She’s giving up a lot of business. “I don’t want to get up that early,” she said. One time I asked if they had anything for lunch. She said they do lunch but only on Thursdays. She makes some quiche and when it runs out, there’s no more lunch until next Thursday.

There’s another coffee shop farther away that opens at 6AM according to their sign, but when I showed up early one day I was surprised to find the lights on and the door open. The owner told me, “I get here about 4:45 and the first thing I do is unlock the door and put coffee on. So if you get here early and the doors are open, you’ll probably be able to get a cup.”

I looked around and noticed there was nothing for lunch. I asked if they served sandwiches. He pointed to the door on the wall across from the counter and said, “That door takes you to the restaurant next door. You can get food there and bring it here, or take your coffee with you over there when you want some lunch.”

I would argue that the lazy lady next door doesn’t know what business she’s in nor who her customers are. The guy who opens early and sends people to the restaurant next door has transcended the coffee shop business and is operating at a state of consciousness that the lady next door can’t even imagine, let alone perceive.

We have a publisher with whom we’d like to do business. They have a Bible translation that we get a lot of requests for. They refuse to license it because they want to protect their own internal sales. They don’t have a software version of this Bible; they just have print. But they worry that an electronic version will cannibalize their print sales.

Electronic publishing costs traditional print publishers nothing. It only generates royalty revenue. It is money applied directly to the bottom line. People purchase electronic books that they would never buy in print, and people who are still buying print in 2020 are not buying electronic Bibles. There are exceptions and the two worlds definitely intersect, but it’s difficult to argue that one robs from the other when you’re looking at a particular title. I would argue that in an effort not to lose the revenue stream with which they are familiar, this publisher is blind to no-cost, revenue-only opportunities. These opportunities are knocking directly on his door, coming to him. He doesn’t even have to work hard to take advantage of them.

I spend a lot of time thinking about what I’m blind to in my business. The coffee shop next door doesn’t realize they’re a coffee shop, and that people want a cup of coffee on their way to work. They aren’t going to her shop. They didn’t realize that serving lunch only one day a week is like not serving lunch. Publishers come out of marketing and sales meetings where they struggle with how to increase revenue, then tell a no-cost revenue stream that they’re not interested in taking money from them. I worry that I’m doing some outrageously silly thing. Other than wasting my time writing blog articles that no one will read, what am I blind to?

Posted on

Laridian Account Security Updates

We don’t talk much about security issues at our website for obvious reasons – any information we provide could inform a hacker and provide them a shortcut to circumventing security on our site. We’ve recently made some changes that we want you to be aware of for a couple of reasons: First, the changes are comprehensive and as a result, could affect you in ways we haven’t anticipated. Second, we want to reassure you that your information is and always has been secure.

Let’s take that last point first: Laridian doesn’t store your PayPal username or password, nor do we store your credit card number on our servers. When you make a payment, you are interacting directly with either PayPal or our payment processor, Authorize.Net. Your financial information does not even pass through our server on its way to those companies. So we have no opportunity to store it even if we wanted to.

This is important. It means that your financial information isn’t here, even if someone did break in looking for it. It is being handled by companies that are significantly more sophisticated and more security-conscious than we are. The data breaches you read about don’t generally happen at banks and credit card processors. They are almost always the result of a retail store or online shopping site with lax security. Laridian avoids these attacks by simply not being in possession of any of that information.

The first point, that the changes are extensive and at least in some small degree affect all users, is addressed below.

What Changed

The changes we’ve made are fairly comprehensive and as a result it’s possible that you’ll have trouble signing into your account if you have inadvertently been taking advantage of a shortcoming in our previous account security methods.

Prior to about January 4, 2020, your Laridian account password was stored in our database in plain text. That’s a little unusual (and arguably unsafe), but it’s the result of the fact that our original website and database implementation was done by an outside company over 20 years ago when security standards for the Internet were very different. While standards have changed, making changes to security protocols while allowing thousands of users acquired over more than 20 years to continue to access their accounts is very challenging. So addressing this issue is something we have avoided for a long time.

Even though passwords were stored in plain text, they were (and are) encrypted when transmitted from PocketBible, and the database itself is behind a firewall. The encryption makes it unlikely that someone could grab your password by monitoring your Internet traffic, and the firewall isolates the database from the Web. Both the database and the server it is hosted on require secure account login, so it would be relatively difficult for someone to access it and view user passwords. Since we weren’t protecting any financial information, we weren’t strongly motivated to make this change.

There were three main problems in the old implementation:

  1. Passwords used to be case insensitive. If your password was PASSword, you could log in with password, Password, or PaSsWoRd. This was apparently caused by the original programmer not understanding that the database was configured to do case-insensitive searches. When we discovered it later, we already had users who were inadvertently taking advantage of this misbehavior, so it became at least difficult, if not impossible, to easily change.
  2. We used to truncate all passwords to 10 characters even if you entered more than that. If your password was password1234, you could log in with password12, password12#$, or password1234567890. The original programmer allowed for longer passwords in the database and in his code, but accidentally limited the length of password fields by the way pages on our website were written. Again, once we figured this out we already had thousands of users who were taking advantage of this without realizing it, so we couldn’t easily change it.
  3. As mentioned before, passwords were stored in plain text in the database. This was the result of the naïve belief by the original implementor that password-protecting the database and the server was sufficient to secure this information. This turned out to be true, but we felt we could do better.

The new method addresses all of the above issues:

  1. Passwords are now case sensitive. If your password is PASSword, then you must enter PASSword or you don’t get in.
  2. The new method does not put a practical limit on the length of passwords. There is a limit, but you won’t encounter it unless you want to type for a long, long time. You could create a 1,000,000-character password if you want. It just wouldn’t be practical.
  3. Your password isn’t stored anywhere.

Wait, what? If the password isn’t stored, how are you able to log in?

The way the new system works is that your password is run through what’s called a hash algorithm. This algorithm calculates a unique value that represents your password. So even if a hacker were able to gain access to the database, they would only have indecipherable numbers, not your password.

The has algorithm is one-way. That is, it’s trivial to calculate the hash value from your password, but it is theoretically impossible to generate your password given the hash value. Again, if our theoretical hacker had a list of hash values, they could not reverse-engineer those values and figure out the passwords that generated them.

When you log into your account, we run the password you give us through the same algorithm to produce a hash value, then we compare that number to the number in the database. If they match, you get in. If not, you don’t.

How You Are Affected

Because of the way we phased in the changes, you shouldn’t notice anything different unless you were accidentally using upper/lower case in a way that didn’t match your original password. If your password is longer than 10 characters, we’ll still use just the first 10 characters to log you in. If you create a new password that is longer than 10 characters, we’ll use the full password.

As mentioned before, changing the way passwords are stored and used on our site and in our apps affects virtually everything we do:

  • Obviously, logging into your account on our website is affected.
  • Viewing the list of books you own from inside one of our apps depends on PocketBible being able to log into your account.
  • Synchronizing your notes/highlights/bookmarks with the Laridian Cloud depends on PocketBible being able to log into your account.
  • PocketBible for Windows Desktop uses an older version of synchronization with our iPocketBible.com server, which is different than the other apps use and takes a different path to log into your account.
  • Requesting a password-reset link from our site works the same way as before but internally is significantly different.

As a result, there could be problems in some remote corner of one of our apps or on our website that we haven’t discovered yet. If you run into any problems, contact us at [email protected]

Posted on

What Americans Believe

Every other year, Ligonier Ministries conduct The State of Theology survey. In it, they question Americans about their religious beliefs. As you might expect, the results are generally disappointing.

While it’s easy to blame one’s neighbor for believing that humans are basically good, or blame the person sitting next to you at church for believing that religious belief is not about Truth but about personal opinion, the fact of the matter is that they’re often not getting good teaching.

I’ve spent the last 30 years helping pastors, teachers, and everyday Christians have everything they need to understand and apply what they read in the Bible. Whether it was QuickVerse for MS-DOS in 1988, PalmBible for Windows CE in 1998, or PocketBible for iOS and Mac OS in 2018, the goal has always been to put the tools in peoples’ hands to help them discover what the Bible has to say and to teach others what they’ve learned.

While the general philosophy of those around us drifts farther and farther from Truth, it’s important that we stay firmly grounded and that we share that Truth with others.

Read the complete survey results here. Read about our new Pastors and Teachers Library here.

Posted on

King James Version: Red Letters and Paragraphs

Title_PageBack in October, 2014 we updated our King James Version text. We had taken some criticism for publishing a low-quality edition of the text which couldn’t seem to be traced back to any known edition of the KJV.

Red Letters

When we published that version, we intentionally left out the “words of Christ in red” feature, because the whole goal was to get to a pedigreed version of the text and red letters were not a part of the KJV text until relatively recently.

This didn’t go over well with folks who rely on red ink to know when Jesus is speaking. So we did more research to see if we could come up with an “authoritative” red-letter edition of the KJV on which to base our editorial decisions. To our surprise, we found one.

In 1899, Louis Klopsch (1852-1910), editor of The Christian Herald, was writing an editorial for his magazine when he read Luke 22:20: “This cup is the new testament in my blood, which is shed for you.” It struck him that a New Testament with Christ’s words written in “blood” would be both useful and highly symbolic. He approached his mentor, Rev. T DeWitt Talmage with the idea, and the men agreed, “It could do no harm and it most certainly could do much good.”

Klopsch Red Letter BibleRight away they discovered that the KJV contains no quotation marks to delineate those words spoken by Jesus and separate them from those of the narrator or other characters in the story. It also occurred to them that there are instances in the Old Testament where it is believed that Jesus appeared to the Old Testament saints and spoke to them. Should those words be in red? What about the words of Jesus when spoken by others in the book of Acts or the epistles?

Klopsch had to make a few choices (such as in John 3:16ff) about where Jesus’ words end and the narrator’s begin. He opted to omit Old Testament christophanies, but to include New Testament quotes in red. The first red-letter New Testament was published in 1899, and an entire Bible, containing the red-letter New Testament, was published in 1901.

Laridian was able to obtain a 1903 New Testament and a 1913 whole Bible, each with Klopsch’s original red-letter text. The New Testament claims an 1899 copyright and the whole Bible, 1901. From these well-used pages we manually marked up our electronic text to indicate the words of Christ.

Paragraphs

Soon after publishing our updated KJV last year we realized that the text we had worked from did not contain paragraph indicators of any kind. With a little effort we were able to find a source of that information that is consistent with the age and quality of the text itself, and have integrated that information into our text.

The King James Version has historically been printed with each verse starting on a new line, and a pilcrow (¶) marking the start of a new paragraph. We have followed that tradition, which means that in versions of PocketBible that allow you to display the text in paragraph form or one verse per line, you will always see the KJV text presented with each verse starting on a new line.

While some might argue that this format is jarring to the modern reader, we would point out that that KJV itself is “jarring” to the modern reader. We think there is great value in upholding the publishing traditions that add to the unique character of the King James Version of the Bible, and are very happy with the results of this effort to update our version of the text.

Most PocketBible users will see a note on the “Add/Remove Books”, “Cloud Library”, or “Download Books” screen in PocketBible to the effect that the KJV and KJV with Strong’s Numbers texts have been updated. Select the updated product to download it to PocketBible. Windows Desktop users will have to download the setup program for the KJV or KJVEC from the Downloads area of our website.