briar issueshttps://code.briarproject.org/groups/briar/-/issues2020-11-15T10:20:33Zhttps://code.briarproject.org/briar/briar/-/issues/973Add 'Select All' Button to Sharing Screens2020-11-15T10:20:33ZTorsten GroteAdd 'Select All' Button to Sharing ScreensMessages traversal in a social graph improves with each added share relationship between contacts. This is especially true for forums, but maybe also blogs and (reveal contacts of) private groups. In order to encourage sharing, I propose...Messages traversal in a social graph improves with each added share relationship between contacts. This is especially true for forums, but maybe also blogs and (reveal contacts of) private groups. In order to encourage sharing, I propose to add a "select all" button to the respective sharing/reveal screens that selects all selectable contacts and still allows the user to unselect individual contacts before proceeding.https://code.briarproject.org/briar/briar/-/issues/929Non-blocking SettingsManager2020-11-15T10:37:10ZakwizgranNon-blocking SettingsManagerThe SettingsManager interface is inconvenient to use because it needs to be called on the DB thread. Make the interface non-blocking by loading settings at startup and writing them back to the DB in the background when they're updated.The SettingsManager interface is inconvenient to use because it needs to be called on the DB thread. Make the interface non-blocking by loading settings at startup and writing them back to the DB in the background when they're updated.https://code.briarproject.org/briar/briar/-/issues/924Tester thought tap target onboarding was a bug2020-11-15T10:43:00ZakwizgranTester thought tap target onboarding was a bugA tester thought the tap target onboarding for the introduction feature was a bug - she held up her phone and asked "Is it meant to look like that?".
Perhaps we should consider using a less bold design, or changing the parameters so tha...A tester thought the tap target onboarding for the introduction feature was a bug - she held up her phone and asked "Is it meant to look like that?".
Perhaps we should consider using a less bold design, or changing the parameters so that the target appears more gradually.https://code.briarproject.org/briar/briar/-/issues/1000Testers had to pair phones via Bluetooth to add each other as contacts2020-11-15T10:50:05ZakwizgranTesters had to pair phones via Bluetooth to add each other as contacts* User feedback: "Took us some time to figure out that we have to first pair our phones via Bluetooth before trying to add a contact."
* Android version: 7.1.2
* Briar version: 0.16.2* User feedback: "Took us some time to figure out that we have to first pair our phones via Bluetooth before trying to add a contact."
* Android version: 7.1.2
* Briar version: 0.16.2https://code.briarproject.org/briar/website/-/issues/18Add RSS icon to website2020-11-15T11:52:28ZakwizgranAdd RSS icon to websiteA user asked for an RSS icon to be added to the website. The icon could point to the news feed produced by Hugo:
https://briarproject.org/news/index.xmlA user asked for an RSS icon to be added to the website. The icon could point to the news feed produced by Hugo:
https://briarproject.org/news/index.xmlhttps://code.briarproject.org/briar/briar/-/issues/1798Delete account if wrong password is entered several times2020-11-15T13:41:23ZakwizgranDelete account if wrong password is entered several timesA user asked for the option to delete the account automatically if the wrong password is entered several times.A user asked for the option to delete the account automatically if the wrong password is entered several times.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-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/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/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/1784Tor settings: Please add a sentence to explain the meaning of 'bridges' to no...2020-11-15T13:53:04ZRobert PollakTor settings: Please add a sentence to explain the meaning of 'bridges' to non-technical usersLike "Connecting via bridges is less prone to surveillance."
Also, what would be an advantage of not using bridges?Like "Connecting via bridges is less prone to surveillance."
Also, what would be an advantage of not using bridges?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.https://code.briarproject.org/briar/briar-gtk/-/issues/64Make it possible to undo contact deletion2020-11-15T14:12:48ZNicoMake it possible to undo contact deletionWe would then not need to confirm whether the contact should be deleted (#63).We would then not need to confirm whether the contact should be deleted (#63).