That might be fine if they're prestigious, such as perhaps Google, but you really ought to think about taking a few years off being "public" carefully in the context of ever getting a job or being invited to co-found something...
"What's the best way to get across to a interviewer...?"
Just tell them. I wouldn't stress too much about it. If the person hiring you doesn't realize that there are tons of good programmers out there who don't blog, then you may not want to be working for them (i.e., they're newbies).
I remember vaguely a case based in Texas where the company was able to claim someone's home brewed work as their own.
I've had to sign a couple of documents that said that any work I created, at work or outside, that was in the domain of the company was owned by the company. This company happens to do software engineering, but I'm not particularly scared since my job has absolutely nothing to do with software engineering. I do, however, do "software engineering" outside of the company on my own time. I believe in order to prove that they own the IP to whatever else I produce, they'd have to prove that either I created it on their time, or that I created it using skills or tools I gained while employed there. They'd also get the IP under the work for hire law, if, say, I happened to be hired to produce some piece of IP, but I'd say that's pretty obvious.
http://en.wikipedia.org/wiki/Work_for_hire#Law_of_the_United...