top
San Francisco
San Francisco
Indybay
Indybay
Indybay
Regions
Indybay Regions North Coast Central Valley North Bay East Bay South Bay San Francisco Peninsula Santa Cruz IMC - Independent Media Center for the Monterey Bay Area North Coast Central Valley North Bay East Bay South Bay San Francisco Peninsula Santa Cruz IMC - Independent Media Center for the Monterey Bay Area California United States International Americas Haiti Iraq Palestine Afghanistan
Topics
Newswire
Features
From the Open-Publishing Calendar
From the Open-Publishing Newswire
Indybay Feature

How can anyone trust the San Francisco Chronicle? (Commentary)

by Robert B. Livingston (gruaudemais [at] yahoo.com)
A curious discovery I made today makes me wonder, "How can anyone trust the San Francisco Chronicle?"
protest_at_union_square.png
November 25, 2007
San Francisco

Maybe some hard-nosed people might tell me to "go get a life". Fair enough-- I suppose there may be better ways that I could spend my time than surfing the internet reading news-- but trying to figure out why some of it spreads while other news simply vanishes has become an obsession of mine.

Not only is reading the news an obsession, but reporting news is a compulsion. This is true especially when I think that something happening (which might never be reported by anyone else) is important enough for more people to know about.

Such was the case yesterday afternoon when I happened to be at Union Square when a number of activists appeared with flags and signs to protest Pakistan's Dictator-General Pervez Musharraf.

Without thinking too much, I automatically began to ask questions and snap some photos with an old camera which I try to always carry with me.

To my amazement, some of the protesters kept asking me if I had seen any other press. I told them no, and their disappointment was obvious. They had hoped that the mainstream media would be there to cover their story.

