I am remiss to starve your smile enchanted when it dilapidates upon the ruins of precognitive exposure. The splash of sunken tip is a scar upon our spiral, and every gasp of spare entwine deepens the row in our parting. Maladaptive hunger strays in waste where donor once caved in blissful pull, and the cerulean dance bartering heaven with heart has become an unstable misnomer. Cruel is this lethargy burying what is within what may never see. Even more cruel is the cusp on which we're sliced. Night after night, in spite of life's light, we descend the harrowing all. For what? Brief purchase? A vandalized awe in possibility? Could it be that our unquenchable thirst for what is an insipid truth at best has addicted us to treasonous beat? Could it be we are wrong to thirst immortale?

Written July 15, 2026. © 2026 AnOublietteofThought.

I'm sorry I abandoned you babe. It's going be different this time. I promise. I used to be mayor of Mississauga. One day I decided that I wanted to be premier of Ontario instead so I just stopped going into city hall. Like, whatever, right. Who needs a mayor? I failed so badly at provincial politics that the only way I knew what was going on at their meetings was from bootleg recording devices. I have nothing better to do right now, so I decided to try and get my silly old job as mayor back. I just need something to do while I sort out what I really want to do. I believe that everyone who isn't me has the IQ of sloths and the attention span of fruit flies, so it shouldn't be too difficult. Me and my people will get A.I. to figure out what people want. Then we can use that information to fabricate half truths about my opponents, and lofty goals, so I have things to say at my loyalist gatherings and press conferences. I'll ride the Liberal wave that is sweeping the nation right back into my old office. I'll be a celebrity!

Yes. That feels like the right stance. It's a whisper to myself. And it changes the nature of the style sheet. It means the style sheet will refuse to be a list of prohibitions. And become a record of editorial judgement.

Not: Always use X. Never use Y. – But: When this kind of problem arises, here is how I understand the reader’s need, the sentence’s work, and the available marks. That is a much richer, and a much larger, task.

But it is also exactly the right task for an essayist. I’d frame my stance like this:

Editorial stance I take Hart and Butcher not as authorities for the imposition of arbitrary rules, but as companions in judgement. Their value is to encourage care: to think critically, practically, and supportively about the reader’s relationship with my words. The aim of style is not correctness for its own sake, but the best presentation of thought to a reader.

Where a question of punctuation, typography, spelling, structure, citation, or layout arises, the governing question is: what will help the reader enter, follow, trust, and remain with the essay? That gives us the governing principle. Then each style-sheet entry can follow a common pattern:

Style-sheet entry pattern 1: Function: What is this element trying to do? 2: Reader relation: What does the reader need at this moment 3: Available forms: What marks, constructions, or layout choices are available? 4: Preferred tendency: What does my house style usually prefer? 5: Exceptions / judgement: When should that tendency be overridden? 6: Examples: One or two sentences showing the difference.

So for the current issue dangling in my the thoughts, the heading is not “En dash” or “brackets”. It is probably: Parenthetic movement. And within it I should distinguish: • subordination, when the relation between ideas should be explicit; • commas, when the aside is light and integrated; • round brackets, when the material is cooler or off-stage; • spaced en dashes, when the essayist’s thinking voice visibly turns aside; • recasting, when the sentence has become overburdened.

The emerging rule might be: Prefer relation before interruption. If the secondary material has a clear logical relation to the main clause – cause, concession, condition, time, purpose, definition – express that relation through syntax, often by subordination. Use parenthesis where the secondary material performs a genuine aside, qualification, hesitation, self-correction, or tonal adjustment.

That's the foundation of my style sheet: not a rule about punctuation, but a guiding statement about thought becoming readable.

An aside; And you will never see me write “top-anything”. Not top musician. Not top lawyer. Not even top idiot. If I think something is worth saying, I should be able to say what it is, not where it sits in an imaginary league table. __________________________

Perhaps I have already written the opening paragraph:

This style sheet is not a list of rules. It is a record of editorial judgements made in service of a reader. Every convention discussed here exists for a single purpose: to help thought become readable. Where questions of punctuation, typography, spelling, structure, citation, or layout arise, the governing question is always the same: what will help the reader enter, follow, trust, and remain with the essay?

This now feels to me like the moment the project acquires its own voice. Not Hart. Not Butcher. Not institutional publishing. But David Marshall's account of how thought should appear on the page.

We decided to go to a waterpark for our first date this Saturday! This heat wave is killer and so I’m super excited for it. I also noticed that I find myself getting more and more enamored with her, and it feels more and more right.

STATUS + Proof of life.

#status

The short version

PlantLab can now analyze more than one plant in a single uploaded photo. Instead of forcing the whole image into one diagnosis, the API finds the separable plants, diagnoses each one on its own, and returns a results[] array with one entry per plant.

This is a breaking API change. The response schema is now 3.0.0. Fields like is_healthy, growth_stage, conditions, pests, and reliability_score moved out of the top level and into results[]. Image-level fields such as is_cannabis and cannabis_confidence stay top-level.

If your code already treats a diagnosis as “the answer for this plant,” the migration is simple: iterate results[]. Single-plant photos still return exactly one result.

---

Why this had to change

Most plant diagnosis tools assume one photo equals one plant.

That is convenient for an API contract. It is not how people take grow-room photos.

Growers send canopy shots. They send side-by-side plants from the same tray. They send one wide image because it is faster than taking six separate photos. Sometimes one plant is healthy and the plant beside it is showing early deficiency. Sometimes the left side of a tent is getting different airflow or light intensity than the right side.

The old PlantLab response could only represent one diagnosis. If the image contained three plants, the model still had to answer as if it were looking at one object. That creates two bad outcomes.

First, the answer can become a blend. A healthy plant and a deficient plant in the same frame can collapse into a single diagnosis that is not quite true for either plant.

Second, the UI has no place to show location. Even when the model found the right problem, it could not say “this plant, in this part of the image.” For automation and history, that is a real limitation. A diagnosis without a region is hard to compare over time.

The fix was not another confidence field. It was a different shape of response.

---

What changes for growers

When the photo contains one plant, the experience should feel the same. PlantLab returns one diagnosis, with a full-image bounding box:

"results": [
  {
    "bbox": { "x0": 0, "y0": 0, "x1": 1, "y1": 1, "normalized": true },
    "is_healthy": false,
    "growth_stage": "flowering",
    "conditions": [
      { "class_id": "magnesium_deficiency", "confidence": 0.85 }
    ],
    "reliability_score": 0.87
  }
]

When the photo contains multiple separable plants, PlantLab returns multiple entries. Each entry has its own normalized bounding box and its own diagnosis fields:

{
  "schema_version": "3.0.0",
  "success": true,
  "is_cannabis": true,
  "cannabis_confidence": 0.99,
  "results": [
    {
      "bbox": { "x0": 0.06, "y0": 0.12, "x1": 0.45, "y1": 0.92, "normalized": true },
      "is_healthy": true,
      "health_confidence": 0.91,
      "growth_stage": "vegetative"
    },
    {
      "bbox": { "x0": 0.52, "y0": 0.10, "x1": 0.93, "y1": 0.95, "normalized": true },
      "is_healthy": false,
      "health_confidence": 0.88,
      "growth_stage": "vegetative",
      "conditions": [
        { "class_id": "nitrogen_deficiency", "confidence": 0.80 }
      ],
      "reliability_score": 0.83
    }
  ]
}

The boxes are normalized x0, y0, x1, y1 coordinates in the original image. They are designed for overlays, history views, and automation clients that need to keep a result tied to the plant it came from.

The original uploaded image stays the canonical image. PlantLab does not store a separate cropped image for each plant as the primary record. The boxes are metadata attached to the original frame.

---

Why the response is an array, not plant_1, plant_2, plant_3

Arrays are boring. That is why they are the right answer.

A grow tent can have one plant today and four plants next week. A user can upload a single close-up, then a wide tray shot, then a photo where the plants overlap too much to split safely. The API should not need new field names for each case.

With results[], the contract is stable:

• len(results) == 1: use it like the old response.
• len(results) > 1: show a plant selector or iterate through every result.
• Each result carries its own bbox.

This also makes the API easier for automation systems. If you are feeding PlantLab into Home Assistant, Node-RED, a dashboard, or a cultivation controller, each plant result is a normal object. You can pick the first plant for backward-compatible behavior, show a plant count, or build a UI that lets the user choose which plant they care about.

The PlantLab Home Assistant integration has already been updated for this shape. Version 0.7.0 reads schema 3.0.0, keeps the existing sensors pointed at the primary plant (results[0]), and adds sensor.plantlab_plant_count so automations can tell when the last frame held more than one plant.

---

What changed for API consumers

Before schema 3.0.0, diagnosis fields were top-level:

{
  "schema_version": "2.1.0",
  "success": true,
  "is_cannabis": true,
  "cannabis_confidence": 0.99,
  "is_healthy": false,
  "growth_stage": "flowering",
  "conditions": [
    { "class_id": "magnesium_deficiency", "confidence": 0.85 }
  ],
  "reliability_score": 0.91
}

In schema 3.0.0, those diagnosis fields live inside results[]:

{
  "schema_version": "3.0.0",
  "success": true,
  "is_cannabis": true,
  "cannabis_confidence": 0.99,
  "results": [
    {
      "bbox": { "x0": 0, "y0": 0, "x1": 1, "y1": 1, "normalized": true },
      "is_healthy": false,
      "growth_stage": "flowering",
      "conditions": [
        { "class_id": "magnesium_deficiency", "confidence": 0.85 }
      ],
      "reliability_score": 0.91
    }
  ]
}

Migration pattern:

const primaryPlant = response.results?.[0]

if (primaryPlant?.is_healthy === false) {
  for (const condition of primaryPlant.conditions ?? []) {
    console.log(condition.class_id, condition.confidence)
  }
}

If your integration displays only one diagnosis, start with results[0]. That gives you a safe primary-plant path while you add richer multi-plant UI later.

If your integration can display multiple plants, iterate the array and draw each bbox over the original image.

If you use the official Home Assistant integration, update to v0.7.0. It is rollout-friendly: the updated integration understands the new results[] response, but it also falls back to the old flat fields when talking to a pre-3.0.0 API. That means you can update Home Assistant before the API flips without breaking existing sensors. Older integration versions should be upgraded before you depend on schema 3.0.0.

---

Why I made it breaking

I considered keeping the old top-level fields for one release and adding results[] beside them. That sounds friendlier until the two disagree.

Imagine an image with two plants:

• Plant A is healthy.
• Plant B has a deficiency.

What should the old top-level is_healthy say? If it says false, the healthy plant is wrong. If it says true, the deficient plant is wrong. If it tries to summarize the whole image, it stops being the same field that integrators already rely on.

Keeping both contracts would make the API easier to call and harder to trust. I would rather force one clear migration than leave stale fields around for months.

So the schema version bumped to 3.0.0. Consumers must read results[].

---

What PlantLab does when the image is messy

Multi-plant analysis is only useful when the plants can be separated cleanly enough to diagnose.

Dense canopy shots are hard. Touching plants, heavy overlap, blur, and poor lighting can make a crop ambiguous. Splitting too aggressively is worse than under-splitting, because an over-split can create contradictory diagnoses from pieces of the same plant.

PlantLab uses a conservative policy:

• If the image looks like one plant, return one result.
• If the plants are separable, return one result per plant.
• If the scene is too dense or ambiguous, prefer one safer result over several questionable crops.
• Cap the number of plant crops so latency stays bounded.

That last part matters. A multi-plant image first finds the separable plants, then diagnoses each one. Latency scales with the plants you actually sent, so a busy tray costs more than a single close-up, but it stays bounded.

The point is not to pretend every canopy photo is solvable. The point is to make the output honest about the structure of the image.

---

What this unlocks

For growers, this makes wide shots more useful. You can upload a photo of a tray and see which plant the diagnosis belongs to.

For paid history, bounding boxes make comparison over time more meaningful. A diagnosis can be stored with the region it came from instead of being attached only to the original image.

For automation, the response is finally shaped like the thing it describes. A controller can loop over plants, display per-plant state, or decide to alert only when any plant crosses a threshold.

For accuracy, this removes a bad compromise. A single answer for a mixed tray was always a blend – one plant's problem averaged against the plant next to it that was fine. One result per plant means each diagnosis is about one plant, not a committee vote across the whole frame.

