Principles Seminar - Session 2: Inclusivity

principles

#1

Session 2 - Inclusivity. See Principles Seminar - Session 1: Openness for session 1.

(Inclusivity slide: https://hackmd.io/p/Byn5ww79m#/)
(Inclusivity notes: https://hackmd.io/uoDbzPoNSYW2_39nG7Jopw?both)


Open remarks

Principles Seminar v0

Session 2 - Inclusivity

Oskar, 2018-10-09


VIII. Inclusivity

We believe in fair and widespread access to our software, with an emphasis on ease-of-use. This also extends to social inclusivity, permissionless participation, interoperability, and investing in educational efforts.


Briefly on ‘Status’

When I say Status, I don’t just mean Status the app. I mean the organization and everything that we do and produce in this cosmos. The state of us. Status Republic. Status Network. “Company” and “product” misleading mental models.


Fair and widespread access

  • Works on many (old) devices and languages
  • Not just first-world users
  • Access not passive => run, use, study, contribute

Ease-of-use

  • Usable for non-experts
  • But also for us as contributors
  • Software compatibility

Social inclusivity

  • Encouraging people to participate
  • Rings on water, activation ladder
  • Barriers to entry and 1/9/90 rule

Everyone’s job and self-interest

(power = responsibility)

  • How many people you onboarded?
  • How many issues (open problems) created?
  • Help in Status or online?
  • => Concrete call to action people to dive deeper

Interoperability

  • Clear and well understood interface
  • Useful and used by others
  • Not isolated network

Educational efforts

  • Put time, money and energy into people learning
  • Bottleneck for crypto adoption
  • Get more people grok new paradigm

(openness, inclusivity)

  • Bigger contributor network != traditional hiring
  • Cost of people: ($, coordination, ~chat)
  • Core contributors as stewards
  • Funded by subset of people who value
  • => Massive parallelization possible
  • See proof of concept called Linux
  • ~1000 MAC, ~12 lieutenants, ~ 1 Linus

Shower thought 1

Measuring Inclusivity and executing on it relentlessly is the same thing as mass adoption of Ethereum.


Shower thought 2

Before mass adoption comes intense micro adoption.

It’s better to make something that 100 people love than something that 1,000 like. – YC motto

  • First Status CCs then larger Ethereum community
  • And/or: specific communities with a strong need
  • Retention is key

(inclusivity, continuance)

The value we generate is in the network.

  • If value is proportional to contributors N…
  • What is N now? Last month?
  • => Importance of contributors metrics

Wall of shame

  1. We don’t know how well we are doing on this front
  2. 99% of our work is never incentivized in open form
  3. App barely useful enough for even us to rely on it
  4. App not available publicly in app store
  5. Hard to get SNT in the first place

Thanks


Notes

Session 2 - Inclusivity

Deliverables

  • wall of shame

[Oskar]
Presented intro slides. Company/product discussion. Have levels of activation on how involved and active someone can be wrt Status. Call to action, e.g. reporting a bug, helping someone install Status, we all have a role in driving engagement. Lack of education is a bottleneck for crypto in general.

Broadening our contributor network is not the same as hiring. Core contributors can be thought of as stewards, and people in the network are funded by other people in the network who like their ideas. This permissionless model negates the need for coordination.

Need better contributor metrics to track our success in developing the network. The value is in our network.

[Michael]
Fair and widespread access - does Status work on many devices? Or are we ashamed because this didn’t happen yet [it’s the latter]. Devices and OSs are older - is this something we can even tackle?

[Oskar]
Living in developed countries, have Apple devices, not all of our users have the same access to technology, are we being inclusive of everyone, or just people who are like us?

[Ricardo]
On being more inclusive on a technical level - what about a light client that can run on older devices, with pared back functionality?

[Michael]
IRC was popular for years and was super lightweight, could we do a text-based version of Status?

[Igor]
Possible, but couldn’t run light client.

[Oskar]
Ignorant of how inclusive we are wrt devices.

[JB]
Can’t install on any of my chromebooks (one off the fastest growing devices for young people)

[Barry]
Looking at DApps that can broadcast over Whisper. Metamask e.g. connects with nodes that’s not running with Whisper enabled.

[Igor]
Setup difficulties deterring people when building Status.

[Barry]
Status Desktop build repo not accessible to the average developer. Lots of different components.

[Akshi]
Need more community-driven contribution into the content itself around education. Should make content freely accessible and not retain revenues from it. If we do have incentive models within the education realm, should be in a closed system, i.e. we are not trying to profit from it and the system sustains itself. Need to make content easier to find, navigate, and access. Translations, access by geography, etc. - could do things differently and be even more inclusive and collaborative.

one of the good approaches at ConsenSys was to be as open as practically possible with collaborations - so companies that wanted to do free translations of our content or foot soldiers outside core org members who wanted to go teach our content etc. There was then of course discussion, debate, and possible trade off in doing that vs. maintaining quality of content etc. but the attitude definitely was to try and be as open as possible towards maximum collaboration with outside parties.

[Shawn]
Taking community on a journey through familiarity with Status to contribution to the project. Want to give people more mechanisms and options to contribute. Not everyone needs to be a CC, but people should be given options to contribute in a way that suits them, e.g. making a one-off translation.

[Oskar]
Attended an event with real-time translation - can we do more with our events, e.g. Town Hall to increase accessibility?

[Ned]
Would be interesting to see, in a hostile environment, how using Status actually works. What would it take to get something up and running there that would be useful?

[Michael]
Could partner with groups in e.g. conflict zones, to stress-test Status.

Action item - explore partnerships with groups/networks to stress-test Status

[Ricardo]
Get complaints about Status Desktop not having certain features, e.g. Windows compatibility.

[Oskar]
Known problem, working to solve.

[Adam]
Slack made good use of bots for automation, something we could look into. From a DApps perspective, could educate people on how to use them.

[Stef]
Lacking geographic diversity - impacts our ability to create an inclusive product. Do we have a blind spot when testing our products, what perspectives are we missing?

[Iuri]
Before going to China, had no idea how widespread/popular WeChat is. Don’t see how people use this software in other contexts. Missing perspectives, only someone with a lived experience of being in these contexts can really tell us how our product works. How can we reach these people more efficiently?

[Lalo]
Doing research on how Status can benefit LatAm community, lots going on politically and in economics. Not being able to use Status with an outdated phone is an issue. Mesh networks, looking to connect with vendors/SMEs to see how they use this technology. Have to be culturally sensitive and not try to apply one Western way of thinking in how we approach people. Most important is education - not just about blockchain, but technology in general - how can this benefit people? General tech awareness is not taught at schools/unis, particularly public schools. Were lucky enough to be invited into a public school to present on Status, students were excited to hear about the possibilities.

[Michael]
What about a multilingual our.status.im? As something we strive towards, may not immediately be able to implement.

[Lalo]
Excluding huge swathes of the globe as not everyone speaks EN. When people can access content in their native language, they can engage with it - there’s a lack of localised content.

Action item - expand linguistic presence in social media / events

[Shawn]
Naver as an example in KR - biggest blogging platform in that region, trying to replicate content in local language is important, but - audiences will use platforms that are familiar to them in their local regions.

[Rajanie]
We want to be able to show that we’re trying and taking steps to localise content. We’re taking steps in the right direction.

[Barry]
SITG3 - all white males involved, can’t help but notice that. Lack of diversity may perpetuate the issue.

[Ned]
Accessibility - need one simple message that people can believe in. Can we roll up the Principles into a common belief that everyone can identify with.

[Michael]
Need a mission statement that’s easily translatable, and that resonates across cultures.

[Ricardo]
Interoperability - IM services typically compete for users. Users as products. The user is not our product, they can use other applications that can communicate with Status.

[Ned]
Need to inventory within the org whether the design language is accessible. Don’t currently have a framework. If we want to act with a decentralised design system, need to agree on it and test it for ourselves.

[Ricardo]
Thinking about forking a client - MSN Messenger Plus was a hacked version that violated ToS, but people used it because it had superior features. Maybe we should incentivise customisation of our client. People are going to do it anyway. Whatsapp+ is customisable, e.g. black background that’s energy-efficient.

Action item - incentivising forks, other usages of Status. Making customisations available. Define separation of status protocol from it’s reference implementation

[Iuri]
Being decentralised already provides value, the reference for the protocol needs to be specified clearly and create their own software. Status becomes a platform that people can build on top of, not just DApps.

Wall of shame - wrt inclusivity

  1. Status developed with new/expensive devices or latest OSs in mind
  2. Won’t install on some tablets (e.g. Android)
  3. Building Status not accessible to the average developer
  4. Need to make educational content more accessible, with more community-driven input
  5. No multi language direct collab stuff
  6. EN-language orientation of our social media
  7. Principles only in english

Let’s keep discussion open about this principle here, as well as add stuff to our wall of shame in this thread .


#2

I would clarify one point:

Need to make educational content more accessible, with more community-driven input

I think it was with regards to our ecosystem and tools that we use. Are we worried that people do not create DApps that talk to Status? Or DApps that use Whisper at all? Well, let’s write some tutorials and show people how to do that! This is also important from a different perspective, that is when people see potential in Whisper, they will be more interested in running Whisper/Status nodes. That’s another issue we are trying to solve and if we get noticed by DApps developers, it’s not gonna be a problem anymore.