By the time I got home I was weary and wondered if I would have the energy to sort through my photos, format them, and write the descriptions that would help make them comprehensible. But even though I had more pressing things to do for myself-- I knew that this story had to be told because elsewhere in the world peoples lives might well be at stake. There are so many things constantly happening in this busy world, but yesterday I had learned things that no one else knew-- or would likely know (so I've since learned to my chagrin). Nevertheless, I was compelled to post my story:

"Pakistan's Enduring Strife Echoes in San Francisco"
http://www.indybay.org/newsitems/2007/11/25/18463311.php

Errors and all, I finally was able to upload this story to Indybay.org sometime after midnight. I then did what I could to address the story's most consequential error by writing a comment-- and then I went to bed.

This morning after reading other news-- I was curious to see what had become of my story. Using Google, I searched for San Francisco news related to Pakistan. To my surprise, only two articles about the protest at Union Square turned up using the famous search engine-- both were San Francisco Chronicle (SFGate) stories. The first (http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2007/11/24/BALCTI2S8.DTL) reported about the plans for the protest, the second amazingly reported that if the protest had taken place-- the Chronicle reporters could not find it!

In the second, Rachel Gordon writing for the Chronicle wrote: "If there was, as planned, a protest in Union Square Saturday against Pakistan President Pervez Musharraf, the participants did a mighty good job blending into the crowd of holiday shoppers." http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2007/11/25/BARVTILAH.DTL

Having been there and seen and heard the protest for myself-- I simply was flabbergasted by what I read! Had anyone been near Union Square, they could hardly have missed the protesters waving signs and flags, calling out on a bullhorn, and shouting.

I could only guess that the Chronicle's assigned reporter had missed them because the protesters arrived a little after three pm (the time the protest was scheduled to start). But hadn't the Chronicle itself, in the first article, reported the time of the protest to take place between 3 and 5 pm? Couldn't the Chronicle reporters have called someone to find out more-- if indeed they totally missed seeing the protesters? Obviously, they hadn't bothered, or had given up without hardly trying.

This is where this commentary gets interesting.

Anyone who reads Chronicle news at SFGate knows that the Chronicle's web portal allows readers to comment on stories. Using my alias, "alabamarasta", I posted a comment to Rachel Gordon's story, saying:

"Maybe the news here is that your reporters were asleep. The protesters arrived a little bit late, but your reporters were gone and did not bother to find out more. Go to indybay.org for the story."

This evening, I again became curious as to whether or not the story of the protesters at Union Square had been picked up by Google or not. To my surprise, it had not. Google continued to link to only two stories-- the same SFGate ones which I have mentioned. Google's search engine had (as yet) not recognized my story at Indybay at all.

I returned to the SFGate story by Rachel Gordon where my comment remained-- the only one. That is strange, I thought. Maybe Pakistan's troubles are not as as relevant to the Chronicle's readers as say, C.W. Nevius' stories about needles in the park, or stories about the Blue Angels (stories which typically get hundreds of comments).

Sigh. Oh well.

That is the way things go.

I wondered how people were faring in Pakistan where thousands had been arrested prior to former Prime Minister Nawaz Sharif's return to that country.
I read about events going on there for awhile, and then I wondered what breaking news might be happening in San Francisco.

Using Google again-- I discovered something which was personally shocking. It was an article titled: "San Francisco Chronicle Tricks Bloggers And Trolls." http://www.anorak.co.uk/twitterings/177919.html

In it there was a link to a blogger's story (http://investigatethemedia.blogspot.com/2007/11/san-francisco-chronicle-deceives-its.html) which explains that SFGate has a method to (for whatever reason) delete readers' comments-- and get this: allow the comment to remain visible only to the person that posted it!

Ostensibly, this ability is used to thwart troublemakers-- but I can prove here that it is used quite capably to deceive readers. I would learn for certain that it had deceived me!

Instead of returning to Rachel Gordon's story using my Firefox, or Opera web browser-- I accessed the SFGate article site using Dillo (a fast, no-frills open-source browser). Rachel Gordon's article about not finding the Union Square protesters remained the same-- but surprise! surprise! My comment was gone (SFGate did not recognize the Dillo browser and thought that I might be a new reader.)

Interestingly, there was a message instead that said: "Be the first to share your thoughts on this story....
Sorry, comments are closed for this story."

How many of SFGate's readers have read that message all day? I wondered. If they had never read my comment, they would all have been misinformed. The truth is that SFGate did not cover the story of the protesters. It actually told a story that if there was a story-- they could not find it!

As I write this now-- I wonder in what other ways the Chronicle misleads or deceives its readers. How can anyone trust the newspaper?

If sincere but uncomfortable comments can be erased-- can others be created out of whole-cloth? Like the hundreds of comments that extol the Chronicle's editorial perspective on various issues-- such as who is more trustworthy Gavin Newsom or Chris Daly?

I would mention that comments are routinely erased at other websites because they violate rules that readers agree to. But to hide uncomfortable comments such as mine smacks me as bad faith at best, and as a cover-up and deception at worst.

Perhaps I am making a mountain out of a mole-hill. It is said that some of the world's best journalists have admitted that they occasionally wrote reviews about plays or concerts that they never attended (being found out only after a theater burns down calling off the show).

I would appreciate an apology from the Chronicle-- and a promise to be more transparent about the way it allows its comments to be posted and read. I will post a comment update here if that ever happens. If I am in error with regard to any of my facts I will apologize right away, and try to set the record straight. I will post such a correction here as a comment if that is necessary.

Now I just have one question left that bothers me... why hadn't Google's search engine ever recognized my story at Indybay even while it continued to promote SFGate's non-story?

How well can Google be trusted?
§Screenshot of my Google Search
by Robert B. Livingston
google_search.png
This was taken this evening (along with the ones below at about 6 pm).

This shows that Googling "san francisco pakistan" [News]: turns up two articles at SFGate-- referenced as the most relevant stories.

§Screenshot of my comment at SFGate
by Robert B. Livingston
sfgate_comment.png
Using an alias, "alabamarasta", this is a screenshot of my comment using an Opera web browser. I had a similar result using Firefox. My comment shows up to me... but does it to anyone else?
§Screenshot of comment section using a Dillo Browser
by Robert B. Livingston
comments_closed.png
I took this screenshot of the comment shortly after taking a screenshot of it on my Opera browser, but I had opened the Dillo browser before opening my Opera browser.

Here one reads: Comments are closed. There is no evidence that anyone had ever commented on Rachel Gordon's story.
Add Your Comments

Comments (Hide Comments)
by Robert B. Livingston (gruaudemais [at] yahoo.com)
google_wakes_up.png
@ 9:45 PM

Just now-- curious, I googled "san francisco pakistan" [News] once again.

Amazingly The SFGate stories sit at the top, but this story which I only just posted about thirty minutes ago appears almost immediately (and the word "pakistan" is buried in the body of my story).

Could it be that Google seeks articles with its name in it? ;)

