briar merge requestshttps://code.briarproject.org/briar/briar/-/merge_requests2021-02-05T13:14:10Zhttps://code.briarproject.org/briar/briar/-/merge_requests/1328Show warning dialog when the expected timer differs from the current timer2021-02-05T13:14:10ZTorsten GroteShow warning dialog when the expected timer differs from the current timerThis MR refactors message sending to return a LiveData that the TextSendController can observe to react to the sending state. The main reason is to be able to reliably catch automatic changes to the auto-delete timer which might surprise...This MR refactors message sending to return a LiveData that the TextSendController can observe to react to the sending state. The main reason is to be able to reliably catch automatic changes to the auto-delete timer which might surprise the user.
Test instructions:
* Add a contact, open private conversation screen and send a message
* Start typing a second message and activate disappearing messages, finish typing the message and send
* check that a warning message appears warning about the changed timer
* Start typing a third message, but don't send
* Let your contact disable disappearing messages and send a message
* Wait for the contact's message to arrive and then send your message
* check that a warning message appears warning about the changed timer
Closes #1864Self-destructing messagesakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/merge_requests/1651Show warning if own mailbox's API version is incompatible2022-06-06T16:23:15ZTorsten GroteShow warning if own mailbox's API version is incompatibleFor now, this very basic and assumes Briar can continue to support old major versions of the mailbox for some time. Also, in core, the version of the mailbox never gets updated and the connectivity check doesn't take new version informat...For now, this very basic and assumes Briar can continue to support old major versions of the mailbox for some time. Also, in core, the version of the mailbox never gets updated and the connectivity check doesn't take new version information into account.
Closes #2319Mailbox: Status UI for Briar apphttps://code.briarproject.org/briar/briar/-/merge_requests/1528Shrink QR code to avoid scrolling2021-08-31T12:21:16ZDaniel LublinShrink QR code to avoid scrollingCloses #2148Closes #2148Install via Bluetooth or Wi-Fihttps://code.briarproject.org/briar/briar/-/merge_requests/1398Simple version of Connect via Bluetooth UI2021-04-21T11:57:59ZTorsten GroteSimple version of Connect via Bluetooth UI![device-2021-04-13-113913](/uploads/085a56e45fa85fe6a5d315f44ddd2e9a/device-2021-04-13-113913.mp4)
Should implement all of #1961 (and more)![device-2021-04-13-113913](/uploads/085a56e45fa85fe6a5d315f44ddd2e9a/device-2021-04-13-113913.mp4)
Should implement all of #1961 (and more)Adapt to changes in the Android platformhttps://code.briarproject.org/briar/briar/-/merge_requests/1512Split ConditionManager into API-specific versions2021-07-26T13:49:24ZSebastianSplit ConditionManager into API-specific versions* On API 29+ we need the location permission to start the hotspot, while
on lower API levels, we don't. In order to handle permissions and
other conditions in a clear manner depending the API level of the
device the app is running ...* On API 29+ we need the location permission to start the hotspot, while
on lower API levels, we don't. In order to handle permissions and
other conditions in a clear manner depending the API level of the
device the app is running on, have separate extensions of the base
ConditionManager class.
* Take special care to handle situations gracefully where the Wifi is
disabled and the user tries to start the hotspot. We cannot simply
rely on Wifi being enabled as a sufficient condition that allows us to
start the hotspot. We need to wait for WifiP2p to be available. While
it is tricky to obtain that state (it involves registering a broadcast
receiver for the WIFI_P2P_STATE_CHANGED_ACTION broadcast, keeping
track of changes there and even then things are still ugly. It can
happen that WifiP2p is available *before* Wifi is. Also it can happen
that WifiP2p never becomes available because some other application
has already opened a hotspot. Instead of checking that state, we now
just try (and retry repeatedly after a delay) to start the hotspot
(and the WifiP2p framework) hoping that is becomes availabe within a
reasonable amount of time after Wifi has been detected to be on.
Currently we try 5 times with a delay of 1 second.
* Improve the behavior of disabling and re-enabling the 'start hotspot'
button, so that it becomes impossible to double-tap it, but still
making sure that the button get re-enabled as soon as the UI is back
in a state where the user should be able to tap the button again.
Closes #2100Install via Bluetooth or Wi-FiTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/merge_requests/1307Store local self-destruct timer duration2020-12-02T13:34:31ZakwizgranStore local self-destruct timer durationThis branch adds methods for storing and retrieving the local self-destruct timer duration. The timer duration is retrieved when sending messages.
Subsequent MRs will ensure that all conversation messages have consistent timestamps, and...This branch adds methods for storing and retrieving the local self-destruct timer duration. The timer duration is retrieved when sending messages.
Subsequent MRs will ensure that all conversation messages have consistent timestamps, and mirror changes in the remote timer duration.
First part of #1832Self-destructing messageshttps://code.briarproject.org/briar/briar/-/merge_requests/1547Store time of last attempted and successful connections to own mailbox2021-11-22T11:09:37ZakwizgranStore time of last attempted and successful connections to own mailboxThis branch stores the time of the last attempted and successful connections to our own mailbox, and the number of attempts since the last success. This information will be used by the mailbox status UI. The number of attempts since the ...This branch stores the time of the last attempted and successful connections to our own mailbox, and the number of attempts since the last success. This information will be used by the mailbox status UI. The number of attempts since the last success can be used for deciding whether to show the "mailbox unreachable" warning.
Closes #2171Mailbox: Status UI for Briar appDaniel LublinDaniel Lublinhttps://code.briarproject.org/briar/briar/-/merge_requests/1800Target SDK 332023-07-03T10:55:48ZTorsten GroteTarget SDK 33Closes #2266 (after review of the open discussions there)Closes #2266 (after review of the open discussions there)https://code.briarproject.org/briar/briar/-/merge_requests/1654Tor reachability monitor2022-06-03T17:08:14ZakwizgranTor reachability monitorThis branch adds a component that monitors the state of the Tor plugin and calls observers when the plugin has been continuously active for 10 minutes. After 10 minutes we assume that our hidden service is reachable and contacts should b...This branch adds a component that monitors the state of the Tor plugin and calls observers when the plugin has been continuously active for 10 minutes. After 10 minutes we assume that our hidden service is reachable and contacts should be able to connect to us directly.
The reachability monitor will be started and destroyed by the mailbox client manager (#2228).
Infrastructure for #2292 and other mailbox workers.Mailbox: Manage mailbox connectionshttps://code.briarproject.org/briar/briar/-/merge_requests/1511Transfer data securely via removable storage2021-07-14T11:23:51ZTorsten GroteTransfer data securely via removable storageThis is a request to merge the feature branch into master.
Puts #1802 ~"S: in QA"This is a request to merge the feature branch into master.
Puts #1802 ~"S: in QA"Transfer content securely via SD cards and USB memory stickshttps://code.briarproject.org/briar/briar/-/merge_requests/1640Troubleshooting wizard for mailbox2022-05-18T17:00:51ZTorsten GroteTroubleshooting wizard for mailboxCloses #2309Closes #2309Mailbox: Status UI for Briar apphttps://code.briarproject.org/briar/briar/-/merge_requests/1752Tweak text for unknown QR code type2022-12-21T12:29:49ZakwizgranTweak text for unknown QR code typeMailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/merge_requests/1302Update blog and forum sharing clients to include self-destruct timers2020-11-30T12:46:33ZakwizgranUpdate blog and forum sharing clients to include self-destruct timersCloses #1830Closes #1830Self-destructing messageshttps://code.briarproject.org/briar/briar/-/merge_requests/1448Update disappearing message bubbles after removing messages2021-05-04T12:38:31ZakwizgranUpdate disappearing message bubbles after removing messagesTest instructions:
* Before building, change disappearing messages timer from DAYS.toMillis(7) to MINUTES.toMillis(1) in AutoDeleteManager.java
* Add two devices (X and Y) as contacts
* Send a message from X to Y
* Enable disappearing me...Test instructions:
* Before building, change disappearing messages timer from DAYS.toMillis(7) to MINUTES.toMillis(1) in AutoDeleteManager.java
* Add two devices (X and Y) as contacts
* Send a message from X to Y
* Enable disappearing messages on X
* Send two disappearing messages from X to Y
* Disable disappearing messages on X
* Send another message from X to Y
* Keep the conversation open and the screen turned on until the messages disappear
* When the first disappearing message disappears, check that the "X's messages will disappear" bubble moves to the second disappearing message
* When the second disappearing message disappears, check that the "X's messages will disappear" and "X's messages will not disappear" bubbles both disappear
Closes #2012Self-destructing messageshttps://code.briarproject.org/briar/briar/-/merge_requests/1300Update introduction client to include a self-destruct timer in each message2020-11-30T12:46:32ZakwizgranUpdate introduction client to include a self-destruct timer in each messageThis branch adds auto-delete timers to the REQUEST, ACCEPT and DECLINE messages of the introduction protocol.
Closes #1829This branch adds auto-delete timers to the REQUEST, ACCEPT and DECLINE messages of the introduction protocol.
Closes #1829Self-destructing messageshttps://code.briarproject.org/briar/briar/-/merge_requests/1453Update MessagesSentEvent to include amount of data sent2021-05-10T11:44:30ZakwizgranUpdate MessagesSentEvent to include amount of data sentCloses #2014Closes #2014Transfer content securely via SD cards and USB memory sticksDaniel LublinDaniel Lublinhttps://code.briarproject.org/briar/briar/-/merge_requests/1299Update messaging client to include a self-destruct timer in each message2020-11-30T12:46:32ZakwizgranUpdate messaging client to include a self-destruct timer in each messageCloses #1828Closes #1828Self-destructing messageshttps://code.briarproject.org/briar/briar/-/merge_requests/1303Update private group sharing client to include a self-destruct timer in each ...2020-11-30T12:46:34ZakwizgranUpdate private group sharing client to include a self-destruct timer in each messageThis branch adds optional self-destruct timers to the INVITE, JOIN and LEAVE messages of the private group invitation protocol. The JOIN and LEAVE messages are used for manually accepting/declining invitations and also for automatically ...This branch adds optional self-destruct timers to the INVITE, JOIN and LEAVE messages of the private group invitation protocol. The JOIN and LEAVE messages are used for manually accepting/declining invitations and also for automatically informing contacts that we've joined or left a group. Thus a JOIN or LEAVE message may be visible in the UI or not, depending on whether it was created manually or automatically. I suggest that we include a self-destruct timer in a JOIN/LEAVE message only if it's going to be visible in the UI. This will be implemented as part of #1832.
Closes #1831Self-destructing messageshttps://code.briarproject.org/briar/briar/-/merge_requests/1317Update profile picture in current chat's app bar2020-12-15T16:24:47ZSebastianUpdate profile picture in current chat's app barCloses #1856Closes #1856Profile pictureshttps://code.briarproject.org/briar/briar/-/merge_requests/1318Update profile pictures in contact list2020-12-16T12:52:20ZSebastianUpdate profile pictures in contact listCloses #1855Closes #1855Profile pictures