briar issueshttps://code.briarproject.org/groups/briar/-/issues2020-11-19T15:51:59Zhttps://code.briarproject.org/briar/briar/-/issues/886New workflow for adding contacts via QR codes2020-11-19T15:51:59ZakwizgranNew workflow for adding contacts via QR codesTesters have had trouble with the QR code workflow in the past. Some testers expected to be able to add multiple contacts by scanning a series of QR codes. We can get closer to meeting this expectation by dividing the workflow into two p...Testers have had trouble with the QR code workflow in the past. Some testers expected to be able to add multiple contacts by scanning a series of QR codes. We can get closer to meeting this expectation by dividing the workflow into two phases: scanning and showing.
In the scanning phase, the user scans any number of QR codes. In the background, her device connects to each scanned device and delivers a contact request. If the scanned device has already sent a contact request to the scanning device, the devices proceed with contact exchange.
In the showing phase, the user's device shows a QR code for other users to scan. A snackbar shows incoming contact requests. Touching the snackbar opens a list of contact requests sent, received and completed. Received requests are marked "scan to confirm". Touching a received request opens the scanning screen.
Pending requests are also indicated by a snackbar at the bottom of the contact list, so the user can leave the contact exchange feature to deal with other tasks, then come back and continue adding contacts.
Separating the initial contact request from the subsequent contact exchange allows users to scan each other's codes in any order. The list of contact requests allows them to keep track of which contacts need to be confirmed.https://code.briarproject.org/briar/briar/-/issues/880Forum topics2020-11-19T15:54:25ZakwizgranForum topicsThis is a suggestion for a different way to organise forum threads.
Each top-level post starts a new topic. The author picks a subject line for the topic. Descendents of the post that started the topic don't have subject lines of their ...This is a suggestion for a different way to organise forum threads.
Each top-level post starts a new topic. The author picks a subject line for the topic. Descendents of the post that started the topic don't have subject lines of their own.
Within each forum, we show a list of topics. These can be sorted by recent activity, so inactive topics fall to the bottom. Subject lines provide a summary of the topics currently being discussed. The user can open an existing topic or start a new topic. Within each topic we show a threaded view like the one we currently use for the forum as a whole.
The aim is to allow parallel conversations to happen within a single forum, while making it easy to navigate between different conversations or focus on the most interesting ones. Subject lines make it easy to collapse inactive conversations down to a summary.
The main disadvantage is adding another level of navigation. The distinction between the forum list and the topic list might not be clear.https://code.briarproject.org/briar/briar/-/issues/878Let contacts know that we've removed them2020-11-19T15:54:55ZakwizgranLet contacts know that we've removed themCurrently we don't tell contacts that we've removed them - we just stop connecting to them and close any connections they make to us, since we no longer recognise the tags.
The main advantage of the current approach is that we can remov...Currently we don't tell contacts that we've removed them - we just stop connecting to them and close any connections they make to us, since we no longer recognise the tags.
The main advantage of the current approach is that we can remove contacts tactfully: the contact can't necessarily tell whether we removed her or whether we just haven't signed in recently. However, if the contact sees us posting to forums, blogs or private groups, she may be able to tell that we've removed her. A second advantage is that we can immediately delete all state relating to the contact. Removing all *identifiable* state is important - it's the equivalent of forward secrecy for the social graph. But removing *all* state is just convenient.
The main disadvantage of the current approach is that the contact wastes battery and bandwidth trying to connect to us indefinitely. Depending on the transport this may expose metadata (#62). These problems will get worse over time as users accumulate defunct contacts.https://code.briarproject.org/briar/briar/-/issues/873Blogs: Reloading when changing orientation2020-11-19T15:55:20ZMegaloxBlogs: Reloading when changing orientationThe blog seems to reload (blank screen and spinner) when the user changes from portarait to landscape mode. Is this intentional?The blog seems to reload (blank screen and spinner) when the user changes from portarait to landscape mode. Is this intentional?https://code.briarproject.org/briar/briar/-/issues/872Blogs: RSS feed import order2020-11-19T15:57:41ZMegaloxBlogs: RSS feed import orderThe posts of the RSS feed were imported in a random order and all of them showed the same timestamp. Wouldn't it be better to (a) import the posts in the correct order (newest on top) and (b) add the timestamp of the original post (that ...The posts of the RSS feed were imported in a random order and all of them showed the same timestamp. Wouldn't it be better to (a) import the posts in the correct order (newest on top) and (b) add the timestamp of the original post (that would be more interesting than the import timestamp IMO)https://code.briarproject.org/briar/briar/-/issues/858Private groups: No feedback that user left2020-11-19T16:05:34ZMegaloxPrivate groups: No feedback that user leftB left the group that A created but A never got any feedback, so she could not reinvite B.B left the group that A created but A never got any feedback, so she could not reinvite B.https://code.briarproject.org/briar/briar/-/issues/859Reveal contacts: No feedback for the revealee2020-11-19T16:06:52ZMegaloxReveal contacts: No feedback for the revealeeA revealed her relationship to B but B did not get feedback (maybe exept the visibility indicator, but that is very subtle)A revealed her relationship to B but B did not get feedback (maybe exept the visibility indicator, but that is very subtle)https://code.briarproject.org/briar/briar/-/issues/862Blogs: Scrolling with low performance2020-11-19T16:07:38ZMegaloxBlogs: Scrolling with low performanceOne tester scrolled the blog up and down and it wasn't really smooth. @ernir suspected the emojis to be responsible for this.One tester scrolled the blog up and down and it wasn't really smooth. @ernir suspected the emojis to be responsible for this.https://code.briarproject.org/briar/briar-gtk/-/issues/86Provide firejail profile2020-11-20T16:52:36ZNicoProvide firejail profileA user of Briar GTK said:
> Contributing a firejail profile would also help [with getting Briar GTK into Debian]!A user of Briar GTK said:
> Contributing a firejail profile would also help [with getting Briar GTK into Debian]!https://code.briarproject.org/briar/briar-gtk/-/issues/83Add backup option2020-11-21T10:03:23ZBressanAdd backup optionAdd an option to automatic save an encrypted backup file, with contacts, messages and id.Add an option to automatic save an encrypted backup file, with contacts, messages and id.https://code.briarproject.org/briar/briar-gtk/-/issues/79Add file-sharing2020-11-21T10:03:23ZdanAdd file-sharinghttps://code.briarproject.org/briar/briar-gtk/-/issues/35Support introductions2020-11-21T10:04:19ZNicoSupport introductionsMeta issue.
Related wrapper issue: https://code.briarproject.org/briar/python-briar-wrapper/issues/12Meta issue.
Related wrapper issue: https://code.briarproject.org/briar/python-briar-wrapper/issues/12https://code.briarproject.org/briar/briar-gtk/-/issues/36Support images2020-11-21T10:04:19ZNicoSupport imagesMeta issue.
Related wrapper issue: https://code.briarproject.org/briar/python-briar-wrapper/issues/13Meta issue.
Related wrapper issue: https://code.briarproject.org/briar/python-briar-wrapper/issues/13https://code.briarproject.org/briar/briar-gtk/-/issues/10Delete single message in chat history2020-11-21T10:04:19ZNicoDelete single message in chat historyRelated to https://code.briarproject.org/briar/briar-gtk/issues/11.Related to https://code.briarproject.org/briar/briar-gtk/issues/11.https://code.briarproject.org/briar/briar-gtk/-/issues/34Support adding contacts nearby2020-11-21T10:04:20ZNicoSupport adding contacts nearbyMeta issue.
Related wrapper issue: https://code.briarproject.org/briar/python-briar-wrapper/issues/11Meta issue.
Related wrapper issue: https://code.briarproject.org/briar/python-briar-wrapper/issues/11https://code.briarproject.org/briar/briar/-/issues/847Transport icons are confusing2020-11-21T12:29:31ZakwizgranTransport icons are confusingA tester asked how it was possible for the wifi and mobile network icons to be active at the same time. We may need to rethink the icons or labels to make it clear that one represents internet connectivity (via wifi or mobile data) and t...A tester asked how it was possible for the wifi and mobile network icons to be active at the same time. We may need to rethink the icons or labels to make it clear that one represents internet connectivity (via wifi or mobile data) and the other represents wifi connectivity (without necessarily being connected to the internet).
Related to #185 and #197.https://code.briarproject.org/briar/briar/-/issues/846Tor plugin doesn't switch to mobile data when router is disconnected from the...2020-11-21T12:30:09ZakwizgranTor plugin doesn't switch to mobile data when router is disconnected from the internethttps://code.briarproject.org/briar/briar/-/issues/843Keyboard closes when rotating private conversation screen to landscape2020-11-21T12:31:17ZakwizgranKeyboard closes when rotating private conversation screen to landscapehttps://code.briarproject.org/briar/briar/-/issues/842Post crash report instability2020-11-21T12:31:58ZErnir ErlingssonPost crash report instabilityAfter sending a crash report due to an OOME, the app re-opens in the Password Activity. The stability of the app is compromised and it can seemingly crash at any time with anything. We need to completely close the app when we experience ...After sending a crash report due to an OOME, the app re-opens in the Password Activity. The stability of the app is compromised and it can seemingly crash at any time with anything. We need to completely close the app when we experience a hard crash and force the user to re-open it to ensure the App's stability (and to prevent we get a lot of crash reports that are related to the first OOME).https://code.briarproject.org/briar/briar/-/issues/833ContactExchangeTaskImpl keeps a reference to KeyAgreementActivity2020-11-21T12:38:56ZakwizgranContactExchangeTaskImpl keeps a reference to KeyAgreementActivityKeyAgreementActivity implements ContactExchangeListener, an interface that ContactExchangeTaskImpl uses to keep the UI informed about its progress. ContactExchangeTaskImpl keeps a reference to the activity via this interface, but the act...KeyAgreementActivity implements ContactExchangeListener, an interface that ContactExchangeTaskImpl uses to keep the UI informed about its progress. ContactExchangeTaskImpl keeps a reference to the activity via this interface, but the activity may be destroyed before the task completes.
The activity's listener methods use runOnUiThreadUnlessDestroyed(), so they should return safely if they're called after the activity's destroyed, but the activity instance will be leaked until the task completes.