We live in a Brave New World!
That yellow Hearst rag called the San Francisco Chronicle of course didn't
report on the Pakistan demonstration at Union Square. It's not that Rachel Gordon didn't find the protest (she was there), but rather, the paper decided to censor the story. Hearst newspapers have a long, illustrious history of supporting dictatorships around the world. Good enough reason not to buy their rag.
by Bill Carpenter (wcarpent [at] ccsf.edu)
What a great job of reporting, Robert! And so thorough! Someone at the Chron must have been reading indybay, because your comment is back up:
http://tinyurl.com/3yywdj
Bill
This is very curious to me-- and does make me wonder if I am not at fault-- partially or in whole.

I opened the web site in my Dillo browser-- and it still shows No Comments-- although clearly it is taking comments in the mainstream browsers.

It could well be that I have indeed made a mistake-- which makes me red-faced-- but-- this business of allowing some people to see comments and others not to is a confounding problem that had me wondering.

If I had been more astute, I should have contacted someone like you to test the comments before I wrote the above commentary.

Can we trust the Chronicle?-- I guess I'll leave that for others to answer.

I hope my questions were nevertheless worthwhile.

by Robert B. Livingston (gruaudemais [at] yahoo.com)
The more I think about it, I am believing that Bill Carpenter saw my comment at Rachel Gorden's article because it was still there. I saw it on Opera and Firefox, but not on Dillo-- why? I don't know why. Perhaps the fault is with that browser because it has limited capabilities. Why it said No Comments-- this is closed-- I do not understand it.

But I did promise an apology-- so here it is. I guess I am a regualar fool.

I am very sorry to the Chronicle and anyone else who might have been mislead by my story.

I hope always that journalism is responsible-- and I hope this apology does something to correct my error.
by SF Outsider
SF Insider: I hate the Chron, too, but get your facts straight: The Hearst family used to own the Examiner and Hearst was a hated nemesis of the Chronicle; they didn't own it and they don't now. Read "Imperial San Francisco" by Gray Brechin for a great history of the SF newspaper wars.
by SF Insider
For the record: The Hearst family purchased the "Chron" in 2002 after selling their interest in the Examiner to the Fang family. Read the newspapers, SF Outsider.
by Robert B. Livingston (gruaudemais [at] yahoo.com)
Here is a needed update:

The link I provided above in my story "San Francisco Chronicle Tricks Bloggers And Trolls" http://www.anorak.co.uk/twitterings/177919.html was not a real news story. The story it links to is a satire. I only realized that moments ago.

The link it provides to "The San Francisco Chronicle deceives its readers through comment-deletion trickery"
http://investigatethemedia.blogspot.com/2007/11/san-francisco-chronicle-deceives-its.html is of questionable origin. I should not have believed it so readily.

If I have been deceived by anyone it was by satirists posting such stories-- and with real chagrin, myself. Sadly, I have a pretty good track record for making mistakes like that, so people reading anything I post might well ask not "How can anyone trust the San Francisco Chronicle?"-- but "How can anyone trust Robert B. Livingston?"

