REALITYWIPE

OLD SCRIPT DETECTED

Both ticks turned blue an hour ago and still no reply

Try this response:

The blue tick tells me they opened it. It doesn't tell me why they haven't answered.

Take the 60-second self-check

SEE THE PRACTICE

Build a response for this thought—and one move to prove it.

THE THOUGHT

Both ticks turned blue an hour ago and still no reply

YOUR RECORDED RESPONSE

The blue tick tells me they opened it. It doesn't tell me why they haven't answered.

ONE PRIVATE MOVE

Set the phone screen-down on the step, finish coiling the hose once at your normal pace, then check the clock against how long the wait actually felt.

The Hose You Keep Re-Coiling

The Coil You Do Twice While WaitingYou're in the driveway coiling the garden hose after washing the car, phone propped on the porch step. The message about splitting the cost of the neighbor's fence went out forty minutes ago, and both ticks turned blue within seconds — they opened it, no question. Now you keep glancing over between loops of hose, because a confirmed read that goes unanswered for an hour doesn't feel like a delay. It feels like they read exactly what you said and decided, deliberately, not to answer it yet.

The Receipt That Turned Into a VerdictThe mechanism is simple: once you know for certain the message was opened, any other explanation for lateness — poor signal, a missed notification — disappears. What's left is a monitored countdown you never agreed to, close to what Hall and Baym describe as the expectation that replies arrive on a schedule the other person owes you. The blue tick removes doubt about whether they saw it, so your mind fills the remaining gap with the one thing it can't verify: intent.

One Coil Length, Screen Face DownNext time the tick turns blue and the reply doesn't, finish coiling the hose with the phone screen-down on the step, untouched, for the length of exactly one full coil. Then check the time. Most coils run three to four minutes; the dread usually insists it's been much longer. This doesn't prove anything about what the silence means — it only tests whether your sense of ignored time matches the actual clock, one coil at a time.

TRACE · 01/04

How this script runs you

  • You keep reopening the chat just to confirm the tick is still blue, not grey, as if it could quietly change back.
  • You count the exact minutes since the read receipt turned blue instead of finishing whatever is in your hands.
  • You draft two or three explanations for the silence before you've finished a single loop of the hose.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Last Seen Loop

If someone has definitely opened and read your message and still hasn't answered within the hour, that confirmed gap is treated as a direct, private verdict on how much you matter to them right now.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • The blue tick tells me they opened it. It doesn't tell me why they haven't answered.
  • An hour of silence after a read receipt is still just an hour, not a ruling.
  • I can finish the task in my hands before the gap gets to write the ending.

Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.

INSTALL · 04/04

The protocol, on one card

When I think

Both ticks turned blue an hour ago and still no reply

I say

The blue tick tells me they opened it. It doesn't tell me why they haven't answered.

Then I do one thing

Set the phone screen-down on the step, finish coiling the hose once at your normal pace, then check the clock against how long the wait actually felt.

STATUS: READY_TO_INSTALL

Wipe this thought

4 minutes. Your voice. Free.

Start this exact wipe in the app →

The wipe protocol
  1. Write the thought exactly as it plays: "Both ticks turned blue an hour ago and still no reply". Word for word — the wipe targets the sentence, not the vibe.
  2. Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
  3. Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
  4. Run the loop: play it every morning and night, log one proof action a day for 7 days.

Straight answers

Does the blue tick mean they read every word, or just that the chat was opened?

A read receipt confirms the conversation was opened on their screen. It doesn't confirm they absorbed the message, remembered to reply, or made any decision about you — those are separate steps the tick can't show.

If a full hour passes after the tick turns blue, isn't that itself proof they're avoiding the topic?

An hour is consistent with dozens of ordinary things — a meeting, a nap, a message they meant to answer later — and with avoidance. The read receipt narrows nothing about which one it is; it only tells you the screen was seen.

Should I keep checking to make sure the tick hasn't somehow reverted to grey?

Read receipts don't revert once sent, so rechecking the color confirms nothing new. The repeated checking is measuring your own unease, not gathering information about their reply.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script