briar issueshttps://code.briarproject.org/groups/briar/-/issues2023-09-12T12:22:53Zhttps://code.briarproject.org/briar/public-mesh-research/-/issues/22Write report2023-09-12T12:22:53ZSebastianWrite reporthttps://code.briarproject.org/briar/briar-spec/-/issues/18Move BSP clients specs from wiki to this repo2023-02-20T15:10:17ZNicoMove BSP clients specs from wiki to this repoAs discussed with @akwizgran, instead of having them in the wiki they should live in this repo so that merge requests can be opened that can be reviewed.
https://code.briarproject.org/briar/briar/-/wikis/home#clientsAs discussed with @akwizgran, instead of having them in the wiki they should live in this repo so that merge requests can be opened that can be reviewed.
https://code.briarproject.org/briar/briar/-/wikis/home#clientsNicoNicohttps://code.briarproject.org/briar/website/-/issues/42Add page for Briar Mailbox2023-06-19T14:02:01ZakwizgranAdd page for Briar MailboxAdd a page explaining what Briar Mailbox does and how to download it.Add a page explaining what Briar Mailbox does and how to download it.Mailbox: Releasehttps://code.briarproject.org/briar/briar-desktop/-/issues/396Report for work after UX and accessibility audit2023-01-09T22:41:09ZSebastianReport for work after UX and accessibility auditI'm working on the report for OTF and am using our summary issues with the checklists as a base for what we put into that report. Whatever is striked through is already mentioned in the report.
## Copied from #366:
Targeting issues rai...I'm working on the report for OTF and am using our summary issues with the checklists as a base for what we put into that report. Whatever is striked through is already mentioned in the report.
## Copied from #366:
Targeting issues raised in #341 and as part of #84.
- ~~Heading structure: > not supported by upstream Compose (https://github.com/JetBrains/compose-jb/issues/2119)~~
- [ ] ~~"Welcome to Briar" on login and main screen (no chats)~~
- [ ] ~~contact name in chat screen~~
- [ ] ~~"Settings" on SettingsScreen~~
- ~~Image(Button) contentDescription:~~
- [ ] ~~Briar logo on login > only of decorative nature, automatically skipped over by VoiceOver~~
- [x] ~~back and info button on login > !223 and info button already "About Briar Desktop" on `main`~~
- [x] ~~menu button in chat screen > already "Show Contact Menu" on `main`~~
- [x] ~~add contact button without chats > fixed on `main`~~
- [x] ~~attachment button in chat screen > fixed on `main`~~
- ~~Missing context:~~
- [x] ~~show password buttons on login/change password > automatically grouped on macOS/VoiceOver~~
- [x] ~~labels for text fields (registration screen) > !225 .~~
- ~~Missing list grouping:~~
- [x] ~~contact list > !218 .~~
- [x] ~~settings as list > !224 .~~
- ~~Missing state information (expanded/collapsed): Dropdowns/Pop-Ups not supported by Compose https://github.com/JetBrains/compose-jb/issues/2185 .~~
- [ ] ~~menu button in chat screen~~
- [ ] ~~theme/language settings, also dynamic changes~~
- Misc:
- [ ] ~~error message on login (not read out loud) > upstream bug: https://github.com/JetBrains/compose-jb/issues/2277 .~~
- [x] ~~about dialog (no exit button, table not marked as such, email is not link) > !221 .~~
- [x] ~~message count/online status in contact list > !218. ~~
- [x] ~~"keyboard trap" in compose message text field (tab button is stuck in text field) > !222 .~~
- [ ] ~~Missing landmarks on MainScreen to convey structure to screen-reader user > not supported by Compose~~
- [x] Keyboard focus does not go to close button on add contact dialog > probably missing OS-functionality on Ubuntu/Orca which is anyhow not supported, confirmed to work on macOS with VoiceOver as expected
- [ ] ~~Dropdown not marked as such (settings) > Dropdowns/Pop-Ups not supported by Compose https://github.com/JetBrains/compose-jb/issues/2185 .~~
- [x] ~~Briar link name/label on Add Contact dialog > !230~~
- [x] ~~Add attachment button not keyboard-focusable on macOS > !222~~
## Copied from #343:
During the accessibility audit #341 several issues were identified concerning poor color contrast:
- [x] ~~registration screen: text field label (light blue on white/black background) > !213 .~~
- [x] ~~settings/change password screen: text field labels (light blue on white) > !213 .~~
- [x] ~~settings screen: "change password" button (light blue on white/black) > !213 .~~
- [x] ~~registration screen: "next" button (black text color on blue/gray (disabled) button) > already fixed on current `main`~~
- [ ] registration screen: visual focus indicator on "show/hide password" button (light gray on white)
- [x] ~~registration screen: password strength indicator (light green on white / dark red on black) > !211 .~~
- [x] ~~registration screen: form error color (red on black) > !202 .~~
- [x] ~~message compose screen: send button (light green on white) > !212 .~~
these two issues were post-poned to #364:
- registration screen: disabled "next" button if some of the fields are not properly filled (light gray on white/black)
- settings/change password screen: disabled button (light gray on white)
as well as:
- add contact screen: close button (system-dependant window decoration, so I don't think we can/should do anything about it)https://code.briarproject.org/briar/briar-desktop/-/issues/327Running on ARM2023-04-15T18:55:05ZSebastianRunning on ARMInstructions for running on ARM-based hardware such as PinePhone, Raspberry Pie etc:
Run using `./gradlew run` locally as described in https://code.briarproject.org/briar/briar-desktop#building-and-running
or build a architecture-specif...Instructions for running on ARM-based hardware such as PinePhone, Raspberry Pie etc:
Run using `./gradlew run` locally as described in https://code.briarproject.org/briar/briar-desktop#building-and-running
or build a architecture-specific jar: `./gradlew packageUberJarForCurrentOS`.
If the software crashes, enable software rendering (how to do that?)https://code.briarproject.org/briar/website/-/issues/35Document in FAQ or manual how introductions work exactly2022-02-04T17:48:45ZNicoDocument in FAQ or manual how introductions work exactlyOpen questions among @sebkur, @ialokim and me:
* when do the 3 people involved in an introduction need to be online? i.e., does the introduced contact appear to you even if you and the introduced contact aren't online at the same time?
*...Open questions among @sebkur, @ialokim and me:
* when do the 3 people involved in an introduction need to be online? i.e., does the introduced contact appear to you even if you and the introduced contact aren't online at the same time?
* there's no 48 hours timeout with introductions, right?Desktop 0.2.0NicoNicohttps://code.briarproject.org/briar/public-mesh-research/-/issues/1Research communication via public mesh2023-09-12T12:23:17ZakwizgranResearch communication via public meshDevelop and evaluate one or more concepts for communicating over a "public mesh" (as opposed to Briar's "social mesh", where users only connect to their contacts). A delay-tolerant, publish-subscribe architecture with end-to-end encrypti...Develop and evaluate one or more concepts for communicating over a "public mesh" (as opposed to Briar's "social mesh", where users only connect to their contacts). A delay-tolerant, publish-subscribe architecture with end-to-end encryption is assumed.
Each concept must include solutions for:
* Discovering nearby peers
* Connecting to peers
* Deciding which data to sync with each peer
* Providing an API for user-facing components (e.g. messaging) to insert data into the mesh and be notified when relevant data is received
Concepts must be suitable for use on unrooted Android devices (taking into account current restrictions on device discovery). Ideally concepts should also be suitable for use on iOS and allow communication between Android and iOS.
Identify and evaluate any risks of passive information leaks or active attacks. Evaluate performance taking Briar's "social mesh" as a baseline.Public mesh research2023-04-30https://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/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.https://code.briarproject.org/briar/social-mesh-research/-/issues/7Select the design candidates that will be simulated2023-08-28T16:04:17ZakwizgranSelect the design candidates that will be simulatedThis should be done on the basis of the initial evaluation (#5).This should be done on the basis of the initial evaluation (#5).https://code.briarproject.org/briar/social-mesh-research/-/issues/6Identify and document the design constraints2023-08-28T16:04:17ZakwizgranIdentify and document the design constraintshttps://code.briarproject.org/briar/social-mesh-research/-/issues/5Carry out and document initial evaluation of design candidates2023-08-28T16:04:17ZakwizgranCarry out and document initial evaluation of design candidatesSome candidates may be ruled out at this stage.
Depends on #1, #3, #6.Some candidates may be ruled out at this stage.
Depends on #1, #3, #6.https://code.briarproject.org/briar/social-mesh-research/-/issues/4Identify and document the design candidates2023-08-28T16:04:17ZakwizgranIdentify and document the design candidateshttps://code.briarproject.org/briar/social-mesh-research/-/issues/3Decide and document evaluation criteria for design candidates2023-08-28T16:04:18ZakwizgranDecide and document evaluation criteria for design candidates