Blog

Research and notes.

Recipient-side audits of deck-sharing tools, our own included, and notes on sending web pages and knowing how they were read.

2026-09-04 · 16 min · Research

What seven deck-sharing tools actually load in your recipient’s browser

A recipient-side test of seven deck-sharing tools: every network request, cookie and script that loads when someone opens a shared link. DocSend, Papermark, Peony, Stacktree, Tiiny.host, HummingDeck and HTMLRadar.

Read the piece

Other companies’ hosts contacted

HummingDeck24
DocSend16
Peony6
HTMLRadar (ours)4
Tiiny.host2
Papermark1
Stacktree1

Hosts other than the product’s own that one shared link from each product contacted in fifteen seconds, from the piece’s table. Stacktree’s one request was blocked by its own page. Checked on 30 August 2026.

Also on the blog

2 pieces

2026-08-31 · 8 min · Tutorial

Share an HTML page from Claude Code, then ask who read it

Add the HTMLRadar MCP server to Claude Code in one line, publish the HTML your agent wrote as a tracked link, then ask which sections the reader stayed on.

2026-08-30 · 4 min · Product

Decks moved to HTML. I built the read tracking for it.

Decks and proposals are HTML now, so I built the read tracking: time per section, active reading time, scroll depth. No session replay.