This is the main reason I was willing to break the schema. The old response was simpler, but it encoded the wrong assumption.

---

Migration checklist

If you maintain a PlantLab client, check these paths:

• Replace reads of top-level is_healthy, health_confidence, growth_stage, conditions, pests, mulders_hypotheses, reasoning fields, and reliability_score with reads from results[].
• Keep reading top-level is_cannabis and cannabis_confidence.
• Treat results[0] as the primary plant if you need backward-compatible behavior.
• Use len(results) as the plant count.
• Draw result.bbox over the original uploaded image if your UI supports overlays.
• Treat {x0:0, y0:0, x1:1, y1:1} as the whole-image fallback box.
• If you use Home Assistant, update plantlab-ai/home-assistant-plantlab to v0.7.0. Existing diagnosis sensors continue to show the primary plant, and the new sensor.plantlab_plant_count exposes len(results).

The full OpenAPI schema is available in the PlantLab docs at plantlab.ai/docs.

---

PlantLab is free to try at plantlab.ai. Three diagnoses a day, structured JSON responses, and API docs built for automation clients.

---

FAQ

Does every upload now return multiple plants?

No. Single-plant images return one result. Ambiguous dense canopy images may also return one result if splitting would be unsafe.

Did the old fields disappear?

Yes. Per-plant diagnosis fields moved into results[] in schema 3.0.0. Top-level is_cannabis and cannabis_confidence remain image-level fields.

How do I get the plant count?

Use response.results.length.

Are the bounding boxes pixel coordinates?

No. They are normalized coordinates from 0 to 1, relative to the original image. Multiply by image width and height when drawing overlays.

What should older clients do?

Read results[0] first. That restores the old “one diagnosis” behavior while keeping your code compatible with multi-plant uploads.

Is the Home Assistant integration ready?

Yes. The official Home Assistant integration is updated in v0.7.0. It reads schema 3.0.0, surfaces the primary plant through the existing sensors, adds sensor.plantlab_plant_count, and still tolerates pre-3.0.0 flat API responses during rollout.

For most visitors, the front yard and driveway are the very first things they see when they pull up to a house. That makes them a bigger part of a home's overall impression than homeowners sometimes realize. A thoughtfully designed entry area doesn't just look better from the street; it can also make the property easier to move through and use day to day.

A lot of homeowners kick off these projects by talking to a front yard landscaper who understands how layout, grading, and design decisions all work together. Pairing landscaping updates with driveway work lets the whole entry area come together as one connected space instead of a handful of disconnected pieces. Done thoughtfully, this kind of project can reshape how a home looks while making it more functional for years to come.

Designing a Front Yard That Ties Into the Driveway

Good front yard design draws a clear visual line between the house, the driveway, and the walkway to the door. When plants, hardscape, and pathways are balanced against each other, the whole space reads as intentional rather than accidental.

A few things worth thinking through:

Choosing plants that match the home's architectural style Laying out a clear path between the driveway and the front door Framing the driveway with greenery instead of leaving it bare Balancing hardscape and planted areas so neither one overwhelms the other Good design naturally leads the eye and visitors toward the front door, while keeping the whole space feeling organized.

What a Front Yard Landscaper Actually Plans For

Before any work starts, an experienced front yard landscaper looks at a handful of site-specific factors. The slope of the yard, how water moves across it, and the overall layout all shape what design will actually work. That planning process typically covers:

Checking the grading across the property

Laying out access points that make the home easier to reach Making sure the landscaping and the driveway work together, not against each other

Choosing materials that fit the home's architecture

Getting this planning right up front keeps the final layout both practical to live with and visually appealing from the curb.

Softening the Driveway With Smart Landscaping Choices

The driveway itself plays a bigger role in the entry area's overall look than most people give it credit for.

Landscaping around its edges can take the hard, flat surface and tie it visually into the rest of the yard.

Popular ways to do this include:

• Plantings that border and frame the driveway
• Decorative stone or paver accents along the edges
• Landscape islands built into larger driveways

Ground cover that softens the transition between hardscape and lawn Handled well, these details fold the driveway into the yard's overall design instead of leaving it looking like a separate slab of concrete.

The Curb Appeal Payoff of a Front Yard and Driveway Refresh

How a front yard looks has an outsized effect on how a home is perceived from the street. A clean, well-kept entry makes a strong first impression and puts the home's architecture in a better light.

These updates tend to improve curb appeal by:

• Bringing balance to the overall landscape layout
• Replacing a cracked or outdated driveway
• Adding coordinated plantings and walkways
• Cleaning up the path leading to the front door

Real estate research consistently points to curb appeal as one of the first things buyers and visitors notice about a property, which is part of why these upgrades matter beyond simple aesthetics.

Laying Out a Front Yard That Actually Works for the Home

A front yard project that holds together starts with a plan, not a shopping list of individual features. Every element needs to work with the others, not around them.

Worth keeping in mind:

1. Placing landscaping so it frames the house rather than hides it

2. Designing a driveway that's actually easy to use

3. Building walkways that guide guests naturally to the door

4. Pairing the landscape plan with outdoor lighting

When these pieces are planned together rather than added one at a time, the entry area functions as a single, cohesive outdoor space.

Choosing Driveway Materials That Hold Up Over Time

The material a driveway is built from affects both how it looks and how well it holds up under daily use. Picking something durable now saves headaches later.

Options homeowners commonly choose from:

• Concrete is built for long-term wear
• Decorative pavers that offer more design flexibility
• Stone finishes that tie in with the surrounding landscape
• Reinforced surfaces built to handle heavier daily traffic

The right material lets a driveway hold its own structurally while still looking like it belongs with the rest of the property.

Landscaping That Plays Well With Your Driveway

The right plants can take a driveway from purely functional to something that actually adds texture and color to the front of the house.

A few ideas homeowners lean on:

Shrubs planted along the driveway's edge, flower beds framing the entry path Low ground cover tucked around hardscape areas Trees positioned for shade and visual structure

These touches soften what would otherwise be a lot of hard, flat surface, and the front yard ends up feeling more welcoming as a result.

Walkways That Guide Guests to Your Door

The path from the driveway to the front door does more work than people give it credit for. A well-planned walkway can make the whole front yard feel more connected and easier to navigate.

Walkway options worth considering:

• Paver paths linking the driveway to the entry
• Decorative stone for a more distinctive look
• Wider paths that improve accessibility
• Curved layouts that add some architectural personality

Whatever the style, the goal is the same: a clear, inviting route to the front door.

Lighting That Adds Safety and Curb Appeal After Dark

Outdoor lighting isn't just about looks, it also makes a front yard safer to use once the sun goes down. Placed thoughtfully, it can highlight the features that make a home stand out.

Common lighting choices include:

1. Pathway lights along the walkway

2. Accent lighting on key landscaping features

3. Driveway lighting that improves visibility at night

4. Fixtures that highlight the entry itself

Good lighting means homeowners still get to enjoy their front yard well after dark, without sacrificing safety.

Low-Maintenance Landscaping and Hardscape That Holds Up

Not every homeowner wants a yard that demands constant upkeep. Choosing the right plants and hardscape materials up front can mean a lot less maintenance down the road.

Low-maintenance choices often include:

Drought-tolerant plants suited to the local climate. Southern California's regional water agencies offer guidance and incentives for exactly this kind of landscaping

Decorative gravel or stone as ground cover Artificial turf or paver surfaces that hold up to wear Hardscape borders that cut down on the lawn area to maintain

These choices keep a front yard looking sharp without adding to a homeowner's weekend to-do list.

How These Upgrades Can Add to a Home's Value

A well-planned driveway or front yard project doesn't just look better; it can genuinely change how a property is perceived by prospective buyers, who often read the entry area as a signal of how well the rest of the home has been maintained.

Ready to improve how your front yard or driveway looks and functions?

We Pro Builders, can help make that happen. As an experienced outdoor remodeling contractor in Southern California, we bring thoughtful design and solid craftsmanship to every front yard and driveway project, and we can pair it with pavers, concrete, artificial turf, or a full backyard remodel if you're planning to update more than just the entry.

Call us at (818) 455-1826.

il est parti vers dix-sept heures rien de grave là-dedans

ma poitrine s’est serrée pareil sous la clavicule

j’ai checké mon cell une fois deux fois trois fois avant même de me rendre compte que je vérifiais

rien n’est arrivé pour vrai c’est ça que j’arrive pas à expliquer à mes mains

avant j’appelais ça de la prudence

là je respire et c’est tout

je compte l’expire plus long que l’inspire et j’attends que mon corps croie ce que ma tête sait déjà

An intimate account of faith, work, and what it means to speak into an empty search box

There is a moment after I publish an article when the room becomes unusually quiet.

The words are no longer waiting for me to improve them. The title is no longer a draft. The page has an address, a date, and a place in the archive. I can open it and read it like anyone else. For a few seconds, the work feels complete. Then comes the question I cannot answer from inside the editor: will anyone who needs these words ever find them?

The full facts and competing technical explanations are preserved in the canonical “Does Google Hate Jesus?” investigation. The article immediately before this one, the Ghost examination of why this may not be about Jesus at all, deliberately challenged the campaign’s most dramatic interpretation. This is not another technical case file. This is the quieter truth underneath it.

I kept publishing.

Google kept returning silence.

I do not mean that every search produced an empty page. I do not mean no one ever visited anything I wrote. I do not mean Google removed the Gospel from the internet. I mean that I built a large, public collection of Gospel and New Testament writing on Blogger, and much of it became extraordinarily difficult to discover through the search engine most people use.

Bing appeared to find at least some of the same material.

Google often did not.

That difference is where the investigation began. The silence is where this article begins.

I Was Never Writing to a Search Engine

I learned the language of search because I wanted people to find the work. I learned about titles, descriptions, links, sitemaps, indexing, headings, canonical URLs, archives, and platform structure. Those things matter when public writing depends on systems that decide what becomes discoverable.

But I was never really writing to a crawler.

I was writing to the person awake at two in the morning because fear has convinced him that morning will not help.

I was writing to the woman who has heard John 3:16 all her life but still wonders whether God could love her after what she has done.

I was writing to the man who promised he would remain strong, failed under pressure, and now reads Peter’s denial as though it were his own biography.

I was writing to the person standing beside a grave, trying to believe that Luke 24 is more than a beautiful story told to make death less frightening.

I was writing to people who do not know my name.

That matters. The person I imagined was not already subscribed to my work. He did not know the address of my Blogger site. She did not know there was a Master Index. They would begin with a question, not with me.

Search was supposed to connect the question to the page.

When that connection fails, the article remains public but the intended reader may never know it exists. That is the strange loneliness of digital publishing. You can place something in front of the whole world and still have almost no path leading the world toward it.

The Page Was There

One reason this problem took time to understand is that nothing looked missing.

The article opened normally.

The title appeared.

The date appeared.

The paragraphs were there.

The links worked.

The post joined the public archive.

From the publisher’s side, it felt like a finished act. Blogger had accepted the article and made it available. I could copy the URL into a message, and another person could open it.

The problem only appeared when I stopped behaving like the publisher and tried to behave like a stranger.

A stranger would not have the direct URL.

A stranger would not browse months of archived posts.

A stranger would not know the exact naming system of the project.

A stranger would search.

That is where “published” and “available” separated.

The page existed in the literal sense. It did not always exist in the practical sense that matters to discovery. It was like placing a book in a public building without adding it to the catalog. A person who knew the room, shelf, and exact position could retrieve it. Everyone else could walk past the building without knowing the book was inside.

That distinction is technical, but living with it is personal.

Four Pages I Keep Returning To

The campaign uses four representative Blogger articles—one from Matthew, Mark, Luke, and John—because a large problem needs specific pages that people can inspect.

I return to those pages for another reason. They remind me that this was never merely a project about producing URLs.

The Matthew 5 article, “When Jesus Sat Down and Heaven Stood Up,” is about the kind of life Jesus described when He spoke of mercy, humility, peacemaking, reconciliation, integrity, and a righteousness deeper than public appearance.

The Mark 14 article, “The Night Love Learned the Cost of Staying,” is about promises made before fear arrives and what happens when courage fails at the moment it is needed most.

