That is what I have come to expect of such web pages.
And it said "Coming soon."
And someone found out they can goto http://thisisstep2.com/.
Should I be able to say "But.. you aren't meant to go there!" ? At what point does your legal boundary lie for what is considered a public webpage and what is considered "not authorised."
That's where I see ease of access coming into it: If you really don't take any effort to keep me out of something (even as little as telling me "stay out"), how do I distinguish that unauthorized content from content I'm authorized to access — and not only that, but make the distinction before I access it?
Do I think you'd be convicted for manipulating URLs and grabbing their entire database? Very possibly.
Do I think you could incur five figures of legal headache in either scenario? Yes, I think you could, depending on how savvy the "victim" is and how close to "fight or flight" you push them.
The way it's been described so far, the reporter thought he had found an undocumented API...which, totally speaking out of guesswork here, could be as simple as seeing the json file being passed through the web inspector, seeing that there's an id field, and then iterating across it. The person has no expectation that when the id is of a private object, that the service would actually return that data.
Let me be clear: I don't think Kickstarter is going to go after the WSJ, or even that most companies would raise a huge stink about this.
This is a very common misconception among tech people about how the CFAA works.