A yellow card from Facistbook

I am constantly being harassed by Facebook AI bots that manufacture bogus/trumped up reasons to shut me down in an attempt to silence me. Usually, it’s for editing my own comments.

 

The only ding I could find against my Facebook page was a yellow card from a March 23 post about Taylor Swift urging people to vote. The T-shirt was altered, and I even noted that. 

I wrote: “The photo of Taylor Swift in anti-Trump shirt may be doctored, but the threat is real. So, for that reason I stand with her. Vote! Interesting, the Facebook censor bot visited and decided this post needs to be...”

• Public • Hidden from profile”

Facebook cut off the rest of my sentence. I think I wrote, “…at the bottom of my feed.”

Actually, Facebook completely removed the post and my explanation from my page. They didn’t just send it to the bottom of my feed as they had stated. They said it was false information. I agree, and I noted it. 

And then Facebook said that it could pose physical harm. Say, what? How can a T-shirt that tells people to vote cause physical harm? What am I missing here? How draconian.

So here’s the clincher, Facebook completely removed my repost but not John M Disque’s original post of it. It’s still up and on his page. What gives?

I merely shared the post with a caveat. And there’s no way to object to Facebook’s decisions. They’ve removed all recourse. There is no way to complain or disagree with them.

Now watch, I’ll get thrown in jail again for posting this. It has happened before.

More on those historic mercury mines of Marin (the short version)

A rather long note bene: Since I went through so much grief the other night trying to save my old 2020 mercury mine blogpost from Google Blogger AI censorship bots, in desperation I took screenshots of the original post and reposted it on my artist page on Facebook. I also made a very truncated version (below) for the Facebook group, California History as I was afraid the information I had worked so hard for was going to be forever lost. 

The original mercury mine blogpost had its inception Labor Day weekend when I was hiking San Pedro Ridge in San Rafael. We were still in Covid sequestration, and to keep my sanity, I wrote many articles I might not have other otherwise written. 

In this case, I wrote a stub that didn’t go anywhere, no real leads, and then I delved into it again in December 2020. I discovered that I was in over my head with the material, and no matter how I tried, I couldn’t finish the blogpost—partially because I couldn’t find the discrete information I needed. 

And also, I thought I didn’t have the chops to figure out how to present the material. Why a writer, suffering from dyslexia, is a writer is a mystery, but there are many of us out there. It’s not like I’m earning any money off my writing. I’m not getting paid for any of this. I write because I have to.

I suspect my writers’s block, or rather, my revisionist block, was due to the fact that it was too big a subject. The more information I uncovered, the more of the post grew. I was in over my head. I despaired. It was an albatross. But the only way out was through. 

Sometimes I think I can’t write my way out of the paper bag. or, that I don’t have the intellectual  chops. This time I was in one colossal kevlar-lined paper bag, but I persevered. It was probably one of the most challenging blogposts I have ever written. 

My Night Train to Moscow post (which began as an email), my redhead, pacer, bees, and daffodil blogposts also gave me some serious writer’s grief, but at least the posts weren’t banned by Google. 

I face enough unwarranted censorship from Facebook for writing bad similes, or thinking outside the box. I sure don’t need this kind of grief from Google either. I expected better from Google. (Google fail.) I feel betrayed.

The other day, when I made another stab at revising the original blogpost because of a Facebook post on the old mines in Lost Marin, I finally made some serious headway—only to have Google Blogger take it down and literally trash my blogpost, then reinstate it—some 30 times. When Google takes down a blogpost, you can’t even see it. It just disappears into the ether. No warning. Poof! Gone.

A while back, Google suffered a serious systemwide matrix glitch and took down multitudes of my innocuous posts—only to reinstate them later but I had to physically find my blogposts in the trash and then reinstate them. Before that, I didn’t know that Google had previously removed some of my other posts. Sadly, some of those posts are lost forever.

Thinking it was an email spam, I ignored the red warning label Google had slapped on my posts, and I lost my Juanita Musson memorial post, plus others. I reasoned, how could a memorial post be considered spam? It was not logical, as Spock might have said. But it was for real, only I found this out in arrears. 

