A Shell & Environment to Play
- A clean UX / UI that was battle-tested at Edge City Lanna, Devcon (15000 people), EthIndia
- At the time thought that coliving would be better environment to incubate than pop-up city / conference
- Embassy as an incubation environment for “Dunbar Tech”
Demo
Value Propositions
- Cross-platform UX
- Depth from the start
- Ex: Andre
- Connection in time is serendipity
- Narrowcasting: Conditional / relevant notifications
- Ex: Calendar PSI + Notification
- Socializing activities, routines
- Ex: Dinner, coworking, impromptu meeting, run, walk, etc
- Spontaneous coordination
- Communal coordination layer?
- Narrowcasting: Conditional / relevant notifications
- Embodied / Embedded relationship with technology
- Physically: NFC chips as configurable, programmable way of interacting with lived environment
- Ex: Location chips
- Ex: Chips embedded into merch
- Data: interoperability means applications can be used in combination, greater than the sum of their parts?
- Ex: Devcon calendar, Telegram
- Physically: NFC chips as configurable, programmable way of interacting with lived environment
- Legibility + group incentives as different games to play
- Legibility as an attention attractor / forcing function
- Ex: tap + onboarding incentives for merch
- Ex: competition, collaboration
The end goal: “being in village means deep connection and serendipity, lets turn cities back into villages… but this time around, memetic villages”
Speculative
- Bottom-up objectivity + verifiable traits
- Transitive connection means social graphs can be shared
- Transitive connection as an effort multiplier
- 2PC vs MPC
- Groups use a lot of the same math and / or could set up a TEE (trusted execution environment )
- Common knowledge? Group preferences? Governance?
What’s Next
- Distribute stickers to embassy residents
- Location chips
- Ex: leaderboard: gym, tasks (trash, recycling, watering, dishwasher)
- Ex: coordination: dining room coworking, dinner
- Admin console for registering social, location chips
- Devcon Calendar PSI ⇒ Google Calendar OAuth App — for timing
- Telegram Integration ⇒ Slack OAuth App (instead of Telegram) — for notifications
- Create some artisanal templates, to get back into the pattern
- Begin generalizing template patterns, come up with draft scheme to allow users to create their own
- Ex: friends, interests, work partner, long-term partner, fling
- can input data after the fact, to “continue the connection”
- Ex: friends, interests, work partner, long-term partner, fling