the sigils provide a simple vocabulary for referencing people and data within a distributed mesh network. the symbols are inspired by unix tradition, and somewhat by secure scuttlebutt sigils. the meaning of a particular expression is fully subjective. sigils allow humans to annotate documents with machine readable context tokens. the subjective context is not attached to replicated documents.

keep in mind that only a "true name" is globally unique. your atoms and the related atoms that you can access using `~` syntax are only lables.


a path. this represents the connections between places.


a reference point. center yourself here. you are in many places at once. prefix a name with this sigil to indicates a reference. a tilde by itself (~/{name}) is a reference to your personal namespace, others would use ~{your_username}/{name} to access the same resource (if they have permission).



a direct link to a resource; this is the "true name". a "true name" is either self-certifying (a blob identified by its hash) or represents a cryptographic identity. both are identified using the same crytographic hash function and represented as base58check encoded values.



refers to a locally unique alias which refers to a particular resource by its "true name" or by reference.

:some-file %GFAMXXPjLU3ASFhfN1kjovbBa5njgqVsPkV7LrNhdTeY
:why-not-http ~solderpunk/gemlog/why-not-just-use-a-subset-of-http-and-html.gmi


in addition to the general application of sigils in shared documents, they can be used together with gemdoc|indental to create the context files that are used to attach subjective meaning to said documents.

  # legacy services like DNS may be accessed though system prefixes
  ~dns : {some_delegate}
  # a name may be bound to multiple values as long as they
  # resolve the same resources
  # delegate to an identity server (finger+shs)
  ~xj9 :
  # link to a particular key
  ~r14c : %{key_hash}