Skip to content

Instantly share code, notes, and snippets.

@dignifiedquire

dignifiedquire/doc.md

Created July 17, 2016 14:51
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save dignifiedquire/869f8eb6beef13266933e8b409975951 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save dignifiedquire/869f8eb6beef13266933e8b409975951 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
doc.md

Audiences

IPFS's audiences are:

  • Developers
  • Protocol Technologists / Academics
  • "Users"
    • Service Providers
    • Content Creators
    • Researchers with Data / Archivists
    • Developing world
  • Tech Journalists (via a "Press Kit" section)

The most important audience is developers—while that is in and of itself an audience, it's an overbroad one. And developers are likely represented in all audience groups, on at least some level.

What "job" do these audiences want to do?

Identifying the "job to be done" of each audience helps us stay focused when drafting content and prioritizing information.

Protocol Technologists / Academics

  • In less than 30 seconds understand the basic theory and architecture behind the approach, including resiliency and security implications
    • If I can do that, I might be interested in reading a longer version of the spec
  • Know whether this is currently being worked on actively

Developers

  • Try it out on the website in less than 30 seconds
    • If I like that, I might take the next level step and install it and do something from the command line
      • If I like that, I might check out a sample project
        • If I like that and understand it and tweak it, I might be interested in complete documentation on how to build something new
  • Understand the underlying tech on a high level and what it means I can do with it.
  • Know whether this is currently being worked on actively

Service Providers

  • Understand in less than 20 seconds if it can do anything relevant to me.
    • Understand in less than 30 seconds if this weird new piece of tech I don't understand can save me money
    • If I can, I might be interested in talking to someone about how I could put IPFS to use

Researchers with Data / Archivists

  • Understand in less than 20 seconds if it can do anything relevant to me.
    • Understand in less than 30 seconds if this weird new piece of tech I don't understand can help me store / analyze / share / archive data in a way that is more useful or better than other alternatives
      • If I can, I might be interested in how I can put it to use in this capacity.

Content Creators

  • Understand in less that 20 seconds if it can do anything relevant to me.
    • Understand in less than 30 seconds if this weird new piece of tech I don't understand can either save me money or help me distribute content that can't be taken down or can't be traced so I can safely share it
      • If I can, I might be interested in one of the projects that would help me do this

Developing World

  • Understand in less than 20 seconds if it can do anything relevant to me.
    • Understand in less than 30 seconds if this weird new piece of tech I don't understand can help me build networks and share content in a low or no bandwidth case.
      • If I can, I might be interested in how I can put it to use in this capacity.

Tech Journalists

  • Understand in less than 30 seconds whethis this is worth writing a story about and why
  • See links to talks and other articles proving relevance
  • Find out who to talk to about this tech so I can get my story written
  • Know that this is currently updated
  • Find logos and photos I can use to make writing my article easier

Highest priority jobs to be done:

  • "Tell me in 5 seconds what it is and why it matters."
  • "Let me try it out."
  • "Help me understand how the technology works on a high level, then let me dive in deeper technical level"
  • "Tell me if I can do anything with it that's relevant to me."
  • "Show me this is actively being worked on and isn't theoretical vaporware."
Raw
doc2.md

Outline of audience groups:

Protocol Technologists and Academics

  • Internet Architects
  • Networks + Crypto Researchers
  • Decentralization/Blockchain Leaders

Builders

  • Blockchain shops
  • Web developers
  • Desktop application developers
  • Mobile app developers
  • DIY hackers

Enterprise Users

  • ISPs and CDNs
  • Cloud services
  • Game publishers / developers
  • Banks and other financial institutions
  • Governments as users
  • Video streaming services
  • Movie production studios
  • Movie festivals

Indie Users

  • Radical/autonomous tech collectives
  • "Freedom" Journalists
  • Artists
  • Subversive groups (good)
  • Indy media / media activists
  • Community networks

Research and Archive Users

  • Archivists
  • Scientists with data
  • Big data

Developing world

Tech Journalists Tech Journalists are a very specific audience with unique needs and should be addressed by calling out a "Press Kit" on the site.

I think there is additionally a category of audience which specifically needs to hear this message:

"IPFS supports copyright and opposes harassment"

  • Subversive groups (bad)
  • "bad bits" sharing
  • Governments as regulators

More references: https://github.com/protocol/collab-with-andyet/issues/5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment