AliasPass

Proof of presence under another name.

AliasPass gives writers, journalists, and publishers working under assumed names a way to confirm authorship or ownership—without revealing their real identity. Version 1.0 enables private code generation via secret URLs. These short-lived, one-time codes can be shown or spoken aloud in person, or shared digitally, allowing a trusted recipient to verify the writer’s chosen identity.

AliasPass is designed for face-to-face meetings, online correspondence, or any moment where a pseudonymous person must be trusted—not exposed.

Status: Operational
Hosted at: aes451.dev/verify
Goal: Help pseudonymous authors assert authorship and affiliation on their own terms—privately, safely, and when needed.

How it works (Version 1.0)

  • Each participant has a private secret URL.
  • Opening that link generates a one-time verification code, valid for a limited time.
  • The code can be shared, spoken, or shown to a trusted person.
  • Anyone can visit /verify to confirm which alias generated the code.
  • Codes expire after one use, so they cannot be reused or archived.

AliasPass codes don’t just confirm a name—they can also convey:

  • A specific identity number tied to the alias.
  • A physical detail, like a tattoo, known only to close collaborators.
  • A call-and-response phrase, such as:
    “I find the weather too cold.”
    “In Svardberg, it is always cold.”

Why it's safe

  • Codes are one-time use and expire quickly.
  • If the verifying person turns out to be untrustworthy, they cannot reuse the code to prove your identity.
  • The verification page is public, but your secret link remains private.
  • No connection is made to your real identity—only your chosen alias.

Planned Features

  • QR Code Generation
    Create scannable one-time codes for fast, discreet identity confirmation.

  • Flash Verification
    Show verification briefly—too fast to screenshot or copy—adding deniability.

  • Optional Logs
    Allow trusted users to privately track when a code was generated or checked.

Real-World Case Studies

Verifying Authorship in a News Interview

An anonymous writer publishes a blog post that goes viral. A foreign journalist reaches out for an interview—but the writer can’t risk exposing their real identity.
During a call, the writer uses AliasPass to generate a one-time code and gives it to the journalist. The journalist enters the code at /verify and receives confirmation:

This person authored the article on alias-blog.org.
The interview proceeds with trust, without exposure.

Building Trust in a High-Risk Publishing Meeting

A pseudonymous publisher meets with two writers interested in working with her. They admire her online presence, but can’t be sure she’s not an infiltrator.
To earn their trust, she uses AliasPass to generate a call-and-response phrase. The writers read the first line on the verification page:

“I find the weather too cold.”
She replies without hesitation:
“In Svardberg, it is always cold.”
Her identity as the trusted publisher is confirmed—without revealing anything further.

Claiming Ownership in a Professional Setting

The curator of the Shadows Index, a well-known censorship-tracking database, attends a closed-door conference. She wants to collaborate, but her identity has never been linked to the project in real life.
Using AliasPass, she generates a one-time code. When one of them enters the code, they receive the message:

This person curates the Shadows Index.
The confirmation is brief and private—just enough to open the door to collaboration.

AliasPass is for those who write in the open—but must live in the shadows. It creates trust without forcing exposure, and confirms presence without demanding names.