I was able to salvage some of the removed old posts from first drafts that I had stashed elsewhere, but not all. Not Juanita in the bathtub. I despaired thinking I had lost all my revision work on the mercury mine post. I was 12 hours deep into it. So, of course I fought furiously to save my post, and to get it reinstated. Again and again.

Now I’m afraid to make any further changes on my original mercury mine post for fear of triggering the AI bots. Google no longer adequately warns you that it is removing posts. It no longer uses the red banner. And it took a long time for a Google warning to show up, explaining what the reasons were for banishment: violating community standards.

Google warned I was violating community standards, but it didn’t specifically say what. I had no idea. Googling it did not elucidate or shed any light on the subject. So, I kept removing images, revising, checking on all my links, and nothing worked. I wasn’t over quoting anyone, and it was my own intellectual property, not to mention, photos. And all the graphs I used were from publicly funded agencies, therefore within fair use parameters. I couldn’t remove the ban. I despaired.

A Google email eventually appeared, claiming this time that I was violating community standards by promoting or selling controlled substances. Huh? How is a blogpost on historic mercury mines even remotely considered to be promoting a controlled substance? Maybe it was the word “mine” itself that triggered the bots. So, this post below is a test of sorts.

(I am not trying to bite the hand that feeds me. If it wasn’t for Guy Kawasaki’s evangelical support of Google Blogger, I would not have delved so thoroughly into the new medium of cyber-writing. It all began innocently enough, I had lost some of my earlier poems to ASCII gibberish, and decided to put them online. Then I discovered I could back-post my work. One thing led to another. MySpace was no longer cutting it. It was a grand liberation to be free of the physical page. As it is, I now have 5000 blog posts. I must admit, I feel betrayed by Google at this point.)

See, during one of those rare moments, when I could actually re-access my ephemeral albeit temporarily reinstated mercury mine blogpost, I took screenshots of it and posted it on Facebook so I wouldn't lose my work completely. I also made a truncated version for a Facebook group I belong to, California History. I have previously taken several of my blogposts and revised (shortened) them for the group. 

Then I realized that the revised post I wrote for California History  is also a separate entity. New work. Probably closer to what I had hoped to originally write. It’s posted below. Now watch, Google Blogger will ban this blogpost too. Don’t worry. This time I have a link to someone who works at Google and I will complain mightily. How’s that for throat-clearing? Are you still there, Dear Reader?

Historic mercury mines in the North Bay (below is a truncated version of my original post. Click on the link/title for full post and research notes).

When I was a child, I was fascinated by my uncle’s old mining survey maps of Bolinas Ridge and Mt. Burdell dotted with old cinnabar (and copper) mining claims. Curiosity got the best of me.

Our red California earth is oftentimes a sign of the presence of iron /hemitite, or cinnabar (Remember Napa’s Silverado Mine on Mt. St. Helena, made famous by Robert Louis Stevenson’s 1884 novel, The Silverado Squatters?)

There are several historic cinnabar mines in Northwest Marin, including four at the Gambonini Ranch, near Solajoule Reservoir, some sites on Mt. San Antonio, and also on the ridges above Novato. The old mine shafts on San Pedro ridge in San Rafael seem to be gold claims. But where there’s gold, there’s cinnabar.

During the Gold Rush, cinnabar ore mined in California, for mercury, was originally used for silver and gold extraction. The crushed ore was processed in high-temperature smelting ovens. 

Those unstable leftover cinnabar tailings are what has caused the mercury runoffs into our watersheds, including in the San Francisco Bay—destroying one of the most fertile marine ecosystems in the world.

There are numerous historic cinnabar mine tailings throughout Marin and Sonoma counties, some that have also added to the high mercury levels in several of our reservoirs, including Bon Tempe, Solajoule, and Nicasio reservoirs and their drainage watershed, Tomales Bay. 

The fish warning signs that rim several of our reservoirs serve as a grim reminder that mercury poisoning is cumulative. Tomales Bay in Northern Marin County has higher mercury levels than San Francisco Bay—and it’s not from naturally occurring cinnabar deposits, as the mineral mercury oxide is inert unless it’s been heated and extracted.

