briar issueshttps://code.briarproject.org/groups/briar/-/issues2022-05-27T12:03:12Zhttps://code.briarproject.org/briar/briar-mailbox/-/issues/125Allow contacts to call status endpoint2022-05-27T12:03:12ZakwizgranAllow contacts to call status endpointTo reduce the cost of connectivity checks, let's make the status endpoint available to contacts and not return any data from it now or in the future.
If we want the owner to be able to access more information about the mailbox's status ...To reduce the cost of connectivity checks, let's make the status endpoint available to contacts and not return any data from it now or in the future.
If we want the owner to be able to access more information about the mailbox's status (eg amount of data waiting to be downloaded) then let's create a new endpoint when the time comes.Mailbox: Manage mailbox connectionsakwizgranakwizgranhttps://code.briarproject.org/briar/briar-mailbox/-/issues/124Handle Huawei and Xiaomi auto-start restrictions2023-08-28T16:01:38ZTorsten GroteHandle Huawei and Xiaomi auto-start restrictionsHuawei has a `StartupManager` where the user needs to allow the app to start: https://stackoverflow.com/a/43914328/4856311
For Xiaomi MIUI there's even a library to check autostart permissions: https://github.com/XomaDev/MIUI-autostart ...Huawei has a `StartupManager` where the user needs to allow the app to start: https://stackoverflow.com/a/43914328/4856311
For Xiaomi MIUI there's even a library to check autostart permissions: https://github.com/XomaDev/MIUI-autostart It seems to use pre-built jars though
If the library isn't helpful, maybe we can bring the user as close to the right screen as possible.
The other vendors preventing auto-start have way smaller market share, maybe not worth dealing with those as well?https://code.briarproject.org/briar/dont-kill-me-lib/-/issues/2Research whether interpolating app names into library strings would cause loc...2022-05-05T16:03:09ZakwizgranResearch whether interpolating app names into library strings would cause localisation issueshttps://code.briarproject.org/briar/briar/-/merge_requests/1636#note_65779https://code.briarproject.org/briar/briar/-/merge_requests/1636#note_65779https://code.briarproject.org/briar/briar-mailbox/-/issues/116Usability testing for Mailbox app2022-11-30T11:05:08ZakwizgranUsability testing for Mailbox appAfter setup and pairing (briar#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use t...After setup and pairing (briar#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use the stop, restart and unlink actions.Mailbox: Usability testingRenata GegajRenata Gegajhttps://code.briarproject.org/briar/briar/-/issues/2316Usability testing for Mailbox app2023-01-19T13:03:49ZakwizgranUsability testing for Mailbox appAfter setup and pairing (#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use the st...After setup and pairing (#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use the stop, restart and unlink actions.Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2315Usability testing for mailbox setup and pairing2022-11-29T14:07:35ZakwizgranUsability testing for mailbox setup and pairingTest whether users understand that the Mailbox app needs to be installed on a separate device, and whether they're able to set up the Mailbox app and pair it with Briar.Test whether users understand that the Mailbox app needs to be installed on a separate device, and whether they're able to set up the Mailbox app and pair it with Briar.Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2314Usability testing for mailbox connection issues2022-11-29T14:08:07ZakwizgranUsability testing for mailbox connection issuesTest that users understand Briar's mailbox status screen (#2172) and can use it to check whether the mailbox is reachable. Test that users understand the UX that warns about the mailbox being repeatedly unreachable (#2175), and that they...Test that users understand Briar's mailbox status screen (#2172) and can use it to check whether the mailbox is reachable. Test that users understand the UX that warns about the mailbox being repeatedly unreachable (#2175), and that they can use the troubleshooting wizard to resolve issues (#2309).Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2311Remind user to wipe mailbox if it's unreachable when unpairing2022-05-02T16:06:29ZakwizgranRemind user to wipe mailbox if it's unreachable when unpairingIf we fail to tell the mailbox to wipe itself when unpairing, remind the user that they should wipe the mailbox next time they have access to it.If we fail to tell the mailbox to wipe itself when unpairing, remind the user that they should wipe the mailbox next time they have access to it.Mailbox: UnpairingTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/105Limit the size of uploaded files2022-07-13T11:13:19ZakwizgranLimit the size of uploaded filesThe mailbox shouldn't allow clients to upload files larger than 1 MiB.The mailbox shouldn't allow clients to upload files larger than 1 MiB.Mailbox: File management APITorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2309Troubleshooting wizard for own mailbox being unreachable2022-05-18T17:02:05ZakwizgranTroubleshooting wizard for own mailbox being unreachableDesign and implement a troubleshooting wizard to guide the user through the steps of diagnosing why their own mailbox is unreachable and fixing the problem.
The wizard will be reachable from the mailbox status page (#2172) when automati...Design and implement a troubleshooting wizard to guide the user through the steps of diagnosing why their own mailbox is unreachable and fixing the problem.
The wizard will be reachable from the mailbox status page (#2172) when automatic reachability checks repeatedly fail, or when the user triggers a manual reachability check which fails.
The UI for warning the user that their mailbox is unreachable (#2175) will guide the user to the status page where they'll be able to use the wizard.Mailbox: Status UI for Briar appTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2302Update contacts about change in mailbox versions that our mailbox (server) su...2022-08-16T13:49:46ZDaniel LublinUpdate contacts about change in mailbox versions that our mailbox (server) supports
When we connect to the Mailbox, we should get the fresh list of mailbox api versions that it supports. Then check it against the latest mailbox properties update sent to each contact, and send a new update if the serverSupports doesn't ...
When we connect to the Mailbox, we should get the fresh list of mailbox api versions that it supports. Then check it against the latest mailbox properties update sent to each contact, and send a new update if the serverSupports doesn't match.
Depends on https://code.briarproject.org/briar/briar/-/issues/2299 https://code.briarproject.org/briar/briar/-/issues/2261 https://code.briarproject.org/briar/briar/-/issues/2290Mailbox: Sync mailbox propertiesakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2301Update contacts about change in mailbox versions that client supports2022-05-19T12:17:40ZDaniel LublinUpdate contacts about change in mailbox versions that client supportsOn startup we should compare the mailbox versions that we support against the latest mailbox properties update sent to each contact. For each contact which doesn't match, we need to send them an update with the new clientSupports.
Depen...On startup we should compare the mailbox versions that we support against the latest mailbox properties update sent to each contact. For each contact which doesn't match, we need to send them an update with the new clientSupports.
Depends on https://code.briarproject.org/briar/briar/-/issues/2261Mailbox: Sync mailbox propertiesDaniel LublinDaniel Lublinhttps://code.briarproject.org/briar/briar/-/issues/2300Show more information about startup failures2022-04-08T12:33:12ZakwizgranShow more information about startup failuresRecently we've had several reports of corrupt databases (StartResult#DB_ERROR). Because these errors prevent the app from starting, we can't use crash reports or user feedback to learn about the cause.
We should expose more information ...Recently we've had several reports of corrupt databases (StartResult#DB_ERROR). Because these errors prevent the app from starting, we can't use crash reports or user feedback to learn about the cause.
We should expose more information about startup failures in the UI. This will involve returning the information from LifecycleManager#startService() and then attaching it to the intent that launches StartupFailureActivity. StartupFailureActivity should allow the user to copy the information so they can send it to us.Android 1.4https://code.briarproject.org/briar/briar/-/issues/2299Method for fetching mailbox's supported API versions2022-05-18T12:19:07ZakwizgranMethod for fetching mailbox's supported API versionsDepends on briar-mailbox#103.Depends on briar-mailbox#103.MailboxDaniel LublinDaniel Lublinhttps://code.briarproject.org/briar/briar-mailbox/-/issues/115Fetch and store mailbox's supported API versions when pairing mailbox2022-04-29T13:21:06ZakwizgranFetch and store mailbox's supported API versions when pairing mailboxDepends on briar-mailbox#104.Depends on briar-mailbox#104.Mailbox: PairingDaniel LublinDaniel Lublinhttps://code.briarproject.org/briar/briar/-/issues/2298Fetch and store mailbox's supported API versions when pairing mailbox2022-05-16T13:59:54ZakwizgranFetch and store mailbox's supported API versions when pairing mailboxDepends on briar-mailbox#104.Depends on briar-mailbox#104.Mailbox: PairingDaniel LublinDaniel Lublinhttps://code.briarproject.org/briar/briar-mailbox/-/issues/104Include supported API versions in pairing response2022-07-13T11:14:30ZakwizgranInclude supported API versions in pairing responseUpdate the pairing endpoint to return the API versions supported by the mailbox, as a list of (major, minor) pairs.Update the pairing endpoint to return the API versions supported by the mailbox, as a list of (major, minor) pairs.Mailbox: PairingSebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/103API endpoint for getting the API versions supported by the mailbox2022-07-13T11:14:54ZakwizgranAPI endpoint for getting the API versions supported by the mailboxThe endpoint should return a list of (major, minor) pairs.The endpoint should return a list of (major, minor) pairs.MailboxSebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2297Adapt status screen when Briar is not connected to Tor2022-11-23T11:48:47ZTorsten GroteAdapt status screen when Briar is not connected to TorWe should track the Briar device's connectivity and show an appropriate status maybe similar to the screen that we show when we couldn't reach the mailbox for some time.
Related to #2175We should track the Briar device's connectivity and show an appropriate status maybe similar to the screen that we show when we couldn't reach the mailbox for some time.
Related to #2175Mailbox: Status UI for Briar appTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2296Defer marking messages as sent/acked until file is uploaded2022-05-16T14:00:06ZakwizgranDefer marking messages as sent/acked until file is uploadedWhen sending data via a mailbox, we should defer marking messages as sent/acked until the file containing the encrypted data has been successfully uploaded to the mailbox.
This complicates the sync layer a bit, but it means we don't hav...When sending data via a mailbox, we should defer marking messages as sent/acked until the file containing the encrypted data has been successfully uploaded to the mailbox.
This complicates the sync layer a bit, but it means we don't have to keep persistent records of sent/acked messages in case of a crash (#2226), or of files awaiting upload in case of a crash or a connectivity loss (#2230), so the design is simpler overall.
When the sync layer is writing messages and acks for a mailbox session, instead of recording the sent/acked message IDs in the DB it should record them via a deferred send handler. This handler will be provided by the upload worker that will subsequently upload the file (#2291). If the upload is successful, the worker will then use the IDs recorded by the handler to mark the messages as sent/acked in the DB.
This approach relies on the fact that there will be one upload worker per contact, and thus messages that have been sent/acked but not yet marked as such in the DB will not be sent/acked concurrently in another mailbox session. (They may be sent/acked concurrently in another session via a low-latency transport, but this is what we want to happen if a low-latency connection becomes available during a mailbox upload.)
This ticket replaces #2226 and #2230, which unfortunately have already been implemented.Mailbox: Manage mailbox connectionsakwizgranakwizgran