Today I have an example scammer to show you. "Chance Carter" is the nom de trompeur for one of the scammers currently infesting the Kindle Store. They are running a book stuffing scam in Kindle Unlimited, and have apparently been operating there with impunity for years. At the same time, "Carter" is also breaking Amazon's rule on incentivized reviews via an ingenious "contest" trick.
The book-stuffing con is one of the long-running problems in Kindle Unlimited.
In the first year of Kindle Unlimited, scammers took advantage of the system by uploading ebooks so short that they got paid after only a few pages were read. Amazon put a stop to that in July 2015 by switching to a system that paid based on pages read, and in response the scammers invented the book-stuffing con and started uploading really long books.
The way that the book-stuffing con works is that scammers stuff lots of extra content into an ebook before uploading it to Kindle Unlimited, and then trick readers into jumping to the end of the book.
Thanks to a flaw in the Kindle platform, namely that the platform knows your location in a book but not how many pages you have actually read, the scammers can get paid for a user having "read" a book in Kindle Unlimited by getting the user to jump to the last page.
This has been a known problem in Kindle Unlimited for over two years now. Amazon has responded by limiting the length of ebooks in KU, and banning practices like putting a TOC at the end of a book, but neither has really had any impact on scammers.
Chance Carter is the perfect example of both how the book-stuffing con works, and how Amazon is completely incapable of stopping the scammers.
Carter's trick is to publish a ghost-written novel, stuff an extra six or seven of their ghost-written novels in the back, and then add a free ebook offer on the last page as bait for unsuspecting readers.
This is a blatant violation of Amazon's existing rules for KDP (see the section on disappointing content) and yet Amazon can't seem to spot Carter's operation, or that of the other scammers.
Remember, some of the scammers have grown so large that Amazon took them to arbitration. While this may have been intended as an object lesson, what it really did was show that there were massive scam operations going on in the Kindle Store.
And operation is a good word for it, because not only does Carter publish scam books, they also instruct readers how to support the scam:
And Carter goes one better; they also encourage reviews through a contest:
This, too, is against Amazon's rules on incentivized reviews.
Amazon is not the first huge tech company to lose control of its ebookstore; in 2015 I showed how Google Play Books was so infested with piracy that Google had to shut down its book publisher portal, and start vetting everyone before letting them sell ebooks in Google Play Books.
One key difference between Amazon and Google, however, is that Amazon is unable to stop the major scammers while at the same is letting its bots go after innocent authors.
David Gaughran recounted his experience yesterday on Twitter.
Here's how enforcement of rules and sanctioning is totally broken at Amazon right now. Last August, I got in trouble with Amazon. I remember clearly what happened because it was my birthday and I was dying in bed with a virus.
Amazon's Kafkaesque "Compliance Team" sent me a nastygram. Said I was breaching the exclusivity terms of Select. I had no idea what they were talking about, of course, I've always played it straight and never took any risks.
Turned out a tiny German ebookstore had a bug and inadvertently reactivated a load of dead listings from 2013. Lots of authors were affected. It was nothing to do with me. I got no benefit from it. But Amazon dropped the hammer.
They threatened to boot me from Select and take away my page reads, and even close my account. For a bug on a site, nothing to do with me.
Not only that, Amazon cancelled my Countdown deal without even telling me. Cost me hundreds of dollars in promo. I was advertising a 99c deal to my readers that didn't exist. It was a real dick move. I appealed - no good.
Even worse than what happened to me are the authors who were rank stripped, page stripped and had accounts closed because Amazon is using a dumb automated system to catch scammers which doesn't work.
The human cost of the actions of cheap crooks like Chance Carter are real. One of my close friends was rank stripped when she was just getting her career back on track. It upset her so much she has given up writing. Thanks Amazon for nothing.
O O O
It is clear at this point that letting large automated systems run without human supervision is a failed idea.
We can see the consequence of bots run amok in Youtube's ContentID, which has a history of false copyright claims, as well as a dozen other examples including the 2012 Hugo livestream getting blocked because it showed clips of the episodes that won awards.
In Google Play Books we have a tacit admission that the only way to keep pirates out of the store is to add humans to the control loop.
And even Amazon's smaller competitor Kobo has realized that automation can only do so much without human supervision. Christine Munroe told me that Kobo has flesh and blood people vetting content:
From a self-published content perspective, we have created two systems: first, trust tiers at the account level where trusted account content goes through with low intervention, known spam/scam offenders are thoroughly vetted, and a substantial in-between yellow tier requires a combination of automation and human approval or rejection. Second, our analysis system scans for piracy and adult content.
Our Publisher Operations team works hand in hand with automation to classify all incoming content, as quickly and seamlessly as possible. When classifications are unclear or flagged, humans must intervene. Currently, our team looks at 65% of new KWL content being published every day, on average.
When do you suppose Amazon will figure this out?
P.S. Numerous complaints have been filed about Carter, and I also brought them to Amazon's attention last night. That account was still active when I published this post.