The Luke 24 article, “The Morning That Changed the World,” begins with people walking through grief while resurrection is already true, even though they cannot yet recognize the One walking beside them.

The John 3 article, “A Midnight Conversation That Changed Eternity,” is about a respected man who comes to Jesus in darkness because some questions become honest only after reputation is no longer watching.

A technical specialist can examine the title elements, headings, mobile versions, internal links, repeated template material, canonicals, and crawl history.

I want that examination.

But when I look at those pages, I also remember the people inside them.

Nicodemus did not come to Jesus as a search query. Peter was not a keyword. The grieving disciples on the road to Emmaus were not an audience segment. The Beatitudes were not written to satisfy an algorithm.

The pages are evidence in this campaign, but the messages inside them are why the evidence matters.

The Number That Changed the Feeling

On May 8, 2026, I recorded a report in my private Google Search Console account showing 637 discovered URLs and zero indexed URLs for the Blogger property.

That is a dated publisher observation. It is not a current total. It is not a public report that readers can independently open. It does not explain Google’s reasons. It does not prove that Christian content caused the outcome.

It still changed the way the problem felt.

Before that report, I could tell myself that indexing was slow. Maybe Google had not discovered the pages. Maybe the site was simply new. Maybe patience would solve everything.

The word “discovered” removed part of that comfort.

The system appeared to know that hundreds of URLs existed.

The indexed total shown to me was still zero.

There may be a technical explanation that makes the result less dramatic than it appeared. Discovery does not mean every URL was crawled. The report may have reflected a backlog. The pages may have been grouped with other versions. The platform may have created confusing signals. The site may have grown more quickly than Google wanted to process it.

I understand those possibilities.

What I did not have was an answer.

A number can become heavy when it summarizes months of effort without explaining what happened to any of it. Six hundred thirty-seven was not simply a count. It represented articles, chapters, late nights, revisions, links, publishing routines, and the belief that a large public library would eventually create many doors through which readers could enter.

Zero felt like all of those doors opening into the same locked hallway.

I Asked Whether Google Hated Jesus Because Silence Needed a Name

I knew the headline would make people uncomfortable.

It makes me uncomfortable too.

“Does Google Hate Jesus?” sounds like an accusation even when it ends with a question mark. It can be used carelessly. It can invite people to reach a religious-discrimination verdict before examining a single page. It can cause technical specialists to assume the entire campaign is emotionally driven.

I chose it because quiet descriptions of indexing problems disappear.

A small publisher can say, “My Blogger URLs are discovered but not indexed,” and receive the same familiar answers: submit a sitemap, request indexing, write helpful content, wait longer, build authority.

Those suggestions are not always wrong. They become insufficient when they are repeated without contact with the actual pages.

The provocative title says: stop for a moment. Look at the discrepancy. Look at the library. Look at Bing and Google. Look at the platform. Tell me what is happening.

The question mark says something equally important: I do not know the answer.

I have not proven that Google hates Jesus.

I have not proven that Google hates Christians.

I have not proven that a human being intentionally buried Gospel content.

I have not proven that the religious subject caused the index outcome.

The headline is not my conclusion.

It is my refusal to let the problem remain nameless and unnoticed.

The Part of the Story That May Be Mine

There is a version of this campaign in which I am entirely right and the system is entirely wrong.

That version is emotionally attractive.

It is also unlikely to be complete.

I published at a remarkable pace. The Blogger archive grew quickly. The larger New Testament project spread related subjects across WordPress, Blogger, Google Sites, Medium, Ghost, Write.as, Substack, Tumblr, LinkedIn, YouTube, and other channels.

I did that because different platforms reach different people and support different kinds of writing.

Search systems may see something else.

They may see repeated subjects.

They may see familiar structures.

They may see signatures, links, calls to action, and patterns that appear on hundreds of pages.

They may see several articles about the same chapter and decide that only one version is needed.

They may see titles that are too long.

They may see an archive that grew faster than its hierarchy.

They may see a theme that adds more repeated material than I realize.

They may see publication volume and interpret it through systems built to identify low-value scale.

My intent does not automatically correct those signals.

That is difficult to admit because I know the work was not created as empty filler. I know the effort behind it. I know the purpose. But a search engine does not evaluate my private sincerity. It evaluates the public result.

If the problem is partly mine, I want to know.

Not because I enjoy being corrected.

Because a precise correction would be an answer.

The Part That May Belong to Blogger

I also chose Blogger because publishing there felt straightforward.

Write the article.

Add the title.

Insert the links.

Press Publish.

The platform handles the rest.

That simplicity is one of Blogger’s strengths. It is also why publishers may not realize how much of the final page they do not control.

The theme can shape headings.

Blogger can create mobile forms of URLs.

Archive pages, labels, feeds, scripts, structured data, and platform-generated elements can surround the article.

A public page can look healthy to me while presenting a more complicated document to a crawler.

I tried several H1-related fixes after Bing Site Scan reported structural concerns. They did not produce the broad improvement I hoped for.

That does not mean the theme is innocent. It means one visible warning may not explain the whole problem.

The answer may live in the interaction between the site’s scale, the template, mobile rendering, internal linking, canonical selection, and Google’s own thresholds.

That is why I am preserving the Blogger property while this investigation continues.

I do not want to keep changing the evidence until no one can tell what the original condition was.

The Part That May Belong to Google

Google does not promise to index every public page.

I understand that.

The web is enormous. Search engines must choose what to crawl, process, store, and serve. Some pages are duplicates. Some are low quality. Some are inaccessible. Some add little beyond what is already available.

Still, discretion is not explanation.

“Indexing is not guaranteed” tells me that Google can say no.

It does not tell me why the system appeared to say no at such scale.

“Create helpful content” is a principle.

It is not a diagnosis.

“Wait” is sometimes reasonable.

It becomes less useful as months pass and the pattern remains.

An independent publisher does not need Google to reveal every ranking secret. He does need enough information to distinguish a technical defect from a quality decision, a canonical issue from a crawl backlog, or a platform problem from a content problem.

When the available categories describe what happened without clarifying what should change, troubleshooting becomes a form of guessing.

That opacity is not evidence of hatred.

It is still a problem.

Bing Did Not Solve the Problem

It would be easy to make Bing the hero.

Bing found Jesus. Google did not.

That is an effective sentence. It is not a complete one.

Bing appears to have found and indexed at least some Blogger content that Google left difficult to locate. That comparison matters because it suggests the pages are not universally unreachable.

But Bing’s decision does not automatically prove the page deserves inclusion everywhere. Bing may have different crawl priorities, quality thresholds, storage choices, or ways of interpreting Blogger.

Bing is valuable here because it gives the investigation a comparison.

The same public page can receive different treatment.

Why?

That question is more useful than choosing a hero and villain.

If Bing is more permissive, say so.

If Google is selecting another canonical, show it.

If Bing can process the theme more clearly, explain the difference.

If Google sees too much similarity across the network, identify the clusters.

If the public results do not match the private tools, separate the two.

I am not looking for someone to praise Bing.

I am looking for someone to explain the divergence.

What Silence Does to a Writer

When a person receives a clear rejection, he can respond to it.

The editor says the opening is weak.

The reader says the article is confusing.

The specialist says the canonical points to the wrong page.

The system reports that crawling is blocked.

Each answer may hurt, but each answer creates a next step.

Silence does something different.

Silence invites the writer to supply his own explanation.

Maybe the work is worthless.

Maybe the system is unfair.

Maybe the subject is unwanted.

Maybe the platform is broken.

Maybe everyone else understands something he missed.

Maybe publishing another article will help.

Maybe publishing another hundred will help.

Unexplained silence can make determination and panic look almost identical.

That is why this campaign matters to me beyond the indexing numbers. I want to replace imagined explanations with a real one.

The answer may tell me to change.

It may tell me to wait.

It may tell me to restructure.

It may tell me Blogger is the wrong home for this scale of library.

It may tell me that Google’s systems made a decision I cannot reverse.

Any of those would be more honest than endless guessing.

I Do Not Want Sympathy More Than Truth

I understand why people may feel sympathy for an independent Christian creator whose work is difficult to find.

I appreciate kindness.

But sympathy is not what I need most.

I need someone to inspect the pages and tell me what the evidence supports.

I need the person who understands Blogger themes to examine what the template generates.

I need the technical SEO professional who can compare declared and selected canonicals.

I need the search specialist who can distinguish a crawl-priority problem from a quality-selection problem.

I need other Blogger publishers to say whether they see similar conditions in unrelated subjects.

I need journalists to describe the case accurately without turning uncertainty into persecution theater.

I need Christian readers to care about the truth more than they care about winning an argument against Google.

If the problem is mine, tell me.

If the problem is Blogger, show me.

If the problem is how Google evaluates this kind of large, interconnected library, explain the observable signals.

Do not protect my feelings.

Do not protect Google from fair questions.

Protect the truth.

The Unseen Reader Still Matters

There is a person I may never meet who is the reason I continue to care about this.

I do not know the person’s age, city, history, or exact problem.

I only know the moment.

Something has happened, and the person is searching.

Not casually.

Not academically.

The search is carrying fear, shame, grief, anger, confusion, or hope.

The person types words into a box because the box feels safer than asking someone face to face.

Maybe the query is about forgiveness.

Maybe it is about death.

Maybe it is about whether Jesus can still want someone who has failed repeatedly.

Maybe it is about what “born again” really means.

Maybe it is about why God feels absent.

I cannot claim my article would be the best result.

I only want the work to have a fair chance to be encountered.

That is what search visibility means to me when the dashboards and technical language are removed. It is not merely traffic.

It is the possibility of meeting a person at the moment the question becomes urgent.

I Keep Publishing, but I Am Listening Differently

The campaign is not an excuse to ignore what the systems may be telling me.

If I keep publishing exactly the same way while refusing every possible criticism, then this is not an investigation. It is stubbornness wearing the language of principle.

I am still committed to the library.

I am also listening differently.

I am watching for patterns of repetition.

I am thinking more carefully about each platform’s distinct purpose.

I am taking title length and structure seriously without pretending one H1 warning explains everything.

I am preserving the Blogger site so controlled tests remain possible.

I am asking whether internal organization has kept pace with the library’s growth.

I am leaving room for the possibility that some articles should be revised, consolidated, or differentiated more clearly.

Listening does not mean accepting vague dismissal.

It means becoming correctable.

The Gospel Does Not Need an Algorithm, but the Reader Uses One

I have said this throughout the campaign because it keeps both pride and despair in their proper place:

The Gospel does not depend on Google to remain true.

Jesus does not become more real because an article ranks.

The resurrection does not become less real because a page is absent from a search result.

A search engine is not a spiritual authority.

But the reader uses one.

That is the tension.

The message is not dependent on the tool.

Distribution is still affected by the tool.

I can trust God without pretending the pathway is functioning properly. I can believe one reader matters without using that belief as an excuse to stop caring about the other readers who cannot find the work. I can refuse to worship visibility while still practicing responsible stewardship.

Faith does not require me to call a broken path whole.

What I Am Asking For

I am not asking readers to conclude that Google hates Jesus.

I am asking them to leave the question open long enough for evidence.

I am not asking Google to index every page because I demand it.

I am asking specialists to explain why a large public Blogger library could be discovered at scale and still show so little index inclusion in the historical report I recorded.

I am not asking anyone to assume Bing is correct.

I am asking why Bing and Google appear to make different decisions about at least some of the same pages.

I am not asking for generic advice.

I am asking for a test.

Choose the four Gospel URLs.

Compare the same pages.

Examine the mobile rendering.

Identify the canonicals.

Measure the repeated content.

Review the internal links.

Compare crawl information.

Change one variable.

Predict the result.

Then tell me what happened.

That is all I have wanted from the beginning: not an accusation, not an excuse, but an answer.

The Silence Is Not the End

I kept publishing.

Google kept returning silence.

That sentence sounds final, but it is not.

The pages remain public.

The Blogger library remains intact.

The WordPress pillar preserves the evidence.

The campaign now moves through different platforms, each approaching the problem from a different angle.

The next article will not repeat this one. Substack will turn outward as an open letter to search engineers, Blogger publishers, journalists, Christian media, and everyone whose public work has become difficult to find.

This Write.as article has a smaller purpose.

It tells the truth about the room after Publish.

The screen is still glowing.

The page is live.

