briar issueshttps://code.briarproject.org/briar/briar/-/issues2023-02-01T14:36:46Zhttps://code.briarproject.org/briar/briar/-/issues/2395Check for Bluetooth timeout setting on stock Android 132023-02-01T14:36:46ZakwizgranCheck for Bluetooth timeout setting on stock Android 13CalyxOS 4.3.0 (based on Android 13) has a "Bluetooth timeout" setting that automatically turns off Bluetooth if no devices are connected for a configurable amount of time (the timeout can also be disabled). This setting could prevent Bri...CalyxOS 4.3.0 (based on Android 13) has a "Bluetooth timeout" setting that automatically turns off Bluetooth if no devices are connected for a configurable amount of time (the timeout can also be disabled). This setting could prevent Briar from connecting to contacts via Bluetooth if the timeout period elapsed with no contact connections.
We should check whether this setting exists upstream (stock Android 13) and whether a timeout is enabled by default.https://code.briarproject.org/briar/briar/-/issues/2408Split big BSP Records2023-01-31T21:44:51ZThomasSplit big BSP RecordsIn #407, the requested feature is to send files with sizes bigger than one BSP Record. The issue is cluttered with user feedback-quotes, therefore I thought I make a new issue to propose an implementation (I don't know if this is the bes...In #407, the requested feature is to send files with sizes bigger than one BSP Record. The issue is cluttered with user feedback-quotes, therefore I thought I make a new issue to propose an implementation (I don't know if this is the best way to handle that ...).
I realized that I basically need the same feature for https://code.briarproject.org/thomas/briar/-/issues/1 (with custom BSP-Record sizes). My thoughts are intended to allow for minimal overhead (saving every byte).
My idea is to introduce message-fragments/slices. I think it is not enough to add a new message-type to BSPv0, I think it will require BSPv1. (the slices will be required also for e.g. the REQUEST-Type)
I imagine to send message fragments like { message-hash, start of slice, slice length, byte-array }.
The message itself is prefixed with its total size (needs only to be transmitted with the first slice; since the message is only composed when all slices are there, it is no problem if the first slice is retransmitted).
The receiver can acknowledge fragments (by hash, start and length). When all fragments are available, the sender internally acknowledges the whole record and the receiver assembles the message. I could also imagine the sender caching which BTP-Frame contains which message-fragments so that the receiver can acknowledge BTP-Frames which might save some space. But it will add additional complexity ...
Having sizes&positions as varints ([an Implementation](https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/util/VarInt.java)) would be awesome.
Btw: Sorry for not replying to https://code.briarproject.org/thomas/briar/-/issues/1 yethttps://code.briarproject.org/briar/briar/-/issues/2318Crash on HTC One M9 when switching between the briar app and the settings ap...2023-01-25T17:23:06ZIvanaCrash on HTC One M9 when switching between the briar app and the settings app in the foregroundSteps to reproduce
- Install Briar and create a user account
- user is asked to "allow connections" (ie allow battery optimisation to be switched off)
- before tapping the "allow connections" button, go to settings app and verify that...Steps to reproduce
- Install Briar and create a user account
- user is asked to "allow connections" (ie allow battery optimisation to be switched off)
- before tapping the "allow connections" button, go to settings app and verify that the battery optimisation is 'on' (although probabky not relevant for this crash)
- then bring briar app back into the foreground tap the "allow connections"
- go to settings
- bring briar back into the foreground -> crash.
This as reproduced 2 times on HTC One M9 (android 7) and it doesn't have when the user performs the same steps with mailbox app.
Logfiles are attached
@akwizgran analysed and here are his comments (from MM)
looks like this is the stacktrace of the crash:
org.briarproject.briar.android.account.SetupActivity}: java.lang.RuntimeException: Parcel android.os.Parcel@7c94038: Unmarshalling unknown type code 6881391 at offset 684
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2729)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2790)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1505)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:173)
at android.app.ActivityThread.main(ActivityThread.java:6523)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:938)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:828)
Caused by: java.lang.RuntimeException: Parcel android.os.Parcel@7c94038: Unmarshalling unknown type code 6881391 at offset 684
at android.os.Parcel.readValue(Parcel.java:2452)
at android.os.Parcel.readSparseArrayInternal(Parcel.java:2807)
at android.os.Parcel.readSparseArray(Parcel.java:2076)
at android.os.Parcel.readValue(Parcel.java:2430)
at android.os.Parcel.readArrayMapInternal(Parcel.java:2726)
at android.os.BaseBundle.unparcel(BaseBundle.java:269)
at android.os.Bundle.getSparseParcelableArray(Bundle.java:910)
at androidx.fragment.app.FragmentStateManager.restoreState(FragmentStateManager.java:405)
at androidx.fragment.app.FragmentManager.restoreSaveState(FragmentManager.java:2735)
at androidx.fragment.app.FragmentController.restoreSaveState(FragmentController.java:198)
at androidx.fragment.app.FragmentActivity$2.onContextAvailable(FragmentActivity.java:149)
at androidx.activity.contextaware.ContextAwareHelper.dispatchOnContextAvailable(ContextAwareHelper.java:99)
at androidx.activity.ComponentActivity.onCreate(ComponentActivity.java:297)
at androidx.fragment.app.FragmentActivity.onCreate(FragmentActivity.java:273)
at androidx.appcompat.app.AppCompatActivity.onCreate(AppCompatActivity.java:115)
at org.briarproject.briar.android.activity.BaseActivity.onCreate(BaseActivity.java:92)
at org.briarproject.briar.android.account.SetupActivity.onCreate(SetupActivity.java:52)
at android.app.Activity.performCreate(Activity.java:6673)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1136)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2682)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2790)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1505)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:173)
at android.app.ActivityThread.main(ActivityThread.java:6523)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:938)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:828) [Briar_crash_11_May_2022_reproduced.txt](/uploads/ddad5db164d4d61b49a3ac11b70d9394/Briar_crash_11_May_2022_reproduced.txt)
[Briar_crash_11_May_2022.txt](/uploads/920b2d55e162d999725a2f03d704348a/Briar_crash_11_May_2022.txt)https://code.briarproject.org/briar/briar/-/issues/1854Provide Tor/obfsproxy arm binaries for Linux2023-01-25T11:44:13ZNicoProvide Tor/obfsproxy arm binaries for Linux_Let's properly document all the ARM binary stuff for Briar Headless._
Briar Headless currently only includes binaries for `linux-x86_64`. While Briar Android works on ARM, we need a special binary for (plain) Linux systems and [enable ..._Let's properly document all the ARM binary stuff for Briar Headless._
Briar Headless currently only includes binaries for `linux-x86_64`. While Briar Android works on ARM, we need a special binary for (plain) Linux systems and [enable them in code](https://code.briarproject.org/briar/briar/-/blob/8d735b30237aaf8212bb42d37783134a56d6e9b6/bramble-java/src/main/java/org/briarproject/bramble/plugin/tor/UnixTorPluginFactory.java#L99).
Here is a table with required flags for specified target devices:
| command | `-march=` | other flags | target devices |
| ------ | ------ | ------ | ------ |
| `arm-linux-gnueabi-gcc` | `armv6` | `-marm` | Raspberry Pi Model B Rev 2 |
| `arm-linux-gnueabi-gcc` | `armv6zk` | `-marm` | Raspberry Pi Model B Rev 2 |
| `arm-linux-gnueabi-gcc` | `armv6zk+fp` | `-marm` | Raspberry Pi Model B Rev 2 |
| `arm-linux-gnueabihf-gcc` | `armv7-a+fp` | `-mmusl` | Google Nexus 5 (postmarketOS) |
| `arm-linux-gnueabihf-gcc` | `armv7ve+simd` | `-marm` | Raspberry Pi 2 Model B (not tested) |
| `arm-linux-gnueabihf-gcc` | unknown | unknown | Raspberry Pi Model 3 (not tested) |
| `aarch64-linux-gnu-gcc` | `armv8-a+crc+simd` | `-marm` | Raspberry Pi 4 Model B (not tested) |
| `aarch64-linux-gnu-gcc` | `armv8-a+crypto+crc` | - | Purism Librem 5 (not tested) |
To add information on another device, the following commands are helpful:
```bash
cat /proc/cpuinfo
gcc -c -Q -march=native --help=target
gcc -v
```
Python also gives interesting information (enter these commands after starting `python3`; you can exit with ctrl + d):
```python
import platform
platform.architecture()
platform.machine()
```
For detecting your device properly, we depend on Java to tell us which is it:
```java
public class Arch {
public static void main(String[] args) {
System.out.println(System.getProperty("os.arch"));
}
}
```
Please compile it with `javac Arch.java` and post the output of `java Arch`.
Once you have that information, feel free to post the output to this issues. Your work will help getting Briar run on your device.
You can further help by trying to do a test compile. Using the following `briar.c`...
```c
#include <stdio.h>
int main() {
float a = 3.33 + 6.66;
printf("Briar rocks, %f!", a);
return 0;
}
```
...you can compile the program using e.g. `arm-linux-gnueabi-gcc test.c -o test.out -march=armv6zk+fp -marm`. Under Debian, there are `gcc-arm-linux-gnueabihf` and `gcc-arm-linux-gnueabi` available as cross-compilers. Please compile the program on your desktop device using the right compiler flags, copy the _test.out_ binary to your target device and try to execute it there. If it works, you can additionally provide the exact compile command that worked for you.NicoNicohttps://code.briarproject.org/briar/briar/-/issues/1897Groups/forums/blogs are shown as "already sharing" if initial connection to c...2023-01-20T14:33:34ZakwizgranGroups/forums/blogs are shown as "already sharing" if initial connection to contact is lostIf the initial connection to a contact is lost before client versioning messages are exchanged, any group/forum/blog we try to share with the contact will be shown as "already sharing".If the initial connection to a contact is lost before client versioning messages are exchanged, any group/forum/blog we try to share with the contact will be shown as "already sharing".Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/90Handle Hyperlinks (Clickable Links)2023-01-20T13:47:10ZakwizgranHandle Hyperlinks (Clickable Links)Users asked for the ability to include clickable links in messages and forum posts.
We need to think about how to handle this safely: hyperlinks can be used to identify forum subscribers ("barium"), or to spread malware.
A warning ...Users asked for the ability to include clickable links in messages and forum posts.
We need to think about how to handle this safely: hyperlinks can be used to identify forum subscribers ("barium"), or to spread malware.
A warning dialog could be shown before opening a hyperlink from an unknown source, but users would probably learn to ignore it. Perhaps hyperlinks should be allowed in private messages but scrubbed from forum posts?https://code.briarproject.org/briar/briar/-/issues/2363Mailbox unreachable screen on Briar side - landscape - Samsung 6810 (small sc...2023-01-19T13:07:05ZIvanaMailbox unreachable screen on Briar side - landscape - Samsung 6810 (small screen) links overwriting each otherOn Samsung 6810 when the mailbox is not reachable, the screen looks like this - links overwriting each other
![Screenshot_20220907_164841](/uploads/d38b4a87b6ae1d09611f0f99d02fd193/Screenshot_20220907_164841.png)On Samsung 6810 when the mailbox is not reachable, the screen looks like this - links overwriting each other
![Screenshot_20220907_164841](/uploads/d38b4a87b6ae1d09611f0f99d02fd193/Screenshot_20220907_164841.png)IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/2367Navigating back from Connection screen to Mailbox setup screens in Briar - se...2023-01-19T13:05:58ZIvanaNavigating back from Connection screen to Mailbox setup screens in Briar - second mailbox setup screen overwrites the first oneSteps to reproduce:
- In Briar go to Briar > settings > Connections and switch the internet and wifi connections off
- Then for to Briar > settings > mailbox => the mailbox is offline screen shows, which is correct
- Tap the check Con...Steps to reproduce:
- In Briar go to Briar > settings > Connections and switch the internet and wifi connections off
- Then for to Briar > settings > mailbox => the mailbox is offline screen shows, which is correct
- Tap the check Connections link on that screen => Connections screen shows, where the user can switch the internet and wifi back on
- switch the internet and wifi back on
- tap on Back button (arrow in upper left corner) and the first mailbox setup screen will show
- then tap continue => the second mailbxo setup screen overwrites the first one, see attached files
![device-2022-09-28-133914](/uploads/edcbf78a75a2348b7c280833da3ed82a/device-2022-09-28-133914.mp4)IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/2343End-to-end integration tests for communication via mailbox2023-01-19T13:05:12ZakwizgranEnd-to-end integration tests for communication via mailboxWrite end-to-end integration tests in which two Bramble components, representing a mailbox owner and a contact, communicate via a mailbox running on localhost.
Depends on #2228.Write end-to-end integration tests in which two Bramble components, representing a mailbox owner and a contact, communicate via a mailbox running on localhost.
Depends on #2228.MailboxSebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2358Rotating screen while "Your Mailbox has been unlinked" dialogue box is displ...2023-01-19T13:04:56ZIvanaRotating screen while "Your Mailbox has been unlinked" dialogue box is displayed causes blank screenSteps to reproduce:
I used the Xiaomi MI11 Lite 5G device, and the Pixel 2 and was able to reproduce on both
- I link the Briar app on either device with a mailbox on another device
- Then I unlink the mailbox using the mailbox device...Steps to reproduce:
I used the Xiaomi MI11 Lite 5G device, and the Pixel 2 and was able to reproduce on both
- I link the Briar app on either device with a mailbox on another device
- Then I unlink the mailbox using the mailbox device, so that the Briar app is unable to reach it.
- Then I tap Unlink on the bottom of the mailbox status screen in the Briar app
- unlinking seems to run OK, and there is the progress wheel, and after that there is the dialogue box "Your mailbox has been unlinked.. Next time you have access to yoru ailbox device, please open the Mailbox app and tap the Unlink button to complete the process..." The only option a user has on this dialogue is to tap Got it.
- But if the screen is rotate at this point, BEFORE taping the Got it, then what we see if this:
![20220825_122023](/uploads/598074b5521d980a4cc7d44ff149a39a/20220825_122023.jpg)
Having problems wiht Android Studio which currently get frozen if i try to take a screenshot - so here's the photo of the screen taken with another phone.
If I tap the Back arrow in the top left corner of this blankscreen, then what I see is the mailbox status screen again.... Whereas the unlinking has been already done, so this screen should not be disaplyed again.
If I go back from that screen, I see Briar settings screen, and if I go into mailbox option, I see that the mailbox linking can be done again.
This happens both with do-not-keep-acitivities on and offIvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/2316Usability testing for Mailbox app2023-01-19T13:03:49ZakwizgranUsability testing for Mailbox appAfter setup and pairing (#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use the st...After setup and pairing (#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use the stop, restart and unlink actions.Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2360Mailbox Problem notification causes crash on Android 42023-01-19T13:02:32ZTorsten GroteMailbox Problem notification causes crash on Android 4When Briar can't connect to the mailbox for some time, we show a notification, so the user is aware of this problem.
On Android 4, this needs a special icon. Vector drawables are not supported.When Briar can't connect to the mailbox for some time, we show a notification, so the user is aware of this problem.
On Android 4, this needs a special icon. Vector drawables are not supported.Mailbox: Status UI for Briar appIvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/1483IllegalArgumentException when adding member to private group2023-01-17T11:21:09ZakwizgranIllegalArgumentException when adding member to private group* Android version: 6.0.1
* Phone model: Neffos Y5L (TP801A)
* Briar version: 1.1.1 (9476782)
* User feedback: "Crash while trying to add person to a group."
Stacktrace:
```
java.lang.IllegalArgumentException
at org.briarproject....* Android version: 6.0.1
* Phone model: Neffos Y5L (TP801A)
* Briar version: 1.1.1 (9476782)
* User feedback: "Crash while trying to add person to a group."
Stacktrace:
```
java.lang.IllegalArgumentException
at org.briarproject.briar.privategroup.invitation.SessionParserImpl.parseCreatorSession(SessionParserImpl.java:54)
at org.briarproject.briar.privategroup.invitation.GroupInvitationManagerImpl.isInvitationAllowed(GroupInvitationManagerImpl.java:482)
at org.briarproject.briar.android.privategroup.creation.CreateGroupControllerImpl.isDisabled(CreateGroupControllerImpl.java:121)
at org.briarproject.briar.android.contactselection.ContactSelectorControllerImpl.lambda$loadContacts$0$ContactSelectorControllerImpl(ContactSelectorControllerImpl.java:51)
at org.briarproject.briar.android.contactselection.ContactSelectorControllerImpl$$Lambda$0.run(Unknown Source)
at org.briarproject.briar.android.controller.DbControllerImpl.lambda$runOnDbThread$0$DbControllerImpl(DbControllerImpl.java:35)
at org.briarproject.briar.android.controller.DbControllerImpl$$Lambda$0.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
```Android 1.4Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2407Crash when getting Bluetooth address2023-01-06T16:28:57ZakwizgranCrash when getting Bluetooth address* Android version: 12
* Phone model: Redmi M2004J19C (galahad_global)
* Briar version: 1.4.18 (4797151)
Edited log:
```
12-17 21:55:20.433 I/AbstractBluetoothPlugin: Bluetooth enabled
```
Stacktrace:
```
java.lang.SecurityException: Ne...* Android version: 12
* Phone model: Redmi M2004J19C (galahad_global)
* Briar version: 1.4.18 (4797151)
Edited log:
```
12-17 21:55:20.433 I/AbstractBluetoothPlugin: Bluetooth enabled
```
Stacktrace:
```
java.lang.SecurityException: Need android.permission.BLUETOOTH_CONNECT permission for android.content.AttributionSource@458c6c33: getAddress
at android.os.Parcel.createExceptionOrNull(Parcel.java:2426)
at android.os.Parcel.createException(Parcel.java:2410)
at android.os.Parcel.readException(Parcel.java:2393)
at android.os.Parcel.readException(Parcel.java:2335)
at android.bluetooth.IBluetoothManager$Stub$Proxy.getAddress(IBluetoothManager.java:789)
at android.bluetooth.BluetoothAdapter.getAddress(BluetoothAdapter.java:1290)
at org.briarproject.bramble.util.AndroidUtils.getBluetoothAddressAndMethod(AndroidUtils.java:70)
at org.briarproject.bramble.util.AndroidUtils.getBluetoothAddress(AndroidUtils.java:63)
at org.briarproject.bramble.plugin.bluetooth.AndroidBluetoothPlugin.getBluetoothAddress(AndroidBluetoothPlugin.java:146)
at org.briarproject.bramble.plugin.bluetooth.AbstractBluetoothPlugin.updateProperties(AbstractBluetoothPlugin.java:239)
at org.briarproject.bramble.plugin.bluetooth.AbstractBluetoothPlugin.$r8$lambda$ZdCFKGKAr5elvl5L48zy5sncMIA(Unknown Source:0)
at org.briarproject.bramble.plugin.bluetooth.AbstractBluetoothPlugin$$ExternalSyntheticLambda2.run(Unknown Source:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.BluetoothManagerService.checkPermissionForDataDelivery(BluetoothManagerService.java:3327)
at com.android.server.BluetoothManagerService.checkConnectPermissionForDataDelivery(BluetoothManagerService.java:3345)
at com.android.server.BluetoothManagerService.getAddress(BluetoothManagerService.java:1951)
at android.bluetooth.IBluetoothManager$Stub.onTransact(IBluetoothManager.java:373)
at android.os.Binder.execTransactInternal(Binder.java:1190)
```Android 1.4akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2403Not enough feedback while connecting to Mailbox2022-12-15T13:02:08ZakwizgranNot enough feedback while connecting to Mailbox> Sometimes the connection took a long time while setting up the Mailbox. In these cases, a few participants assumed that they were having problems with either the app or the internet connection. There is not enough feedback for the user...> Sometimes the connection took a long time while setting up the Mailbox. In these cases, a few participants assumed that they were having problems with either the app or the internet connection. There is not enough feedback for the user on this screen.Mailbox: Usability testingIvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/2400Testers didn't realise that text buttons were buttons2022-12-07T16:54:37ZakwizgranTesters didn't realise that text buttons were buttons![buttons-1](/uploads/72a3c9f24adea51777db39592588ef50/buttons-1.png)
> A few participants didn’t notice the “Check connection settings” button. In this case, the “Try again” button grabs the attention and it’s hard to tell that “Check ...![buttons-1](/uploads/72a3c9f24adea51777db39592588ef50/buttons-1.png)
> A few participants didn’t notice the “Check connection settings” button. In this case, the “Try again” button grabs the attention and it’s hard to tell that “Check connection settings” is a button, it looks like a text/link.
![buttons-2](/uploads/965fe0ae27bc7520d2f1b1dc9e32ca31/buttons-2.png)
> The same goes for the screenshot on the right, “Fix problem” and “Unlink” look like links. There is a mismatch in these patterns. Use buttons in every case the user is required to take action and use colors to distinguish their importance.
We're using the Material 2 "text button" style for these buttons. Maybe we should use the "outlined button" style instead.
https://m2.material.io/components/buttons/android#using-buttons
There's also some inconsistency in the colouring: we're using the link colour for the "fix problem" button (like the positive button in dialogs), but the app's primary colour for the "check connection settings" button.Mailbox: Usability testingakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2314Usability testing for mailbox connection issues2022-11-29T14:08:07ZakwizgranUsability testing for mailbox connection issuesTest that users understand Briar's mailbox status screen (#2172) and can use it to check whether the mailbox is reachable. Test that users understand the UX that warns about the mailbox being repeatedly unreachable (#2175), and that they...Test that users understand Briar's mailbox status screen (#2172) and can use it to check whether the mailbox is reachable. Test that users understand the UX that warns about the mailbox being repeatedly unreachable (#2175), and that they can use the troubleshooting wizard to resolve issues (#2309).Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2315Usability testing for mailbox setup and pairing2022-11-29T14:07:35ZakwizgranUsability testing for mailbox setup and pairingTest whether users understand that the Mailbox app needs to be installed on a separate device, and whether they're able to set up the Mailbox app and pair it with Briar.Test whether users understand that the Mailbox app needs to be installed on a separate device, and whether they're able to set up the Mailbox app and pair it with Briar.Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2319Show warning if own mailbox's API version is incompatible2022-11-23T12:10:47ZakwizgranShow warning if own mailbox's API version is incompatibleShow a warning in the mailbox status screen if the API versions supported by our mailbox are incompatible with the versions we support as a client.
The warning could either ask the user to check that Briar and the Mailbox are updated to...Show a warning in the mailbox status screen if the API versions supported by our mailbox are incompatible with the versions we support as a client.
The warning could either ask the user to check that Briar and the Mailbox are updated to the latest version, or if we want to be clever we could work out which one needs to be updated and show an appropriate message.
Depends on #2299Mailbox: Status UI for Briar appTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2297Adapt status screen when Briar is not connected to Tor2022-11-23T11:48:47ZTorsten GroteAdapt status screen when Briar is not connected to TorWe should track the Briar device's connectivity and show an appropriate status maybe similar to the screen that we show when we couldn't reach the mailbox for some time.
Related to #2175We should track the Briar device's connectivity and show an appropriate status maybe similar to the screen that we show when we couldn't reach the mailbox for some time.
Related to #2175Mailbox: Status UI for Briar appTorsten GroteTorsten Grote