briar issueshttps://code.briarproject.org/briar/briar/-/issues2022-01-06T14:43:23Zhttps://code.briarproject.org/briar/briar/-/issues/1214Don't allow introductions if introducee doesn't support introduction client2022-01-06T14:43:23ZakwizgranDon't allow introductions if introducee doesn't support introduction clientIf the ClientVersioningManager says a contact doesn't support the same major version of the introduction client as us, don't allow an introduction request to be sent.If the ClientVersioningManager says a contact doesn't support the same major version of the introduction client as us, don't allow an introduction request to be sent.https://code.briarproject.org/briar/briar/-/issues/45Reduce mobile data consumption2021-12-13T14:17:30ZakwizgranReduce mobile data consumptionBriar uses a lot of bandwidth considering the small amount of data it transfers. The most likely culprit is the Tor plugin, which maintains circuits to several introduction points and regularly tries to build circuits to contacts' introd...Briar uses a lot of bandwidth considering the small amount of data it transfers. The most likely culprit is the Tor plugin, which maintains circuits to several introduction points and regularly tries to build circuits to contacts' introduction points. Can we reduce the amount of bandwidth it uses?
~~Ricochet has a nice solution to this: each time we (re)connect to Tor, try to connect to our peers, and while we remain connected, expect them to connect to us rather than vice versa.~~
~~https://github.com/ricochet-im/ricochet/issues/68~~
~~There may be a race condition, however, if our hidden service doesn't become reachable until after we've polled our contacts' services. Can we poll our own hidden service to check its reachability?~~
~~Another possible culprit is the LAN plugin, which will bind to an interface with a non-local address if no local address is available. This is meant to enable the plugin to work on internal networks that use non-local addresses, such as UCL -- but it may also lead to observable connections across the WAN, so perhaps we should change it.~~https://code.briarproject.org/briar/briar/-/issues/1943Warn the user when the last shutdown wasn't clean2021-07-26T10:31:11ZakwizgranWarn the user when the last shutdown wasn't cleanShow some kind of warning (a notification, or something in the main UI when signing in) when the last shutdown wasn't clean (see #57).
We may also want to know whether the dirty shutdown happened before or after the last reboot.
Subtas...Show some kind of warning (a notification, or something in the main UI when signing in) when the last shutdown wasn't clean (see #57).
We may also want to know whether the dirty shutdown happened before or after the last reboot.
Subtask of #1824.https://code.briarproject.org/briar/briar/-/issues/20Make messages searchable2020-11-21T20:32:52ZakwizgranMake messages searchableWhen a message is fully reassembled, extract a list of words from the message body and place them in a separate DB column, which can be full-text indexed.When a message is fully reassembled, extract a list of words from the message body and place them in a separate DB column, which can be full-text indexed.https://code.briarproject.org/briar/briar/-/issues/65Two-factor authentication2020-11-21T20:09:51ZakwizgranTwo-factor authenticationAdd optional two-factor authentication to the Android app via NFC -- to log in, the user must tap a particular NFC tag as well as entering their password. Data from the NFC tag is incorporated into the PBKDF. This prevents brute force pa...Add optional two-factor authentication to the Android app via NFC -- to log in, the user must tap a particular NFC tag as well as entering their password. Data from the NFC tag is incorporated into the PBKDF. This prevents brute force password cracking if the Android device is captured but the NFC tag is not.
NFC tags may be readable at long distances, so this won't prevent password cracking by an attacker who can read the NFC tag in advance.
This is weaker than 2FA protocols based on public keys, such as U2F, but those require a trusted server that can deny access to the account if the signature doesn't match.https://code.briarproject.org/briar/briar/-/issues/98Show how many messages/posts are waiting to be sent2020-11-21T19:47:59ZakwizgranShow how many messages/posts are waiting to be sentThis might involve creating some kind of outbox on the dashboard that contains messages and posts that are waiting to be sent, with a badge similar to the badges for newly received messages and posts.This might involve creating some kind of outbox on the dashboard that contains messages and posts that are waiting to be sent, with a badge similar to the badges for newly received messages and posts.https://code.briarproject.org/briar/briar/-/issues/289Improve UX for notifications2020-11-21T19:26:17ZakwizgranImprove UX for notificationshttps://code.briarproject.org/briar/briar/-/issues/349Explain Panic Button settings better2020-11-21T19:04:18ZakwizgranExplain Panic Button settings betterSome users discovered the Panic Button settings and were confused by them.Some users discovered the Panic Button settings and were confused by them.https://code.briarproject.org/briar/briar/-/issues/457Personal detail screen / My profile2020-11-21T18:54:24ZMegaloxPersonal detail screen / My profileWe need some screen to ~~edit nick names, create additional identities,~~ edit avatars, ~~select identities~~, sign out and display the users single feed. Could even be a navigation target in the drawer.We need some screen to ~~edit nick names, create additional identities,~~ edit avatars, ~~select identities~~, sign out and display the users single feed. Could even be a navigation target in the drawer.https://code.briarproject.org/briar/briar/-/issues/469Identify errors and improve error messages2020-11-21T18:45:01ZMegaloxIdentify errors and improve error messagesAt the moment we implement a standard error message (#380). We could improve the UX with distinct error messages. If we can identify the specific nature of an error we can tell the user (1) what went wrong and (2) what she can do about i...At the moment we implement a standard error message (#380). We could improve the UX with distinct error messages. If we can identify the specific nature of an error we can tell the user (1) what went wrong and (2) what she can do about it. We could also define what kind of errors trigger special behaviour like sending error reports to the developer.https://code.briarproject.org/briar/briar/-/issues/503Deliver private messages in order2020-11-21T18:37:21ZakwizgranDeliver private messages in orderTo reduce confusion when private messages arrive asynchronously, deliver them in the order they were sent, either by using a message queue or by making each message depend on the previous one.To reduce confusion when private messages arrive asynchronously, deliver them in the order they were sent, either by using a message queue or by making each message depend on the previous one.https://code.briarproject.org/briar/briar/-/issues/508Don't warn about leaving forum unless the user has shared it2020-11-21T18:35:19ZakwizgranDon't warn about leaving forum unless the user has shared itWhen the user leaves a forum we ask for confirmation, with a warning that any contacts the user has shared the forum with may stop receiving updates if she leaves. This warning should only be shown if the user has shared the forumWhen the user leaves a forum we ask for confirmation, with a warning that any contacts the user has shared the forum with may stop receiving updates if she leaves. This warning should only be shown if the user has shared the forumhttps://code.briarproject.org/briar/briar/-/issues/537Create back stack when opening activities from notifications2020-11-21T17:51:33ZakwizgranCreate back stack when opening activities from notificationsWhen opening an activity in response to the user touching an incoming message notification, the back stack should be populated. Currently the activity is stacked above any previously visited activities, so backing out of it may lead to t...When opening an activity in response to the user touching an incoming message notification, the back stack should be populated. Currently the activity is stacked above any previously visited activities, so backing out of it may lead to the home screen or an unrelated activity.https://code.briarproject.org/briar/briar/-/issues/645UX for groups that are no longer synced with any contacts2020-11-21T17:04:16ZakwizgranUX for groups that are no longer synced with any contactsDecide how to display blogs, forums and private groups that are no longer synced with any contacts (thus no messages will be sent or received).Decide how to display blogs, forums and private groups that are no longer synced with any contacts (thus no messages will be sent or received).https://code.briarproject.org/briar/briar/-/issues/716Warn when entered text is too long2020-11-21T16:38:26ZakwizgranWarn when entered text is too longWe do this for forum posts, we should also do it for:
* Private messages
* Introduction messages
* Invitation messages
* Blog posts
* Blog commentsWe do this for forum posts, we should also do it for:
* Private messages
* Introduction messages
* Invitation messages
* Blog posts
* Blog commentshttps://code.briarproject.org/briar/briar/-/issues/717Up navigation2020-11-21T16:38:01ZakwizgranUp navigationWe're currently treating the "up" action in the action bar as equivalent to the "back" action. Instead it should navigate to the current activity's parent.
https://developer.android.com/training/implementing-navigation/ancestral.htmlWe're currently treating the "up" action in the action bar as equivalent to the "back" action. Instead it should navigate to the current activity's parent.
https://developer.android.com/training/implementing-navigation/ancestral.htmlhttps://code.briarproject.org/briar/briar/-/issues/721UX design for showing client protocol errors in the UI2020-11-21T16:37:13ZakwizgranUX design for showing client protocol errors in the UIIf we receive an invalid sequence of messages in a client protocol, it may not be possible to continue with the protocol. If this makes certain actions unavailable to the user, the UI should inform the user about that in some way.
We sh...If we receive an invalid sequence of messages in a client protocol, it may not be possible to continue with the protocol. If this makes certain actions unavailable to the user, the UI should inform the user about that in some way.
We should go through the relevant actions and decide on appropriate UX for each case.https://code.briarproject.org/briar/briar/-/issues/792Tester could not find a private group they'd been invited to2020-11-21T12:57:05ZTorsten GroteTester could not find a private group they'd been invited toDuring a testing session (#788), a user was confused about where to find the private group they just had been invited to. They expected to find the group in the contact list screen. The group agreed that this is where they would expect t...During a testing session (#788), a user was confused about where to find the private group they just had been invited to. They expected to find the group in the contact list screen. The group agreed that this is where they would expect to find groups, because they know this from other messengers that have a list of conversation that include private conversations and group conversations in one screen.
The list of contacts could be made available elsewhere.https://code.briarproject.org/briar/briar/-/issues/818UX design for errors that interrupt the user's workflow2020-11-21T12:44:25ZTorsten GroteUX design for errors that interrupt the user's workflowThis ticket is for creating the UX design for when errors occur that interrupt the user's workflow and don't have any corrective action.
For example, you open your private conversation with someone, but it just closes again (or shows an...This ticket is for creating the UX design for when errors occur that interrupt the user's workflow and don't have any corrective action.
For example, you open your private conversation with someone, but it just closes again (or shows an error message) because an error occurred while loading it. You open a private group, but when finding out whether it is dissolved an error occurs, so it stays in the disabled state by default. Or you are in a multi-step process and an error prevents you from reaching the next step like when creating a private group fails and you are not getting to the next step of inviting contacts to it.
Errors while loading blog posts, private message, forum posts, contacts, basically anything in lists falls into this category.
Subticket of #469.https://code.briarproject.org/briar/briar/-/issues/819UX design for errors that don't interrupt the user's workflow2020-11-21T12:43:46ZTorsten GroteUX design for errors that don't interrupt the user's workflowThis ticket is for creating the UX design when errors occur that don't interrupt the user's workflow.
Imagine you share a forum with someone or invite two contacts to each other. These operations might fail, but since the invitation scr...This ticket is for creating the UX design when errors occur that don't interrupt the user's workflow.
Imagine you share a forum with someone or invite two contacts to each other. These operations might fail, but since the invitation screen closes anyway, it does not really interrupt your work-flow anymore. Another possible error might happen when a title of the blog or the number of online users is loaded to be shown in the action bar. There will just be the default title maybe "Blog" and the user might not even notice, but it is a bug we might want to know about. Another example is when we fail to store the fact that we already showed you the onboarding and then show it to you again.
So more general, the kinds of errors I imagine to fall in this category are:
* user actions that are not completed, but don't interrupt the workflow because it finishes at this point anyway
* loading of non-essential information
Subticket of #469.