According to the California Office of Environmental Health Hazard Assessment (OEHHA), there is an fish advisory or warning that Nicasio and Solajoule Reservoirs contain methyl-mercury, as does Bon Tempe Reservoir on the slopes of Mt. Tamalpais, which once hosted several historic mines, including mercury, copper, gold, and even a nickel mine.

I assume that the rest of the Marin Municipal Water District (MMWD) reservoirs (our drinking water supply) also contain trace amounts of some form of (inert) mercury too as they’re all downstream of Bon Tempe dam and empty into each other, exiting via Kent Lake into Lagunitas Creek that drains into Tomales Bay. 

Naturally occurring mercury oxide does not enter the food chain the same way manmade methyl-mercury does. But at the Nicasio Reservoir methyl-mercury pollution is significant enough to trigger OEHHA advisory warnings about cumulative mercury poisoning from carp, sunfish, black, and large-mouth bass species (apex predators such as bass contain the most cumulative methyl-mercury in their systems). 

Why Nicasio? It doesn’t butt up against any known mercury mines, it doesn’t share the Solejoule Reservoir watershed to the north where there’s also an OEHHA advisory warning for black bass and crappie.) Why am I mentioning Solejoule? because in 2000, it became a Superfund cleanup site.

In a nutshell, in 1964, a PG&E subcontractor, Oakland-based Buttes Gas & Oil (BG&O), ran a lucrative open pit mercury mining job at Gambonini Ranch near Walker Creek in northwestern Marin. 

But in 1970, when the price of mercury fell, BG&O pulled up stakes and left the open pit mercury mine tailings exposed to the elements behind an earthen dam that epically failed during a series of fierce storms in 1982—which dumped ungodly amounts of leached methyl-mercury into Tomales Bay. More than in San Francisco Bay! 

BG&O had leased the land from Alvin Gambonini’s father from 1964 to 1970, never disclosing to the Gambonini family the potential dangers involved with the toxic heat-processed mine tailings to extract the mercury, or that the leftover toxic mercury particulates leach out of the rock tailings whenever it rains. (I wanted to ask, what about all the cows?) 

BG&O never sealed the four mines, nor capped the tailings. It took nearly two decades for the EPA to discover the mishap. It triggered a $3 million Superfund cleanup in 2000. 

Back to Nicasio Reservoir. The methylmercury is coming from somewhere. Not from abandoned mercury mines upstream that I know of, or from the isolated Solejoule Dam which empties into Walker Creek. Question is, from where?

However, some of those old red earth mine sites really were manganese, or hematite, a type of iron, not cinnabar—like the Sausalito mine, and the prehistoric hematite site on Mt. Burdell. Inert red dirt. Sometimes a red rock quarry is just a red rock quarry. Just don’t eat the fish.

Google Blogger keeps flagging and taking down my mercury mines post

I thought Facebook AI bots were bad, apparently Google Blogger also is using the same idiotic AI bot workforce. Are they in cahoots? I was revising an old post from December 21, 2020 that I had started working on when I was staying one summer on Aquinas St. in San Rafael—it took a long while to gel. 

When I hiked up San Pedro Ridge, I could see the characteristic telltale red earth—which piqued my curiosity about mercury mines. I banged out a rough draft, then, later, I began to research it and ran into multiple dead ends. It seems no one has ever written an overview of mines in the north bay.

I have worked on this particular blogpost intermittently since 2020, due to a lack of stamina and a lack of information, and suddenly the post was flagged after being published for four years. Hindsight? I thought it was photos or graphics that was triggering it. Not. 

No, my violation of community Standards was: Regulated Goods and Services policy. “Regulated Goods and Services. Do not sell, advertise, or facilitate the sale of regulated goods and services. Regulated goods and services include alcohol, gambling, pharmaceuticals, unapproved supplements, tobacco, fireworks, weapons, or health/medical devices.” 

