briar issueshttps://code.briarproject.org/groups/briar/-/issues2022-06-14T12:29:48Zhttps://code.briarproject.org/briar/briar/-/issues/2326Briar's mailbox status screen should fetch the mailbox's supported API versions2022-06-14T12:29:48ZakwizgranBriar's mailbox status screen should fetch the mailbox's supported API versionsBriar's mailbox status screen uses the `status` API endpoint for its connectivity check. Let's use the `versions` endpoint instead, so that if we've warned the user that Briar and the Mailbox are using incompatible API versions, and the ...Briar's mailbox status screen uses the `status` API endpoint for its connectivity check. Let's use the `versions` endpoint instead, so that if we've warned the user that Briar and the Mailbox are using incompatible API versions, and the user has upgraded one of the apps to fix the issue, the user can use the "check connection" button in the status screen to check that the issue has been fixed.
(This is specifically needed for the case where the user has upgraded the Mailbox, because in the case where the user has upgraded Briar, Briar should automatically check the mailbox's API versions when it comes back online after upgrading.)Mailbox: Status UI for Briar appTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/126Potentially display special screen on status screen when last connection from...2022-07-13T11:01:42ZSebastianPotentially display special screen on status screen when last connection from owner was long agoMailbox: Status UI for Mailbox apphttps://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-mailbox/-/issues/122Do not kill me screen shown again (empty) if activity gets killed2023-01-19T13:04:14ZakwizgranDo not kill me screen shown again (empty) if activity gets killedIf no battery settings need to be changed (eg Android < 6, or stock Android >= 6 with battery optimisations already disabled) then we should skip the battery settings screen rather than showing the graphic and the continue button with no...If no battery settings need to be changed (eg Android < 6, or stock Android >= 6 with battery optimisations already disabled) then we should skip the battery settings screen rather than showing the graphic and the continue button with no other content.
![Screenshot_20220512_134501](/uploads/55c24730f28f15e821a879c78f213396/Screenshot_20220512_134501.png)Mailbox: First runhttps://code.briarproject.org/briar/briar-mailbox/-/issues/118Tapping notification creates duplicate instance of status screen2022-07-13T11:39:48ZakwizgranTapping notification creates duplicate instance of status screenSteps to reproduce:
* Start the Mailbox app and pair it with Briar
* While the status screen is in the foreground, pull down the notification drawer and tap the Mailbox app's ongoing notification
* Close the notification drawer
* Tap the...Steps to reproduce:
* Start the Mailbox app and pair it with Briar
* While the status screen is in the foreground, pull down the notification drawer and tap the Mailbox app's ongoing notification
* Close the notification drawer
* Tap the Stop button in the status screen
* Expected: The app closes
* Actual:
* The status screen closes, revealing another status screen underneath
* The stop button in the second status screen does nothingMailbox: Status UI for Mailbox appSebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/117Status screen should warn when device is offline2022-07-13T11:08:17ZakwizgranStatus screen should warn when device is offlineAfter setup is complete, the status screen should monitor connectivity changes and show a warning when the device is offline.
The text used for the warning should be synced with the text in Briar's troubleshooting wizard (briar#2309).After setup is complete, the status screen should monitor connectivity changes and show a warning when the device is offline.
The text used for the warning should be synced with the text in Briar's troubleshooting wizard (briar#2309).Mailbox: Status UI for Mailbox apphttps://code.briarproject.org/briar/briar-mailbox/-/issues/116Usability testing for Mailbox app2022-11-30T11:05:08ZakwizgranUsability testing for Mailbox appAfter setup and pairing (briar#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 t...After setup and pairing (briar#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 testingRenata GegajRenata Gegajhttps://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/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/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-mailbox/-/issues/114Mailbox hangs at "Starting services" when relaunching after remote wipe2022-08-01T13:44:21ZakwizgranMailbox hangs at "Starting services" when relaunching after remote wipeSteps to reproduce:
* Pair mailbox-android with Briar
* Use !1637 or !1639 to wipe the mailbox remotely
* Use the back button to clear the mailbox UI (workaround for #113)
* The log shows that **the process doesn't exit**
* Relaunch the ...Steps to reproduce:
* Pair mailbox-android with Briar
* Use !1637 or !1639 to wipe the mailbox remotely
* Use the back button to clear the mailbox UI (workaround for #113)
* The log shows that **the process doesn't exit**
* Relaunch the mailbox app
* As expected, the onboarding screens are shown again
* After going through onboarding, "Starting services" is shown
* The log shows that the lifecycle hasn't been restarted, so no services are started and the UI remains in the "Starting services" state indefinitelyMailbox: UnpairingSebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/113Clear UI when mailbox is wiped remotely2022-08-01T13:44:01ZakwizgranClear UI when mailbox is wiped remotelyWhen the mailbox is wiped remotely by Briar we should clear the UI (perhaps using something like Briar's HideUiActivity). Currently the UI stays visible. Tapping the home button and then relaunching the app shows the status screen with "...When the mailbox is wiped remotely by Briar we should clear the UI (perhaps using something like Briar's HideUiActivity). Currently the UI stays visible. Tapping the home button and then relaunching the app shows the status screen with "Mailbox is running" (on Android 5 at least - on Android 12 I think the home button would behave differently).Mailbox: UnpairingSebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2312Briar fails to start if clock was unreasonably wrong on first run2022-05-11T14:23:37ZakwizgranBriar fails to start if clock was unreasonably wrong on first runSteps to reproduce:
* If a Briar account exists, delete it
* Set the system clock to a date before 1 Jan 2021
* Launch Briar and create an account
* Briar will show the startup failure screen due to the clock being wrong
* Set the system...Steps to reproduce:
* If a Briar account exists, delete it
* Set the system clock to a date before 1 Jan 2021
* Launch Briar and create an account
* Briar will show the startup failure screen due to the clock being wrong
* Set the system clock to the right date
* Launch Briar again
* The password screen will be shown
* Enter the password
* Briar will show the startup failure screen, saying the database is corrupt
Log snippet from the second run (after correcting the clock):
```
2022-04-27 08:54:55.872 22506-22542/org.briarproject.briar.android.debug I/H2Database: Contents of account directory before opening DB:
2022-04-27 08:54:55.872 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug 4096
2022-04-27 08:54:55.872 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug/lib 4096
2022-04-27 08:54:55.882 22506-22542/org.briarproject.briar.android.debug I/H2Database: F /data/data/org.briarproject.briar.android.debug/lib/libobfs4proxy.so 6481961
2022-04-27 08:54:55.882 22506-22542/org.briarproject.briar.android.debug I/H2Database: F /data/data/org.briarproject.briar.android.debug/lib/libtor.so 5957620
2022-04-27 08:54:55.882 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug/cache 4096
2022-04-27 08:54:55.882 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug/cache/com.android.renderscript.cache 4096
2022-04-27 08:54:55.882 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug/shared_prefs 4096
2022-04-27 08:54:55.892 22506-22542/org.briarproject.briar.android.debug I/H2Database: F /data/data/org.briarproject.briar.android.debug/shared_prefs/org.briarproject.briar.android.debug_preferences.xml 115
2022-04-27 08:54:55.892 22506-22542/org.briarproject.briar.android.debug I/H2Database: F /data/data/org.briarproject.briar.android.debug/shared_prefs/_has_set_default_values.xml 126
2022-04-27 08:54:55.892 22506-22542/org.briarproject.briar.android.debug I/H2Database: F /data/data/org.briarproject.briar.android.debug/shared_prefs/db.xml 65
2022-04-27 08:54:55.892 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug/app_key 4096
2022-04-27 08:54:55.892 22506-22542/org.briarproject.briar.android.debug I/H2Database: F /data/data/org.briarproject.briar.android.debug/app_key/db.key.bak 218
2022-04-27 08:54:55.892 22506-22542/org.briarproject.briar.android.debug I/H2Database: F /data/data/org.briarproject.briar.android.debug/app_key/db.key 218
2022-04-27 08:54:55.902 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug/app_db 4096
2022-04-27 08:54:55.902 22506-22542/org.briarproject.briar.android.debug I/H2Database: D /data/data/org.briarproject.briar.android.debug/app_tor 4096
2022-04-27 08:54:55.902 22506-22542/org.briarproject.briar.android.debug I/H2Database: Reopening DB: false
```
Stacktrace:
```
2022-04-27 08:55:00.046 22506-22542/org.briarproject.briar.android.debug W/LifecycleManagerImpl: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.bramble.identity.IdentityManagerImpl.loadIdentityWithKeyPair(IdentityManagerImpl.java:159)
at org.briarproject.bramble.identity.IdentityManagerImpl.getCachedIdentity(IdentityManagerImpl.java:147)
at org.briarproject.bramble.identity.IdentityManagerImpl.onDatabaseOpened(IdentityManagerImpl.java:95)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.lambda$startServices$0(LifecycleManagerImpl.java:129)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.$r8$lambda$R30tTgoiROvN8ROsUbPogFK9rjY(LifecycleManagerImpl.java)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl$$ExternalSyntheticLambda0.run(Unknown Source)
at org.briarproject.bramble.db.DatabaseComponentImpl.transaction(DatabaseComponentImpl.java:200)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.java:123)
at org.briarproject.briar.android.BriarService.lambda$onCreate$0(BriarService.java:141)
at org.briarproject.briar.android.BriarService.$r8$lambda$HDU85pNkqbcIvjlH9WM8JDDv2bo(BriarService.java)
at org.briarproject.briar.android.BriarService$$ExternalSyntheticLambda5.run(Unknown Source)
at org.briarproject.bramble.system.AndroidWakeLockManagerImpl.lambda$executeWakefully$1(AndroidWakeLockManagerImpl.java:95)
at org.briarproject.bramble.system.AndroidWakeLockManagerImpl.$r8$lambda$HU3N-m0ADiLNH1gKAKkCiyTw2fM(AndroidWakeLockManagerImpl.java)
at org.briarproject.bramble.system.AndroidWakeLockManagerImpl$$ExternalSyntheticLambda0.run(Unknown Source)
at java.lang.Thread.run(Thread.java:856)
```
It looks like the DB key was saved on the first run but the DB wasn't created. On the second run we assumed an identity had already been created so we didn't store one, and then we got an exception when trying to load an identity from the newly created DB.Android 1.4https://code.briarproject.org/briar/briar-mailbox/-/issues/107Crash when creating database on Android 42022-07-11T15:08:52ZakwizgranCrash when creating database on Android 4* Android version: 4.2.2
* Phone model: Huawei Ascend Y330
Stacktrace:
```
2022-04-27 12:54:22.506 3426-3618/org.briarproject.mailbox E/AndroidRuntime: FATAL EXCEPTION: Thread-370
org.briarproject.mailbox.core.db.DbException: org.h2...* Android version: 4.2.2
* Phone model: Huawei Ascend Y330
Stacktrace:
```
2022-04-27 12:54:22.506 3426-3618/org.briarproject.mailbox E/AndroidRuntime: FATAL EXCEPTION: Thread-370
org.briarproject.mailbox.core.db.DbException: org.h2.jdbc.JdbcSQLNonTransientException: General error: "java.lang.NoClassDefFoundError: java.nio.charset.StandardCharsets" [50000-200]
at org.briarproject.mailbox.core.db.JdbcDatabase.startTransaction(JdbcDatabase.kt:261)
at org.briarproject.mailbox.core.db.JdbcDatabase.startTransaction(JdbcDatabase.kt:235)
at org.briarproject.mailbox.core.db.JdbcDatabase.transaction(JdbcDatabase.kt:669)
at org.briarproject.mailbox.core.db.JdbcDatabase.read(JdbcDatabase.kt:657)
at org.briarproject.mailbox.core.db.H2Database.databaseHasSettingsTable(H2Database.kt:71)
at org.briarproject.mailbox.core.db.JdbcDatabase.open$mailbox_core(JdbcDatabase.kt:120)
at org.briarproject.mailbox.core.db.H2Database.open(H2Database.kt:64)
at org.briarproject.mailbox.core.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.kt:115)
at org.briarproject.mailbox.android.MailboxService$onCreate$1.invoke(MailboxService.kt:103)
at org.briarproject.mailbox.android.MailboxService$onCreate$1.invoke(MailboxService.kt:102)
at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30)
Caused by: org.h2.jdbc.JdbcSQLNonTransientException: General error: "java.lang.NoClassDefFoundError: java.nio.charset.StandardCharsets" [50000-200]
at org.h2.engine.Database.openDatabase(Database.java:333)
at org.h2.engine.Database.<init>(Database.java:301)
at org.h2.engine.Engine.openSession(Engine.java:74)
at org.h2.engine.Engine.openSession(Engine.java:192)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:171)
at org.h2.engine.Engine.createSession(Engine.java:166)
at org.h2.engine.Engine.createSession(Engine.java:29)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:340)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:173)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:152)
at org.h2.Driver.connect(Driver.java:69)
at java.sql.DriverManager.getConnection(DriverManager.java:175)
at org.briarproject.mailbox.core.db.H2Database.createConnection(H2Database.kt:115)
at org.briarproject.mailbox.core.db.JdbcDatabase.startTransaction(JdbcDatabase.kt:254)
at org.briarproject.mailbox.core.db.JdbcDatabase.startTransaction(JdbcDatabase.kt:235)
at org.briarproject.mailbox.core.db.JdbcDatabase.transaction(JdbcDatabase.kt:669)
at org.briarproject.mailbox.core.db.JdbcDatabase.read(JdbcDatabase.kt:657)
at org.briarproject.mailbox.core.db.H2Database.databaseHasSettingsTable(H2Database.kt:71)
at org.briarproject.mailbox.core.db.JdbcDatabase.open$mailbox_core(JdbcDatabase.kt:120)
at org.briarproject.mailbox.core.db.H2Database.open(H2Database.kt:64)
at org.briarproject.mailbox.core.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.kt:115)
at org.briarproject.mailbox.android.MailboxService$onCreate$1.invoke(MailboxService.kt:103)
at org.briarproject.mailbox.android.MailboxService$onCreate$1.invoke(MailboxService.kt:102)
at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30)
Caused by: java.lang.NoClassDefFoundError: java.nio.charset.StandardCharsets
at org.h2.mvstore.MVStore.writeStoreHeader(MVStore.java:1096)
at org.h2.mvstore.MVStore.<init>(MVStore.java:390)
at org.h2.mvstore.MVStore$Builder.open(MVStore.java:3579)
at org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:170)
at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:103)
at org.h2.engine.Database.getPageStore(Database.java:2659)
at org.h2.engine.Database.open(Database.java:675)
at org.h2.engine.Database.openDatabase(Database.java:307)
at org.h2.engine.Database.<init>(Database.java:301)
at org.h2.engine.Engine.openSession(Engine.java:74)
at org.h2.engine.Engine.openSession(Engine.java:192)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:171)
at org.h2.engine.Engine.createSession(Engine.java:166)
at org.h2.engine.Engine.createSession(Engine.java:29)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:340)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:173)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:152)
at org.h2.Driver.connect(Driver.java:69)
at java.sql.DriverManager.getConnection(DriverManager.java:175)
at org.briarproject.mailbox.core.db.H2Database.createConnection(H2Database.kt:115)
at org.briarproject.mailbox.core.db.JdbcDatabase.startTransaction(JdbcDatabase.kt:254)
at org.briarproject.mailbox.core.db.JdbcDatabase.startTransaction(JdbcDatabase.kt:235)
at org.briarproject.mailbox.core.db.JdbcDatabase.transaction(JdbcDatabase.kt:669)
at org.briarproject.mailbox.core.db.JdbcDatabase.read(JdbcDatabase.kt:657)
at org.briarproject.mailbox.core.db.H2Database.databaseHasSettingsTable(H2Database.kt:71)
at org.briarproject.mailbox.core.db.JdbcDatabase.open$mailbox_core(JdbcDatabase.kt:120)
at org.briarproject.mailbox.core.db.H2Database.open(H2Database.kt:64)
at org.briarproject.mailbox.core.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.kt:115)
at org.briarproject.mailbox.android.MailboxService$onCreate$1.invoke(MailboxService.kt:103)
at org.briarproject.mailbox.android.MailboxService$onCreate$1.invoke(MailboxService.kt:102)
at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30)
```
Looks like the crash ultimately comes from H2's MVStore#writeStoreHeader():
```
byte[] bytes = buff.toString().getBytes(StandardCharsets.ISO_8859_1);
```
StandardCharsets was added in Java 7, so it won't be available on Android < 7. Looks like we might need to downgrade H2 to the same version we're using for Briar.
Incidentally there's a Soup Nazi reference in the StandardCharsets source. :-)Mailbox: Databaseakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2311Remind user to wipe mailbox if it's unreachable when unpairing2022-05-02T16:06:29ZakwizgranRemind user to wipe mailbox if it's unreachable when unpairingIf we fail to tell the mailbox to wipe itself when unpairing, remind the user that they should wipe the mailbox next time they have access to it.If we fail to tell the mailbox to wipe itself when unpairing, remind the user that they should wipe the mailbox next time they have access to it.Mailbox: UnpairingTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/105Limit the size of uploaded files2022-07-13T11:13:19ZakwizgranLimit the size of uploaded filesThe mailbox shouldn't allow clients to upload files larger than 1 MiB.The mailbox shouldn't allow clients to upload files larger than 1 MiB.Mailbox: File management APITorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-desktop/-/issues/342Briar Desktop Usability Audit2022-05-03T14:59:57ZElio Qoshielio@ura.designBriar Desktop Usability AuditWe worked with Kay from Blickwinkel Digital, an external UX expert group who tested Briar Desktop as part of their Usability Audit according to ISO 9241-110.They have been immensely helpful in identifying common usability issues on the B...We worked with Kay from Blickwinkel Digital, an external UX expert group who tested Briar Desktop as part of their Usability Audit according to ISO 9241-110.They have been immensely helpful in identifying common usability issues on the Briar Desktop app. As someone without prior experiences with Briar, their insights were refreshing and much needed after we ourselves have worked with Briar over 4 years. As part of this collaboration we produced a PDF presentation including over 17 UX issues identified by Blickwinkel (including commentary from our side for further context) as well additional 8 issues identified by our Lead UX Researcher, Renata according to the UX Heuristics framework by Nielsen Norman Group.
![image](/uploads/4e87ec2fe74911cb7fd63a8ae77d58fb/image.png)
In a similar manner to the accessibility audit, the usability audit includes an issue description, an annotated screenshot, a recommendation, the severity as well as the criteria/heuristics being violated in this case.
Majority of the review has been conducted on a Mac M1 (with apparently an older version of Briar Desktop), though most things apply on both versions.
Presentation:
https://docs.google.com/presentation/d/1tDmSPzW26luF3ySaGUwbNelhvkRwXAFJ/edit?usp=sharing&ouid=100104676494073512080&rtpof=true&sd=true
[Briar_Desktop_Usability_Audit.pdf](/uploads/78097e2dcba23fe82e2fd0384041ad14/Briar_Desktop_Usability_Audit.pdf)Desktop 1.0.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/341Briar Desktop Accessibility Audit (Ubuntu+Mac)2023-01-09T21:39:55ZElio Qoshielio@ura.designBriar Desktop Accessibility Audit (Ubuntu+Mac)The accessibility audit supported by OTF has been completed, following is a detailed spreadsheet report with screenshots and recommendations on how to address over 70 accessibility issues. The accessibility audit has been conducted with ...The accessibility audit supported by OTF has been completed, following is a detailed spreadsheet report with screenshots and recommendations on how to address over 70 accessibility issues. The accessibility audit has been conducted with keyboard as well as screen readers (Voice Over on macOS and Orca on Ubuntu).
https://docs.google.com/spreadsheets/d/17G_qYlHzXJJwyc7d2y6vXC-qyDA2ia-dqbBpuQXnteE/edit?usp=sharing
Each issue includes various details for triaging and provided required context:
- Issue Number
- Environment (Operating System details)
- Page Name (which screen of the application this issue appears in)
- Issues/Summary (issue description)
- Actual Result (the behavior of the issue)
- Expected Result (how the experience should behave ideally)
- User Impact (the repercussions of the issue)
- Screen Images (annotated screenshot)
- Recommendation (how to solve this issue)
- WCAG Guideline (link on the WCAG chapter the issue violates)
- Severity ( how severe this issue is)
[Briar_Desktop_Accessibility_Report.ods](/uploads/5360e4fc7f43fe4336d1e29345e2d628/Briar_Desktop_Accessibility_Report.ods)[Screenshots.zip](/uploads/b180dda7e0374769cb8936cca798c546/Screenshots.zip)Desktop 1.0.0SebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2309Troubleshooting wizard for own mailbox being unreachable2022-05-18T17:02:05ZakwizgranTroubleshooting wizard for own mailbox being unreachableDesign and implement a troubleshooting wizard to guide the user through the steps of diagnosing why their own mailbox is unreachable and fixing the problem.
The wizard will be reachable from the mailbox status page (#2172) when automati...Design and implement a troubleshooting wizard to guide the user through the steps of diagnosing why their own mailbox is unreachable and fixing the problem.
The wizard will be reachable from the mailbox status page (#2172) when automatic reachability checks repeatedly fail, or when the user triggers a manual reachability check which fails.
The UI for warning the user that their mailbox is unreachable (#2175) will guide the user to the status page where they'll be able to use the wizard.Mailbox: Status UI for Briar appTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2302Update contacts about change in mailbox versions that our mailbox (server) su...2022-08-16T13:49:46ZDaniel LublinUpdate contacts about change in mailbox versions that our mailbox (server) supports
When we connect to the Mailbox, we should get the fresh list of mailbox api versions that it supports. Then check it against the latest mailbox properties update sent to each contact, and send a new update if the serverSupports doesn't ...
When we connect to the Mailbox, we should get the fresh list of mailbox api versions that it supports. Then check it against the latest mailbox properties update sent to each contact, and send a new update if the serverSupports doesn't match.
Depends on https://code.briarproject.org/briar/briar/-/issues/2299 https://code.briarproject.org/briar/briar/-/issues/2261 https://code.briarproject.org/briar/briar/-/issues/2290Mailbox: Sync mailbox propertiesakwizgranakwizgran