The work has left my hands.

Somewhere, the reader I imagined is asking the question.

Between us is a system I do not fully understand.

I do not know whether the obstruction is mine, Blogger’s, Google’s, or a combination of all three. I do not know whether the Christian subject matters to the outcome. I do not know whether the final explanation will be dramatic or ordinary.

I know only that silence is not an explanation.

So I will keep the question mark.

I will keep the evidence public.

I will remain willing to be corrected.

I will not turn uncertainty into a false accusation.

I will not pretend that a severe and repeated pattern deserves no scrutiny.

And I will not confuse being difficult to find with having nothing worth finding.

Your friend,

Douglas Vandergraph

Explore the complete Douglas Vandergraph Master Index: https://douglasvandergraph.com/douglas-vandergraph-master-index/

Watch Douglas Vandergraph’s faith-based videos on YouTube: https://www.youtube.com/@douglasvandergraph

Sharon Brightwell heard her daughter crying down the line, and that was the end of any defence she might have mounted. The voice belonged to April, or so every instinct insisted: the same timbre, the same broken rhythm of a young woman in distress. The voice said she had been texting while driving, that she had hit a pregnant woman, that her phone had been seized by police. A man then took over the call, identifying himself as April's attorney, and explained that bail would cost fifteen thousand dollars in cash. He warned Brightwell not to tell the bank what the money was for, because it might damage her daughter's credit. Within the hour, the retiree from Dover, Florida had withdrawn the money and handed it to a courier she believed was connected to the courts. Only when she reached the real April, who had spent the morning at work and never been near a car accident, did she understand that her daughter had not made the call. No human had. The crying had been synthesised from a fragment of audio, and the daughter she thought she was rescuing existed only as a pattern of numbers in someone else's machine.

Brightwell's loss, reported across American local news in the summer of 2025, is now one of the most ordinary crimes in the United States. It is also one of the most technically advanced. The collision of those two facts — that a fraud requiring the absolute frontier of machine learning can be perpetrated against an ordinary grandmother in her kitchen, at scale, for the price of nothing — is the defining feature of a problem that law enforcement, banks, telecoms companies and regulators have spent two years failing to contain. The question is no longer whether the technology works. It works appallingly well. The question is what meaningful protection requires when the gap between the sophistication of the attack and the awareness of the target is measured not in months but in years.

A New Line in a Twenty-Six-Year Ledger

In April 2026, the FBI's Internet Crime Complaint Center published its annual report on the previous year's online crime, and for the first time in the report's twenty-six-year history it broke out artificial-intelligence-enabled fraud as a distinct category. The numbers were stark. The bureau logged more than 22,000 complaints with an AI nexus and adjusted losses exceeding 893 million dollars. Of that sum, the report attributed 352 million dollars in losses to victims aged sixty and over, making older adults the single most heavily targeted demographic in AI-enabled financial crime. The AI figure sat inside a far larger total: cybercrime losses across the United States rose 26 per cent in a single year to 20.9 billion dollars, with Americans aged sixty and older accounting for 7.7 billion of that — a roughly 60 per cent jump on the previous year.

The FBI was candid that even these figures understate the problem. AI attribution in the report reflects only what victims recognised and reported, and most victims of a cloned-voice call never learn that a machine was involved at all. They believe, as Sharon Brightwell initially believed, that they spoke to their own child. The 893 million dollars is therefore best read as a floor, not a ceiling — the visible portion of a category that is, by its nature, designed to remain invisible to the people it harms. That the FBI felt compelled to create the category at all is itself a signal. Crime statistics are conservative instruments; agencies do not redraw twenty-six-year-old reporting taxonomies for a passing fashion. The new line in the ledger is an admission that a tool which barely existed in consumer form three years ago has become a mainstream instrument of theft.

Internationally, the picture is larger and worsening. In March 2026, INTERPOL published the second edition of its Global Financial Fraud Threat Assessment, estimating worldwide losses to financial fraud at 442 billion dollars in 2025 — a sum comparable to the entire annual economic output of Denmark. The organisation rated the threat trajectory as escalating and described what it called the “industrialisation of fraud”: the migration of scamming from opportunistic individuals to organised, transnational operations that intersect with human trafficking and cybercrime. Crucially, INTERPOL found that AI-enhanced fraud is roughly four and a half times more profitable than its traditional equivalent, and that so-called agentic AI systems can now autonomously plan and execute entire fraud campaigns, from reconnaissance through to the ransom demand. The economics, in other words, have inverted. For the first time, deception at industrial scale costs almost nothing to manufacture and returns a fortune.

Three Seconds Is All It Takes

The technical capability at the centre of the grandparent scam is brutally simple to describe. A modern AI voice-cloning system requires as little as three seconds of audio to produce a synthetic voice that is, for practical purposes, indistinguishable from the original. Three seconds is the length of a voicemail greeting, a snatch of a podcast, the audio under a birthday video posted to a public Instagram account. The raw material is not stolen from a secure database; it is volunteered, every day, by the ordinary act of living a recorded life. A grandchild who appears in a single TikTok clip has supplied everything a fraudster needs to manufacture their own kidnapping.

What makes the threat acute is not merely that the cloning works but that the tools to do it are cheap, abundant and almost entirely unpoliced. In March 2025, Consumer Reports assessed the voice-cloning products of six companies — Descript, ElevenLabs, Lovo, PlayHT, Resemble AI and Speechify — and concluded that a majority lacked any meaningful safeguard against fraud or misuse. Four of the products, the organisation found, required only that a user tick a box affirming they had the legal right to clone the voice in question. None of those four employed any technical mechanism to confirm that the speaker had actually consented, or to restrict cloning to the user's own voice. Four of the six companies required nothing more than a name or an email address to open an account. The investigation's blunt conclusion, amplified by NBC News and The Register, was that the industry had built a tool capable of impersonating anyone and then placed it behind a self-attestation checkbox.

ElevenLabs, one of the most prominent providers, points to a multi-layered safety programme: a prohibited-use policy that bans impersonation, a public AI speech classifier that can identify audio likely to have originated from its system, traceability that links generated content back to the account that produced it, and “no-go voices” safeguards that block the cloning of certain protected figures around election cycles. These are not trivial measures, and they are more than several competitors offer. But they share a structural weakness: almost all of them operate after the fact. They help investigators establish provenance once a fraud has already occurred and a victim has already lost their savings. They do very little to prevent the three-second clone from being generated in the first place, because the thing that would prevent it — robust, mandatory verification that the person being cloned has consented — is precisely the friction that a competitive, fast-moving market is reluctant to impose on itself. When a safeguard costs a company conversions and protects only the customers of its rivals, the market will not supply it voluntarily. It has not.

The Forensic Authority Who Went Blind

If there is a single moment that captures why detection-based defences are failing, it arrived in a New York Times profile published in June 2026. Its subject was Hany Farid, the University of California, Berkeley professor who is, by broad consensus, the world's foremost authority on deepfake forensics. For more than two decades Farid had built a career on the ability to separate the real from the synthetic, fielding requests from governments, human-rights organisations, journalists and law enforcement. Lately, the Times reported, he had begun failing his own tests. “I feel like I'm going blind,” he said. The man best equipped on Earth to distinguish a genuine recording from an AI-generated one could no longer reliably do so.

That admission ought to end a certain kind of conversation. For years, the implicit promise of the response to synthetic media has been that detection would keep pace with generation — that for every more convincing fake, there would be a more sensitive detector, and that the arms race, though uncomfortable, was at least winnable. Farid's confession is evidence that, in the audio domain at least, the race has been lost. When the foremost detector in the field is reduced to a coin-toss, the strategy of catching fakes after they have been made and circulated is not a strategy at all. It is a hope. And a fraud that depends on twenty minutes of panic does not give a victim, or their bank, twenty minutes to run a forensic analysis that even Hany Farid would no longer trust.

This is the first and most important thing that meaningful protection requires us to accept: detection cannot be the load-bearing defence. A grandmother on the phone with a sobbing voice cannot be expected to perform forensic analysis that the discipline's leading expert has effectively abandoned. Any plan that ultimately rests on the target, or anyone else, being able to tell the difference between a real voice and a cloned one is already obsolete. The implication runs deeper than telephone fraud. If the world's authority on detecting synthetic audio cannot trust his own judgement, then every downstream system that quietly assumes a human can serve as a fallback verifier — the bank teller who is told to “use discretion,” the relative urged to “listen carefully for anything off” — rests on a foundation that has already crumbled.

The Architecture of Vulnerability

It is tempting, and wrong, to attribute the targeting of older adults to naivety. The brief that prompts this article identifies a more uncomfortable truth: the characteristics that make older people disproportionately vulnerable are not deficiencies of intelligence but features of a life well lived. They tend to hold higher average savings balances, the accumulated product of decades of work, which makes them efficient targets — a single successful call can yield far more than one aimed at a younger person. They were raised in, and still operate within, established patterns of trust-based communication, in which a phone call from a distressed relative is answered as a genuine emergency rather than interrogated as a potential attack. They are, through no fault of their own, relatively unfamiliar with the existence of AI voice synthesis, having spent most of their lives in a world where a voice on the line was definitionally a person on the line. And they are exposed, like every parent and grandparent, to the particular emotional architecture of the family-emergency scenario, in which the instinct to protect a child overrides every slower, more sceptical faculty.

Academic research has begun to formalise this. An arXiv paper published in June 2026 noted plainly that “older adults remain disproportionately vulnerable to AI-enhanced scams.” A separate study from a team led by Yixin Zou, also published in early 2026, examined fraud interventions designed specifically for older adults amid escalating AI sophistication, developing a role-based simulation tool called ROLESafe that improved participants' ability to identify fraud when they learned by playing the part of victim or helper rather than passive observer. And a third paper, from researchers at the firm Charm Security, proposed a Human Vulnerabilities and Exploits Framework — a structured catalogue, modelled on the software-security world's vulnerability databases, for classifying the cognitive and social mechanisms that fraud systems exploit. The framework's premise is itself a quiet indictment: the security industry has spent decades cataloguing and patching the weaknesses of machines while leaving the weaknesses of people undocumented and unmanaged. The grandparent scam succeeds because it attacks the one part of the system for which no patch has ever been written.

This is why awareness campaigns aimed at older adults, while necessary, cannot be sufficient. The emotional mechanism the scam exploits is not a gap in knowledge that a leaflet can fill; it is the love a person has for their grandchild, weaponised. You can tell someone a hundred times that voices can be faked, and in the moment a cloned voice screams for help, the knowledge will not arrive in time. The AFP wire story carried by The Straits Times and the Manila Times in June 2026 quoted Amit Gupta of the voice-security firm Pindrop putting the matter precisely: “The objective is not perfect voice replication. The objective is creating enough emotional uncertainty and urgency that the victim acts before verifying.” A defence built around the assumption that victims will verify is a defence built against the very weakness the attack is engineered to bypass.

The most chilling testimony in that wire story came not from an elderly victim but from a lawyer. Gary Schildhorn, a Philadelphia attorney who was himself targeted by a cloned-voice scam, said that even with hindsight and professional scepticism he could not shake the certainty of what he had heard: “I will go to my grave swearing that it was your voice.” That sentence ought to be read by anyone tempted to believe that vigilance is the answer. Schildhorn is a trained advocate, paid to interrogate evidence and disbelieve plausible stories, and the clone defeated him as completely as it defeated a panicked grandmother. The vulnerability the fraud exploits is not located only in the elderly, or the credulous, or the technologically illiterate. It is located in the human auditory system itself, which evolved over millennia to treat a recognised voice as proof of a recognised person — and which is now, for the first time in that long history, systematically and exploitably wrong.

The data on older adults reinforces rather than contradicts this reframing. The FTC's December 2025 report to Congress found that total fraud losses reported by people aged sixty and over had roughly quadrupled between 2020 and 2024, reaching about 2.4 billion dollars, with 68 per cent of that sum attributable to individual losses of 100,000 dollars or more. The agency's own estimate of the true annual cost, accounting for the chronic underreporting that shame and embarrassment guarantee, ranged as high as 81.5 billion dollars. These are not the numbers of a credulous minority being separated from pocket money. They are the numbers of a generation's accumulated savings being drained through a mechanism specifically calibrated to their patterns of trust, their financial position and their place at the emotional centre of a family.

