briar issueshttps://code.briarproject.org/briar/briar/-/issues2023-05-22T15:36:21Zhttps://code.briarproject.org/briar/briar/-/issues/2391Share a link to the Briar download page via another app2023-05-22T15:36:21ZakwizgranShare a link to the Briar download page via another appDesign and implement a feature for sharing a link to the Briar download page via another app, similar to the way Signal and many other apps do it. This will make it easier for users to encourage their friends to use Briar.
![Screenshot_...Design and implement a feature for sharing a link to the Briar download page via another app, similar to the way Signal and many other apps do it. This will make it easier for users to encourage their friends to use Briar.
![Screenshot_20221123-143159](/uploads/e38a7154c11887a30a50a869c9f63564/Screenshot_20221123-143159.png)Sponsor 6 usability improvementsTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2419Adding Slovak to language menu2023-03-15T12:28:47ZJozef GaalAdding Slovak to language menuI have completed the translation for the Slovak language.
Can you please add Slovak to the language menu for Android app?I have completed the translation for the Slovak language.
Can you please add Slovak to the language menu for Android app?https://code.briarproject.org/briar/briar/-/issues/1230Adding contacts remotely2023-02-23T10:15:44ZakwizgranAdding contacts remotelyUmbrella ticket for adding contacts remotely (sponsor 1, objective 1).Umbrella ticket for adding contacts remotely (sponsor 1, objective 1).Android 1.4https://code.briarproject.org/briar/briar/-/issues/2354After remote wiping - add a small confirmation message that wiping was succes...2022-08-18T09:42:16ZIvanaAfter remote wiping - add a small confirmation message that wiping was successfulAfter remote wiping of the mailbox app, there is no any kind of confirmation message to the user that the wiping was successful.
After discussion in the MM testing channel today, it was concluded that a message may be nice, and maybe t...After remote wiping of the mailbox app, there is no any kind of confirmation message to the user that the wiping was successful.
After discussion in the MM testing channel today, it was concluded that a message may be nice, and maybe the toast message would be the easiest to do.
Reporting this ticket to keep track of this issueMailbox: Unpairingakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2329Translations for TrustIndicatorView trust levels2022-07-14T17:37:37Zjohndoe4221Translations for TrustIndicatorView trust levelsThe `TrustIndicatorView` can display 5 different trust levels:
- ANONYMOUS
- UNVERIFIED
- VERIFIED
- OURSELVES
- default
In order to implement features like #1052 and make the trust levels easier to understand we need descriptive trans...The `TrustIndicatorView` can display 5 different trust levels:
- ANONYMOUS
- UNVERIFIED
- VERIFIED
- OURSELVES
- default
In order to implement features like #1052 and make the trust levels easier to understand we need descriptive translations of trust levels and what they mean for a contact.
I suggest to create the translation keys:
- `contact_trust_level_anonymous`
- `contact_trust_level_unverified`
- `contact_trust_level_verified`
- `contact_trust_level_ourselves`
- `contact_trust_level_default`
The this can be used to show the symbolic trust level and the descriptive text side by side, e.g:
![trust_level_translation](/uploads/f7c70c4002729ffc3fbe5537b654b742/trust_level_translation.png)Android 1.4https://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/-/issues/2175Implement UI for warning user when own mailbox is unreachable2022-05-26T20:10:36ZakwizgranImplement UI for warning user when own mailbox is unreachableWhen we repeatedly fail to connect to our own mailbox, we need some way of grabbing the user's attention and guiding them to the mailbox status page. This could be a system notification or a warning within the app, for example.
Depends ...When we repeatedly fail to connect to our own mailbox, we need some way of grabbing the user's attention and guiding them to the mailbox status page. This could be a system notification or a warning within the app, for example.
Depends on #2174.Mailbox: UnpairingTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1562Improve handling of external intents2022-05-26T15:49:41ZTorsten GroteImprove handling of external intentsUse `ENTRY_ACTIVITY` from !1087 as a central router for external intents:
> Not signed into Briar. The password screen is shown, then after signing in the remote contact activity is shown, as expected. The contact's link field is empty....Use `ENTRY_ACTIVITY` from !1087 as a central router for external intents:
> Not signed into Briar. The password screen is shown, then after signing in the remote contact activity is shown, as expected. The contact's link field is empty. If I use the up button to navigate away from the remote contact screen or the pending contact list, the task is closed. I'd expect to navigate to the contact list when pressing the up button. If I don't use the up button to navigate away, then later reopen Briar from the foreground notification, a second Briar task is created. I assume the same would happen with private message notifications, etc - the issue being that the notification expects us to have a task that can be reused by clearing the stack down to NavDrawerActivity, but the existing task doesn't have that activity in its stack.
There's also some other issues with AddContactActivity to resolve:
> If an instance of AddContactActivity already exists it's brought to the foreground but the link isn't populated (I'm assuming this is because the new intent is delivered without calling onCreate() again).
>
> If I open the remote contact activity via the speed dial, then put Briar into the background via the home button and relaunch via the ongoing notification, the contact list appears as expected. But when I back out, the remote contact activity and another instance of the contact list are underneath.
>
> Similarly, if I open the remote contact activity with a share intent, then press the home button, relaunch via the ongoing notification, and back out of the contact list, the remote contact activity is underneath (but without the second instance of the contact list).
>
> Finally, if I open the remote contact activity with a share intent, then back out or press the up button, the task is cleared. If I relaunch via recent apps, the remote contact activity is shown again. Backing out or pressing the up button clears the task again, so I can't reach the rest of the app!
Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2173Implement UI for unpairing the mailbox2022-05-02T16:06:37ZakwizgranImplement UI for unpairing the mailboxDepends on briar-mailbox#3, briar-mailbox#62, #2164.Depends on briar-mailbox#3, briar-mailbox#62, #2164.Mailbox: UnpairingTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2172Implement status UI for mailbox connection2022-04-29T13:16:37ZakwizgranImplement status UI for mailbox connectionDepends on #2207, #2163, #2171, #2267.Depends on #2207, #2163, #2171, #2267.Mailbox: Status UI for Briar appTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1237Image attachments2022-04-19T11:28:49ZakwizgranImage attachmentsUmbrella ticket for image attachments (sponsor 1, objective 2).Umbrella ticket for image attachments (sponsor 1, objective 2).Android 1.4https://code.briarproject.org/briar/briar/-/issues/1746Expose unread messages count in API's contacts list2022-02-25T15:06:24ZNicoExpose unread messages count in API's contacts listImplementation notes:
* Add variable in `list` function: [ContactControllerImpl/list](https://code.briarproject.org/briar/briar/-/blob/3c63fecb5dad2a3f8174ae40b804679780644a00/briar-headless/src/main/java/org/briarproject/briar/headless/...Implementation notes:
* Add variable in `list` function: [ContactControllerImpl/list](https://code.briarproject.org/briar/briar/-/blob/3c63fecb5dad2a3f8174ae40b804679780644a00/briar-headless/src/main/java/org/briarproject/briar/headless/contact/ContactControllerImpl.kt#L78)
* Get data from [GroupCount](https://code.briarproject.org/briar/briar/-/blob/master/briar-api/src/main/java/org/briarproject/briar/api/client/MessageTracker.java#L79)
Needed for https://code.briarproject.org/briar/briar-gtk/-/issues/29.NicoNicohttps://code.briarproject.org/briar/briar/-/issues/1779Expose message delivery state changes to websockets API2022-02-25T15:06:16ZNicoExpose message delivery state changes to websockets APIWe already indicate whether a message was sent/acked, but we don't inform about updates.
Needed for https://code.briarproject.org/briar/briar-gtk/-/issues/69.We already indicate whether a message was sent/acked, but we don't inform about updates.
Needed for https://code.briarproject.org/briar/briar-gtk/-/issues/69.NicoNicohttps://code.briarproject.org/briar/briar/-/issues/2162Implement UI for pairing Briar with mailbox2022-02-25T14:58:21ZTorsten GroteImplement UI for pairing Briar with mailboxImplement the UI designed in #2161. Depends on #2167.Implement the UI designed in #2161. Depends on #2167.Mailbox: PairingTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1546Support Bluetooth discovery for connecting to contacts2022-01-26T13:50:35ZakwizgranSupport Bluetooth discovery for connecting to contactsOn Android 8+ apps don't have access to the device's own Bluetooth address, so we can't share our address with contacts. When adding contacts we use discovery to work around this (#1147). Users have reported that Bluetooth works when add...On Android 8+ apps don't have access to the device's own Bluetooth address, so we can't share our address with contacts. When adding contacts we use discovery to work around this (#1147). Users have reported that Bluetooth works when adding contacts, but not when subsequently trying to communicate.
Learning our Bluetooth address from contacts would raise some tricky security and privacy issues, such as revealing to existing contacts, by adding a Bluetooth address to our transport properties, that we've just added a contact via Bluetooth.
After adding a contact we could store the contact's address for subsequent connection attempts, but that would only let us connect to contacts who were added via Bluetooth. To let us connect to any nearby contact we need to make the device discoverable and perform discovery.
Making the device temporarily discoverable requires user confirmation each time. Making the device permanently discoverable has privacy implications, and doesn't work on all devices (e.g. the Sony Xperia Tipo). Discovering nearby devices may require a lot of power and may interfere with wifi (#699). BLE discovery uses less power and doesn't require user confirmation, but not all devices can be discovered via BLE (#303).
A possible solution would be to make the device temporarily discoverable, and perform discovery, when the user enables the Bluetooth transport (#185). Then we could provide some way of manually triggering discovery, such as a "nearby contacts" tab with a "scan" button. This would limit the discoverability window, and the battery and interference impact of running discovery, to periods when the user had explicitly shown an interest in connecting to nearby contacts. Confirmation dialogs would only be shown in response to user actions.
This falls short of the goal of effortless connectivity, but it may be the best we can achieve within the constraints of the platform.https://code.briarproject.org/briar/briar/-/issues/1010Share app via Bluetooth2021-08-27T11:42:59ZakwizgranShare app via BluetoothA tester asked for the ability to share the app via Bluetooth. Briar used to support this feature, but we couldn't get it to work reliably.A tester asked for the ability to share the app via Bluetooth. Briar used to support this feature, but we couldn't get it to work reliably.https://code.briarproject.org/briar/briar/-/issues/2104Show startup failure activity immediately instead of showing a notification2021-07-28T10:11:31ZakwizgranShow startup failure activity immediately instead of showing a notificationWhen testing #2061 we found that the startup failure notification wasn't very noticeable, so it appeared that the app had just closed itself. Let's show the startup failure activity immediately and skip the notification.When testing #2061 we found that the startup failure notification wasn't very noticeable, so it appeared that the app had just closed itself. Let's show the startup failure activity immediately and skip the notification.Transfer content securely via SD cards and USB memory sticksIvanaIvana2021-07-31https://code.briarproject.org/briar/briar/-/issues/2009Give instructions during setup for protecting app from Xiaomi/Redmi power man...2021-07-06T10:02:52ZakwizgranGive instructions during setup for protecting app from Xiaomi/Redmi power managementWhile working on #1743 I found that the [Snooze app](https://code.briarproject.org/akwizgran/snooze) was killed when running overnight on the Redmi Note 7. [Locking the app to the recent apps list](https://code.briarproject.org/briar/bri...While working on #1743 I found that the [Snooze app](https://code.briarproject.org/akwizgran/snooze) was killed when running overnight on the Redmi Note 7. [Locking the app to the recent apps list](https://code.briarproject.org/briar/briar/-/issues/1743#note_49341) prevented this from happening. We should recommend this during account setup, as we do for Huawei's protected apps and app launch settings.
(The user can also [change the app's background setting to "No restrictions"](https://code.briarproject.org/briar/briar/-/issues/1743#note_49269), which is recommended in various places but didn't help in the case of the Snooze app.)Adapt to changes in the Android platformIvanaIvana2021-04-30https://code.briarproject.org/briar/briar/-/issues/1862Show a bomb icon on the send button when the self-destruct timer is enabled2021-07-06T09:56:55ZakwizgranShow a bomb icon on the send button when the self-destruct timer is enabledSubtask of #804.Subtask of #804.Self-destructing messagesTorsten GroteTorsten Grote2021-01-31https://code.briarproject.org/briar/briar/-/issues/1837Conversation settings screen2021-04-13T11:49:41ZakwizgranConversation settings screenAdd a per-conversation settings screen, accessible via the conversation screen's menu.
The screen will initially have one setting: a switch that enables or disables self-destructing messages, with an explanation of the timer duration an...Add a per-conversation settings screen, accessible via the conversation screen's menu.
The screen will initially have one setting: a switch that enables or disables self-destructing messages, with an explanation of the timer duration and the fact that changes made by the contact will be followed automatically.
Subtask of #804Self-destructing messagesSebastianSebastian2021-01-31