Why it matters
Guest-first access lets every visitor enter the Town Square without completing an account form. Generalized guest presence can show exploration without exposing form contents, search terms, raw IP addresses, or private browsing details.
Preservation costs time, disk, bandwidth, and maintenance, so accountable node operation remains distinct from low-friction guest exploration.
How ForkMesh handles it
A registered user supplies an email and password, then verifies that email. Local desktop identities use device-held Ed25519 keys; public profile, device, platform, time, and activity fields remain separately configurable.
The distinction is explicit: a guest can explore, while account-only actions require an active authenticated session and any repository-specific authorization.
Where it fits
Use guest access to learn and explore; register when identity, collaboration, node operation, or rewards need an accountable user session.
It pairs with configurable badges and generalized public activity so immediate entry does not become precise surveillance.