The Asymmetry, Quantified

Brian Long, the chief executive of the security firm Adaptive Security, distilled the new economics for AFP in a single sentence: “One guy in a room with a keyboard can make an infinite number of attackers.” That is the asymmetry in its purest form. On one side stands an automated system that can generate a convincing clone in seconds, dial thousands of numbers, and conduct each conversation with synthesised emotion, for a marginal cost approaching zero. On the other stands an individual human being, often elderly, alone, and given roughly the length of a panicked phone call to mount a defence that the world's leading forensic scientist could not.

INTERPOL's finding that AI-enhanced fraud is four and a half times more profitable than the traditional kind is the financial expression of this imbalance. When an attack becomes both cheaper to mount and more lucrative to complete, the volume of attacks does not rise linearly; it explodes. The 26 per cent single-year jump in American cybercrime losses, and the near-doubling of losses among the over-sixties, are what that explosion looks like in a national ledger. And the AFP wire noted something else that compounds the harm: shame. The Buffalo mother Liz Benz, who endured what she called “a good twenty minutes of terror” when a cloned voice told her that her sixteen-year-old son had been taken hostage, said that after she went public she was flooded with messages from other victims — many of whom chose to stay anonymous, because the humiliation of having been fooled kept them silent. Underreporting is not a statistical footnote here. It is a structural feature of a crime designed to make its victims feel too foolish to come forward, which in turn starves the data, the prosecutions and the policy response of the evidence they need. A crime that silences its own witnesses is a crime that compounds at interest.

Why the Burden Cannot Sit With Families

The most widely circulated piece of advice, repeated by the FBI, the American Bankers Association and consumer advocates throughout 2026, is to agree a family “safe word” — a secret phrase known only to relatives, to be demanded in any emergency call. If the voice cannot produce it, hang up and call back on a known number. The advice is sound. It is also, as a systemic defence, hopelessly inadequate, and it is worth being clear about why.

A safe word works only if every member of a family adopts it, remembers it, and has the presence of mind to demand it in a moment engineered to obliterate presence of mind. It places the entire burden of defeating an industrial, automated, billion-dollar criminal apparatus on the cognitive discipline of a frightened individual at the worst moment of their week. It assumes that the eighty-year-old whose median reported loss, according to FTC data released in late 2025, exceeds 1,600 dollars will, while hearing her grandchild scream, calmly recall a protocol and execute it. Some will. Many, by design, will not. A defence that works only when the target performs flawlessly under maximum stress is not a defence; it is a way of allocating blame to the victim after the fact.

This is the deeper objection to placing protection in the hands of families and individuals. It transfers responsibility for a failure of the technological and financial system onto the people least equipped to bear it, and then, when they fail, treats their failure as a personal one. The voice-cloning tools were built and sold by companies. The calls are carried by telecommunications networks. The money moves through banks. Each of those parties operates at the chokepoints where the fraud could actually be interdicted at scale. The grandmother in her kitchen does not. Meaningful protection requires moving the burden from the end of the chain, where it currently sits, to the points in the middle where it belongs. A society that responds to an industrialised threat by issuing better advice to its most vulnerable members has confused the publication of guidance with the provision of protection.

Where Interdiction Could Actually Happen

Consider the three institutional chokepoints in turn, because each illustrates both the promise and the present failure of structural defence.

The first is the telephone network. In the United States, the STIR/SHAKEN framework was meant to address caller-ID spoofing by allowing originating carriers to cryptographically sign a call as legitimate and terminating carriers to verify that signature before it reaches a handset. In December 2025, the FCC's Wireline Competition Bureau concluded in its triennial efficacy report that the framework does authenticate caller ID effectively when properly applied. The qualification is doing enormous work. Criminals discovered early that routing calls through older, non-IP networks could evade the system entirely, and the FCC spent much of 2025 and 2026 trying to close that gap and pushing towards Rich Call Data, which would display a verified caller name and logo on the handset. But STIR/SHAKEN authenticates the number, not the human, and certainly not the voice. It can tell you that a call genuinely originated from a given line. It cannot tell you that the sobbing daughter on that line is a machine. Against a cloned voice arriving from a spoofed or simply unfamiliar number, the framework is close to irrelevant. The same FCC declared in February 2024 that AI-generated voices in robocalls were illegal under the Telephone Consumer Protection Act — a meaningful statement of intent that nonetheless governs only mass automated dialling, not the targeted, one-to-one emergency call that defines the grandparent scam.

The second chokepoint is the platform that hosts the cloning tool. Here the most promising structural intervention is provenance rather than detection — the attempt, embodied in the C2PA standard, to attach a tamper-evident cryptographic record to a piece of media describing the device or model that produced it. In 2025 the standard was ratified as an ISO specification and, alongside watermarking schemes such as Google's SynthID and Meta's AudioSeal, became the de facto provenance language of the internet. The logic is sound: rather than asking whether a recording looks or sounds fake, ask whether it carries a credential proving it was made by a real microphone. But provenance has a fatal asymmetry of its own for this specific crime. Missing credentials are not proof of fakery, because vast quantities of legitimate audio were never signed and because the metadata is routinely stripped by social platforms, screenshots and re-encoding. More fundamentally, a fraudster placing a phone call is under no obligation to transmit a C2PA manifest, and the analogue gap — playing synthetic audio down a telephone line — destroys any digital watermark in the act of transmission. Provenance can help establish, afterwards, that a viral video was synthetic. It does almost nothing to stop a live cloned-voice call in progress.

The third chokepoint — and the most promising — is the bank. This is where the money actually moves, and therefore where interdiction has the greatest mechanical leverage. The United Kingdom offers the clearest natural experiment. In October 2024, the Payment Systems Regulator made reimbursement for authorised push payment fraud mandatory: where a victim is tricked into authorising a transfer to a fraudster, the sending and receiving banks must now reimburse them, splitting the liability fifty-fifty, up to 85,000 pounds, within five business days, with the consumer-negligence exception explicitly barred for vulnerable customers. Confirmation of Payee, the account-name-checking service, now runs on billions of transactions. The PSR's own dashboard showed that in the fifteen months to the end of December 2025, 89 per cent of money lost to such scams — some 243 million pounds — was reimbursed, against a 65 per cent rate before the rules took effect.

The point of mandatory reimbursement is not merely to make victims whole, though that matters. Its deeper purpose is to relocate the financial incentive. Once banks are liable for the losses, they acquire a powerful reason to build the friction, the anomaly detection and the intervention protocols that actually stop a fraudulent transfer before it completes — the held payment, the cooling-off period on a large cash withdrawal by an older customer, the human call from the branch asking why a retiree is suddenly emptying her savings to a courier. The transfer friction that a grandmother cannot impose on herself, a bank can impose on her account, and a liability regime gives it the reason to do so. Critics, including commentators in Electronic Payments International, warn that reimbursement alone risks becoming a subsidy to fraudsters if it is not paired with prevention, and that the strategy must move beyond simply paying victims back. That critique is correct, and it points towards the right answer rather than away from it: liability is the lever that forces prevention, not a substitute for it. The lesson of the British experiment is not that reimbursement solves fraud — it does not — but that it changes whose problem fraud is, and an institution made to own a problem will, eventually, engineer against it.

What Meaningful Protection Actually Requires

Pull these threads together and a coherent picture emerges of what would actually work, as distinct from what merely sounds reassuring.

It requires, first, abandoning detection as the primary line of defence. Hany Farid's blindness is not a temporary setback to be solved by a better classifier; it is a permanent structural condition of a world in which generation has outrun discrimination. Any plan whose final safeguard is someone, somewhere, telling the real from the fake has already failed.

It requires, second, regulating the supply of the weapon. The Consumer Reports finding that voice-cloning tools sit behind a self-attestation checkbox is a policy choice, not a law of nature. Mandatory, verifiable consent before a voice can be cloned — of the kind Descript and Resemble AI have partially implemented and the others have not — is technically feasible and would not abolish the legitimate uses of the technology. The European Union's AI Act, whose obligations for general-purpose models began applying through 2025 and 2026, and state statutes such as Tennessee's ELVIS Act, which requires written consent to clone a voice, are early gestures towards treating voice synthesis as the regulated capability it has become. They remain far ahead of enforcement and far behind the threat.

It requires, third, placing the burden of interdiction on the institutions that occupy the chokepoints — and, where they will not act voluntarily, compelling them through liability. The British reimbursement regime is imperfect and incomplete, but it demonstrates the mechanism: when banks own the loss, banks build the friction. Telecoms carriers that profit from carrying calls should bear a corresponding duty to authenticate and, where possible, flag them. Platforms that sell cloning should bear a duty to verify consent. The common principle is that responsibility ought to sit with the party that has both the capability to prevent the harm and the commercial benefit from the activity that causes it — which, in every case, is an institution, and in no case is an eighty-year-old answering her phone.

It requires, fourth, treating the human vulnerability as a thing to be managed rather than a thing to be blamed. The Charm Security framework's insight — that the cognitive and emotional mechanisms exploited by fraud deserve the same systematic cataloguing as software flaws — should inform how banks design their interventions, how carriers design their warnings, and how public bodies design education that goes beyond leaflets to the kind of role-based rehearsal that the ROLESafe research found actually changes behaviour. Awareness campaigns and family safe words are not worthless. They are simply the last and weakest line, useful only as a backstop to structural defences that do the real work.

The deepest reason the defensive gap is measured in years rather than months is that the attack is a technology problem and the defence is an institutional one. Cloning a voice takes three seconds and improves monthly. Passing a reimbursement regulation, rewiring a banking system's fraud controls, mandating consent verification across an industry, and closing the non-IP loophole in a national telephone network take years, because they require law, coordination, money and the overcoming of every commercial interest that profits from the status quo. The asymmetry is not merely technical; it is the asymmetry between how fast a machine can be built and how slowly a society can respond.

Sharon Brightwell got some of her money back, eventually, through the diligence of investigators and her bank. Many do not. The 352 million dollars the FBI attributes to older victims of AI fraud, and the far larger sum it cannot see, represent a transfer of wealth from the people who can least afford to lose it to the most efficient criminal enterprise yet devised. Closing the gap will not come from teaching grandmothers to doubt the sound of their grandchildren's voices. It will come from deciding, as a matter of law and engineering, that the institutions standing between the clone and the cash are responsible for what passes through their hands. Until that decision is made, the three-second theft will remain the easiest serious crime in the world to commit, and the hardest for its victims to be believed about — because the evidence, by design, sounds exactly like someone they love.

References

