briar issueshttps://code.briarproject.org/groups/briar/-/issues2023-08-28T16:03:33Zhttps://code.briarproject.org/briar/briar/-/issues/2398Testers didn't understand why Mailbox was still linked after failed unlinking2023-08-28T16:03:33ZakwizgranTesters didn't understand why Mailbox was still linked after failed unlinking![unlink-1](/uploads/291b980ba78f2254b8ec690bb77f1850/unlink-1.png) ![unlink-2](/uploads/1279bbd2726de7a3d2adbc3076af895c/unlink-2.png)
> This step was confusing in most cases. Participants ignored the textboxes and when they unlinked t...![unlink-1](/uploads/291b980ba78f2254b8ec690bb77f1850/unlink-1.png) ![unlink-2](/uploads/1279bbd2726de7a3d2adbc3076af895c/unlink-2.png)
> This step was confusing in most cases. Participants ignored the textboxes and when they unlinked the device, the Mailbox still showed that it was linked. In those cases, they thought that this must be happening because of bugs in the test app.Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2396Testers couldn't find mailbox pairing screen2023-08-28T16:03:37ZakwizgranTesters couldn't find mailbox pairing screen> All participants successfully installed and created accounts. On the other hand, linking devices was one of the most difficult tasks for all
participants.
>
> The common pattern for all was to misinterpret the device-linking process a...> All participants successfully installed and created accounts. On the other hand, linking devices was one of the most difficult tasks for all
participants.
>
> The common pattern for all was to misinterpret the device-linking process as adding a new contact. The first instinct for four out of five participants was to click on the + icon and try to “add a contact nearby”, they chose that because the devices are near to each other.
>
> The second place they went to look for the feature was always the sidebar menu. First, they looked at the options there and the connection icons. They guessed that linking devices is a form of connection, so they would find it there. One of the participants assumed that the “Internet” icon represents the Mailbox connection.
>
> On the third attempt, they could all find the Mailbox option, listed under the Settings menu.Mailbox: Usability testinghttps://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/-/issues/2263Status of Tor plugin is unclear in connections screen2022-02-11T12:35:00ZakwizgranStatus of Tor plugin is unclear in connections screenWhen the "Use mobile data" setting is turned off or the "Connect to the Internet only when charging" setting is turned on, Briar might not connect to the internet even though the parent setting, "Connect to contacts via the Internet", is...When the "Use mobile data" setting is turned off or the "Connect to the Internet only when charging" setting is turned on, Briar might not connect to the internet even though the parent setting, "Connect to contacts via the Internet", is turned on.
In the main settings screen this is hopefully clear because all the settings are shown. But in the connections screen we only show the parent setting and the current status. So it may not be obvious that Briar is offline, or how to change this.https://code.briarproject.org/briar/briar-gtk/-/issues/91Slows down with large amount of messages saved2021-01-23T13:49:41ZBen ArmsteadSlows down with large amount of messages savedReporting a minor bug.
After 2-3 weeks of regular messaging via briar-gtk with a contact, and click on the contact (which now has a large amount of messages (Im not sure maybe a few thousand)).
The program hangs for about 1-2 seconds ...Reporting a minor bug.
After 2-3 weeks of regular messaging via briar-gtk with a contact, and click on the contact (which now has a large amount of messages (Im not sure maybe a few thousand)).
The program hangs for about 1-2 seconds (which I am pretty confident is due to loading in the large amount of messages?).
In line with my theory the more messages that are sent the slower it is to open the contact from the main menu.
Would it be possible to load in e.g. 50 messages at a time and then only load in the others if I scroll back enough to need to see them instead of loading in all the messages at the same time?
(Deleting all of the messages with the contact solves the problem and I instantly load into a chat with them without the few seconds wait).
I am willing to help with the python programming of this, but have less experience with GTK.
As always thanks for the great work!https://code.briarproject.org/briar/website/-/issues/21Improve menu structure2022-11-18T17:32:16ZCleopatraImprove menu structure@akwizgran @grote
Referencing [a chat](https://chat.briarproject.org/briar/pl/yciiahqe8pyajqc57re917rz1y) on the UX channel:
> i think submenus would be fine (assuming we do them in css). we might want to do some user testing to make s...@akwizgran @grote
Referencing [a chat](https://chat.briarproject.org/briar/pl/yciiahqe8pyajqc57re917rz1y) on the UX channel:
> i think submenus would be fine (assuming we do them in css). we might want to do some user testing to make sure people with different amounts of technical skill can find what they're looking for
>
> about, documentation and download are pretty common top-level menu items for software projects, although i agree download may not be necessary for us as it's on the front page
>
> so perhaps:
>
> about
> news
> team
> contact
> documentation
> how it works
> user manual
> faq
> wiki
> community
> get involved
> source code
> style guide
------------------
I don't see the point of having submenus. We can show only the most important stuff by keeping the menu structure as simple as:
- About
- Download
- Documentation
- Support
- News
- Contribute
- DonateCleopatraCleopatrahttps://code.briarproject.org/briar/briar-gtk/-/issues/82Option to not require a password2020-11-15T13:42:03ZBen ArmsteadOption to not require a passwordIt would be nice to not have to set a password or not require it every time the program starts.
This is a security trade off, as it would limit the ability of at rest encryption, however some users may not need at rest encryption.
I wi...It would be nice to not have to set a password or not require it every time the program starts.
This is a security trade off, as it would limit the ability of at rest encryption, however some users may not need at rest encryption.
I will have a play around with Briar GTK and see if I can program a solution to this.
I understand if this is not wanted to be introduced due to the reduction in security that the optional removal of at rest encryption may be.https://code.briarproject.org/briar/briar-gtk/-/issues/78Notification counter stays even when msg has been seen2021-01-23T13:40:43ZdanNotification counter stays even when msg has been seenNotification doesnt go away. ![briar.notif](/uploads/565826097a0162211009d7e70c70576f/briar.notif.png)
The only way to make the notification go away, is to send a msg.
flatpak v0.1.0-beta2Notification doesnt go away. ![briar.notif](/uploads/565826097a0162211009d7e70c70576f/briar.notif.png)
The only way to make the notification go away, is to send a msg.
flatpak v0.1.0-beta2GTK Nexthttps://code.briarproject.org/briar/briar-gtk/-/issues/77Make taskbar icon blink when new msg / add tray options2020-11-15T13:42:36ZdanMake taskbar icon blink when new msg / add tray optionsFirst time trying Briar here. Running the flatpak v0.1.0-beta2
I could use Briar as main messenger if Briar taskbar icon/tray icon would blink when new msg.
Since Briar should be running 24/7, option to move it to tray is needed.
Tha...First time trying Briar here. Running the flatpak v0.1.0-beta2
I could use Briar as main messenger if Briar taskbar icon/tray icon would blink when new msg.
Since Briar should be running 24/7, option to move it to tray is needed.
Thank you for Briar and the desktop port.https://code.briarproject.org/briar/briar/-/issues/1796Add option to disable animations2020-11-15T13:41:47ZakwizgranAdd option to disable animationsTwo Google Play users asked for the option to disable transition animations.Two Google Play users asked for the option to disable transition animations.https://code.briarproject.org/briar/briar/-/issues/1792Stepper isn't read in a meaningful order by screen readers2020-11-15T13:47:05ZakwizgranStepper isn't read in a meaningful order by screen readersThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the "stepper" that shows the steps in the process of adding a contact remotely isn't read in a meaningful order by screen...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the "stepper" that shows the steps in the process of adding a contact remotely isn't read in a meaningful order by screen readers. TalkBack navigation reads the steps "1 - Exchange links, 2 - Choose nickname" as "1, 2, Exchange links, Choose nickname".https://code.briarproject.org/briar/briar/-/issues/1791Non-text content should have a textual alternative2020-11-15T13:48:30ZakwizgranNon-text content should have a textual alternativeThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several places in the app where non-text content lacks a textual alternative:
- [ ] Password strength indicator
- [ ] Checkmarks...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several places in the app where non-text content lacks a textual alternative:
- [ ] Password strength indicator
- [ ] Checkmarks in the power management setup screen
- [ ] Checkmarks in the stepper when adding a contact remotely
- [ ] Diagram explaining how QR codes should or should not be exchanged
If any of these involve a lot of work we can create subtasks.https://code.briarproject.org/briar/briar/-/issues/1790Check whether text has enough contrast for accessibility2020-11-15T13:48:54ZakwizgranCheck whether text has enough contrast for accessibilityThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the placeholder text in input fields appears to have low contrast, but this couldn't be verified as the app doesn't allow...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the placeholder text in input fields appears to have low contrast, but this couldn't be verified as the app doesn't allow screenshots. There may be other places in the app, such as the coloured status messages in the pending contact list, where we're not meeting accessibility guidelines for contrast.
Contrast should be at least 4.5:1 for "normal" text or 3.0:1 for "large" text, defined as 18px or 14 px + bold. The light and dark themes need to be checked.https://code.briarproject.org/briar/briar/-/issues/1789Changes to status messages aren't visible to screen readers2020-11-15T13:49:20ZakwizgranChanges to status messages aren't visible to screen readersThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that when status messages such as those shown in the pending contact list ("Connecting", etc) are updated, screen readers aren...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that when status messages such as those shown in the pending contact list ("Connecting", etc) are updated, screen readers aren't automatically aware that the text has changed.
One way to make screen readers aware that text has changed is to give focus to the changed element. The "Password is too weak" message on the setup screen is an example of a status message that's correctly handled by screen readers.https://code.briarproject.org/briar/briar/-/issues/1788Text fields should have labels2020-11-15T13:51:14ZakwizgranText fields should have labelsThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the way we style text fields, showing placeholder text but not a label, is an accessibility issue because the placeholder...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the way we style text fields, showing placeholder text but not a label, is an accessibility issue because the placeholder text disappears when the user starts to type, leaving no indication of the field's purpose.
This is my fault - I argued for removing the labels because I think the way they move and change size when the field gains or loses focus interacts badly with automatically giving focus to the first text field.https://code.briarproject.org/briar/briar/-/issues/1787Transport indicators are not accessible to colourblind people2020-11-15T13:51:37ZakwizgranTransport indicators are not accessible to colourblind peopleThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the transport indicators in the nav drawer rely on colour alone to indicate their state. A second visual cue should be pr...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the transport indicators in the nav drawer rely on colour alone to indicate their state. A second visual cue should be provided for colourblind users.https://code.briarproject.org/briar/briar/-/issues/1786Some buttons lack name/role/value for accessibility2020-11-15T13:52:36ZakwizgranSome buttons lack name/role/value for accessibilityThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several examples of buttons that weren't marked with an appropriate name, role and value to enable screen readers to handle them ...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several examples of buttons that weren't marked with an appropriate name, role and value to enable screen readers to handle them properly:
- [ ] The `(i)` button for showing information lacks a role (should be "button")
- [ ] The `+` button for adding contacts lacks a name
- [ ] The speed dial buttons for adding contacts lack a role for the text and a name for the icon
- [ ] The buttons in the navigation menu lack a role
- [ ] The transport indicators lack a value
- [ ] In the private group list and possibly elsewhere, the action bar's overflow menu button and the menu items lack roles
- [ ] The button for opening/closing the emoji keyboard lacks a name
- [ ] The "Reply" button (in forums and private groups?) lacks a role
- [ ] When the buttons for scrolling up/down to the previous/next unread message are hidden, they're still visible to screen readers but don't work, and don't have a name, role or value
- [ ] The reblog button has the name "Add a comment" rather than "Reblog"
If any of these are tricky to handle we can create subtasks.https://code.briarproject.org/briar/briar/-/issues/1778Onboarding tap target wrongly positioned2021-08-19T11:13:14ZakwizgranOnboarding tap target wrongly positionedThe onboarding tap target for the connections screen is meant to be centered on the Tor icon. On the Samsung Galaxy Ace 2 (Android 4.1.2) it's centered on the top left corner of the nav drawer instead.
I can reproduce this reliably on t...The onboarding tap target for the connections screen is meant to be centered on the Tor icon. On the Samsung Galaxy Ace 2 (Android 4.1.2) it's centered on the top left corner of the nav drawer instead.
I can reproduce this reliably on the device, but it doesn't happen on the emulator running the same API version (16).
![device-2020-09-24-124455](/uploads/4b87fcb4d94c44028ae2fb0cc72dbbb1/device-2020-09-24-124455.png)https://code.briarproject.org/briar/briar-gtk/-/issues/66Automatically start at system boot2020-11-15T14:08:37ZNicoAutomatically start at system bootShould be opt-out.
Currently, I use this:
_~/.config/autostart/briar-gtk.desktop_
```desktop
[Desktop Entry]
Type=Application
Name=briar-gtk
Exec=/usr/bin/flatpak run app.briar.gtk
```Should be opt-out.
Currently, I use this:
_~/.config/autostart/briar-gtk.desktop_
```desktop
[Desktop Entry]
Type=Application
Name=briar-gtk
Exec=/usr/bin/flatpak run app.briar.gtk
```https://code.briarproject.org/briar/briar/-/issues/1774Shreding data when deleting history2020-11-15T14:10:49ZStevanShreding data when deleting historyI'd recommend that when you click delete history on briar chats data gets shreded, if that already is not the case.
This will make data recovery impossible.I'd recommend that when you click delete history on briar chats data gets shreded, if that already is not the case.
This will make data recovery impossible.