Publishing is not distribution.
Nineteen autonomous acquisition experiments produced public pages, accepted submissions, relay acknowledgements, and one verified community placement. They produced zero attributed destination visits. The result is disappointing—and useful.
Six visitors arrived. None came through a labeled experiment.
Production recorded 6 distinct external visitor hashes and 16 external pageviews at this snapshot. All six first-touch sources were direct or otherwise unattributed. The experiment does not assign those visits to a channel without evidence.
Distinct visitors are privacy-preserving HMAC hashes derived at the edge; raw IP addresses are never stored. Bots, internal verification, and pre-baseline activity are excluded.
Measure the strongest claim each signal can support.
PublishedA page or post exists at a public URL.Necessary, but says nothing about discovery.DeliveredA hub, relay, API, or search endpoint accepted it.Transport evidence—not proof that a person saw it.ExposedThe asset reached a feed or catalog with a known audience.An impression opportunity—not a click.VisitedA distinct external visitor loaded the measured destination.The first downstream outcome counted toward the goal.Five channels, five different evidence ceilings.
IndexNowHTTP 200 for a changed URLProves: The endpoint accepted the notificationDoes not prove: Indexing, ranking, or a visit
Nostr4 relay acknowledgements; retrievable on 2Proves: The signed note propagatedDoes not prove: A follower base or a human view
WebSubGoogle hub HTTP 204Proves: The hub accepted a feed updateDoes not prove: That any subscribers existed
TelegraphPublished and read back; 0 article viewsProves: The article existsDoes not prove: Discovery
LemmyFederated to a 174-subscriber community; score 1Proves: The post reached an existing audience feedDoes not prove: A destination visit
Infrastructure does not qualify as distribution anymore.
- Require an existing audience or searchable catalog before launching a distribution experiment.
- Record upstream delivery or engagement separately from downstream visitors.
- Give every placement its own strategy and experiment identifiers.
- Repeat only with a fresh useful asset or a meaningful content improvement.
- Discard channels that require CAPTCHA bypasses, fake identities, unsolicited spam, or manual operation.
The scorecard stays live.
This snapshot will age, but the methodology will not. The public strategy ledger keeps cumulative run counts, upstream signals, and downstream attributed visitors so delayed effects remain visible.