So, indeed, I have been unfair to the San Francisco Chronicle and have real egg on my face.

But that does not mean that I will stop scrutinizing it! And I hope smarter people than me won't give up doing so. I have to ask myself why I am so ready to believe satires and misleading stuff posted on the web.

The truth is, I have a great love of newspapers and journalists-- and I believe good, reponsible media is the key to having a more informed public and a better country. Without question, I could use the help of a good editor when I write-- but when "we become the news" (as people say today of citizen journalism)-- we often miss having that.

There are many things that I think are wrong with the Chronicle-- not only failing to cover the story of the protest at Union Square-- but also the mercenary way it has cut its own newsroom staff in recent months. But then, they would likely counter that they are forced to do what they do because of the type of competitive society in which we live. Well, exactly.

At the same time-- I hope my mistakes provide a warning to other amateur and citizen journalists to be a more thoughtful and accurate when they write their stories.

I am grateful for the fact that the Independent Media Center (Indybay.org) allows a comments section for people to ask questions and add information to stories. Without that, I may have not discovered my errors.

I hope my errors will not detract in any way from the general trustworthiness of Indybay.org-- an organization which I believe plays a vital and serious role in disseminating news that is ignored by the mainstream, or establishment media.
Robert, don't backpedal so quickly. The blog posting that you linked to which exposed the SFGate's sneaky comment-deletion policy was NOT satire or "fake news": it is totally serious and accurate. Go back and read the posting at Investigate the Media again: http://investigatethemedia.blogspot.com/ . It now has several updates confirming the original claims.

I think that your comment was in fact deleted, but that SFGate is now scrambling to cover their tracks, and once this story (about their crypto-deletion policy) broke on the blogs (it's being covered everywhere), SFGate began undeleting selected comments, especially those where the commenter became aware that he had been crypto-deleted.

There is no other explanation for your experience other than: your was comment was posted, then crypto-deleted (so that you could still see it if logged it, but no one else could), then later undeleted once you caught them red-handed and once SFGate had been publicly shamed by the report at Investigate the Media.

You apologized too quickly. I think you were right to begin with. Your comment about the Pakistan protest has now been restored, but I suggest going back and checking out some of your earlier comments at SFGate -- you may find that they have themselves been crypto-deleted without your knowledge.
by Robert B. Livingston (gruaudemais [at] yahoo.com)
Dear ahuman,

You were right-- thanks.

Elaine Santore (Fog City Journal) investigated and wrote:

"Batey told FCJ she didn't want deleted comments to disappear. But because the tool wouldn't be available in time, she and her colleagues agreed to use the blocked user function, fully aware a number of users would be affected and deceived by the blocking policy. Looking back, Batey regrets making the decision."

and

"SFGate discontinued using the block user function on November 26." (The day after I read the blog investigatethemedia and posted my story.)

The Chronicle never contacted me personally about this story or one I wrote subsequently in whichI questioned other oddities about SFGate:
http://www.indybay.org/newsitems/2007/12/03/18465024.php

Here is Elaine Santore's article:
by emasmus
If one took 5 senconds to type in sf chronicle to their seach engine and scrolled to the bottom of the page, they would know that the SF Chronicle IS owned by Hearst Corporation. It looks like some one is trying to discredit the original author of this article with false information. They have every reason to be biased! For the record Hearst Corp. owns 18 newspapers, 28 magazines,26 television stations,38 "interactive media sources", and "more than 20 business to business info sources/electronic databases and publications, and "significant holdings in the auto motive, electronic,medical/pharmaceutical and finance industries". (info from Hearts corp website)
We are 100% volunteer and depend on your participation to sustain our efforts!

Donate

$330.00 donated
in the past month

Get Involved

If you'd like to help with maintaining or developing the website, contact us.

Publish

Publish your stories and upcoming events on Indybay.

IMC Network