[ToC]

# Brief with Dietrich 27 jan, 2021

## Plans for Berty Messenger in 2021

* **🎯 MAIN GOAL: BEING PUBLIC**
* Q1 : Closed Beta (March)
only for dev, experts, early contributors
* Q2 : Open Beta (May)
open to all curious folks
* Q3 : Public Launch (July)
open to all granmas, friends, general public
* Q4 : Road to a worldwide community network!
massive migration from Signal to Berty?

## SOW 1 - Gomobile-IPFS

Initial plan: https://hackmd.io/bRSgnACJRbWuHhXywPrqRQ

### Updates on Gomobile-IPFS

* We extended gomobile-ipfs configuration, so we can integrate it within Berty Messenger
* We prepared the codebase in order to make it easy to add new drivers over time
* Everything was made in a way that allows various usages:
- **full** gomobile-ipfs: use the library without custom go code
- **hybrid** gomobile-ipfs: extend & make custom configuration of the library with go code
* At the end of the week, Berty Messenger will depends on gomobile-ipfs, we will then start using it on a daily basis

Current architecture detailed here: https://github.com/berty/berty/blob/master/docs/architecture/2020-11-27-adr-gomobile-ipfs.md

Our plan stays the same as before:
1. we experiment drivers, concepts on Berty, and then
2. we can port the stable components on gomobile-ipfs, for everyone.

### Next steps:

- add drivers interface, that will be exposed to both `gomobile-ipfs/bind` package & `berty/bridgeframework` package
- move basic drivers from Berty to gomobile-ipfs
- native-logger driver
- connectivty driver
- discuss with PL team about mobile optimizations
- rendezvous-point: what's the future of https://github.com/libp2p/go-libp2p-rendezvous/pull/1
- recycling connections when switching from a network to another
- long-term roadmap stays the same as before: https://github.com/berty/community/blob/master/meeting-notes/2020/Q4/2020-11-27--sow-gomobile-ipfs.md

## SOW 2 - BLE

* We didn't finish the discussion with PL about this SOW
* Here is the initial brief https://hackmd.io/M-SCOH44TxC2DMde_TLZ6Q
* What are the next steps?

## New proposal: SOW/RFP for `Go-Libp2p-Tor-Transport`

* We are currently working on integrating Tor with libp2p
* We already have something working that is using CTor (the official C daemon), with go bindings
* This version is not the best one but already working and potentially already interesting for the rest of the community and the projects in the IPFS ecosystem
* We hope to invest some time to make a better solution that could be potentially integrated with IPFS, Filecoin, etc with more confidence
* Here is some doc about what we've in mind https://hackmd.io/EiW-D7p5Q1iyxXdEw2ncrg
* What do you think?

## Other points

* Communication: can we talk about our grant publicly? do you have a link that we can share?
* As part of the SOW, we will have to write blogposts that can be cross-posted; what are the next steps?
* We didn't sent any bills for now, is it ok to wait?