Why Reader Identity Belongs in the Comment Experience

Protocols compound. Apps compete.

Threadline's focus is the managed comment experience: reader profiles, reputation, and publisher controls in one hosted service.

The Strategic Rationale

When we started building Threadline, we faced a choice: build a walled garden or build infrastructure for the open web. We chose the latter - but with a twist.

Reader identity is a product feature. It is designed to help people build a consistent profile and reputation across supported Threadline communities, with controls for publishers and readers.

Threadline Comments is the product. It's the best implementation of TIP - the one we pour our engineering effort into, the one we monetize, the one we're responsible for.

Why This Works

Think of SMTP for email. The protocol is open. Gmail, Outlook, and thousands of other implementations compete on quality. Nobody owns email. Everybody benefits.

We want the same for web identity. If TIP becomes the standard, publishers win (no vendor lock-in), readers win (portable reputation), and we win (best-in-class implementation).

What We Kept Proprietary

The managed service. The analytics dashboard. The moderation tools. The ad network. The infrastructure that makes it all just work with one script tag.

If you implement TIP yourself, you get the protocol—not the hosted Threadline service. Hosting, moderation tools, operational support, and availability depend on the implementation and any separate service agreement.

The Long Game

We believe the next decade of the web will be defined by protocols, not platforms. TIP is our bet on that future.

If you're building on the open web, we'd love to have you as a partner.