News outlets generally take this time to reflect on the best and worst of the past year, and offer predictions for the years to come. I don't have a top or bottom ten list, and I'm not going to pretend I know what tomorrow will bring. For all I know the internet could disappear and be replaced with a virtual reality implantation device connected directly to our brains, so all we have to do is think "google" and our next thought triggers a nanosecond search on the subject.
I'm not a Luddite nor am I a technophile. There are useful inventions being created every day, but history spins in cycles that appear different only because the context has changed. As wonderful as the open source and free content movement is, it does not change the fundamental problems that prevent society from moving forward and beyond the real divisions that keep barbarism and ignorance thriving. By focusing so much on how wonderful the new tools and technologies are, are we missing the deeper meaning of it all?
Showing posts with label google. Show all posts
Showing posts with label google. Show all posts
01 January 2012
31 December 2011
Business Insider story advises Patch to "keep scraping content"
A former Patch salesman advised the company to keep scraping content, ostensibly because "cheap content is king."
Nate Carter, I am glad you have high hopes for the future of local news. But tell me, why should an editorial department listen to a salesperson about content generation? I'm sure you have an intelligent perspective, but the mingling of news with sales in any way is exactly where journalism should not be going.
But this is beside the point. Consider Mr. Carter's grand homage to Huffington Post's (over) aggregation techniques:
Sometimes over-aggregation could be copyright infringement. It's not fair use if an aggregation provides enough content to prevent a person from visiting the site where the original story was published, as this post by AdAge's Simon Dumenco illustrates.
Some of Mr. Carter's suggestions to make Patch more efficient make sense. Patch should cut its editorial staff, but the suggestion to employ freelancers to cover beats is already happening, at least at some Patch sites.
The bottom line is we should all be appalled that content scraping is being suggested. What happens when we scrape the scrape of a scrape? When does it end?
Nate Carter, I am glad you have high hopes for the future of local news. But tell me, why should an editorial department listen to a salesperson about content generation? I'm sure you have an intelligent perspective, but the mingling of news with sales in any way is exactly where journalism should not be going.
But this is beside the point. Consider Mr. Carter's grand homage to Huffington Post's (over) aggregation techniques:
Keep scraping content. This should be done at HQ. Have 4 or 5 low-level staffers at Patch HQ who just content scrape from around the nation. We all hate it, but see point #2. This could be managed with simple Google News alerts and a copy and paste technique. If they perform well they could be promoted to the Huffington Post.
Does this only scare me? How could anyone talk so blatantly about plagiarism as if it were normal? (The #2 he referred to mentioned a heavier load for the local editors, so I'm guessing that scraping would help them hit their story quota. I almost think this entire post is sarcasm...)
Aggregation can be a great story supplement, and smart aggregators such as Jim Romenesko offer a valuable service for content creators. But over-aggregators such as the Huffington Post straddle an ethical line and in some cases cross that line and leave it in a dust-filled distance.
Aggregation can be a great story supplement, and smart aggregators such as Jim Romenesko offer a valuable service for content creators. But over-aggregators such as the Huffington Post straddle an ethical line and in some cases cross that line and leave it in a dust-filled distance.
Sometimes over-aggregation could be copyright infringement. It's not fair use if an aggregation provides enough content to prevent a person from visiting the site where the original story was published, as this post by AdAge's Simon Dumenco illustrates.
Some of Mr. Carter's suggestions to make Patch more efficient make sense. Patch should cut its editorial staff, but the suggestion to employ freelancers to cover beats is already happening, at least at some Patch sites.
The bottom line is we should all be appalled that content scraping is being suggested. What happens when we scrape the scrape of a scrape? When does it end?
Labels:
aaron wall,
AdAge,
Business Insider,
content scrape,
DJC seo services,
google,
Huffington Post,
jim romenesko,
nate carter,
Patch,
reuters,
ryan mccarthy,
seo,
seo book,
simon dumenco,
simon felix
Subscribe to:
Posts (Atom)