News for hackers. Stuff that matters.
Re:How We Tested Our Food Blog’s Expected CPM with Premium I... by ankitjain_hn on Tuesday August 11, 2015 @01:19PM (#10042748)
We are trying to avoid "loading a wallet" concept. It adds whole lot of other complexities. This microtransaction is clean. No future committments. Now only if payment gateways made it viable.
Re:How We Tested Our Food Blog’s Expected CPM with Premium I... by dyladan on Tuesday August 11, 2015 @01:31PM (#10042864)
You could try the reverse and float visitors credit. Once they're 5$ in the hole they can't view images anymore until they pay off the balance or something similar. Of course you'd have to find a way to make it so users can't just create a new account after they hit the 5$ limit (possibly by requiring a credit card and deduplicating by that?). Digital Ocean uses a similar model where they automatically bill your credit card once a month for accrued charges.
Re:How We Tested Our Food Blog’s Expected CPM with Premium I... by ne0n on Tuesday August 11, 2015 @04:25PM (#10044121)
Are there any examples of that being used successfully? My guess would be that people will just create new accounts. This might be the perfect place to test that model, though. The content is already free, you don't have to worry about losing royalties that people don't pay for if the test fails. There might need to be a strong emphasis for having an account (being able to customize or save recipes without losing data from creating a new account).
Re:How We Tested Our Food Blog’s Expected CPM with Premium I... by sixQuarks on Tuesday August 11, 2015 @06:17PM (#10044785)
I like this idea. You could present it as $5 of free recipes. It's like a try before you buy, or how casinos send people $100 free gambling credits. Yeah, some people will abuse it, but it's worth a try.