Background

  • Developed with Cursive at Edge Lanna in Chiang Mai in Thailand.
  • Stated objective: apply cryptography to enable people to safely and expressively connect.
  • Ran at Devcon for 15,000 people
  • Felt like we nailed the user experience, user interface, and merchandise, but didn’t fully realize its functional potential

UX / UI

  • NFC chip + sticker could be associated with user account
  • When either was tapped by a phone, it was used to:
    • Swap contact
      • Platform agnostic — doesn’t matter if you’re iOS or Android
    • Run a series of Private Set Intersections on:
      • Self-inputted content:
        • Templates
        • Preferences
      • Imported content (via OAuth flow):
        • Calendar
        • Activities
          • Strava
          • Github
          • Social Layer
      • Location chips:
        • Use location to signify an activity attendance
    • Only reveal symmetries

Functionality

  • Central server only used for:
    • Networking
    • Encrypted backup
  • Accountless feature
    • UX / UI step improvement for local-first apps!
  • NFC Chips
    • User chips
      • Extensible by user
    • Location chips
      • Extensible by community admin
  • Extensible communities + activities
  • Increasingly sophisticated crypto matching
    • All cryptography performed on user devices
      • Local cryptography is cheap, local AI is expensive
  • OAuth Syncer

OAuth Imports (Syncer)


Aftermath

  • Told the team that I thought coliving would be ideal place to continue the work
  • They said I could continue the work, but they couldn’t support it bc there was no direct business model
  • Ideal shell to develop on, but need to nail functional benefits
  • Been waiting for the right incubation environment to continue the work

Conspirio

  • What:
    • If user data was available and safely shareable, non-fungible connection is a solvable problem.
    • Etymology:
      • “Conspire”: comes from the Latin word conspirare, which literally means “to breathe together”. Words ending in -spire (like inspire, expire, or conspire) come from the Latin verb spīrāre, which means “to breathe” or “to blow”. The Latin spīrāre gave English words dealing with breath, life, and spirit.
      • Conspirio: “to share spirit, life with”
  • How:
    • How (UX):
      • “being in village means deep connection and serendipity, this turns a city back into a village”
      • Depth from the start
        • Commonality, complementarity, contrast:
          • Ex: Andre — if only we had known we had dweb, coliving, embodiment, and authentic relating in common? depth is in the intersections.
        • Non-negotiables up front:
          • Compatibility for friendship, work, long-term partnership, flings, etc
          • Examples:
            • Friendship and work: Compatible (symmetric, complementary) interests?
            • Long-term partnership:
              • Do they want children?
              • Are they monogamous vs polyamorous?
          • Could provide a good incentive to fill out data after the fact:
            • Input more missing data, “unlock” more matches
            • Data could be an input to an arbitrary number of templates
          • Turn alienation into connection:
            • Example: imposter syndrome. Turn isolation into a basis of solidarity.
        • Bottom-up Objectivity:
          • Imported data could be verifiably true.
      • Spontaneous coordination
        • Connection + time = serendipity.
          • Example: location chip + calendar PSI. Narrowcast dinner, routines, parties, etc
          • Structuring serendipity at the group level = spontaneous coordination
        • Narrowcasting:
          • Relevant notifications
      • Utilizing transitive commonality:
        • Ex: sharing social graph, commonality of commonalities can also be shared.
    • How (Technically):
      • Cryptographic primitives are sufficiently accessible and expressive to build out interesting functionality
      • In the wild, cryptography is cheap while local AI is expensive
  • For Who:
    • Start with Embassy, for now.
    • Could be ideal for third spaces: Commons, Frontier Tower, Gloundfloor, and other Dunbar-sized communities.

What’s Next:

  • Looking for collaborators, especially folks interested in:
    • Programmable cryptography, specifically the question:
      • “How to offer customizable cryptographic templates for matching?”
    • Local AI:
      • “How to use Local AI to fill out templates?”
    • Business model:
      • “How could this make money?”
        • Managed version
        • Community version
          • Pay-per-update?
    • General engineering:
      • When and how to pull out the Syncer and generalize between applications?
  • Continue development…