briar issueshttps://code.briarproject.org/groups/briar/-/issues2022-01-18T15:26:32Zhttps://code.briarproject.org/briar/briar-desktop/-/issues/218Contact Search Field Bug2022-01-18T15:26:32ZpaulContact Search Field BugCurrently on the main branch, when your search string causes the filtered contact list to return no contacts (i.e. search Fred and have no contacts whos names match that string) the screen switches to the newly added screen for a user wi...Currently on the main branch, when your search string causes the filtered contact list to return no contacts (i.e. search Fred and have no contacts whos names match that string) the screen switches to the newly added screen for a user with no contacts.
The attached gif is me typing an 'a' and then an 'f'.![briar_searchbar_bug](/uploads/8f93826d5b0f4c1c70130c62c095ca9b/briar_searchbar_bug.gif)Desktop 0.1.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/216Strip leading/trailing whitespace from messages2022-01-18T15:38:58ZNicoStrip leading/trailing whitespace from messagesBriar Android seems to strip whitespace from messages, even if the actual messages contains whitespace. To reproduce:
* send a message from Briar Desktop with trailing whitespace/newlines
* see how the whitespace gets stripped in Briar A...Briar Android seems to strip whitespace from messages, even if the actual messages contains whitespace. To reproduce:
* send a message from Briar Desktop with trailing whitespace/newlines
* see how the whitespace gets stripped in Briar Android, it's not visible in the received message
* see how the whitespace is displayed in Briar Desktop
When sending trailing whitespace from Briar Android, it seems to strip that, because the received message on Briar Desktop no more contains the whitespace.Desktop 0.1.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/215Swap order of delete account buttons2022-02-14T08:35:57ZNicoSwap order of delete account buttonsI was testing out the delete account dialog without the intentions to actually delete my account. I noticed how intuitively my mouse moved to the left button, as I have the feeling that there's always the "cancel" button, while the "exec...I was testing out the delete account dialog without the intentions to actually delete my account. I noticed how intuitively my mouse moved to the left button, as I have the feeling that there's always the "cancel" button, while the "execute" button uses to be on the right I think. This might be something for team @elioqoshi, but especially given that we don't ask again whether the user _really_ wants to delete their account (new issue?), we might should consider swap the buttons here. Really don't know, it's just a feeling. But there might be a Material guideline about this.
![Screenshot_from_2022-01-17_21-01-46](/uploads/51042d0541d374cb65e4b68a6d9e76e7/Screenshot_from_2022-01-17_21-01-46.png)Desktop 0.2.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/214It's possible to add one's own briar:// links when appending one or multiple ...2022-01-18T16:18:52ZSebastianIt's possible to add one's own briar:// links when appending one or multiple charsWhen checking wheter the user-provided link is our own link, we use the whole string and compare that to our own link while we really should only compare the valid part found by `HandshakeLinkConstants.LINK_REGEX.matcher(link).find()`When checking wheter the user-provided link is our own link, we use the whole string and compare that to our own link while we really should only compare the valid part found by `HandshakeLinkConstants.LINK_REGEX.matcher(link).find()`Desktop 0.1.0SebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2253Test Execution Ticket - Test requested in MR !15762022-07-13T11:19:40ZIvanaTest Execution Ticket - Test requested in MR !1576
### Install, Create Account, Add contacts
| Executed | Passed | Test case | Device | API Level |
| ------ | ------ | ------ | ------ | ------ |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/install-first-time | Samsung A0...
### Install, Create Account, Add contacts
| Executed | Passed | Test case | Device | API Level |
| ------ | ------ | ------ | ------ | ------ |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/install-first-time | Samsung A01 Core| 29|
| y | y | https://code.briarproject.org/briar/briar/-/wikis/upgrade-version | Samsung A01 Core| 29|
| y | y | https://code.briarproject.org/briar/briar/-/wikis/create-account | Samsung A01 Core | 29 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/connect-at-a-distance| Samsung A01 Core, PIxel 2 | 29, 30 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/add-already-added-contact-at-distance | Samsung A01 Core, Pixel 2 | 29,30 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/add-contact-at-distance-one-contact-offline | Samsung A01 Core, Pixel 2 | 29,30 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/rotate-screen-whilst-adding-contact-at-distance | Samsung A01 Core, Pixel 2 | 29,30 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/add-contact-whilst-pending-contacts | Samsung A01 Core, Pixel 2, Motorola E2 2nd gen | 29, 30, 23|
| ------ | ------ | https://code.briarproject.org/briar/briar/-/wikis/add-contact-after-time-out | ------ | ------ |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/connect-with-nearby-contact | HTC One M9, Samsung Galaxy A01 Core, Motorola E2 | 18, 29, 23 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/add-nearby-contact-bluetooth-off | HTC One M9, Pixel 2 | 19, 30 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/deny-briar-access-to-location | HTC One M9, Pixel 2 | 19, 30 |
| Y | Y | https://code.briarproject.org/briar/briar/-/wikis/deny-briar-access-to-location-many-times | HTC One M9, Pixel 2 | 19, 30 |
| y | n | https://code.briarproject.org/briar/briar/-/wikis/location-off-during-contact-creation | HTC One M9, Pixel 2, Motorola E2, HTC One M9 | 19, 30, 23, 24 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/receive-messages-during-contact-creation | HTC One M9, Pixel 2, HTC One M9 | 19, 30, 24 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/delete-recreate-nearby-contact | HTC One M9, Pixel 2 | 24, 30 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/add-nearby-contact-twice | Pixel 2, Samsung A01 Core | 30, 29 |
| ? | ------ | https://code.briarproject.org/briar/briar/-/wikis/add-nearby-contact-that-was-already-added-at-distance | PIxel2, Samsung A01 Core | 30, 29 |
### Bluetooth setup screen
| Executed | Passed | Test case | Device | API Level |
| ------ | ------ | ------ | ------ | ------ |
| y | y |https://code.briarproject.org/briar/briar/-/wikis/bluetooth-setup-screen| Pixel2, HTC One M9 | 30, 24 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/reconnect%20via%20BT%20when%20BT%20=%20OFF | Pixel2, HTC One M9 | 30, 24 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/reconnect-via-BT-when-Briar-BT-OFF-and-device-BT-OFF | Pixel2, HTC One M9 | 30, 24 |
| ------ | ------ | https://code.briarproject.org/briar/briar/-/wikis/reconnect-via-BT-when-Briar-BT-OFF-and-device-BT-OFF-device-location-OFF-Briar-no-access-to-location | Pixel2, HTC One M9 | 30, 24 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/add-nearby-contact-then-reconnect-via-BT | Pixel2, HTC One M9 | 30, 24 |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/fresh-install-add-contact-distance-reconnect-via-BT | ------ | ------ |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/fresh-install-add-nearby-contact-BT-reconnect-BT | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ |
### Profile pictures
| Executed | Passed | Test case | Device | API Level | Bug ID |
| ------ | ------ | ------ | ------ | ------ | ------ |
| y | n | https://code.briarproject.org/briar/briar/-/wikis/profile-pictures | Motorola E2, Samsung Mini I9195, Nokia 3.1, Pixel 2 | 23, 19, 29, 30 | #2258, #2260, #2143 |
| ------ | ------ | ------ | ------ | ------ | ------ |
### Self Destructing messages
| Executed | Passed | Test case | Device | API Level | Bug ID |
| ------ | ------ | ------ | ------ | ------ | ------ |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/disappearing-messages-sent-to-direct-contacts | Motorola E2, Samsung Mini I9195, Nokia 3.1, Pixel 2, Samsung 6810 | 23, 19, 29, 30, 16 | |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/make-introductions-disappearing-messages-on-intro-accepted | Motorola E2, Samsung Mini I9195, Nokia 3.1, Pixel 2, Samsung 6810 | 23, 19, 29, 30, 16 | ------ |
| y | y | https://code.briarproject.org/briar/briar/-/wikis/make-introductions-disappearing-messages-onoff-intro-accepted | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |
| ------ | ------ | ------ | ------ | ------ | ------ |Android 1.4https://code.briarproject.org/briar/briar-desktop/-/issues/212Settings persistence2022-02-17T10:04:11ZSebastianSettings persistenceI think !49 didn't add persinstence across settings, i.e. changes don't get written back to the database?I think !49 didn't add persinstence across settings, i.e. changes don't get written back to the database?Desktop 0.2.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/210Copy 0.1.0 beta artifacts to release server for persistence2022-01-21T13:10:04ZSebastianCopy 0.1.0 beta artifacts to release server for persistenceI think nightly builds are deleted after a few days, if we want our 0.1.0 release to be available longer, we need to copy it somewhere.I think nightly builds are deleted after a few days, if we want our 0.1.0 release to be available longer, we need to copy it somewhere.Desktop 0.1.0NicoNicohttps://code.briarproject.org/briar/briar/-/issues/2252Password screen when setting up the account on new account - shows password w...2022-01-13T13:39:04ZIvanaPassword screen when setting up the account on new account - shows password when it should be hidden and the other way aroundSteps to execute
- Install briar debug on a device (I sued Pixel 2)
- Enter a nickname into the Nickname field when asked
- On the next screen type in the password
Expected results
- Password should be visible when they 'eye' icon is ...Steps to execute
- Install briar debug on a device (I sued Pixel 2)
- Enter a nickname into the Nickname field when asked
- On the next screen type in the password
Expected results
- Password should be visible when they 'eye' icon is on, and hidden when the 'eye' icon is crossed
Actual results
- Password behaves the other way around, it shows when the 'eye' icon is crossed, and it is masked when the 'eye' icon is not crossed.
- Screenshot attached
![device-2022-01-13-141405](/uploads/a1566f1ae139000bf68707d26a224089/device-2022-01-13-141405.png)https://code.briarproject.org/briar/briar-desktop/-/issues/207Exceptions on UI layer don't make the app crash2022-01-18T18:31:40ZSebastianExceptions on UI layer don't make the app crashAs we noticed with #173, when an exception is thrown in the AWT thread, for example when something goes wrong in response to a button click, it can happen that the UI crashes with an error dialog usually. While the UI is gone after confi...As we noticed with #173, when an exception is thrown in the AWT thread, for example when something goes wrong in response to a button click, it can happen that the UI crashes with an error dialog usually. While the UI is gone after confirming the dialog, it can happen that the briar process lives on. That's kind of bad because the app will still be online, receiving messages without the user noticing. Worse, it will probably not be possible to launch a new briar-desktop afterwards as the Tor-ports will be blocked.
I think it would be best to somehow hook into the graceful shutdown that already seems to exist for the UI somehow (a dialog is shown after all explaining the exception) and shut down the whole app.Desktop 0.1.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/201Write another short Transifex announcement2022-01-17T22:05:42ZNicoWrite another short Transifex announcement* beta release on January 21st with almost full private chat experience
* people can test translations with nightly builds (https://code.briarproject.org/briar/briar-desktop/-/merge_requests/96)
* we'll make sure to update translations o...* beta release on January 21st with almost full private chat experience
* people can test translations with nightly builds (https://code.briarproject.org/briar/briar-desktop/-/merge_requests/96)
* we'll make sure to update translations on a (daily?) basis till that date
Depending on whether @sebkur and @ialokim want to have a chat with Muna vom LocLab this week, we should wait for this or publish it without having talked to her before.Desktop 0.1.0NicoNico2022-01-15https://code.briarproject.org/briar/social-mesh-research/-/issues/17Write abstract2023-08-28T16:04:16ZakwizgranWrite abstractDepends on #16.Depends on #16.https://code.briarproject.org/briar/social-mesh-research/-/issues/16Write introduction2023-08-28T16:04:17ZakwizgranWrite introductionDepends on #15.Depends on #15.https://code.briarproject.org/briar/social-mesh-research/-/issues/15Write conclusion2023-08-28T16:04:17ZakwizgranWrite conclusionDepends on #1, #6, #2, #5, #14.Depends on #1, #6, #2, #5, #14.https://code.briarproject.org/briar/social-mesh-research/-/issues/14Carry out and document final evaluation of design candidates2023-08-28T16:04:17ZakwizgranCarry out and document final evaluation of design candidatesDepends on #3, #5, #13.Depends on #3, #5, #13.https://code.briarproject.org/briar/social-mesh-research/-/issues/13Carry out and document simulations for each design candidate2023-08-28T16:04:17ZakwizgranCarry out and document simulations for each design candidateDepends on #7, #8, #9, #10, #11.Depends on #7, #8, #9, #10, #11.https://code.briarproject.org/briar/social-mesh-research/-/issues/12Carry out and document baseline simulations (current architecture)2023-08-28T16:04:17ZakwizgranCarry out and document baseline simulations (current architecture)Depends on #8, #9, #10, #11.Depends on #8, #9, #10, #11.https://code.briarproject.org/briar/social-mesh-research/-/issues/11Find or create a suitable simulation framework2023-03-15T12:40:07ZakwizgranFind or create a suitable simulation frameworkDepends on #8.Depends on #8.https://code.briarproject.org/briar/social-mesh-research/-/issues/10Find or create a suitable traffic model or dataset2023-03-15T12:40:24ZakwizgranFind or create a suitable traffic model or datasetDepends on #8.Depends on #8.https://code.briarproject.org/briar/social-mesh-research/-/issues/9Find or create a suitable mobility model or dataset2023-03-15T12:40:41ZakwizgranFind or create a suitable mobility model or datasetDepends on #8.Depends on #8.https://code.briarproject.org/briar/social-mesh-research/-/issues/8Decide and document the scenarios that will be simulated2023-08-28T16:04:17ZakwizgranDecide and document the scenarios that will be simulatedDepends on #1, #3, #6.Depends on #1, #3, #6.