briar issueshttps://code.briarproject.org/groups/briar/-/issues2021-07-06T09:39:13Zhttps://code.briarproject.org/briar/briar/-/issues/2022Implement website for app sharing2021-07-06T09:39:13ZSebastianImplement website for app sharingSubtask of #1081Subtask of #1081Install via Bluetooth or Wi-FiTorsten GroteTorsten Grote2021-07-31https://code.briarproject.org/briar/briar/-/issues/2021Permission requests cleanup in hotspot test app2021-07-06T09:40:50ZTorsten GrotePermission requests cleanup in hotspot test appThe hotspot test app currently asks for permissions once when it starts and then just refuses to work if they were not granted. We should probably introduce some sort of PermissionController that encapsulates all that logic and ensures t...The hotspot test app currently asks for permissions once when it starts and then just refuses to work if they were not granted. We should probably introduce some sort of PermissionController that encapsulates all that logic and ensures that the necessary permissions and enabled system settings (wi-fi, location) are requested properly.
Subtask of #1081Install via Bluetooth or Wi-FiTorsten GroteTorsten Grote2021-07-31https://code.briarproject.org/briar/briar/-/issues/2020Implement UI prototype for app sharing2021-07-06T09:40:41ZSebastianImplement UI prototype for app sharingSubtask of #1081
1 acitivty + 3 fragments + 1 troubleshooting fragmentSubtask of #1081
1 acitivty + 3 fragments + 1 troubleshooting fragmentInstall via Bluetooth or Wi-FiTorsten GroteTorsten Grote2021-07-31https://code.briarproject.org/briar/briar/-/issues/2019ViewModel Cleanup (in hotspot test app)2021-07-06T09:40:45ZSebastianViewModel Cleanup (in hotspot test app)Subtask of #1081Subtask of #1081Install via Bluetooth or Wi-FiSebastianSebastian2021-07-31https://code.briarproject.org/briar/briar/-/issues/2018Create RemovableDriveWriterTask2021-06-17T13:35:02ZakwizgranCreate RemovableDriveWriterTaskCreate an interface in bramble-api, with an impl in bramble-core, for a task that writes data to a file for syncing with a given contact. It should be possible to attach and detach observers for observing the progress of the task (see #2...Create an interface in bramble-api, with an impl in bramble-core, for a task that writes data to a file for syncing with a given contact. It should be possible to attach and detach observers for observing the progress of the task (see #2013 and #2014). The task should unregister itself with the RemovableDriveManager (see #2016) when it finishes running.
Subtask of #1802Transfer content securely via SD cards and USB memory sticksakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/2017Create RemovableDriveReaderTask2021-06-17T13:35:19ZakwizgranCreate RemovableDriveReaderTaskCreate an interface in bramble-api, with an impl in bramble-core, for a task that reads data from a file for syncing with a given contact. It should be possible to attach and detach observers for observing the progress of the task (see #...Create an interface in bramble-api, with an impl in bramble-core, for a task that reads data from a file for syncing with a given contact. It should be possible to attach and detach observers for observing the progress of the task (see #2013 and #2014). The task should unregister itself with the RemovableDriveManager (see #2016) when it finishes running.
Subtask of #1802Transfer content securely via SD cards and USB memory sticksakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/2016Create RemovableDriveManager2021-06-17T13:35:40ZakwizgranCreate RemovableDriveManagerCreate a manager interface in bramble-api, with an impl in bramble-core, to manage access to the RemovableDrivePlugin (#2015). The manager will provide methods for doing the following:
* Retrieve the current reader/writer task, if any, ...Create a manager interface in bramble-api, with an impl in bramble-core, to manage access to the RemovableDrivePlugin (#2015). The manager will provide methods for doing the following:
* Retrieve the current reader/writer task, if any, for a given contact
* Register and start a reader/writer task for a contact (fails if an equivalent task is already registered)
* Unregister a task (for use by the task itself, when it finishes running)
We may later want to convert this to some kind of abstract TaskManager interface with TaskKeys and so on, and refactor other long-running tasks to use it, but let's not do that yet.
Subtask of #1802Transfer content securely via SD cards and USB memory sticksakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/2015Create RemovableDrivePlugin2021-05-10T13:07:16ZakwizgranCreate RemovableDrivePluginCreate a RemovableDrivePlugin that extends FilePlugin, along with a suitable PluginFactory. The plugin's writerFinished() method can be a no-op. The readerFinished() method should try to delete the file if the tag was recognised and the ...Create a RemovableDrivePlugin that extends FilePlugin, along with a suitable PluginFactory. The plugin's writerFinished() method can be a no-op. The readerFinished() method should try to delete the file if the tag was recognised and the read completed without an exception, failing gracefully if the file is on a read-only filesystem.
The ~~UI~~ read/write tasks (#2017 and #2018) will interact with the plugin via its createReader() and createWriter() methods, which are already provided by FilePlugin.
Subtask of #1802Transfer content securely via SD cards and USB memory sticksakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/2014Update MessagesSentEvent to include amount of data sent2021-05-10T12:00:41ZakwizgranUpdate MessagesSentEvent to include amount of data sentSubtask of #1802Subtask of #1802Transfer content securely via SD cards and USB memory sticksakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/2013Add database method for getting amount of data to sync2021-05-10T12:00:48ZakwizgranAdd database method for getting amount of data to syncSubtask of #1802Subtask of #1802Transfer content securely via SD cards and USB memory sticksakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/1995Test sharing an app when offline2022-07-20T10:38:40ZTorsten GroteTest sharing an app when offlineYou will need *two* Android phones to help with testing sharing an app in an offline scenario.
It starts by download this test app on the first phone: https://grobox.de/tmp/hotspot.apk
Then please respond to this ticket, copying and pa...You will need *two* Android phones to help with testing sharing an app in an offline scenario.
It starts by download this test app on the first phone: https://grobox.de/tmp/hotspot.apk
Then please respond to this ticket, copying and pasting the text below into your response, giving the phone models in the first line.
You can check boxes by replacing `[ ]` with `[x]` or sending your response and then go through the steps, checking boxes by clicking them.
If you don't have or want an account to respond here, you can also send your response to `contact@briarproject.org` via email.
Please also respond, if you fail to complete all the steps. We would especially like to hear from you!
If something didn't go as expected, please feel free to add extra info to the questionnaire.
This is an example, how going through these steps could look like on the first phone:
[<img src="/uploads/b78344755319ed1b0830ce528b8c9637/device-2021-04-13-141128.png" width="200">](/uploads/b78344755319ed1b0830ce528b8c9637/device-2021-04-13-141128.png)
[<img src="/uploads/cdf3ae921106e98ee9dabbec2dfb3ac8/device-2021-04-13-141146.png" width="200">](/uploads/cdf3ae921106e98ee9dabbec2dfb3ac8/device-2021-04-13-141146.png)
[<img src="/uploads/750cd78087a215ede1c8a295eb9eb8a2/device-2021-04-13-142703.png" width="200">](/uploads/750cd78087a215ede1c8a295eb9eb8a2/device-2021-04-13-142703.png)
[<img src="/uploads/2e720826106e1fbedad1dde85b1683cd/device-2021-04-13-142720.png" width="200">](/uploads/2e720826106e1fbedad1dde85b1683cd/device-2021-04-13-142720.png)
[<img src="/uploads/6ccedfa1a0f8475383e43eb202645258/device-2021-04-14-102618.png" width="200">](/uploads/6ccedfa1a0f8475383e43eb202645258/device-2021-04-14-102618.png)
```
1. My phone models are: **[ModelOfPhone1]** and **[ModelOfPhone2]** running **[AndroidVersion1]** and **[AndroidVersion2]**
1. Download and install app on the first phone only
1. Start app and allow location permission (if requested)
1. [ ] Below the `START HOTSPOT` button, it says that `5GHz Wi-Fi is supported`.
1. Press the `START HOTSPOT` button
1. [ ] A QR code for a Wi-Fi appears
1. [ ] The Wi-Fi's name starts with `DIRECT-`
1. [ ] Below the `START HOTSPOT` button, it says `Hotspot started` and there's this text behind: **[no text]**
1. With a second phone I was able to connect to this Wi-Fi by
1. [ ] Scanning the QR code with a reader app
1. [ ] Entering the Wi-Fi data manually in the phone's Wi-Fi settings
1. Once the second phone is connected, press the `PEER CONNECTED` button
1. [ ] The app shows `http://192.168.49.1:9999` at the bottom
1. Press the menu/overflow icon and select `Network interfaces`
1. [ ] A new page shows text that includes the line `p2p0: /192.168.49.1`
1. Press the back button to come back to the (second) QR code screen
1. I was able to visit the shown site with the second phone by
1. [ ] Scanning the QR code with a reader app
1. [ ] Entering the link manually in my browser app
1. [ ] I could not visit this site
1. [ ] I could download the app on the second phone
1. [ ] I could install and open the app on the second phone
1. [ ] The second phone stayed connected to the first phone's Wi-Fi and I did not need to reconnect
1. While still connected to the first phone's Wi-Fi, go to system settings on the second phone.
* Open Wi-Fi settings and select the first phone's Wi-Fi.
* Try to find the `Frequency` (e.g. `5 GHz`) the Wi-Fi is using and write it down here: **[frequency]**
1. [ ] Bonus step: I could repeat the process by switching phones and it works the same or different in what aspect?
```
You can see how this will look like below or when using the "Preview" tab in your response.
Subtask of #1992Install via Bluetooth or Wi-FiTorsten GroteTorsten Grote2021-07-31https://code.briarproject.org/briar/briar/-/issues/1993Define overall technical and UX approach2021-07-13T10:34:36ZakwizgranDefine overall technical and UX approachUX/dev collaboration to define the overall technical and UX approach for this feature.UX/dev collaboration to define the overall technical and UX approach for this feature.Transfer content securely via SD cards and USB memory sticksTorsten GroteTorsten Grote2021-07-31https://code.briarproject.org/briar/briar/-/issues/1992Initial experiments to decide whether to use Bluetooth or Wi-Fi2021-07-06T09:40:57ZakwizgranInitial experiments to decide whether to use Bluetooth or Wi-FiInstall via Bluetooth or Wi-FiTorsten GroteTorsten Grote2021-07-31https://code.briarproject.org/briar/briar/-/issues/1985Register public mesh research app's signing key and package name with Google ...2022-01-21T14:13:18ZakwizgranRegister public mesh research app's signing key and package name with Google PlayIf we plan to develop a research app as part of #1817, register the package name and app signing key with Google Play before the end of July 2021 so we're not required to let Google manage the signing key.
https://android-developers.goo...If we plan to develop a research app as part of #1817, register the package name and app signing key with Google Play before the end of July 2021 so we're not required to let Google manage the signing key.
https://android-developers.googleblog.com/2020/11/new-android-app-bundle-and-target-api.html
Subtask of #1817.Public mesh researchakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar/-/issues/1984Register social mesh research app's signing key and package name with Google ...2021-09-01T09:47:43ZakwizgranRegister social mesh research app's signing key and package name with Google PlayIf we plan to develop a research app as part of #1816, register the package name and app signing key with Google Play before the end of July 2021 so we're not required to let Google manage the signing key.
https://android-developers.goo...If we plan to develop a research app as part of #1816, register the package name and app signing key with Google Play before the end of July 2021 so we're not required to let Google manage the signing key.
https://android-developers.googleblog.com/2020/11/new-android-app-bundle-and-target-api.html
Subtask of #1816.akwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar-mailbox/-/issues/9Register mailbox app signing key and package name with Google Play2022-02-07T09:46:53ZakwizgranRegister mailbox app signing key and package name with Google PlayRegister the package name and app signing key of the mailbox app with Google Play before the end of July 2021 so we're not required to let Google manage the signing key.
https://android-developers.googleblog.com/2020/11/new-android-app-...Register the package name and app signing key of the mailbox app with Google Play before the end of July 2021 so we're not required to let Google manage the signing key.
https://android-developers.googleblog.com/2020/11/new-android-app-bundle-and-target-api.htmlMailboxakwizgranakwizgran2021-07-31https://code.briarproject.org/briar/briar-mailbox/-/issues/62API endpoint for wiping the mailbox2022-02-25T14:52:36ZakwizgranAPI endpoint for wiping the mailboxThis endpoint allows the owner to wipe the mailbox remotely.
Depends on #49.This endpoint allows the owner to wipe the mailbox remotely.
Depends on #49.Mailbox: UnpairingTorsten GroteTorsten Grote2021-11-15https://code.briarproject.org/briar/briar/-/issues/2169Store hidden service address and auth token for own mailbox in Briar DB2021-11-25T13:25:48ZakwizgranStore hidden service address and auth token for own mailbox in Briar DBMailbox: Pairingakwizgranakwizgran2021-11-15https://code.briarproject.org/briar/briar-mailbox/-/issues/50API endpoint for pairing2022-02-07T09:46:20ZakwizgranAPI endpoint for pairingThe pairing endpoint should:
* Check that the auth token provided by the client matches the one in the DB
* Reject the token if it doesn't match, or if there's no unused token in the DB
* Generate, store and return an auth token for the ...The pairing endpoint should:
* Check that the auth token provided by the client matches the one in the DB
* Reject the token if it doesn't match, or if there's no unused token in the DB
* Generate, store and return an auth token for the owner
Depends on #42.Mailbox: PairingTorsten GroteTorsten Grote2021-11-15https://code.briarproject.org/briar/briar/-/issues/2167Decode QR code for pairing with mailbox2022-02-25T14:52:29ZakwizgranDecode QR code for pairing with mailboxDecode the mailbox's hidden service address and the single-use auth token from the QR code payload.
Depends on briar-mailbox#48.Decode the mailbox's hidden service address and the single-use auth token from the QR code payload.
Depends on briar-mailbox#48.Mailbox: PairingDaniel LublinDaniel Lublin2021-11-15