# IPFS All Hands Call

Recording:
Moderator: @jonnycrunch
Notetaker: @hsanjuan

## Attendees

* hsanjuan
* whyrusleeping
* lgierth
* jonnycrunch
* frankpetrilli
* Marten Seemann
* Jay Carpenter
* daviddias
* not making it: kubuxu, dignifiedquire, flyingzumwalt
* victor

## Agenda

* Start recording
* Call for additional agenda items (moderator)
* Using Discourse (@lgierth)
* Docs sprint report (@lgierth)
* Status of sprints?

## Notes

Jay Carpenter, Marten introduce themselves

### Discourse

The process for choosing discourse is finished (we chose to use it). Seems we are going to have to host it ourselves if we want to run on top of our own SSL certs

### Docs sprint report

Wrote a bunch of documentation (go-ipfs/libp2p/js-ipfs/multiformats). Work on automating deployment of websites and documentation.

The test-lab stuff is not related to this sprint (Frank has been working on the testlab) but there is no work on linking Jenkins and testlab.

A small js-ipfs in browsers sprint is going to happen this week.

### DC Blockchain conference (@jonnycrunch)

Jonnycrunch: I ran the code-a-thon as part of the DC Blockchain Summit last week, which was sponsored by the Health and Human Services Office of the National Coordinator for Health IT (ONC). This was the first US Government Sponsored code-a-thon focused on blockchain technologies partnering with the Chamber of Digital Commerce. Unfortunately DC had a major snowstorm so we switched it to a virtual code-a-thon and streamed everyting to youtube (https://www.youtube.com/channel/UCjR-m6q3NEp-0CNZfxkVl2w/videos).

During the summit, I had a very interesting meeting with Dr. Robert Kahn (invented TCP/IP) regarding Digital Objects Identifiers and the Global Handler Registry, in that I expressed my conern that using centralized certificate registry authorities is repeating the mistakes of ICANN and DNS. He seemed open the the idea of content addressing with multihash and ipfs. He was open to talking about this in more depth. Perhaps Juan can coordiate a visit to DC to discuss?

During the code-a-thon, a couple of teams used IPFS as part of their solution. Some approaches to encryption on IPFS.

Q: Will private networks help with the encryption front? (healthcare data etc...)
Jonny: Yes, but my colleagues don't think so. Corporations are slow to move so while it has potential it's probably not happening right away. I this up with Manu Sporny in W3C Verifiable Claims task force, but current solutions seem still to be http focused.

Jeremy: ipfs dag put could take JSON-LD encoding.

Jonnycrunch: Yes, but what parsing the @context stored on ipfs without a http gateway?

### General questions

Jay: When someone is active on IRC, is anyone going out and finding who these people are, where they are from etc.? There's amazing people there so it might be interesting to gather some data and have a sort of IPFS LinkedIn/Profile. This would be valuable in building/connecting communities

V: It might be a good idea to start luring them to discuss...
L: Let's get this started along with discourse

### Demos

### Links from the sprint chat (Any mistakes in this posting of links is the responsibility of @JayCarpenter)
From David to Everyone: (09:41 AM)
https://github.com/libp2p/js-libp2p-circuit/blob/master/implementation-notes.md

From David to Everyone: (09:40 AM)
WebSockets - https://github.com/ipfs/js-ipfs/pull/740#discussion_r107808722

From David to Everyone: (09:35 AM)
https://github.com/libp2p/specs/tree/master/relay

From Victor - Protocol Labs to Everyone: (09:33 AM)
Sprint issue: https://github.com/ipfs/pm/issues/358
following: https://github.com/ipfs/pm/issues/351