briar issueshttps://code.briarproject.org/groups/briar/-/issues2022-02-04T17:48:45Zhttps://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/-/issues/1817Research communication via public mesh2022-07-20T10:38:58ZakwizgranResearch 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/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/-/issues/2180Design sync client for mailbox properties2022-04-01T13:18:12ZakwizgranDesign sync client for mailbox propertiesDesign a BSP client for syncing mailbox properties (onion address, auth token, incoming and outgoing folder IDs) between contacts. Unlike the transport properties client we want to send different properties to each contact, so it probabl...Design a BSP client for syncing mailbox properties (onion address, auth token, incoming and outgoing folder IDs) between contacts. Unlike the transport properties client we want to send different properties to each contact, so it probably makes sense to use a separate client, but the basic design can be similar (include a version number in each update, delete all but the latest update from each contact).Mailbox: Sync mailbox propertiesDaniel LublinDaniel Lublinhttps://code.briarproject.org/briar/briar-gtk/-/issues/88Revise contributing guide2021-02-04T09:28:42ZNicoRevise contributing guideThere's at least an error with the `component` thing in merge requests. Might have other issues, too.There's at least an error with the `component` thing in merge requests. Might have other issues, too.GTK 0.1.0-beta3NicoNicohttps://code.briarproject.org/briar/briar/-/issues/1577Some questions about Headless API2020-10-31T12:52:40ZNicoSome questions about Headless API@grote asked me to read carefully over the [Briar Headless API documentation](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md) in order to find things that needs more explanation. And I do have some ...@grote asked me to read carefully over the [Briar Headless API documentation](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md) in order to find things that needs more explanation. And I do have some questions that I'll copy-paste from our chat into separate discussion boxes below. With these questions, I hope to make clear in how far the documentation needs to be improved in order to make it easier for third-party developers to implement the API.Headless MVPNicoNicohttps://code.briarproject.org/briar/briar/-/issues/1271Update manual for Tor bridges2018-10-09T14:10:00ZakwizgranUpdate manual for Tor bridgesSubtask of #647.Subtask of #647.Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1264Document Tor's behaviour in all Android power management states2019-01-30T16:39:56ZakwizgranDocument Tor's behaviour in all Android power management statesSubtask of #1263.Subtask of #1263.Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1262Update manual for power management improvements2019-02-21T10:33:59ZakwizgranUpdate manual for power management improvementsSubtask of #1260.Subtask of #1260.Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1253Update manual for dark theme2018-09-03T18:53:45ZakwizgranUpdate manual for dark themeSubtask of #976.Subtask of #976.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1249Update manual for account sign-in improvements2018-09-17T16:10:26ZakwizgranUpdate manual for account sign-in improvementsSubtask of #1245.Subtask of #1245.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1236Update manual for adding contacts remotely2019-10-09T12:16:03ZakwizgranUpdate manual for adding contacts remotelySubtask of #1230.Subtask of #1230.Android 1.2Torsten GroteTorsten Grotehttps://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/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/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.