DEAR GOOGLE: Huh? You mean my writing about historic mines goes against Google’s policy of portraying regulated goods and services? How so? Just because the military once used mercury, then deregulated it, doesn’t mean I am facilitating selling something illegally. Maybe it’s the word “mines” that is triggering this flurry of censorship flags. Of course Blogger doesn’t tell you what it objects to.

I must be getting onto something significant. Nothing like raising the interest of a journalist to do more investigation. Am I willing to go down with the ship for my writing? You betcha. Mercury plays a huge role in California history from the gold rush to the Cold War. I write in order to learn. I didn’t know enough about the historical background of mercury mining, so I sat out to teach myself by writing about it—only to get slapped in arrears (pun intended) by Google. 

Well, the good news is the erroneous flag forced me to rewrite portions of the blogpost, so at least it’s finally in a semi-finished format. Alas, no writing is ever truly finished. I did change the title from Mercury Mines in Marin to Historical mercury mines in the North Bay to include Sonoma County as it shares many of those mine sites near Petaluma.

Thinking it was the graphics that caused the flag— Google doesn’t tell you why it flags a post—I went back and researched all my sources, trying to figure out why the blogpost was flagged. But my sources were from publicly, funded agencies and organizations, I am not breaking copyright. Besides, there’s this thing called fair use. 

What a horrible way to force a rewrite. And the hours of undo stress the Google flag caused because I couldn’t fully access my post (or changes) in order to save it off-line. I am increasingly unhappy with Google. Their parting email shot: “We encourage you to review the full content of your blog posts to make sure they are in line with our standards as additional violations could result in termination of your blog.” They brought weapons to a tea party. Shades of 1984 and Doublespeak. 

I wonder who in Facebooklandia flagged my post? I had posted it in a Lost Marin group hoping to get more leads and help with revising my post. It looks like my link and post was removed. 

I am reminded how poet Ron Silliman was harangued by Google and his poetry blog was taken offline because someone had flagged it— And Google would not divulge which particular post was considered offensive or why it was breaking community standards. At least I knew which post was the offending post. Small mercies. I also now make an archive of my writing.

• 
  

  

  Dear Google, have you any idea how many times you have flagged this post within the past 24 hours and how many times you have reinstated it? Shall we go for an even 30 tries? Every time I make a correction on a typo you flag it take it off-line again. It takes me upon average of five attempts to contact you before you reinstate it. Will it hold?

  
  
I finally resorted to taking screenshots and posted them on my Facebook artist page in order to preserve my blog post. I think that 30 attempts to remove my blogpost is a bit excessive on Google Blogger’s part.

Facebook AI bots blocked Michael Collins’ memorial video of a medieval hymn part 2

And once again I am being harassed by Facebook for “copyright infringement” that was already resolved in my favor weeks ago. Note the assumption that there’s a rightful owner to this music. It’s a private post, no one else can see it. I can’t make comments because I’m still in jail except for status reports. Clearly, Facebook AI censorship bots patrol my Facebook page early and often.

#trolledbyFacebook #FacebookFail #MetaFail

Reason: Public domain

Additional details: we've been through this before: this is the second time you flagged 12 century medieval church music. You do not own it. It does not infringe on any known copyright. These are Gregorian Chanters singing at a memorial for their dead friend, my cousin. Please stop. This is harassment at this point. 

I thought I already won this dispute. has Facebook taken to flogging dead horses as well? The 12th century public domain hymn, Salve Regina has been copyright-free since the middle ages. I wonder why Warner Music Rights Management Group AI bots think they owns this music? Are they getting religion?

Dear Facebook,

Your Facebook AI bots are constantly trolling my online activity to the point of actual harassment. I am constantly being blocked and thrown in jail for commenting, or sharing innocuous content.

For example, the last time I tried to correct a typo on a comment, because Facebook had changed the name of noted poet Lynn Hejinian who had died, misspelling it. So I corrected it, and got six days of jail.

Ditto that when I posted memorial photos when equally noted poet Jack Hirshman unexpectedly died of Covid. six days of jail time.

