Friday, 17 April 2026

Explanatory note to the previous post

Hi C@W readers - you'll may have tried to open the previous post and found a warning, courtesy of our kindly blog platform hosts.  It's safe to click through - we're not advertising anything lewd! 

But some bot, somewhere, has auto-identified the topic as worthy of, err, deflecting readership away from.  The warning came up about 60 seconds after I posted.

If I find from the stats that nobody is reading the post, I'll experiment with a defused version of the title, to see if that gets it past the censors for wider access.

And later I may post on this whole episode!

ND

UPDATE: have reposted under a different title, and trashed the original post which was getting no traffic.

7 comments:

  1. dearieme10:06 am

    Google insisted I "sign in". They can just fuck off.

    ReplyDelete
  2. dearieme10:16 am

    May I lighten the tone? I've just seen a statement from the Chinese government which I find a hoot - the statement, not the government.

    "No foreign country has the right to meddle in China’s internal affairs. Leaders around the world should weigh their words carefully before speaking."

    ReplyDelete
  3. Nick Drew10:40 am

    Thanks. You were not alone in not signing in - it was picking up virtually no traffic.

    So, cutting the Gordian knot, I'm hoping the re-post works the trick. (If it is really AI at work, it might not ... but I'm thinking a less discriminating bot was at work. We'll see ...)

    ReplyDelete
  4. Anonymous10:57 am

    Do you think it was just a coincidence that Google suddenly made access to your comments more difficult after you posted a thoughtful & informative article involving My Noble Lord Inside Trader Fondlebum ?

    ReplyDelete
  5. Nick Drew11:06 am

    Let's see if the repost survives intact. I've stayed with 'Mandygate' but removed mentioned of the famous US suicide from the header. I rather think it was the latter that triggered the response.

    ReplyDelete
  6. Anonymous5:49 pm

    I'm now getting a 404 notice when trying to access the article "The requested URL was not found on this server" .

    ReplyDelete
  7. Nick Drew6:34 pm

    I deleted it, Anon, or fear it might poison the well

    Systems-wise, that is. In terms of content, go to Mandygate: rumbles on and on, getting louder. Maybe still as poisonous as before ...

    ReplyDelete