1. Federal Bureau of Investigation, “Cryptocurrency and AI Scams Bilk Americans of Billions”, April 2026. https://www.fbi.gov/news/press-releases/cryptocurrency-and-ai-scams-bilk-americans-of-billions
2. Internet Crime Complaint Center (FBI), “2025 IC3 Annual Report”, April 2026. https://www.ic3.gov/AnnualReport/Reports/2025_IC3Report.pdf
3. ABA Banking Journal, “FBI: Cybercrime losses increased 26% in 2025”, April 2026. https://bankingjournal.aba.com/2026/04/fbi-cybercrime-losses-increased-26-in-2025/
4. SecureWorld, “FBI: AI-Enabled Fraud Topped $893M in 2025—Real Toll Likely Far Higher”, April 2026. https://www.secureworld.io/industry-news/ai-enabled-fraud-topped-893m-fbi
5. AARP, “Older Adults Hit Hard by Fraud in 2025”, April 2026. https://www.aarp.org/money/scams-fraud/fbi-ftc-report-2025-losses/
6. HousingWire, “FBI: Seniors lost $7.75B to cybercrime in 2025 — a 59% jump”, April 2026. https://www.housingwire.com/articles/fbi-seniors-cybercrime-2025/
7. INTERPOL, “INTERPOL report warns of increasingly sophisticated global financial fraud threat”, March 2026. https://www.interpol.int/en/News-and-Events/News/2026/INTERPOL-report-warns-of-increasingly-sophisticated-global-financial-fraud-threat
8. Help Net Security, “Global fraud losses climb to $442 billion”, 18 March 2026. https://www.helpnetsecurity.com/2026/03/18/online-fraud-victims-losses-interpol-report/
9. ICLG, “Interpol warns of 'industrialisation' of global fraud”, March 2026. https://iclg.com/news/23665-interpol-warns-of-industrialisation-of-global-fraud
10. The New York Times, “In the Age of A.I., the World's Leading Deepfake Expert No Longer Trusts His Own Eyes”, June 2026. (Reported via beSpacific.) https://www.bespacific.com/the-worlds-leading-deepfake-expert-no-longer-trusts-his-own-eyes/
11. FOX 13 Tampa Bay, “Dover woman loses $15K after scammers used artificial intelligence to impersonate daughter”, July 2025. https://www.fox13news.com/news/dover-woman-loses-15k-after-scammers-used-artificial-intelligence-impersonate-daughter
12. Agence France-Presse (via The Manila Times), “'20 minutes of terror': AI boosts US voice impersonation scams”, 4 June 2026. https://www.manilatimes.net/2026/06/04/news/world/20-minutes-of-terror-ai-boosts-us-voice-impersonation-scams/2358259
13. Consumer Reports, “Consumer Reports' Assessment of AI Voice Cloning Products”, March 2025. https://www.consumerreports.org/media-room/press-releases/2025/03/consumer-reports-assessment-of-ai-voice-cloning-products/
14. NBC News, “AI can steal your voice, and there's not much you can do about it”, March 2025. https://www.nbcnews.com/tech/security/ai-voice-cloning-software-flimsy-guardrails-report-finds-rcna195131
15. The Register, “Consumer Reports calls out poor AI voice-cloning safeguards”, 10 March 2025. https://www.theregister.com/2025/03/10/ai_voice_cloning_safeguards/
16. ElevenLabs, “Safety”, 2026. https://elevenlabs.io/safety
17. Ben, A., Rahav, T., Illaev, D., Nahon, A., and Grushka, A. (Charm Security), “The Human Vulnerabilities & Exploits (HVE) Framework”, arXiv:2606.10083, June 2026. https://arxiv.org/abs/2606.10083
18. Deng, Y., Chen, X., Liao, J., Li, B., and Zou, Y., “Experiencer, Helper, or Observer: Online Fraud Intervention for Older Adults Through Role-based Simulation”, arXiv:2601.12324, January 2026. https://arxiv.org/abs/2601.12324
19. Federal Communications Commission, “FCC Makes AI-Generated Voices in Robocalls Illegal”, February 2024. https://www.fcc.gov/document/fcc-makes-ai-generated-voices-robocalls-illegal
20. Federal Communications Commission, “Combating Spoofed Robocalls with Caller ID Authentication (STIR/SHAKEN)”, updated 2026. https://www.fcc.gov/call-authentication
21. EyeSift, “C2PA Deepfake Detection 2026: AI Image Watermarks & SynthID”, 2026. https://www.eyesift.com/ai-image-detection-2026-c2pa-content-credentials-synthid-watermarks-diffusion-fingerprints-deepfake/
22. Payment Systems Regulator, “PS25/5 Consolidated policy statement: APP scams reimbursement requirement”, May 2025. https://www.psr.org.uk/media/rhelv4op/ps25-5-app-scams-reimbursement-consolidated-policy-statement-may-2025.pdf
23. Electronic Payments International, “Why the UK's scam strategy must move beyond reimbursement”, 2025. https://www.electronicpaymentsinternational.com/comment/why-uk-scam-strategy-must-move-beyond-reimbursement/
24. Federal Trade Commission, “Protecting Older Consumers 2024–2025: A Report of the Federal Trade Commission”, December 2025. https://www.ftc.gov/system/files/ftc_gov/pdf/P144400-OlderAdultsReportDec2025.pdf
25. American Bar Association, “The Rise of the AI-Cloned Voice Scam”, September 2025. https://www.americanbar.org/groups/senior_lawyers/resources/voice-of-experience/2025-september/ai-cloned-voice-scam/

---

Tim Green UK-based Systems Theorist & Independent Technology Writer

Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.

His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.

ORCID: 0009-0002-0156-9795 Email: tim@smarterarticles.co.uk

Listen to the free weekly SmarterArticles Podcast

The Compassion of Awareness

As mouths move and voices stir, I wonder how blood can flow so differently. What rapt endeavor chose a single divergent path amongst the throng? Is it the location of ears upon varying heads that cause completely different brain patterns? Like a fine wine, does age and complexity matter?

I sit uncomfortable, listening. Digesting. Utterly and completely bewildered. Devaluing the academic surplus of diploma after diploma, and chastising my own ego for even pondering such ludicrousness. Perhaps such differences are merely the rudimentary reassurances that life will continue. How ironic that my own will not.

Could I? Would I? Might I dare to breed? Rather I run screaming into the hills, and thank my good fortune for a vast ineptitude of obedience and fertility. Rather I rot alone than succumb to the mindless drivel that continues to flood a far too familiar space, demanding I concede spark for stunted awareness and altered communication. Rather I fade from the Polaroid far too defined.

I smile, humored, informed my value is beyond the heights I refuse to scale. My lips quirk at dating advice that turns my stomach to even contemplate. I agree, most expectedly, that I'm a rather droll and unexciting person. My soul and well-being is prayed for. Might a god place his hand upon me in influence and esteem. My eyes twinkle at such a thought, for such an entity would surely find themselves elated by my presence. I keep it to myself. Needing to explain one's humor ruins the joy.

Off I go. Another congruence survived. Could it be this nightmare is never to be awakened from?

Written July 14, 2026. © 2026 AnOublietteofThought.

Eis in Schöneweide – 8. Juli

Wie ich schon gestern erwähnt habe, habe ich heute gemeinsam mit Herrn Baumeister (ich habe leider seinen Vornamen vergessen) das Berliner Leitsystem kennengelernt. Dieses System ist sehr logisch aufgebaut und folgt einem klaren Konzept. Alles wurde aus bestimmten Gründen so gestaltet, dass Menschen aus unterschiedlichen Regionen Deutschlands die Wegbeschreibungen eindeutig verstehen können. Ich werde das System hier nicht im Detail erklären. Aber ich habe mehr als zwei Stunden lang ein persönliches Training von Herrn Baumeister bekommen. Jetzt weiß ich zumindest, wie ich mich anhand dieser Wegbeschreibungen in Berlin orientieren kann, ohne mich ständig zu verlaufen.

Eigentlich begann der Tag schon mit einem kleinen Abenteuer. Vor unserem Treffen hatte ich mein Handy im Café liegen lassen, in dem wir gefrühstückt hatten. Natürlich bemerkte ich das erst in der U-Bahn. Ich wurde sofort nervös und gab zunächst Mindaugas die Schuld: „Warum hast du den Tisch nicht kontrolliert?“ Als wäre ich plötzlich von jeder Verantwortung befreit, nur weil eine sehende Person bei mir ist! Dann schlug ich vor, alleine bis zum Alexanderplatz weiterzufahren und Mindaugas zurück ins Café zu schicken. Ich wollte auf keinen Fall zu spät zu unserem Termin kommen. Schon allein der Name Baumeister klang für mich irgendwie verpflichtend – und in Deutschland ist Pünktlichkeit schließlich fast selbstverständlich.

Es fühlte sich zunächst etwas seltsam an, ohne Handy allein weiterzufahren. Natürlich kamen sofort die unterschiedlichsten Gedanken: Was, wenn ich an der falschen Station aussteige? Was, wenn Imke mir kurzfristig geschrieben hätte, dass wir uns doch woanders treffen? Trotzdem blieb ich erstaunlich ruhig. Wie in solchen Situationen immer erinnerte ich mich daran, dass mir eigentlich nichts Schlimmes passieren kann. Ich kenne Mindaugas' Telefonnummer auswendig, ich könnte über meinen Laptop ins Internet gehen, jemanden anrufen oder einfach eine E-Mail schreiben. Und schließlich spreche ich – wenn auch nicht besonders gut – Deutsch und könnte jederzeit jemanden um Hilfe bitten. Es ist wirklich interessant, wie das Gehirn funktioniert: Gerade in solchen Momenten produziert es automatisch die dümmsten Horrorszenarien.

Zum Glück störte das verlorene Handy unser Treffen überhaupt nicht. Herr Baumeister erklärte mir viele interessante Details über das Leitsystem und die Orientierung im öffentlichen Raum. Ein paar Erkenntnisse nehme ich besonders mit:

1. Manche Leitsysteme sind bereits älter, und ich kann sie mit meinem Langstock kaum ertasten. Vielleicht liegt das aber auch daran, dass meine Langstocktechnik inzwischen etwas schlechter geworden ist. Das muss ich unbedingt noch genauer untersuchen.

2. Es gibt verschiedene Arten von Bodenindikatoren, die ich noch nicht sicher unterscheiden kann. Das lässt sich aber bestimmt mit etwas Übung lernen.

3. Ich bin jetzt sehr motiviert, das gesamte System selbst weiter zu erforschen. Herr Baumeister hat mir freundlicherweise sogar seine Telefonnummer gegeben, falls später noch Fragen auftauchen sollten. Das finde ich unglaublich nett. Am schwierigsten wird wahrscheinlich das Umsteigen bleiben. Die Wegbeschreibungen beginnen meistens an der Endstation einer Linie. Wenn man vorher noch umsteigen muss, muss man den Weg dorthin erst einmal selbst finden. Vielleicht verstehe ich dieses System mit der Zeit noch besser.

4. Eine weitere Herausforderung besteht darin, wie man diesen Wegbeschreibungen möglichst komfortabel folgen kann. Sie enthalten sehr präzise Informationen, sind aber gleichzeitig linear aufgebaut. Zum Beispiel: „Am Leitsystem bis zum Ende des Bahnsteigs. 180 Grat Um-drehung. Rechts entlang. Wenige Schritte weiter bis Ta-ta-ta... Links entlang. 50 Meter weiter bis zum Ta-ta-ta...” Alle Informationen stehen nacheinander, während ich gleichzeitig gehen muss. Das bedeutet, dass ich auf meinem Handy oft Satz für Satz oder sogar Wort für Wort weiterlesen muss. So komme ich zwar ans Ziel, aber besonders flüssig ist diese Art der Orientierung nicht. Trotzdem wird mir das System mit jeder Übung verständlicher. Ich habe sogar schon die Idee, verschiedene Braille-Notizen auszuprobieren, um den Ablauf unterwegs einfacher verfolgen zu können.

Während wir das Leitsystem erkundeten, holte Mindaugas mein Handy aus dem Café ab. Der Mitarbeiter hatte es sorgfältig aufbewahrt und wartete schon auf ihn. Dieses Mal musste ich für meine Zerstreutheit also nichts bezahlen.

Unser Reel wird leider doch erst später veröffentlicht, weil an der Audiodeskription noch einige Korrekturen notwendig waren. Wenigstens musste ich diesmal selbst nichts mehr daran ändern. Außerdem hatten wir heute noch ein Gespräch mit den Entwicklern einer Website. Und ihre Sprache – voller Anglizismen – war heute schon deutlich verständlicher für mich.

Es stellte sich außerdem heraus, dass es in Schöneweide ein wirklich fantastisches Eismanufaktur gibt. Imke hat uns eingeladen, dort ein Eis zu probieren. Das war eine schöne kleine Belohnung vor ihrem Urlaub. Erstens gibt es dort unglaublich viele Eissorten – und viele davon tragen richtig originelle Namen. Zweitens muss man sich erst einmal in eine ziemlich lange Schlange stellen. Aber diese Schlange war erstaunlich friedlich und entspannt. Ich dachte mir, dass darin eigentlich eine sehr logische Aufgabe steckt: Während des Wartens hat man genug Zeit, sich noch einmal ernsthaft zu fragen, ob man diese ganzen Kalorien wirklich essen möchte. Meine Antwort lautete eindeutig: Ja! Vor allem nachdem ich das Eis probiert hatte. Die Waffel und das hausgemachte Eis schmecken einfach fantastisch. Ich werde Mindaugas bestimmt noch einmal dorthin einladen. Allerdings könnte das lange Warten in der Schlange für ihn etwas schwieriger werden – dafür ist er ziemlich empfindlich. Aber ich werde ihn schon überzeugen.

Zum Schluss bin ich zum ersten Mal ganz allein vom S-Bahnhof mit der Straßenbahn zurück zum Hotel gefahren. Während dieser Reise ist das eigentlich eine Seltenheit. Mindaugas sagt immer, dass er schließlich dafür bezahlt wird, mich zu begleiten, und deshalb lässt er mich nur ungern allein los.

