Readership & Editions
Did the overnight desk file, and is anyone reading. Measured from the live database, not typed.
The overnight desk
An agent files at 06:00 New York time (about 10:00 UTC), commissions three stories against the AP wire, and publishes only if every check on the desk is green. On red, nothing ships and the day shows as zero here. Times of day are Ithaca time; the calendar day of an edition is UTC.
The last fourteen days, story by story
| Day | Filed | Stories |
|---|---|---|
| Oct 21Wed · today (UTC) | 0 | Nothing yet today. The desk files at about 10:00 UTC. |
| Oct 20Tue | 0 | No stories filed. |
| Oct 19Mon | 0 | No stories filed. |
| Oct 18Sun | 0 | No stories filed. |
| Oct 17Sat | 0 | No stories filed. |
| Oct 16Fri | 0 | No stories filed. |
| Oct 15Thu | 0 | No stories filed. |
| Oct 14Wed | 0 | No stories filed. |
| Oct 13Tue | 0 | No stories filed. |
| Oct 12Mon | 0 | No stories filed. |
| Oct 11Sun | 0 | No stories filed. |
| Oct 10Sat | 0 | No stories filed. |
| Oct 9Fri | 0 | No stories filed. |
| Oct 8Thu | 0 | No stories filed. |
Readers
The "readers" figure printed on every story was seeded for the fiction and is bumped by every non-bot request, including our own checks. It is not used here. What follows counts only browsers that ran the paper's own script, measured since September 8, 2026. No cookie is set; no IP address or full user-agent is kept.
engaged reads (45 s on the page, or three-quarters of the way down a story) · views
Where readers come from
Volume is not attention. A channel with many views and a low read rate is sending people who leave.
| Channel | Views | Reads | Read rate | Sessions | Time on page |
|---|---|---|---|---|---|
| direct | 19 | 4 | 21% | 10 | 39s |
| campaign:chatgpt.com | 3 | 1 | 33% | 3 | — |
| ai | 2 | 0 | 0% | 2 | — |
| organic | 1 | 0 | 0% | 1 | — |
Referring sites
| Site | Views | Sessions |
|---|---|---|
| google.com | 1 | 1 |
Devices
Most read, measured
Ranked by real views in the window, not by the seeded counter on the story page.
By desk
| Desk | Stories opened | Views | Reads | Read rate |
|---|---|---|---|---|
| Deep History | 2 | 3 | 1 | 33% |
| The Body | 1 | 1 | 1 | 100% |
Pages other than stories
| Page | Views | Sessions | Time on page |
|---|---|---|---|
| / | 6 | 5 | 5s |
| /topic/ancient-aliens | 3 | 3 | 62s |
| /about | 2 | 2 | 27s |
| /right-of-reply | 2 | 2 | — |
| /topic/chemtrails | 2 | 2 | — |
| /start-here | 1 | 1 | 24s |
| /topic/mk-ultra | 1 | 1 | — |
| /topic/reptilians | 1 | 1 | 44s |
| /topic/ufo | 1 | 1 | 102s |
| /topics | 1 | 1 | — |
| /vault | 1 | 1 | — |
Shares, by network
Every story carries a share bar. This is where readers sent them: "copy" is the link copied to the clipboard, "native" the phone's own share sheet.
Nobody has sent a story on yet in this window.
What earns the next click
Each internal link a reader follows is tagged with the block of the page it sat in. A block that appears on every page and earns three clicks is a different problem from one that appears twice and earns two.
| Block | Clicks | Sessions |
|---|---|---|
nav-list | 4 | 2 |
nameplate | 4 | 2 |
tag | 3 | 1 |
start-title | 1 | 1 |
row-title | 1 | 1 |
nav-start | 1 | 1 |
Method
A view is one page load in a browser that ran the paper's script; crawlers and command-line tools are dropped at the server. An engaged read is forty-five seconds of foreground time on a page, or three-quarters of the way down a story. A completion is the bottom of a story. Time on page counts only the time the tab was in front, between two seconds and thirty minutes. A session is one browser tab; the id lives in sessionStorage and is gone when the tab closes. Channels are inferred from the referrer and any utm_source. The same figures are available as JSON at /api/analytics.