briar issueshttps://code.briarproject.org/groups/briar/-/issues2020-11-15T18:06:51Zhttps://code.briarproject.org/briar/briar/-/issues/1615Upgrade process like apt and use torrents2020-11-15T18:06:51ZPratiwirUpgrade process like apt and use torrentsI would like to suggest doing a more modular upgrade process the same way that is used in termux where apt is used to fetch code. Thus Briar could be upgraded piecewise using a cut down version of apt.
I also propose using torrents soft...I would like to suggest doing a more modular upgrade process the same way that is used in termux where apt is used to fetch code. Thus Briar could be upgraded piecewise using a cut down version of apt.
I also propose using torrents software within Briar, as an additional way to fetch and verify any upgrade files, so that play store could become superfluous once the initial install is made. The torrents component could be activated as needed and used to voluntarily help distribute system files to other users.
I am suggesting this because other apps have this problem of constantly having to uograde. To do this anonymously needs f-droid or yalp store over tor, but the downloads are slow and have a high failure rate, needing to keep restart the download when secure communications apps are being fetched.
It is imho key to have anonymous downloads and easy software distribution not subject to packet injection and blocking.https://code.briarproject.org/briar/briar/-/issues/1614Android studio - No dependency for integrity assertion2020-11-16T10:32:41ZjomocuAndroid studio - No dependency for integrity assertionI have finally managed to load the project correctly.
When I open android studio, everything appears right.
**Screenshot:** https://i.imgur.com/0ffGl14.png
But when trying to run the program on the virtual machine it shows me this erro...I have finally managed to load the project correctly.
When I open android studio, everything appears right.
**Screenshot:** https://i.imgur.com/0ffGl14.png
But when trying to run the program on the virtual machine it shows me this error ...
*No dependency for integrity assertion 'com.android.support.test.uiautomator:uiautomator-v18:2.1.3:uiautomator-v18-2.1.3.aar:15e6b3c7104859630bf844e31805aa7cb2eb4b385e6119ab34132c8258eee2c4'*
**Screenshot:** https://i.imgur.com/qMLVVqR.png
I am running the virtual machine "Nexus One API 23", I use android 6 without the api of google play.
Any idea how to solve this?
Thankshttps://code.briarproject.org/briar/briar/-/issues/1613Briar dependency error (Android studio)2020-11-15T18:07:51ZjomocuBriar dependency error (Android studio)Hi, I'm trying to edit and compile briar.
I have imported the project, but it shows the following error.
**ERROR: No dependency for integrity assertion 'cglib:cglib:3.2.0:cglib-3.2.0.jar:adb13bab79712ad6bdf1bd59f2a3918018a8016e722e8a357...Hi, I'm trying to edit and compile briar.
I have imported the project, but it shows the following error.
**ERROR: No dependency for integrity assertion 'cglib:cglib:3.2.0:cglib-3.2.0.jar:adb13bab79712ad6bdf1bd59f2a3918018a8016e722e8a357065afb9e6690861'**
What am I doing wrong?
Thanks greetingshttps://code.briarproject.org/briar/briar/-/issues/1608Can't scan QR code in low light2020-11-15T18:09:33ZakwizgranCan't scan QR code in low lightSome phones can't scan QR codes from screens in low light because the camera automatically adjusts the exposure, making the other phone's screen a white blur. I've seen this before on older phones but assumed it was a dying problem. But ...Some phones can't scan QR codes from screens in low light because the camera automatically adjusts the exposure, making the other phone's screen a white blur. I've seen this before on older phones but assumed it was a dying problem. But the problem also exists on the Honor 8A (Android 9), making it impossible to add contacts between the Honor 8A and the Ascend Y330 in low light. (The Y330's low res screen contributes to the problem; the Honor 8A can scan the Nexus 5's screen in the same lighting conditions, for example.)
We should see whether auto exposure can be disabled, and whether this helps.https://code.briarproject.org/briar/briar/-/issues/1605Allow access to urls with a click2019-06-28T09:28:15ZjomocuAllow access to urls with a clickIt would be great, to support that function, even for special domains (.bit .o among many others)
https://www.opennic.org
regardsIt would be great, to support that function, even for special domains (.bit .o among many others)
https://www.opennic.org
regardshttps://code.briarproject.org/briar/briar/-/issues/1604Briar desktop (Idea)2019-06-28T09:27:21ZjomocuBriar desktop (Idea)It would be great to have "briar desktop" for computers.
Windows, Linux and Mac
RegardsIt would be great to have "briar desktop" for computers.
Windows, Linux and Mac
Regardshttps://code.briarproject.org/briar/briar/-/issues/1603Calls and videocalls (Idea)2019-06-28T10:36:21ZjomocuCalls and videocalls (Idea)I think it would be great to add calls and video calls to the application.
With the possibility of "Compressing data" in mobile data...
Greetings and good projectI think it would be great to add calls and video calls to the application.
With the possibility of "Compressing data" in mobile data...
Greetings and good projecthttps://code.briarproject.org/briar/website/-/issues/13Update screenshots2021-01-15T14:19:48ZakwizgranUpdate screenshotsCleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1600AttachmentRetrieverIntegrationTest fails on emulator2020-11-15T18:13:33ZakwizgranAttachmentRetrieverIntegrationTest fails on emulatorSeveral tests in AttachmentRetrieverIntegrationTest fail on the API 21 emulator. It looks like some of them failed in the original commit of the test (it was called AttachmentControllerTest at the time) and others have been broken by sub...Several tests in AttachmentRetrieverIntegrationTest fail on the API 21 emulator. It looks like some of them failed in the original commit of the test (it was called AttachmentControllerTest at the time) and others have been broken by subsequent changes.
The failures from the original commit all seem to involve the same issue: the file extension being `jpeg` rather than `jpg`. I guess the platform's behaviour probably changed some time between API 21 and now, and it doesn't seem likely to cause problems beyond the test failure.
```
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.conversation.AttachmentControllerTest.testSmallJpegImageHealsWrongMimeType(AttachmentControllerTest.java:125)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.conversation.AttachmentControllerTest.testHighError(AttachmentControllerTest.java:317)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.conversation.AttachmentControllerTest.testWideError(AttachmentControllerTest.java:332)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.conversation.AttachmentControllerTest.testNoSizeJpeg(AttachmentControllerTest.java:71)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.conversation.AttachmentControllerTest.testSmallJpegImage(AttachmentControllerTest.java:109)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.conversation.AttachmentControllerTest.testBigJpegImage(AttachmentControllerTest.java:141)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.conversation.AttachmentControllerTest.testLottaPixels(AttachmentControllerTest.java:203)
```
The failures on current master involve content types as well as file extensions.
```
org.junit.ComparisonFailure: expected:<image/[gif]> but was:<image/[jpeg]>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testGimpCrash(AttachmentRetrieverIntegrationTest.java:156)
...
org.junit.ComparisonFailure: expected:<image/[gif]> but was:<image/[jpeg]>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testUberGif(AttachmentRetrieverIntegrationTest.java:111)
...
org.junit.ComparisonFailure: expected:<image/[pn]g> but was:<image/[jpe]g>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testImageIoCrash(AttachmentRetrieverIntegrationTest.java:141)
...
org.junit.ComparisonFailure: expected:<image/[gif]> but was:<image/[jpeg]>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testOptiPngAfl(AttachmentRetrieverIntegrationTest.java:171)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testHighError(AttachmentRetrieverIntegrationTest.java:241)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testWideError(AttachmentRetrieverIntegrationTest.java:256)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testSmallJpegImage(AttachmentRetrieverIntegrationTest.java:65)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testBigJpegImage(AttachmentRetrieverIntegrationTest.java:81)
...
org.junit.ComparisonFailure: expected:<jp[]g> but was:<jp[e]g>
at org.briarproject.briar.android.attachment.AttachmentRetrieverIntegrationTest.testLottaPixels(AttachmentRetrieverIntegrationTest.java:127)
```https://code.briarproject.org/briar/briar/-/issues/1599[headless] obsolete dependency integrity assertion2019-08-14T14:22:42Ziwakeh[headless] obsolete dependency integrity assertion[Line 61](https://code.briarproject.org/briar/briar/blob/master/briar-headless/witness.gradle#L61) in briar-headless/witness.gradle seems redundant.[Line 61](https://code.briarproject.org/briar/briar/blob/master/briar-headless/witness.gradle#L61) in briar-headless/witness.gradle seems redundant.https://code.briarproject.org/briar/briar/-/issues/1598headless: add RSS feed functionality2019-08-08T12:58:09Ziwakehheadless: add RSS feed functionalityIt would be great to have the RSS feed functionality in briar-headless.
(I could help with the implementation with a little info about how to approach this best.)It would be great to have the RSS feed functionality in briar-headless.
(I could help with the implementation with a little info about how to approach this best.)https://code.briarproject.org/briar/briar/-/issues/1597make headless module start w/o running Tor2019-07-14T15:57:14Ziwakehmake headless module start w/o running TorIs there a way to reuse an existing Tor connection and avoid starting a Tor instance when running the headless jar?
Or, simply run it w/o Tor?Is there a way to reuse an existing Tor connection and avoid starting a Tor instance when running the headless jar?
Or, simply run it w/o Tor?https://code.briarproject.org/briar/briar/-/issues/1596Make migrations idempotent where possible2020-11-15T18:14:12ZakwizgranMake migrations idempotent where possibleThe database migrations use data definition commands (`ALTER TABLE`, etc) that H2 commits automatically as soon as they're executed, even though we execute the commands within a transaction. If a crash happens during a migration, the DB ...The database migrations use data definition commands (`ALTER TABLE`, etc) that H2 commits automatically as soon as they're executed, even though we execute the commands within a transaction. If a crash happens during a migration, the DB may be left in a state where the migration has been partially applied. If the data definition commands aren't idempotent then subsequent attempts to apply the migration will fail, making it impossible to complete the migration and open the DB.
Where possible we should use data definition commands that are idempotent. For example, `DELETE COLUMN` should be `DELETE COLUMN IF EXISTS`, `CREATE COLUMN` should be `CREATE COLUMN IF NOT EXISTS`, etc.https://code.briarproject.org/briar/briar/-/issues/1589Use consistent scroll behaviour across the app2021-12-21T23:12:35ZakwizgranUse consistent scroll behaviour across the appFollowing the discussion on #713 and other tickets listed below, let's use consistent scroll behaviour across the app.
Related to #713, #872, #1073, #1192, #1200, #1361, #1337, #1467, #1493.Following the discussion on #713 and other tickets listed below, let's use consistent scroll behaviour across the app.
Related to #713, #872, #1073, #1192, #1200, #1361, #1337, #1467, #1493.https://code.briarproject.org/briar/briar/-/issues/1588New setting: Time window / Interval in which Briar goes online2022-01-04T16:11:37ZmicressorNew setting: Time window / Interval in which Briar goes onlineI want a way to set Briar so that the app connects at an interval of X for Y minutes to synchronize messages.
As a second possibility, a period where Briar connects to synchronize messages. For example between X and Y o'clock every day....I want a way to set Briar so that the app connects at an interval of X for Y minutes to synchronize messages.
As a second possibility, a period where Briar connects to synchronize messages. For example between X and Y o'clock every day.
The idea behind it is to make online time more effective due to the high battery consumption. Two users could agree to configure their Briar Apps between X and Y to go online and synchronize messages.https://code.briarproject.org/briar/briar/-/issues/1582Pending contact snackbar and add contact FAB are sometimes displaced2022-04-19T11:29:51ZakwizgranPending contact snackbar and add contact FAB are sometimes displacedThe pending contact snackbar sometimes appears in the wrong place, with a blank space below it and overlapping the FAB. After the snackbar is hidden, the FAB doesn't always return to the right position.
![device-2019-06-07-162517](/uplo...The pending contact snackbar sometimes appears in the wrong place, with a blank space below it and overlapping the FAB. After the snackbar is hidden, the FAB doesn't always return to the right position.
![device-2019-06-07-162517](/uploads/9109a6a1d3e0fbeccdb1e25d1c5796b7/device-2019-06-07-162517.png)
![device-2019-06-07-162537](/uploads/01cc37afca368254ff312281f3f8d992/device-2019-06-07-162537.png)
I've seen the first problem on the Huawei Ascend Y330 (Android 4.2.2) and the Vivo Y11 (Android 4.4.4). I've seen the second problem on those phones and also the Honor 8A (Android 9).https://code.briarproject.org/briar/briar/-/issues/1581Add pending contact via ENTER or IME action2020-11-15T18:20:32ZTorsten GroteAdd pending contact via ENTER or IME actionWhen entering the nickname for a pending contact pressing enter or the Go IME action in the soft keyboard should be equivalent to pressing the button.When entering the nickname for a pending contact pressing enter or the Go IME action in the soft keyboard should be equivalent to pressing the button.https://code.briarproject.org/briar/briar/-/issues/1580Warn when adding pending contact with Tor disabled2019-06-18T09:54:35ZTorsten GroteWarn when adding pending contact with Tor disabledAdding contacts remotely won't work with the Tor plugin not running. We should notify contacts when that is the case, so they can go online or enable Tor.Adding contacts remotely won't work with the Tor plugin not running. We should notify contacts when that is the case, so they can go online or enable Tor.Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1578Improve structure of Briar Headless API documentation2021-03-22T10:52:52ZNicoImprove structure of Briar Headless API documentationCurrently, the documentation for the API is directly written into [its readme file](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md). That's fine for the beginning, [I was even able to build a first ...Currently, the documentation for the API is directly written into [its readme file](https://code.briarproject.org/briar/briar/blob/release-1.1.7/briar-headless/README.md). That's fine for the beginning, [I was even able to build a first prototype with it](https://nico.dorfbrunnen.eu/posts/2019/briar-first-demo/).
However, I suggest to improve the structure of the documentation by moving it into a separate repository. My suggestion was to create a Hugo page with a docs theme (or some other static site generator) at docs.briarproject.org.
@grote's response to this was (loosely translated by me): "Best to make the documentation directly into the code with swagger"
My response to this now: OK, we can do this, but I don't know how much sense it makes to put a lot of basic explanations into code. E.g. all the valuable information collected in https://code.briarproject.org/briar/briar/issues/1577.
**Update:** I agree with Torsten that it's best to generate the documentation from code. That's what I do with [`briar_wrapper`](https://code.briarproject.org/briar/python-briar-wrapper), too, at https://wrapper.docs.briarproject.org/ and the API's docs can be hosted at https://api.docs.briarproject.org/, imho.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1575exclude the redundant rome-utils jar from being packaged2019-08-20T09:03:04Ziwakehexclude the redundant rome-utils jar from being packagedPlease, see comment below.Please, see comment below.