briar issueshttps://code.briarproject.org/groups/briar/-/issues2020-11-21T20:34:00Zhttps://code.briarproject.org/briar/briar/-/issues/16Pairing confirmation pops up when first connecting via Bluetooth2020-11-21T20:34:00ZakwizgranPairing confirmation pops up when first connecting via BluetoothWhen the HTC Wildfire S first connects to another device via Bluetooth (while adding a contact), a dialog pops up asking the user to confirm pairing with the other device. If the user refuses the pairing, the devices fail to connect.
Th...When the HTC Wildfire S first connects to another device via Bluetooth (while adding a contact), a dialog pops up asking the user to confirm pairing with the other device. If the user refuses the pairing, the devices fail to connect.
This device uses the new API -- `BluetoothAdapter.listenUsingInsecureRfcommWithServiceRecord()` and `BluetoothDevice.createInsecureRfcommSocketToServiceRecord()` -- which should not require confirmation.https://code.briarproject.org/briar/briar/-/issues/14Sony LiveWare pops up when first connecting via Bluetooth2020-11-21T20:34:24ZakwizgranSony LiveWare pops up when first connecting via BluetoothThe LiveWare Manager app bundled with the Sony Xperia tipo pops up when first connecting to a new device via Bluetooth while adding a contact. It asks which app should be started when the device is connected.
This doesn't happen every t...The LiveWare Manager app bundled with the Sony Xperia tipo pops up when first connecting to a new device via Bluetooth while adding a contact. It asks which app should be started when the device is connected.
This doesn't happen every time - it may depend on whether the connection is incoming or outgoing, or there may be a cache of known devices that's cleared when the phone is restarted or reset.
![Screenshot_2014-10-06-13-12-40](/uploads/b94df454ee369fd23adb2544d37ae3b7/Screenshot_2014-10-06-13-12-40.png)https://code.briarproject.org/briar/briar/-/issues/12Timeout while adding a contact2020-11-21T20:35:27ZakwizgranTimeout while adding a contactSeveral users reported timeouts while adding contacts. The problem seemed to be more severe in larger groups. One user experienced a long series of timeouts before successfully adding a contact.
If this problem is caused in some cases b...Several users reported timeouts while adding contacts. The problem seemed to be more severe in larger groups. One user experienced a long series of timeouts before successfully adding a contact.
If this problem is caused in some cases by congestion at the Bluetooth MAC layer, we may be able to mitigate it by keeping a cache of discovered devices and trying to connect to them before performing discovery. If a group of users are adding each other as contacts, the first discovery by each user should put most of the other users' devices in the cache.
If this problem is caused in some cases by poorly performing Bluetooth drivers or hardware, we may not be able to work around it at the application level.
This could be caused by the limit of eight devices (one master and seven slaves) in a Bluetooth piconet. If so, closing any open Bluetooth connections before attempting a new connection may help.https://code.briarproject.org/briar/briar/-/issues/9Support copy and paste2022-10-27T21:53:59ZakwizgranSupport copy and pastehttps://code.briarproject.org/briar/briar/-/issues/6Message delays are confusing for users2020-11-21T20:37:12ZakwizgranMessage delays are confusing for usersFeedback from user testing:
Case 1: "From one of the participants of our test:
They had bluetooth and WiFi transports available (3 parties in close proximity). It seemed messages were being sent via mobile data as opposed to bluetooth....Feedback from user testing:
Case 1: "From one of the participants of our test:
They had bluetooth and WiFi transports available (3 parties in close proximity). It seemed messages were being sent via mobile data as opposed to bluetooth. This resulted in sometimes significant delays being seen in sending/receiving messages. With ancedotal measurement these delays were seen between 2-3 minutes and 9-10 minutes.
The users expected bluetooth to be used (as they were all physically near each other). These delays did not match how people were thinking bluetooth would be "instantaneous" communications.
It did not affect things too much but confused people.
Can we clarify how messages are sent received when there are multiple transports available?"
Case 2: "UserA was waiting outside UserB's house. UserA sent UserB a message and said there was approx a 2 minute delay, using mobile data."
Case 3: "I've been at a meeting today. Have checked Briar this morning and twice during the afternoon but not been signed in at length. I've just received all the messages from today at 22:01ish. Some of which had occured before I signed in earlier so I should have received them then. I imagine that maybe I wasn't signed in long enough to receive the data package. As a Whatsapp user id expect to sign in and within a minute have received all the updates from other people. So the response time for thread updates in one issue."https://code.briarproject.org/briar/briar/-/issues/2Allow existing contacts to be re-added2023-03-15T13:04:32ZakwizgranAllow existing contacts to be re-addedRe-adding an existing contact currently throws a ContactExistsException. But re-adding a contact may be necessary if transport properties get out of sync, making it impossible to connect via BTP. If we re-add a contact we should keep any...Re-adding an existing contact currently throws a ContactExistsException. But re-adding a contact may be necessary if transport properties get out of sync, making it impossible to connect via BTP. If we re-add a contact we should keep any existing private messages and group subscriptions.
If one contact uses the same identity as last time and the other doesn't, they'll disagree about whether it's a re-add, so we can't re-derive the same transport keys. Can we reuse the contact ID (if any), import the new transport properties, delete the old transport keys (if any), and create new transport keys?