The (November) 2016 Tahoe-LAFS Summit

This is a loosely organized gathering of Tahoe-LAFS developers, enthusiasts, and perhaps some hecklers.

Dates / Location

Tuesday+Wednesday 2016-11-08 and 2016-11-09, 9am-5pm.

We're meeting in the "Board Room" of the ​Mechanics Institute Library, 57 Post St, San Francisco, CA (next to the Montgomery St BART station).

The room has wifi, a whiteboard, and a projector screen. Brian will bring a small projector. There are plenty of restaurants and bars nearby for later in the evening.

We'll try to set up videochat so remote folks can join in the fun: contact us on IRC (#tahoe-lafs on freenode) and we'll make something work.

Attendees

(please add your name!)

For sure:

• Brian
• Daira
• meejah
• Zooko
• David

Probably:

• Liz

Nope:

• str4d

Agenda Items

(please add things you want to talk about)

• 1.12 release items
• (daira) 2-phase commit
• (warner) (meejah) (zooko) Accounting
• (warner) compelling applications
• (meejah) magic-wormhole based "setup" flow
• (meejah) integration (with other applications)
  • write down use-cases
  • e.g. what sorts of grids are there etc.
• (meejah) GUI (/WUI/CLI) things (e.g moar JSON endpoints, ...)
• (meejah) allow/deny storage servers (i.e. I want a grid where only "my" storage servers are used)
• (zooko) #1382 (We don't need to talk about it, we just need to do it. Brian and I can sit elbow to elbow until it is done, if he wants. ☺)
• (david) asymmetric crypto "caps"
• (david) chacha20 crypto caps
• (david) (meejah) data structures and or caps that support group revocation schemes via threshold of valid signatures
• (meejah) general "deletion" stuff: the different use-cases/scenarios and brainstorm ways to do this
• (meejah) magic-folder datamodel improvements (e.g. "leif's design" etc)
• (david) high level mixnet discussions of attacks and mitigations; n-1 attack mitigation via integration with reputation systems for increased reliability or heartbeat onions addressed to sender for verification of mix reliability etc.
• (david) code review of pylioness and go-lioness; clean up api design for parameterizing crypto primitives and thereby genericizing the lioness cipher construct
• (david) api design review of sphinxmixcrypto a fork of Ian's sphinx reference python code but modified to be more pep8 compliant and to parameterize the crypto primitives.
• (david) review of crypto primitive selection for sphinx mixnet packet header format; offered security bits versus packet header overhead etc.

things referred to during the Summit

• (notes to be added here)