Sure. And valid question. My Sorry for the ambiguity.
In order to better integrate with the look-and-feel of sites, the plugin passes an argument on the embed code to remove the standard border and the "description" text at the top of the story (usually grey/italic below the title).
Realizing that the description was being stripped, starting with 1.0.4, on save, the plugin grabs the description, and sticks it in the post as normal in-post text directly above the story. Put another way, 1.0.4+ pulls the description out of the story and inserts it into the post.
Problem being then, from a UX standpoint, what happens if I had a story in a post previously, noticed the problem, and manually corrected it. I wouldn't want the plugin to now start double adding the description. So to err on the side of caution, it loops through prior posts, and if they have a story in them, sticks on a meta flag to indicate not to add the description.
The actual loop itself, in hindsight, does not scale well, and could have been done a lot smarter (e.g., just running an SQL query directly for
post_content LIKE %storify.com%).
Incrementing the DB version flag should prevent the loop from running, and assuming you don't have 20,000 Storify posts, you should be fine. Even if so, the description would only be inserted on save.
Hope that clears things up?