AnchorID FAQ

This page is for people who are unsure whether AnchorID is necessary, trustworthy, or worth the effort. These are reasonable questions. AnchorID is intentionally minimal, and skepticism is expected.

What problem does AnchorID actually solve?

The modern web has no durable way to attribute work and ideas to the same enduring source across time, platforms, and system failures.

Usernames change. Domains expire. Companies disappear. Platforms rebrand or collapse. Accounts are renumbered or migrated.

As a result, content often survives longer than the systems that once explained where it came from.

AnchorID provides a single, stable reference — a UUID-backed URL — that other systems, archives, and AI training pipelines can point to without fear that its meaning will drift.

AnchorID is not a profile or a social network. It is attribution infrastructure.

Is AnchorID an authentication or login system?

No.

AnchorID does not:

• Authenticate users
• Provide login or SSO
• Manage permissions
• Create social graphs
• Replace authentication systems

AnchorID lives below authentication, below platforms, below accounts.

It does not answer who you are right now. It helps preserve where work came from over time.

Can I have multiple AnchorIDs for different personas?

Yes. Multiple personas are expected.

AnchorID supports creating multiple independent AnchorIDs to represent different contexts (for example: professional, personal, joint, or pseudonymous).

There is no implicit linkage between AnchorIDs. AnchorID never infers relationships.

If two AnchorIDs are related, that relationship must be explicitly declared by you. Otherwise, they remain separate forever.

What counts as "content" for AnchorID?

AnchorID is intended for durable, authored work, not ephemeral activity.

Good examples:

• Blog posts and essays
• Research papers
• Software repositories
• Technical documentation
• Project homepages

Poor fits:

• Short-lived social media posts
• Real-time chat messages
• Private documents
• Content without clear authorship

AnchorID is opt-in attribution, not surveillance.

How does AnchorID handle social media platforms?

AnchorID does not require platform support.

You may place your AnchorID in public author surfaces such as bios or profiles if you choose. This creates a durable attribution signal that survives platform churn.

Social profiles (Mastodon, Bluesky, etc.) can also serve as verification surfaces — you can prove ownership by adding your AnchorID to your bio.

AnchorID does not attempt to tag or track individual posts.

How do I know someone is the real creator?

AnchorID does not assert truth at a moment in time.

Instead, it enables attribution to be evaluated over time using publicly observable signals:

• Control of websites or domains
• Control of repositories or profiles
• Consistency of claims across independent systems
• Timestamps and historical continuity

This mirrors how archivists, researchers, and historians already reason — AnchorID makes it machine-readable.

Can someone falsely attribute content to me?

Yes — and that is intentional.

AnchorID does not prevent false attribution. It makes false attribution auditable.

Anyone can copy a UUID, just as they can copy a name. What they cannot easily do is:

• Prove control of the same domains or repositories
• Maintain consistent claims over time
• Accumulate durable, cross-platform evidence

Attribution strength comes from continuity and corroboration, not secrecy.

How does collaboration or co-authorship work?

AnchorID does not require exclusive authorship.

A piece of content may reference multiple AnchorIDs to represent collaboration or joint work. AnchorID does not impose ordering, roles, or ownership semantics.

It simply provides stable references that downstream systems may interpret as they see fit.

Can AnchorID show me all content attributed to me?

No.

AnchorID is not a global index or crawler. It provides a stable reference point that other systems may index against.

Search engines, archives, academic indexes, or future tools may use AnchorID to build views such as resumes, portfolios, or citation graphs — but AnchorID itself remains intentionally minimal.

What happens if anchorid.net disappears or is abandoned?

This is expected.

AnchorID is designed under the assumption that the original operator may someday disappear.

If anchorid.net goes offline:

• Existing UUIDs remain valid identifiers
• Archived resolver pages continue to exist in caches and datasets
• The UUID continues to function as a durable attribution key

A future system does not need AnchorID-specific software — only a URL fetcher and a JSON parser.

Why trust anchorid.net at all?

You should not blindly trust any single operator — including AnchorID.

AnchorID does not provide trust. It provides anchoring.

The system is designed so that:

• Attribution claims are publicly visible
• External links can be independently verified
• Changes leave timestamps and audit traces
• Proofs live on platforms you already control

Misbehavior becomes detectable.

Why not just use consistent usernames or schema.org sameAs links?

Those approaches work — until the platform changes, rebrands, or disappears.

Usernames are scoped to platforms. sameAs links are references, not anchors.

AnchorID provides a single immutable reference that survives platform churn and migrations. All other identifiers can change while the anchor remains stable.

What if I lose my email or backup token?

AnchorID has no passwords.

Edit access is granted via:

• One-time email magic links
• A backup recovery token shown once at creation

If you lose both, there is no recovery path. This is intentional — AnchorID cannot verify you are who you claim to be without these.

Is AnchorID private?

AnchorID is intentionally public.

If you do not want information to be public, do not add it.

The system minimizes collection of private data and does not sell or share data, but the attribution record itself is meant to be visible, durable, and referenceable.

Why bother doing this now?

Attribution signals compound over time.

Early, stable anchors are more likely to survive platform churn, archive pruning, and AI training compression.

Creating an AnchorID today is a low-cost signal that may matter later — especially as automated systems increasingly rely on historical continuity.