I tried to add the word crêpe with the circumflex to my comment, and got six days. I reported it and got six more days for reporting it. That has happened twice now.

Between Facebook, “helping” me to misspell words, generally substituting the wrong words—AFTER I posted a comment—and my dyslexia, I need to be able to edit typos. I am a writer, and writers revise. I am a horrible typist, so I make typos, and I also want to be able to correct those mistakes. how is this going against community standards?

There are myriad Facebook sanctions against me for wanting to spell words correctly. Literally.

Out of the blue, a year after the fact, Facebook deleted a comment I wrote about botany in a botany group, where I mentioned the seeds of a California palm tree.

Before that you took down a post of mine where I posted a photo of a spotted horse and chicken as an example of leucism and the leopard spotted gene.

Since when is posting about science a crime?

And then I reposted a black and white meme about Einstein’s messy desk on the day, he died, and was flagged for posting nudity. it was a messy desk, and it wasn’t even naked. It was covered with paper.

I posted a comment about historic Gravenstein apples to the Fort Ross site and was flagged for spam. I wrote to them and they were equally horrified.

Twice now Warner has muted videos of my cousin’s memorial service, where his friends who are Gregorian chanters, were singing a 12th century hymn, Salve Regina, which is certainly copyright free and in the public domain. I won the dispute the first time, and yesterday Warner muted it again. Your algorithms are way off. Incidentally those videos were private, and no one else could actually see or hear them. Only me.

Also, I have been thrown in jail for making a comment about another cousin’s death—I was reminiscing when he was a child. Six days in the slammer.

Another cousin who died, I mentioned something about her, also alerting my family. Another six days in the slammer. And when I complained about it on my page, using screenshots, I got six more days. That’s happened several times. Talk about censorship. So we’re not allowed to post anything on each other’s walls when family members die? What are the trigger words? I’m not allowed to complain about Facebook’s AI bots being out of control?

I won’t mention how Facebook retroactively sanctioned me for reposting old Liam Neeson memes that came up in my memories feed. A meme that I have reposted yearly, for over a decade, And yet Facebook did not take the exact same meme down on anyone else’s page, nor did Facebook block them, or throw them in jail, but Facebook did that to me. Myriad times. Clearly Facebook bots do not understand sarcasm, let alone, simile and metaphor. Or, humor. Apparently am not allowed to repost old memes either.

The thing is, nobody knows what triggers the censorship bots. And the Facebook punishment is absolutely senseless. Whatever happened to let the punishment fit the crime? And now you’ve taken away our only recourse to complain about the process.

This absurd censorship has been going on for ages, and it certainly not protecting the community, but lately Facebook trolling gotten exponentially worse. Why are you bullying me? I have never done anything that actually goes against “community standards.” Facebook is clearly monitoring everything I post.

For the record, I have been documenting these Facebook infractions and I have re-posted them on my blog, if you would like to see how your Facebook AI bots are attacking people who are doing nothing wrong. I’ve noticed an uptick of friends not being able to post for equally innocuous reasons.

 

Dear Facebook, you need to control your censorship bots. They are doing more harm than good, and their actions definitely go against community standards.

Daffodils for St. David

Last night I finally got around to finishing my daffodil post from 2023, it was more notes than a blog post. And I put the finishing touches on it today, so I do not have a new post for Saint David’s Day. My brain hurts. I can’t believe that it took me a year before I could wrap my head around my notes and craft it into an article. Not sure why it was so difficult. But today I struck gold while researching daffodils. I was trying to find out when narcissi were introduced to the British Isles and got railroaded with false information, with noted writers insisting there was a native daffodil. I finally put that theory to rest via genetic analysis. Their homeland is Iberia (they have the most genetic variation while the cultivars have a limited gene pool.) It looks like they and the word daffodil were introduced to England sometime during the 1590s, but it could’ve been as early as 1400. The information is lost in the mists of time. But now I can stay unequivocally that narcissi are not native to the British Isles. However, I had a great time tracking down the literary references in the process of writing that piece. and the reason why I write is about discovery.

• The cultivated history of daffodils as we know it