briar issueshttps://code.briarproject.org/groups/briar/-/issues2021-03-11T12:26:10Zhttps://code.briarproject.org/briar/briar/-/issues/1836Automatically decline incoming private group invitations when they self-destruct2021-03-11T12:26:10ZakwizgranAutomatically decline incoming private group invitations when they self-destructWhen an incoming private group invitation self-destructs without being answered, automatically decline the request. This may require a protocol update (coordinated with #1831) to flag the decline as an automatic response that shouldn't b...When an incoming private group invitation self-destructs without being answered, automatically decline the request. This may require a protocol update (coordinated with #1831) to flag the decline as an automatic response that shouldn't be shown in the UI.
Subtask of #804Self-destructing messagesIvanaIvana2021-01-31https://code.briarproject.org/briar/briar/-/issues/1835Automatically decline incoming blog/forum invitations when they self-destruct2021-07-06T09:56:40ZakwizgranAutomatically decline incoming blog/forum invitations when they self-destructWhen an incoming blog/forum invitation self-destructs without being answered, automatically decline the invitation. This may require a protocol update (coordinated with #1830) to flag the decline as an automatic response that shouldn't b...When an incoming blog/forum invitation self-destructs without being answered, automatically decline the invitation. This may require a protocol update (coordinated with #1830) to flag the decline as an automatic response that shouldn't be shown in the UI.
Subtask of #804Self-destructing messagesIvanaIvana2021-01-31https://code.briarproject.org/briar/briar/-/issues/1834Automatically decline incoming introduction requests when they self-destruct2021-05-05T16:17:22ZakwizgranAutomatically decline incoming introduction requests when they self-destructWhen an incoming introduction request self-destructs without being answered, automatically decline the request. This may require a protocol update (coordinated with #1829) to flag the decline as an automatic response that shouldn't be sh...When an incoming introduction request self-destructs without being answered, automatically decline the request. This may require a protocol update (coordinated with #1829) to flag the decline as an automatic response that shouldn't be shown in the UI.
Subtask of #804
Test instructions:
* Use three devices, users A, B and C
* Enable self-destructing messages in the conversations A-B and A-C
* Let A introduce contacts B and C
* Expect invitation messages to arrive at B and C about the invitation
* Expect the invitation messages to have a auto-delete timers
* Let those timers expire. Expect that to trigger an automatic decline of the invitation, i.e. on all three devices it is visible that the introduction failed (due to the expired response)
* Expect all messages from that interaction to destroy after each message's timer expires
* Let A introduce B and C again. Expect this *not* to fail due to an introduction that is already going on (because none should be going on any longer)
* Let B and C accept the introduction
* Expect the introduction to work
* Confirm that B and C have each other in the contact list
* Expect all messages involved in the transaction to have auto-delete timers
* Let those timers expire and expect all those messages to disappearSelf-destructing messagesIvanaIvana2021-01-31https://code.briarproject.org/briar/briar/-/issues/1833Delete messages when their self-destruct timers expire2021-03-11T12:25:31ZakwizgranDelete messages when their self-destruct timers expireCreate a component that tracks pending self-destruct timers and deletes messages when their self-destruct timers expire.
Conversation clients will register messages for deletion during delivery. The new component will be responsible for...Create a component that tracks pending self-destruct timers and deletes messages when their self-destruct timers expire.
Conversation clients will register messages for deletion during delivery. The new component will be responsible for calling back into the client when a message is due to be deleted. This will allow the client to take any necessary steps before deletion, such as declining an open introduction.
Subtask of #804Self-destructing messagesIvanaIvana2021-01-31https://code.briarproject.org/briar/briar/-/issues/1824Adapt to power management restrictions2021-04-30T13:42:29ZakwizgranAdapt to power management restrictionsAdapt to changes in the Android platform2021-04-30https://code.briarproject.org/briar/briar/-/issues/1793Feedback screen has wrong title in screen reader2021-07-06T10:03:53ZakwizgranFeedback screen has wrong title in screen readerWhen opening the feedback screen, the TalkBack screen reader reads the title as "Briar crash reporter". I'm guessing this is the default title for the activity and it's changed to "Feedback" after the point where the screen reader reads ...When opening the feedback screen, the TalkBack screen reader reads the title as "Briar crash reporter". I'm guessing this is the default title for the activity and it's changed to "Feedback" after the point where the screen reader reads the title.Adapt to changes in the Android platformTorsten GroteTorsten Grote2021-04-30https://code.briarproject.org/briar/briar/-/issues/1743Research whether our wake lock tags are still effective2021-09-01T10:10:21ZakwizgranResearch whether our wake lock tags are still effectiveLeave Briar running on devices with recent versions of Huawei PowerGenie and Evenwell PowerMonitor to see whether our wake lock tags still protect us from being killed.Leave Briar running on devices with recent versions of Huawei PowerGenie and Evenwell PowerMonitor to see whether our wake lock tags still protect us from being killed.Adapt to changes in the Android platformakwizgranakwizgran2021-04-30https://code.briarproject.org/briar/briar/-/issues/2148Hotspot QR codes aren't fully visible without scrolling2021-08-31T12:21:34ZakwizgranHotspot QR codes aren't fully visible without scrollingOn devices with relatively square aspect ratios, the QR codes that are shown when sharing the app offline aren't fully visible without scrolling. It may not be obvious that the view is scrollable.On devices with relatively square aspect ratios, the QR codes that are shown when sharing the app offline aren't fully visible without scrolling. It may not be obvious that the view is scrollable.Install via Bluetooth or Wi-FiDaniel LublinDaniel Lublin2021-07-31https://code.briarproject.org/briar/briar/-/issues/2011App offline sharing UX2021-10-29T11:45:23ZElio Qoshielio@ura.designApp offline sharing UX![All_Screens](/uploads/bd9eb2dd5bbb58e2287fd8e9a036f12f/All_Screens.png)
I drafted an initial UX proposal for sharing an app offline.
Figma specs: https://www.figma.com/file/NgBKOW1GcLk1NXzHQBcYdY/Offline-App-Installer-Sharing?node-id=...![All_Screens](/uploads/bd9eb2dd5bbb58e2287fd8e9a036f12f/All_Screens.png)
I drafted an initial UX proposal for sharing an app offline.
Figma specs: https://www.figma.com/file/NgBKOW1GcLk1NXzHQBcYdY/Offline-App-Installer-Sharing?node-id=1%3A5491
Considerations:
- This doesn't take into account that we are automatically detecting if a fellow peer connects to the hotspot. The hosting user needs to manually confirm this.
- There should be plenty of space for instructions and help text, as well as a separate help option via the dropdown menu if needed. The texts are of course only placeholders, though their I included their notion, more or less.
- An illustration should make the process feel more engaging (like the start of onboarding).
- Not sure about the steppers on the bottom. Open to hear what you think.Install via Bluetooth or Wi-FiElio Qoshielio@ura.designElio Qoshielio@ura.design2021-07-31https://code.briarproject.org/briar/briar/-/issues/1802Sync data via SD card or USB stick on Android2022-01-21T14:12:16ZakwizgranSync data via SD card or USB stick on AndroidImplement a plugin and user interface for syncing data via external storage (SD card or USB stick) on Android.Implement a plugin and user interface for syncing data via external storage (SD card or USB stick) on Android.Transfer content securely via SD cards and USB memory sticksIvanaIvana2021-07-31https://code.briarproject.org/briar/briar-desktop/-/issues/138Add Contact Dialog TextBox Visual Bug2022-01-06T22:00:22ZpaulAdd Contact Dialog TextBox Visual BugOn Trisquel Linux, with the default Briar desktop window size, the bottom textbox's content is not visible.
![dialog-bug](/uploads/e0c98ac0c82e3564208d4100e157f285/dialog-bug.gif)On Trisquel Linux, with the default Briar desktop window size, the bottom textbox's content is not visible.
![dialog-bug](/uploads/e0c98ac0c82e3564208d4100e157f285/dialog-bug.gif)Desktop 0.1.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/125Ability to select and delete single messages in chat history2022-01-08T17:42:43ZMikolai GütschowAbility to select and delete single messages in chat historyOn Android, the selection is instantiated by a long press. Not sure what is the best practice for desktop applications nowadays: Right-click on the message, activate an option in the context menu and show checkbox next to each message, o...On Android, the selection is instantiated by a long press. Not sure what is the best practice for desktop applications nowadays: Right-click on the message, activate an option in the context menu and show checkbox next to each message, or something else?Desktop 0.1.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/124Option to delete all messages in chat history2022-01-07T22:09:08ZMikolai GütschowOption to delete all messages in chat historyBasically an implementation of the context menu entry "Delete all messages"Basically an implementation of the context menu entry "Delete all messages"Desktop 0.1.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/248New messages in open chat are marked as read even if window is not on screen2022-02-18T07:26:16ZMikolai GütschowNew messages in open chat are marked as read even if window is not on screenSteps to reproduce:
1. open a chat
2. minimize or hide the window behind another window in your environment
3. send a message from the other side of the chat
4. wait some time
5. show window again
6. notice that no messages are marked a...Steps to reproduce:
1. open a chat
2. minimize or hide the window behind another window in your environment
3. send a message from the other side of the chat
4. wait some time
5. show window again
6. notice that no messages are marked as unreadDesktop 0.2.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/158Allow renaming of contact (alias)2022-02-14T08:35:59ZMikolai GütschowAllow renaming of contact (alias)Desktop 0.2.0SebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/1011Offline message delivery (mailbox)2023-06-19T14:01:29ZakwizgranOffline message delivery (mailbox)Two testers asked for the ability for messages to be delivered while the recipient is offline. "Some of my global contacts are rarely online with me."Two testers asked for the ability for messages to be delivered while the recipient is offline. "Some of my global contacts are rarely online with me."Mailbox2022-10-31https://code.briarproject.org/briar/briar-desktop/-/issues/310Play notification sound when new messages arrive while window is not focused2022-09-10T08:35:04ZSebastianPlay notification sound when new messages arrive while window is not focusedImproving on !151 and addressing more of #156, I think it is customary for chat apps to play a sound when new messages arrive to draw the user's attention to the app. Of course, the user should be able to turn that off. I know it on the ...Improving on !151 and addressing more of #156, I think it is customary for chat apps to play a sound when new messages arrive to draw the user's attention to the app. Of course, the user should be able to turn that off. I know it on the desktop from RocketChat, Mattermost and on mobile basically any messaging app does this.Desktop 0.4.0https://code.briarproject.org/briar/briar-desktop/-/issues/156Show native notification for new messages / new contacts2023-02-21T11:27:38ZMikolai GütschowShow native notification for new messages / new contactsThis should :tm: be easy with Compose: https://github.com/JetBrains/compose-jb/tree/master/tutorials/Tray_Notifications_MenuBar_new
We have to decide what should be shown in the notification: The actual message text or as in Android onl...This should :tm: be easy with Compose: https://github.com/JetBrains/compose-jb/tree/master/tutorials/Tray_Notifications_MenuBar_new
We have to decide what should be shown in the notification: The actual message text or as in Android only a generic "You have {} new message(s)".Desktop 0.4.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-mailbox/-/issues/180Outline button style2022-12-16T17:22:01ZSebastianOutline button styleIt wasn't mentioned in the usability report that users had problems to find the non-outlined buttons on the mailbox app. But now that we have that style in the briar app, I'm thinking it might make sense for visual consistency between bo...It wasn't mentioned in the usability report that users had problems to find the non-outlined buttons on the mailbox app. But now that we have that style in the briar app, I'm thinking it might make sense for visual consistency between both apps to also use that style on the mailbox app.
Related: https://code.briarproject.org/briar/briar/-/merge_requests/1746Mailbox: Usability testingSebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2403Not enough feedback while connecting to Mailbox2022-12-15T13:02:08ZakwizgranNot enough feedback while connecting to Mailbox> Sometimes the connection took a long time while setting up the Mailbox. In these cases, a few participants assumed that they were having problems with either the app or the internet connection. There is not enough feedback for the user...> Sometimes the connection took a long time while setting up the Mailbox. In these cases, a few participants assumed that they were having problems with either the app or the internet connection. There is not enough feedback for the user on this screen.Mailbox: Usability testingIvanaIvana