If you start from this statement and read the rest of the article I think it's a good start to better understand the parameters of the article. Post-medium publishing is an area I'm working on and I must say reading this article gives me another way to think about the problem.
"... If free copies of your content are available online, then you're competing with publishing's form of distribution, and that's just as bad as being a publisher ..."
Instead of looking how to make money I was looking at "solving a what users want" and still exploring the "and willing to pay for" bit. In this case users want "instructions" to build stuff but the cost of magazine producers is pretty high and the alternatives are primitive. Not making the "instructions" free or at least freeium-ish means a "chicken and the egg problem" ~ http://www.joelonsoftware.com/articles/fog0000000054.html
So I'll have to explore these problems from a couple of different perspectives. Having read the article though I can think of how to get users to pay by letting others create, use or modify as well as access to tools and low-rez "instructions".
One example I can think of post-medium publishing is http://stackoverflow.com but I didn't see the same emphasis on how to make money. Just making SO the place to look for technical programming answers.
I do like the way you identify readers who pg has passed to read the article. It's like looking at the names on papers circulated at post-grad level to see who's read the latest ideas.
If you start from this statement and read the rest of the article I think it's a good start to better understand the parameters of the article. Post-medium publishing is an area I'm working on and I must say reading this article gives me another way to think about the problem.
"... If free copies of your content are available online, then you're competing with publishing's form of distribution, and that's just as bad as being a publisher ..."
Instead of looking how to make money I was looking at "solving a what users want" and still exploring the "and willing to pay for" bit. In this case users want "instructions" to build stuff but the cost of magazine producers is pretty high and the alternatives are primitive. Not making the "instructions" free or at least freeium-ish means a "chicken and the egg problem" ~ http://www.joelonsoftware.com/articles/fog0000000054.html
So I'll have to explore these problems from a couple of different perspectives. Having read the article though I can think of how to get users to pay by letting others create, use or modify as well as access to tools and low-rez "instructions".
One example I can think of post-medium publishing is http://stackoverflow.com but I didn't see the same emphasis on how to make money. Just making SO the place to look for technical programming answers.
I do like the way you identify readers who pg has passed to read the article. It's like looking at the names on papers circulated at post-grad level to see who's read the latest ideas.