Governance Public Utilities for @zksync at @thezknation
Jan 14 • 14 tweets • 1 min read
A bill of rights for us, onchain:
0/
Right to Exit: The ability to voluntarily leave the system, service, platform, organization, or protocol without facing undue burden such as excessive costs, penalties, or roadblocks.
Jul 31, 2022 • 9 tweets • 2 min read
Community building is a holistic practice - we can’t isolate and combine specific actions, like pharmaceutical molecules, into a cocktail of medication. Doing this creates a brief sense of progress towards community but not a deep rooted home for growth.
Instead, community is built through an embodiment of connection, embedding it throughout the entire environment. This means the frame requires a full on perspective and priority to make it happen.
Strange, I can definitely envision a new social attack vector. If services are based on Sybil resistance, you can imagine a situation where a coordinated group of people report you as a Sybil or threaten it. Then social ostracism might be accidentally paired with service removal.
@spengrah this is pretty interesting imo
Jul 30, 2022 • 18 tweets • 3 min read
“Yes we understand you want to consume content from people you’re interested in.
But we need to grow the target ads we show you, so here are all the ways we’re going to force you to consume algorithmically chosen content.”
“At the end of the day, we want every user to be able to discover great content.
The business model is predicated on two items: engagement and ad performance. So we’ve designed a discovery system that supports both keeping you online as long as possible and getting you to spend”
Mar 31, 2022 • 39 tweets • 5 min read
Often, communities stumble when they hit their first internal conflict between members. It's useful to remember that conflict is normal.
If members involved are asked to leave or decide to leave, the other members should reflect on why this was the case.
(1/X)
I would wager 9/10 times, asking a member to leave or having a member leave is the wrong approach. Forking is OK, exit to leave is OK, and yet:
Mar 30, 2022 • 11 tweets • 2 min read
It’s one thing to realise the existence of something (steam),
and another thing to design a system that harnesses it’s power (engine).
We know “Lore” is a thing, but it’s currently known as a raw material, not a harnessed material.
If we think of:
Steam <> Movement Engine
Then we can explore:
Lore <> Cultural Force
Mar 26, 2022 • 19 tweets • 3 min read
Thinking about an outline for an essay on Decentralized Media. I think I’m gonna pronounce is DeMe (pronounced Dimi? or maybe Demi like demigod might be cool)
Here’s what I’m thinking for the outline:
The rise of DeMe, a new Headless God
- The Everything Exchange
- Our Identity, in Shares (or, everything is fashion)
- A new headless god: Decentralized Media
- Content Liquidity Wars (or, the race for inventory)
- A whole new (derived) world
Mar 25, 2022 • 6 tweets • 1 min read
There are definitely at least three ecosystems of ETH-art forming:
- Dom et al
- Yuga et al
- ArtBlocks et al
These also are defining boundaries around DAO/Digital-Community collaboration.
Artistic Value Expression as
Cultural Boundary Definitions
It seems the communities will eventually Center around two axis:
1. IP Default
— CC0
— Collector Derivative IP
— Creator Priority
2. Content Permanence
— On chain
— Off chain
Mar 25, 2022 • 6 tweets • 1 min read
What if we thought of Decentralized Media as an ecosystem with actions and players analogous to DeFi?
Whereas DeFi focuses on Assets, DeMe? focuses on Content.
Assets may be a proxy of Content and may be Content itself.
Whereas the output of DeFi is economic, DeMe?’s output is heritage/culture?
Rhythms for Team of 3 people:
- One 1-hour weekly alignment call together
- Three 1-hour working session between each teammate (1:1s)
- Individual email summaries weekly
- Sync chat group, threads for subtopics
- 1 doc with North Star and weekly workpackets
- Multiple shared docs
I think this works up to 5 people, if there’s strong discipline. Break down afterwards.
Jan 15, 2022 • 4 tweets • 1 min read
Been noticing a fork in how web3 orgs are evolving:
Different approaches to mission development, interaction paths, and energy focus. Both excellent adventures for community development.
In product-communities, a small team creates a product and mobilizes a community that supports and rallies around the mission.
Then the community helps shape the product through active input, advocacy and partnership in testing as well as adoption.
Nov 23, 2021 • 6 tweets • 2 min read
Let’s get readddyyyyyy. Welcome to the FIFTH week of
***Vibe Ops🌞***
Each week, DAO contributors share their stories, articles, and do a Q&A with folks.
This week's topic: Digital Space Design
Once community comms infrastructure in place, then comes parallelisation: mission, projects, incentives, governance.
But no scale until reliable comms in place for community mobilisation. A strong influential network lead is a shortcut… but unsustainable, point of failure.
In the short term, effective. In the long term you need to replace personal network influence with tech power. And that means inspiring comms delivered at scale. In other words: fan development.
Nov 22, 2021 • 5 tweets • 2 min read
Every community should have a living manifesto, that get's reviewed every season, and re-written from scratch every age (4-5 seasons).
It is the north star, a call-to-action, and summary of values, and a primary form of alignment between new members.
A well-written manifesto should be an articulation of the vibe, a spawner of memes, and a decision framework for potential as well as current contributors.
Nov 22, 2021 • 14 tweets • 7 min read
✨Some news✨
I'll be joining @viamirror team as their DAO Lead! 🪞
My journey into web3 started in 2014, as a crypto-lurker, then a year and a half ago I fell into the rabbithole of digital communities. And barely 2 months ago I decided to go full web3.
What a ride.
In the role, I'll be supporting Mirror's journey to full decentralization:
- Building community infrastructure
- Mobilizing the most talented group of web3 writers, creators, and communities in our space today
- Nurturing an ecosystem of mutual support and D2D partnerships
Five types of community messaging:
- Sharing (Ideas, News)
- Signalling (Direction)
- Scheduling (Events)
- Summary (Newsletter)
- Sh*tposting (Connection)
We need interfaces that can handle them all, and create feeds tailored by type.
Sharing ideas evolve often from a dedicated channel, into some signalling milestone - then into gDocs, knowledge mgmnt or exploration interface. Very fragmented today.
Nov 21, 2021 • 11 tweets • 2 min read
Community scale is based on parallelisation, not sequential speed. Investing in core foundations to support multiple decoupled projects is the key.
Reflecting on this thought: why does it feel like traditional companies are constrained by this? What are the characteristics that help parallel execution vs. coupled dependencies?
Nov 21, 2021 • 6 tweets • 2 min read
The scale of digital communities is constrained by the clarity in how to prioritise, not by the clarity in what to prioritise.
How to make decisions >> What should we do now
The former supports decentralized and parallelised execution - the later centers on group consensus
How to make decisions is a recipe book that should be written for every community:
- Clarity in values
- Clarity in evaluation criteria
- Clarity in appropriate governance pathway
