Content API design

[benhylau]

Motivations & goals

The Content API will serve metadata about the website content that is published by the Distributed Press server. For example, what are the list of URLs we can access one.compost.digital/foreword/ at? In this case, they are:

• https://one.compost.digital/foreword/
• ipns://one.compost.digital/foreword/
• hyper://one.compost.digital/foreword/

Or what are the historic versions of this page? For example:

• ipfs://bafybeie7utfcwapu6av5qojfca3eiovd4v2dqxgaj6jzjszexy5zmc3jey/foreword/

These should be served by the Content API.

In addition, to facilitate sharing of content into distributed social networks, the API should serve alternative formats of content. For example, if I am reading something on Beaker, I should be able to request a markdown version that I can share to Scuttlebutt or Aether (both markdown based).

Full text can be made available by multiple formats, signed by authors, editors, and third-parties (e.g. truth verification groups).

Design proposal

See:

• API endpoint for fetching signed content.
• Potential content identifier spec ISCN

Identity and signature schemes should be multi-provider.

What can we do with it?

• Locate content across the DWeb across different protocols
• Reference historic versions of content on the DWeb
• Share full text of content in different formats to distributed social networks where communities gather and discussions can take place
• Sign and verify full text of content in different formats (e.g. a markdown blob reproduced to a social network can be signature verified)

[jackyzha0]

Closing (applies to v0)

[RangerMauve]

Gonna revisit this in milestone 4

[fauno]

We're punting this, right?