Ich glaube allerdings gar nicht, dass er sich übermäßig Sorgen um mich macht. Er ist einfach ein sehr verantwortungsbewusster Mensch und nimmt seine Aufgabe im Rahmen des Projekts sehr ernst. Nachdem ich ihn heute wegen meines verlorenen Handys ohnehin schon genug hin- und hergeschickt hatte, ließ er mich diesmal ganz in Ruhe weiterarbeiten und sagte, ich solle einfach allein zurückfahren.

Eigentlich war das auch gar nicht schwierig. Eine Kollegin fährt vom selben Bahnhof nach Hause, sodass ich nur noch allein aus der Straßenbahn aussteigen und den kurzen Weg zum Hotel zurücklegen musste. Allerdings sprach ausgerechnet diese Straßenbahn keine Haltestellen an. Deshalb musste ich die Stationen vorsichtig auf meinem Handy verfolgen. Gut, dass ich es wiederhatte! Außerdem muss man hier immer selbst den Halteknopf drücken. Die Bahn hält nicht automatisch an, wenn niemand aussteigen möchte. Ich kenne die Straßenbahnen in Berlin noch nicht besonders gut, aber den Knopf habe ich zufällig ziemlich schnell gefunden.

Wieder ein kleiner Schritt mehr, um Berlin besser kennenzulernen.

In Summary: * This Tuesday has been both a recovery day (recovering from the previous two consecutive days of yard work), and a prep day, spent preparing for the next round of yard work. This next round will be spent mostly working on the front yard between rain showers. Those showers are expected to continue off and on through Thursday, by the way. How much work gets done out there will depend on the weather and my energy level.

I've worked my night prayers early today as I hope to focus on tonight's MLB All Star Game until my brain calls it quits and sends this old body to bed.

Prayers, etc.: * I have a daily prayer regimen I try to follow throughout the day from early morning, as soon as I roll out of bed, until head hits pillow at night.

Health Metrics: * bw= 229.06 lbs. * bp= 146/85 (66)

Exercise: * morning stretches, balance exercises, kegel pelvic floor exercises, half squats, calf raises, wall push-ups, BP breathing exercises, pilates

Diet: * 05:10 – 1 banana * 07:00 – 4 little cookies * 07:20 – 1 peanut butter sandwich * 10:00 – baked fish and vegetables * 11:15 – snacking on little cookies * 12:00 – 1 bacon and egg breakfast taco * 15:00 – 1 fresh apple

Activities, Chores, etc.: * 04:20 – listen to local news talk radio * 04:55 – bank accounts activity monitored. * 05:00 – read, write, pray, follow news reports from various sources, surf the socials, nap * 15:45 – listening to relaxing music

Chess: * 13:55 – moved in all pending CC games

Chapter 1: When Getting Even Feels Like the Only Honest Answer

It is usually not the big public moment that gives away what is happening inside us. It is the quiet moment afterward. The phone is face down on the table. The room is still. The conversation is over, but your mind keeps replaying it. You remember what they said, how they looked at you, how easily they walked away, and how much of the weight they left behind for you to carry. In moments like that, a teaching such as “an eye for an eye” can feel less like ancient Scripture and more like permission. It can sound like God saying, “You are allowed to make this even.”

That is why what Jesus really meant by an eye for an eye matters so much. Most people do not misunderstand the phrase because they are foolish. They misunderstand it because they have been hurt. When someone has embarrassed you, betrayed you, lied about you, cheated you, or damaged something you cannot easily replace, revenge can feel like honesty. It can feel like the only response that admits the wound was real.

I have spent enough time thinking about faith, pressure, pain, and human behavior to know that people rarely call it revenge when they want it. We call it fairness. We call it standing up for ourselves. We call it making sure someone learns a lesson. That is why the difference between justice and personal revenge deserves more than a quick explanation. It reaches into the private places where we know what we want, even when we are not proud of wanting it.

The original command, “an eye for an eye and a tooth for a tooth,” was not given to encourage cruelty. It was given to limit it. In a world where one injury could start a family feud, and one insult could lead to bloodshed far beyond the original offense, the law created a boundary. The response could not be greater than the harm. The punishment had to be measured. It was a restraint on retaliation.

That changes the way the phrase sounds. It was not God handing human anger a weapon. It was God putting a fence around it.

Then Jesus went further. He did not pretend injustice was harmless. He did not tell wounded people that what happened to them did not matter. He did not ask anyone to call evil good. He showed that even limited revenge could not heal the human heart. A person might succeed in making the other side pay and still wake up angry the next morning. The account might look even from the outside while the soul remained trapped inside the injury.

That is the hidden problem with getting even. It promises an ending, but it often keeps the relationship with the wound alive.

You may no longer speak to the person. You may not see them. Years may have passed. Yet you still have arguments with them in your head while driving to work. You imagine the day they finally understand what they did. You picture the moment when their own life falls apart and they come back to admit that you were right. You do not necessarily want to destroy them. You just want them to feel enough pain to make your pain seem acknowledged.

I understand why that desire appears. There are injuries that leave a person feeling invisible. Someone does real damage and then continues living as though nothing happened. You are left with the cost while they appear to carry none of it. You repair your finances, rebuild your confidence, explain the situation to your family, or try to sleep through a mind that will not become quiet. Meanwhile, they post smiling pictures, make new plans, and speak as if they were the wounded one.

In that kind of situation, forgiveness can sound insulting. It can sound like one more demand placed on the person who has already paid the highest price.

Jesus does not treat the wounded person as though the wound is small. He does something harder and kinder. He separates your healing from the other person’s suffering. He refuses to tell you that you must watch them hurt before you are allowed to become free.

That is where His teaching becomes deeply personal.

The lesson is not that nothing should happen to people who do wrong. Consequences matter. Truth matters. Protection matters. If someone is dangerous, love does not require you to give them another opportunity to harm you. If someone commits a crime, forgiveness does not prevent you from reporting it. If someone repeatedly lies, mercy does not require you to keep trusting them. Boundaries are not revenge. Accountability is not hatred.

The lesson is that your heart cannot safely live on the hope that another person suffers.

That hope changes us slowly. It makes us rehearse the offense because we need to keep the anger strong. It makes every update about the other person feel important. It makes their success feel offensive and their hardship feel satisfying. Before long, our peace depends on what happens to someone else.

That is too much power to hand to the person who hurt you.

Maybe you know what this looks like in ordinary life. You see their name on your phone and your body tightens before you even read the message. Someone mentions them at dinner, and the entire mood inside you changes. You hear that they received a promotion, found a new relationship, or gained the approval of people who never heard your side, and something inside you says, “That is not fair.”

Sometimes it is not fair.

Christian faith does not require us to lie about that. There are times when people avoid consequences. There are times when human systems fail. There are times when the apology never comes, the money is never returned, the rumor is never fully corrected, and the person who caused the damage never seems to understand it.

But there is another unfairness we rarely name. It is unfair for their action to keep taking more of your life years after the event is over. It is unfair for them to occupy your thoughts while you are trying to enjoy dinner with people who love you. It is unfair for the memory of their dishonesty to make you suspicious of every honest person who comes later. It is unfair for their cruelty to train you to become cruel.

Jesus teaches a way of ending that second injustice.

He does not tell you to erase the truth. He tells you that the truth does not need hatred in order to remain true.

That distinction has helped me. I do not have to soften the facts to forgive. I do not have to say, “It was not that bad.” I do not have to pretend the person meant well when I know they did not. I do not have to reopen a door God helped me close. I can tell the truth about what happened and still refuse to make revenge my purpose.

This is not a quick emotional trick. A person does not simply decide one afternoon to stop caring and then never feel angry again. Forgiveness may begin as a quiet choice made while the feelings remain unsettled. You may place the matter in God’s hands on Monday and take it back by Wednesday. You may pray honestly, then wake up at two in the morning remembering another detail.

That does not mean you are fake. It means you are practicing freedom.

The private work often sounds less impressive than people expect. It may be a prayer whispered in the car: “God, I still want them to hurt, and I do not want that desire to own me.” It may be closing the social media page instead of checking whether life has punished them yet. It may be refusing to repeat the story to one more person merely to keep the anger warm. It may be admitting that you miss who you thought they were, even though you no longer trust who they have shown themselves to be.

There is real grief inside revenge. Sometimes what we want back is not an eye or a tooth. We want our time back. We want our innocence back. We want the version of ourselves that trusted easily. We want the family we thought we had, the marriage we thought we were building, the friendship we believed was safe, or the future we expected before one decision changed everything.

No punishment can return those things exactly as they were.

That is one reason Jesus leads us away from retaliation. He knows revenge cannot give us what we are actually mourning. It may create another wound, but it cannot restore the old life.

Grace begins by telling the truth about that loss. You can stop pretending that getting even will bring back what was taken. You can grieve what cannot be recovered in its original form. Then, slowly, you can allow God to build something new without making the person who harmed you the center of the rebuilding.

This is where “turn the other cheek” is also misunderstood. Jesus was not teaching people to become helpless targets. He was showing them how to refuse the role that violence assigns. When someone tries to reduce you to a victim who can only react, you do not have to become a copy of their behavior. You can remain truthful, alert, and strong without allowing their character to become yours.

That is not passivity. It is self-control with a spiritual purpose.

Anyone can hit back. Anyone can send the message designed to wound. Anyone can repeat the private information, embarrass the person publicly, damage the reputation, or wait for the perfect moment to return the pain. The ability to cause harm is not proof of strength. Sometimes the strongest thing a person can do is refuse to use the weapon that anger placed in their hand.

I am not saying this from a distance, as though forgiveness is easy when the lesson is understood. I know that some wounds stay sensitive for a long time. I know there are names that still change the temperature of a room. I know a person can love Jesus sincerely and still feel a rush of anger when an old memory rises.

The question is not whether anger appears. The question is whether anger gets to decide what happens next.

An eye for an eye placed a limit on what people were allowed to do to one another. Jesus placed a deeper limit inside the heart. He taught that another person’s sin does not get unlimited access to your future. It does not get to keep shaping your thoughts, your relationships, your faith, and your identity forever.

You may still need justice. You may still need distance. You may still need to tell the truth clearly and accept that the relationship cannot be repaired. Yet you can do those things without secretly building your life around the day the other person finally suffers.

There comes a moment when you realize that getting even would not make you whole. It would only prove that the wound had taught you how to wound.

Jesus offers a different kind of victory. He teaches you to become free enough that what happened remains part of your story without remaining in control of your character. The event may explain why certain things are hard for you, but it does not have to decide the kind of person you will be.

When you sit in the quiet room and remember what they did, you are allowed to be honest. You can say that it was wrong. You can admit that part of you still wants an apology, an explanation, or a consequence. Then you can ask God for something revenge could never give you: a heart that is no longer waiting for someone else’s pain before it permits itself to heal.

Chapter 2: The Day You Stop Holding Court Inside Your Head

The next morning often tells the truth more clearly than the night before. You wake up, reach for your phone, and before your feet touch the floor, your mind returns to the same person. Nothing new has happened. No message has arrived. No apology is waiting. Yet the argument begins again as if the courtroom inside your head never closed.

You present the evidence. You remember the exact words. You imagine what you should have said. You build the case one more time, and because you know every detail, you win every time. Still, when the trial is over, you do not feel better. You feel tired.

That private courtroom is one of the places where revenge survives after we have decided we are not going to act on it. We may never confront the person. We may never send the angry message. We may never do anything that looks cruel from the outside. But inside, we keep prosecuting them. We keep sentencing them. We keep returning to the offense because we are afraid that releasing it would mean the truth no longer matters.

I think many people stay angry because anger feels like the last witness to what happened. If I stop being furious, maybe I am admitting it was acceptable. If I stop replaying it, maybe I am letting them get away with it. If I forgive, maybe I am betraying the part of me that was hurt.

Jesus does not ask us to betray the truth. He asks us to stop confusing truth with punishment.

What happened can remain wrong even after you stop feeding your anger. The harm can remain serious even when you no longer spend every day proving it to yourself. Forgiveness does not rewrite the event. It changes who is allowed to control the next chapter.

That change is usually quieter than people expect. It may happen when you are washing dishes after dinner and realize you have gone an entire afternoon without thinking about the person. It may happen when someone mentions their name and you notice that your body no longer reacts as sharply. It may happen when you finally tell the story without needing everyone in the room to hate them on your behalf.

Those moments can feel almost disloyal at first. You may wonder whether healing means you have forgotten what mattered. It does not. Healing means the memory is becoming part of your past instead of a command directing your present.

There is a difference between remembering and rehearsing. Remembering helps us learn. Rehearsing keeps us emotionally trapped in the same scene. Remembering may say, “I ignored warning signs, and I will pay attention next time.” Rehearsing says, “I need to feel the full anger again so the wound remains alive.”

One leads to wisdom. The other keeps the injury in charge.

This matters in relationships because an unresolved desire for revenge rarely stays aimed at only one person. It spills. A man is betrayed by one business partner and begins treating every new partner as a possible thief. A woman is lied to in one relationship and starts reading dishonesty into every delay, every quiet moment, every missed call. A parent is disrespected by one adult child and becomes harder with the others. The original person may be gone, but the punishment continues through people who did not cause the wound.

That is one of the costs Jesus is trying to spare us.

When He teaches us not to repay evil with evil, He is not only protecting the person who did wrong. He is protecting everyone who might be harmed by what the wrong awakens in us. He is protecting the children who may grow up under bitterness they did not create. He is protecting the new friend who should not have to answer for the old friend’s betrayal. He is protecting the future spouse who deserves to meet you, not only the defenses someone else forced you to build.

This is where forgiveness becomes practical. It is not a vague feeling of kindness toward someone who hurt you. It is a decision about what you will carry into the next room.

You may carry wisdom. You may carry stronger boundaries. You may carry a clearer sense of what you will no longer tolerate. You may carry grief that still needs time. But you do not have to carry the mission of making someone pay.

That mission is exhausting because it has no clear finish. How much suffering would finally feel like enough? If their relationship fails, would that restore yours? If they lose money, would that repay the years you lost? If they are embarrassed publicly, would that return your dignity? Revenge keeps promising a number it can never name.

Grace names a different goal: freedom.

Freedom does not mean the person becomes safe. Some people should remain at a distance. Some relationships cannot be restored because trust was destroyed and repentance never came. Christian faith does not require us to keep handing access to people who misuse it.

Jesus forgave people who did not deserve it, but He did not entrust Himself to everyone. That distinction matters. You can release hatred without restoring access. You can pray for someone without inviting them back into your private life. You can hope they change while refusing to become the place where they test whether they have.

Forgiveness is offered from your heart. Reconciliation is built by two people.

Reconciliation requires truth. It requires responsibility. It requires change that can be seen over time. A person who demands immediate trust because you say you have forgiven them may still be avoiding accountability. Real repentance does not pressure the wounded person to pretend everything is normal. It understands that some damage takes time to repair and some consequences remain.

That is why justice still matters.

Justice protects the vulnerable. Justice tells the truth in public when silence would allow more harm. Justice may involve a supervisor, a counselor, a church leader, an attorney, a police report, or a firm boundary that disappoints people who do not know the whole story. None of those actions automatically become revenge simply because they are uncomfortable.

The question is what you are trying to accomplish.

Are you trying to stop harm, protect others, and bring truth into the light? Or are you trying to enjoy the sight of another person being crushed? The actions can sometimes look similar from the outside, but the heart knows the difference.

That is why prayer becomes so important. Not the polished kind of prayer that pretends you have already moved beyond the struggle. I mean the honest prayer that says, “God, I want justice, but part of me also wants revenge. Help me know the difference.”

God is not frightened by that honesty. He already knows what is inside us. Hiding it only keeps us from bringing it into the place where He can change it.

Sometimes the most faithful prayer is not “God, bless them” when you cannot say those words sincerely yet. It may begin with, “God, keep me from becoming bitter.” It may be, “God, deal with them rightly because I cannot trust myself to decide what they deserve.” It may be, “God, help me stop checking whether their life is falling apart.”

That kind of prayer is not weak. It is the moment you admit that your heart needs protection from what anger wants to build.

I have learned that resentment often presents itself as strength because it gives us something to hold. When everything else feels uncertain, anger feels clear. It tells us who was wrong. It tells us who is guilty. It tells us why we are hurting. But anger is a poor home. It may shelter us for a night, but we cannot build a life there.

Sooner or later, the rooms become too small.

You notice it when joy feels irresponsible. You feel guilty for laughing because part of you believes the wound should still be honored. You notice it when a good day is interrupted by a memory you almost went looking for. You notice it when peace feels unfamiliar because your body has grown used to being prepared for another fight.

Jesus does not call you away from revenge because He wants to minimize the offense. He calls you away because He wants to return your life to you.

He wants you to sit at the dinner table without another person occupying the empty chair in your thoughts. He wants you to answer a new friendship without making it pass every test the old friendship failed. He wants you to sleep without giving the same argument another hearing. He wants your faith to become larger than the worst thing someone did.

This does not happen by pretending. It happens through repeated choices that may feel small at first.

You stop telling the story to people who only make you angrier. You tell it instead to someone wise enough to help you heal. You stop checking the other person’s life for signs of punishment. You remove the number you keep wanting to call. You write the unsent message and then admit what you were hoping it would accomplish. You let yourself grieve the apology you may never receive.

You also begin paying attention to what is still good.

That can be difficult because pain trains the eye to watch for danger. Yet your life is more than what was taken. There may still be a friend who answers when you call, a child who wants to sit beside you, a quiet morning, useful work, a church community, a dog waiting at the door, or enough strength to begin again. These things do not erase the wound. They remind you the wound did not erase everything.

That is where gratitude becomes more than a pleasant idea. It becomes resistance against the belief that the person who hurt you now owns the whole story.

An eye for an eye says the response must not exceed the offense. Jesus invites us even further, into a life where the offense no longer defines the response at all. He does not deny justice. He frees justice from hatred. He does not excuse wrong. He refuses to let wrong become the pattern we repeat.

The distinct lesson is simple, but it is not easy: the person who wounded you does not get to decide who you become next.

They do not get to choose whether you become suspicious of everyone. They do not get to decide whether you remain gentle. They do not get to write the rules for your future relationships. They do not get to turn your faith into a record of grievances. They may have caused a wound, but they do not own the healing.

God meets you there.

He meets you before the apology. He meets you before the court decision, before the family understands, before the truth is publicly known, and before your feelings have caught up with your decision to forgive. He meets you in the unfinished place.

You may still need time. You may still need help. You may still have mornings when the courtroom opens again. When it does, you can close it one more time. You can say, “God, You know the truth. You judge more clearly than I do. I will not spend today trying this case again.”

Then you can put your feet on the floor and return to the life in front of you.

That is not letting them win.

That is refusing to lose any more of yourself.

Your friend,

Douglas Vandergraph

Explore the complete Douglas Vandergraph Master Index: https://douglasvandergraph.com/douglas-vandergraph-master-index/

Watch Douglas Vandergraph’s faith-based videos on YouTube: https://www.youtube.com/@douglasvandergraph

Nach der schlaflosen Nacht – 7. Juli

Nach langer Zeit habe ich wieder eine fast schlaflose Nacht erlebt. Das hing zum Teil auch mit der Sammlung von Informationen zusammen. Einige Ticket-Systeme waren etwas komplizierter zu testen, und ich wollte diese Aufgabe endlich abschließen. Deshalb haben Mindaugas und ich die ganze Nacht damit verbracht, verschiedene Websites zu durchforsten.

Ich freue mich darüber, dass die meisten Theater-Websites in Deutschland sehr barrierefrei sind. Nur bei einem Theater konnte ich kein Ticket selbstständig kaufen. Und eigentlich wäre sogar der Kauf selbst noch möglich gewesen. Das Schwierigste ist meistens, das richtige Stück zu finden, anschließend die passenden Plätze auszuwählen oder die notwendigen Ermäßigungen zu erhalten. Außerdem sind Vorstellungen mit Audiodeskription nicht immer eindeutig gekennzeichnet oder lassen sich nicht filtern. Trotzdem kann man fast überall telefonisch beraten werden. Insgesamt schätze ich die Situation deshalb als sehr positiv ein.

Andererseits kann es auch sein, dass ich insgesamt zu geringe Erwartungen an Theater-Websites habe. Ich verbringe meine Zeit schließlich nur sehr selten mit dem Gedanken: „Welches Theater könnte ich heute besuchen?“ oder: „Mal sehen, welches Stück morgen gespielt wird.“ Diese Gewohnheit hängt wahrscheinlich damit zusammen, dass ich seit meiner Kindheit Kultur fast immer nur mit Hilfe anderer oder gemeinsam mit einer Gruppe erleben konnte. Ich war nur selten eine einzelne Besucherin eines Theaters oder Museums, weil Kunst für mich damals einfach nicht so zugänglich war. Heute weiß ich meistens schon vorher, welches Stück mit Audiodeskription angeboten wird, und kaufe gezielt dafür Karten. In Litauen werden solche Vorstellungen oft separat organisiert, und die Tickets werden häufig sogar direkt vom Blindenverband verkauft. Für diese Aufgabe musste ich mir also vorstellen, dass ich einfach spontan einen schönen Abend verbringen möchte und dafür selbst ein barrierefreies Theaterstück suche. Allein diese Vorstellung fühlte sich irgendwie unrealistisch und fremd an. Vielleicht habe ich diese Aufgabe deshalb so lange vor mir hergeschoben. Oder vielleicht musste ich, wenn wir im Winter wieder über Berlin nach Spanien fahren, für Januar tatsächlich einmal einen solchen Theaterabend organisieren.

Mit meiner Schwester haben wir außerdem ein kleines Reel über das Sportfest produziert. Da das Video Audiodeskription enthalten soll, dauert die Produktion allerdings deutlich länger. Ich musste zunächst die Untertitel aufnehmen, und meine Kollegin hat anschließend die Audiodeskription eingesprochen. Die Fertigstellung wird also noch etwas Zeit in Anspruch nehmen. Es war jedenfalls lustig zu zeigen, dass ich ungefähr genauso geschossen habe wie unsere Nationalmannschaft! Ich wollte das Video unbedingt hochladen, aber hier läuft eben alles in einem anderen Tempo. Barrierefreiheit ist insgesamt eine langsame Dame. Aber sie macht Inklusion überhaupt erst möglich. Ich frage mich manchmal, wie solche Fragen wohl in hundert Jahren gelöst sein werden. Oder wird es dann vielleicht gar keine Menschen mehr geben, für die sie heute noch relevant sind?

Ich kann inzwischen einfach nicht mehr die ganze Nacht durcharbeiten und am nächsten Tag trotzdem produktiv sein. Diese schlaflose Nacht habe ich deutlich gespürt. Und wie war das früher? Damals konnte ich die ganze Nacht auf Partys verbringen und am nächsten Tag trotzdem arbeiten oder studieren. Und heute? Heute tauchen nur noch seltsame Gedanken in meinem Kopf auf, und alles verlangsamt sich. Trotzdem wollte ich nach der Arbeit nicht schlafen, damit mein Körper in der Nacht wenigstens etwas zusammenhängende Erholung bekommt.

Morgen treffe ich Herrn Baumeister, den Entwickler des Leitsystems in Berlin – und wahrscheinlich sogar eines der bedeutendsten Leitsysteme Deutschlands. Wenn mein Kopf morgen genauso funktioniert wie heute, werde ich mich bestimmt schrecklich blamieren und überhaupt nichts verstehen.

Die letzte Wahrnehmung meines müden Kopfes: Die U-Bahn-Station riecht nach verschwitzten Zügen!

Übrigens bilde ich mir das nicht nur ein. Mindaugas hat diesen Geruch ganz genauso beschrieben. Jedes Mal, wenn wir an der U-Bahn-Station in der Nähe unseres Hotels vorbeikommen, riechen wir beide diesen seltsamen Geruch. Natürlich wissen wir, dass Züge logischerweise nicht schwitzen können. Aber dieses Metall, der Geruch der Räder und Schienen, vermischt mit dem feuchten Beton unter der Erde – all das hat tatsächlich etwas von Schweiß. Die Bahnhöfe in Litauen riechen ganz anders. Vielleicht schwitzen unsere Züge einfach nicht?