mekarpeles - jbenet meeting notes for archival

[jbenet]

Why type of applications are the community making?

• discussion board
  -- aggregation (posts ordering)
  -- linking posts (references), linked-lists for ref'ing edits
  -- how do we deal with users connecting to the same device? "client"

pubsub for notifications

Questions:
- Rate limiting?

Digital signature could include a user_id and a client

Attachments: list of merkel-links on a message

ipld - similar to jsonld context

The POST Specification

A "POST" (Core) can be used to support the following mediums (aka Ext's):

1. Post (Core)
   1. From (ids) [direction]:
   2. To (ids) [direction]:
   3. Title (opt):
   4. Tags (ids):
      1. "from" + "to" tags all use the same id namespace -> RDF Wikidata / wikibase (use ipns) use domain
   5. Client?
   6. Message/Body
   7. Response to (merkle-links):
   8. Edit of (merkle-link):
   9. Time* (untrusted):
   10. References: map of merkle-links
       1. link w/ (opt) type [cite|response|edit]
       2. OpenAnnotations? See IIIF's spec
   11. Signature (digital) (opt):
2. Post (Ext)
   1. Chat @haadcode @mek @jbenet
      1. #mentions
      2. instead of channels, global stream + views / filters
      3. Imagine seeing a real-time filter as a chat room
      4. Sound/audo? video chat?
      5. topics: (streaming; orgs, servers, channels, search)
   2. Calendar
      1. Invites & Reminders
      2. accept / confirm messages
   3. Todos
      1. Tickets, issues, & checklists
      2. flags (as complete, etc)
   4. Articles
      1. blogs, journals
   5. Attachments
      1. Binary files
      2. streaming
   6. Notifications

TODO:

1. Identity (SIR, http://www.weboftrust.info/)
   1. What kind of stub can we use to design the POST
      1. a From/To can be a list of SIR identifiers
   2. For now, let's assume identities exist (so we can iterate on)
      1. maybe email.
   3. What is the public key?
      1. Phone number? Remember your own key
      2. writable by hand
   4. How to prove identity?
   5. Permenance of private key
      1. (SIR) registry of numbers
      2. 2-factor auth to protect key
      3. decentralized way
      4. (bad?) easy identification of unique "numbers" by hashing, concatenating, and re-hashing
         1. help people remember their number (securely encodes their details in the public key)
      5. Auto-complete module for finding people's keys
         1. javascript module, like auto-complete
2. Sharing
   1. We should discuss how Posts can be encapsulated in (a venn diagram) of circles / access controls.

Notes

• A post with a From/To can be considered a ping (callback?)
• Reminder: Ion (IPFS Object Notation) "Cannon"