Skip to content
Sharelinknow
About Sharelinknow · Architecture & Purpose

Built for temporary hand-offs. Designed to forget.

Sharelinknow is an ephemeral utility for bundling links, code snippets, and plain text notes behind a single, anonymous six-character pickup code. No accounts, no user tracking, and no permanent data retention.

01 · Problem

The friction of permanent platforms

Most modern collaboration tools are designed for perpetual storage. When you need to send a temporary URL, an API snippet, or a configuration note to a colleague, another machine, or a temporary partner, you are frequently forced to:

  • Create an account with an email address and strong password.
  • Authenticate through third-party social or enterprise identity providers.
  • Leave sensitive or transient information permanently indexed in chat histories, email threads, or cloud drives.

Sharelinknow was created to eliminate this friction. We treat temporary information as truly temporary: bundle what you need, deliver the pickup code, and let the data expire automatically.

02 · Audience

Who uses Sharelinknow

Software Engineers & Sysadmins

Move configuration snippets, SSH public keys, terminal logs, and staging URLs across distinct devices, test servers, or virtual machines without cluttering corporate message channels.

Writers, Researchers & Students

Organize reference links and research citations into a structured slip to hand off between desktop workstations, tablets, or shared laboratory terminals.

03 · Workflow

The hand-off mechanics

1

Compose the slip

Add up to 40 items across links, formatted code blocks with syntax hints, and markdown notes (up to 256 KB total payload).

2

Set lifecycle and protection

Select an expiration interval (1 hour, 24 hours, 7 days, or 30 days). Optionally set a ticket password, which is hashed with scrypt before storage to guard sensitive contents.

3

Hand off the pickup code

Share the six-character alphanumeric code or direct retrieval link. The recipient enters the code to unlock and view the bundled items.

4

Automated deletion

When the expiration timestamp is reached, the database row is deleted. Subsequent retrieval requests receive an explicit 410 Gone response.

04 · Publications

Field Notes: Engineering & Design Publications

Beyond our core utility, we maintain Field Notes, an educational engineering publication. Field Notes documents our architectural decisions, investigations into modern web protocols, cryptographic best practices, and the challenges of building high-performance, minimalist web applications using Next.js, TypeScript, and relational databases.

Our articles focus on practical technical concepts: implementing constant-time credential verification, managing stateless HMAC-SHA256 session lifecycles, preventing cross-site request forgery, and designing responsive interfaces free of intrusive third-party scripts.

05 · Standards

Commitment to transparency and privacy

Our operational principles are straightforward:

  • Zero public accounts: We do not ask for names, email addresses, or telephone numbers to create or retrieve tickets.
  • No data harvesting: We do not sell, rent, or trade payload contents or visitor metadata.
  • Responsible disclosure: We welcome constructive technical audits and peer feedback through our Contact page.