HackMD
Status Principles Seminar
Oct 9, 2018 - Oct 19th, 2018
Copyright and related rights waived via CC0.
Welcome!
- What's up with the order and succession?
- Format, opening talk, personal bias
- Why do this?
-
To get people to engage with principles in a more high resolution way. Why?
-
To increase our individual and collective ability to think about these things. Why?
-
To make sure we are building the right thing in the right way. Why?
-
To give access to better tools to socially coordinate, communicate and transact. Why?
-
To increase liberty for everyone.
Status
The goal of Status is widespread adoption of the decentralized web. Our challenge is achieving mass adoption while staying true to our principles outlined below.
Let's begin…
The Plan
- Oct 09: Openness & Inclusivity
- Oct 10: Security & censorship-resistance
- Oct 11: Decentralization (people and computers)
- Oct 16: Privacy & Transparency
- Oct 17: Continuance & resourcefulness
- Oct 17: Liberty & Anon chat
Principles Seminar v0
Session 1 - Openness
Oskar, 2018-10-09
Copyright and related rights waived via CC0.
VI. Openness
The software we create is a public good. It is made available via a free and open source license, for anyone to share, modify and benefit from. We believe in permission-less participation.
Public goods
| Excludable | Nonexcludable | |
|---|---|---|
| Rival | food | fish in sea |
| Nonrival | private parks | air |
Public goods (cont)
- Anyone can use it
- Antifragile torrent files
- Networks, not stovepipes
Free license
- Freedom to run, study, share and modify code
- Status LLC gone? Software survives
Permission-less
- Anyone able to participate in creation
- Ethereum nodes
- Less coordination (just contribute!)
- Open to unique perspective
- Free culture vs permission culture
Principles pairing
Like pairing wine and food. That's where the real discussion happens.
thesis + antithesis => synthesis
(openness, security)
- Free modification => risk of malicious versions
- Mitigations: reputation, signed binaries
- Scope: under Security
(openness, continuance)
Using individual SNT (private good) to keep the public good public and good?
"Build Status with Status"
(openness, privacy)
Certain legal agreements require salary information to be private, how does that interact with open compensation models?
(openness, liberty)
Live in a world where people benefit freely?
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety – Ben Franklin
Wall of shame
A conversation starter.
- Changing code requires privileges
- License situation unclear: some CC0, some not
- Cluster repo private, harder to participate
- Slack and GDocs, closed and permissioned
- Network non-rival good?
Thanks!
With that, handing it over to the facilitator. Coming up: next speaker, open discussion, wall of shame generation, and more.
