1) I can guarantee that it isn't review length that is causing the problem with the reviews showing.
2)I believe that the bots and the issues they cause have been mostly done away with with the new MapMaker Upgrade (see http://blumenthals.com/blog/2013/11/27/google-mapmaker-update-summary-one-database-to-rule-them-all/
3)I am not a Google fan boy but I would say that we are nearing the end of the train wreck stage (http://blumenthals.com/blog/2012/11/29/google-local-train-wreck-at-the-junction/
) and are rapidly moving into a relatively stable development timeframe.
There are still some kinks in the transition from old dashboard to new, old indexing system to the new knowledge graph, old data pipelines to new pipelines and moving towards a single trusted repository of local data but it is happening. Google has essentially been rolling these upgrades out to local in real time while keeping the results showing. The transition has been going on for almost two years and is nearing some sort of terminus if not an end.
These issues are none of what +Dan Petrovic
was writing about. He is writing about review spam algos that have singled him out.
The spam review algo, like all algos, is a broad stroke of coding that attempts to show good reviews and minimize the showing of fake reviews.... It is a broad stroke that breaks down when analyzed at a very granular level.... it is crude as are most big data algos when dealing with the vagaries of human behaviors.
Too crude in this case and hopefully someone from Google will take a look. (Oops I didn't see +Jade Wang
comment when I was writing this. Thanks for taking a look.)