Skip to content

Changes

Page history
Add OuiSync-Briar collaboration report. authored by akwizgran's avatar akwizgran
Show whitespace changes
Inline Side-by-side
Public-Mesh-Research-Report.md
View page @ 9daee0ce
...@@ -951,34 +951,6 @@ When connecting to the Linux device as an ordinary Wi-Fi access point, Android d ...@@ -951,34 +951,6 @@ When connecting to the Linux device as an ordinary Wi-Fi access point, Android d
But when connecting to the access point via the Wi-Fi Direct API, Android devices would not route their traffic through the access point. But when connecting to the access point via the Wi-Fi Direct API, Android devices would not route their traffic through the access point.
This was tested with the Samsung Galaxy A21s, LGE Nexus 5X and Moto G 4G. This was tested with the Samsung Galaxy A21s, LGE Nexus 5X and Moto G 4G.
## Alternative Transports
TODO: Move this to the OuiSync/Briar collaboration report
### OuiSync
It is currently possible to transport Briar messages between contacts via a OuiSync repo by using Briar's file export function.
This idea could be further explored by adding features to Briar to more easily export large amounts of messages, or even automate the import and export of encrypted files.
A video demonstrating OuiSync as a Briar transport layer can be found here: <https://vimeo.com/839579124>
#### P2P Connections over Intranets
One open question related to OuiSync and other alternative networking tools is how they perform in situations where there is a national-level intranet that is cut off from the global internet, and two peers inside the intranet want to connect to each other.
If reliable ways to make p2p intranet connections are found, it could be an interesting transport layer for Briar or a similar app to implement.
### Filesystem API
During our research on using OuiSync as a transport layer, we had some thoughts on an approach to generalize this "file import/export" feature. As Briar already includes the necessary methods to import and export Bramble streams to files, this could be used in an automated way to link Briar with outside Android applications like OuiSync automatically, by using the Android filesystem.
A description of a possible implementation of this idea:
- Outgoing messages would be encrypted and written to a list of directories for each contact/group, if there is no assigned directory for a given contact or group, it falls back to either a default directory or is simply not written to a file.
- Users set a watch-list of directories for Briar to periodically scan for new files to test for contact tags
This approach is not limited to OuiSync; developers of arbitrary data transport layers could create Android applications also following this file import/export system, allowing Briar messages to be tunneled through outside transport systems like a public mesh propagation application.
For more information visit: <https://code.briarproject.org/briar/public-mesh-research/-/issues/23#note_77366>
## Future Considerations ## Future Considerations
### Combining Transport Layers ### Combining Transport Layers
......