briar issueshttps://code.briarproject.org/briar/briar/-/issues2017-07-07T17:43:18Zhttps://code.briarproject.org/briar/briar/-/issues/977Crash when opening a blog2017-07-07T17:43:18ZakwizgranCrash when opening a blogAn anonymous user reported the following crash with Briar 0.13-alpha8 (an old build, so it may be fixed already):
```
java.lang.IllegalArgumentException
at org.briarproject.briar.sharing.SharingManagerImpl.respondToInvitation(Sh...An anonymous user reported the following crash with Briar 0.13-alpha8 (an old build, so it may be fixed already):
```
java.lang.IllegalArgumentException
at org.briarproject.briar.sharing.SharingManagerImpl.respondToInvitation(SharingManagerImpl.java:271)
at org.briarproject.briar.android.contact.ConversationActivity.respondToBlogRequest(ConversationActivity.java:1030)
at org.briarproject.briar.android.contact.ConversationActivity.access$3100(ConversationActivity.java:118)
at org.briarproject.briar.android.contact.ConversationActivity$26.run(ConversationActivity.java:969)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
```
"Crashed opening a Briar blog (RSS repost) shared via chat."
Android 7.1.2, Briar commit ID 7929ba9.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/976Dark theme2019-04-25T09:18:03ZakwizgranDark themeA user asked for a dark theme.A user asked for a dark theme.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/975Load group item perspective before creating the Items2020-11-19T15:06:22ZJulian DehmLoad group item perspective before creating the ItemsCurrently, the perspective/creator of a group is loaded concurrently with the items. If the items are loaded before the creator, the perspective will be displayed wrongly (race condition).
Quote from @grote
>If I remember correctly, i...Currently, the perspective/creator of a group is loaded concurrently with the items. If the items are loaded before the creator, the perspective will be displayed wrongly (race condition).
Quote from @grote
>If I remember correctly, it would be better to change things so the perspective for the messages is known before they are created and then it can be passed to the message constructor instead of dynamically changing the adapter. Since this code is shared with forums, it might not be a trivial change though.
(see !532 for the initial discussion)https://code.briarproject.org/briar/briar/-/issues/974Show Onboarding for new Forums and Groups2020-11-19T15:07:21ZTorsten GroteShow Onboarding for new Forums and GroupsWhen a user first created a forum or a private group, we should show an onboarding screen that includes and action to open the sharing/invite screen.When a user first created a forum or a private group, we should show an onboarding screen that includes and action to open the sharing/invite screen.https://code.briarproject.org/briar/briar/-/issues/973Add 'Select All' Button to Sharing Screens2020-11-15T10:20:33ZTorsten GroteAdd 'Select All' Button to Sharing ScreensMessages traversal in a social graph improves with each added share relationship between contacts. This is especially true for forums, but maybe also blogs and (reveal contacts of) private groups. In order to encourage sharing, I propose...Messages traversal in a social graph improves with each added share relationship between contacts. This is especially true for forums, but maybe also blogs and (reveal contacts of) private groups. In order to encourage sharing, I propose to add a "select all" button to the respective sharing/reveal screens that selects all selectable contacts and still allows the user to unselect individual contacts before proceeding.https://code.briarproject.org/briar/briar/-/issues/972Allow user to choose security profile2022-10-27T17:43:53ZTorsten GroteAllow user to choose security profileThis is an idea for how to make Briar easier to use: When the user creates her account, we could ask the user to choose one of three security options: low, medium and high security (that come with a description about what they mean exact...This is an idea for how to make Briar easier to use: When the user creates her account, we could ask the user to choose one of three security options: low, medium and high security (that come with a description about what they mean exactly).
Based on what the user chooses, we can adapt certain settings or simplify certain things, so it gets easier to use. For example, if the user chooses medium security we could show private notifications on the lock screen. If they chose low, we could even show the content of messages on the lock screen (crazy, I know). In that case, we could also reveal contacts by default in private groups, for example. If a high security profile has been choose, we do not show any notifications on the lock screen and we display a warning before clicked links are opened. The latter warning would not be shown on a low security profile.
The idea is that Briar would be a useful and valuable tool also for users with lower security but higher convenience requirements.
**Addition from #2138 on 26th of July 2021 by @nicoalt:**
With the increased interest in disaster communication and the upcoming research on [multi-hop social mesh](https://code.briarproject.org/briar/briar/-/issues/1816) and [public mesh](https://code.briarproject.org/briar/briar/-/issues/1817), it might be cool if users could specify their security settings in Briar, similar to [Tor Browser's security settings](https://tb-manual.torproject.org/security-settings/). Tor Browser's settings could translate to Briar like this:
* Standard (I would rather call it "disaster" or "insecure"): public mesh
* Safer: multi-hop social mesh
* Safest: single-hop social mesh like at the moment
![Tor Browser's security settings screenshot](/uploads/0cb63741449cdaebc37c487fad810d67/security-settings-safest.png)
I can see, though, that this is both difficult to implement and difficult to understand for users, but I'm still curious what UX experts like @elioqoshi think about it. If we don't do security settings but want to provide a solution with public mesh, I think forking Briar is the only viable alternative we have.https://code.briarproject.org/briar/briar/-/issues/971Detect and report Tor crashes2022-07-20T10:38:39ZakwizgranDetect and report Tor crasheshttps://code.briarproject.org/briar/briar/-/issues/970Settings title cut/ellipsized2017-07-03T14:20:23ZJulian DehmSettings title cut/ellipsizedThe german translations for the notification settings exceed the display size on some phones.
<img src="https://code.briarproject.org/goapunk/briar/raw/fileStorage/screens/Settings-translation.png" width="256">
We should change the ti...The german translations for the notification settings exceed the display size on some phones.
<img src="https://code.briarproject.org/goapunk/briar/raw/fileStorage/screens/Settings-translation.png" width="256">
We should change the title to something more concise and provide an explanation in the summary field.Julian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/969Galaxy S3 can not send message in private conversation2017-07-03T15:42:17ZTorsten GroteGalaxy S3 can not send message in private conversationDuring a recent user test, one of the testers was unable to send private messages. Clicking the send button did just not work. The workaround was to close the softkeyboard. Then, the send button worked.
Maybe related to our tap jacking ...During a recent user test, one of the testers was unable to send private messages. Clicking the send button did just not work. The workaround was to close the softkeyboard. Then, the send button worked.
Maybe related to our tap jacking protection?https://code.briarproject.org/briar/briar/-/issues/968H2 crashes on Android 4.0.42017-07-03T14:20:22ZakwizgranH2 crashes on Android 4.0.4Briar fails to start on the Sony Xperia Tipo (Android 4.0.4) because H2 crashes with the following stacktrace:
```
06-30 09:51:48.069 2888-3099/org.briarproject.briar E/ACRA: ACRA caught a NoClassDefFoundError for org.briarproject.briar
...Briar fails to start on the Sony Xperia Tipo (Android 4.0.4) because H2 crashes with the following stacktrace:
```
06-30 09:51:48.069 2888-3099/org.briarproject.briar E/ACRA: ACRA caught a NoClassDefFoundError for org.briarproject.briar
java.lang.NoClassDefFoundError: java.util.concurrent.ThreadLocalRandom
at org.h2.util.MathUtils.randomBytes(MathUtils.java:290)
at org.h2.engine.User.setUserPasswordHash(User.java:71)
at org.h2.engine.Engine.openSession(Engine.java:72)
at org.h2.engine.Engine.openSession(Engine.java:176)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)
at org.h2.engine.Engine.createSession(Engine.java:137)
at org.h2.engine.Engine.createSession(Engine.java:27)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)
at org.h2.Driver.connect(Driver.java:69)
at java.sql.DriverManager.getConnection(DriverManager.java:175)
at org.briarproject.bramble.db.H2Database.createConnection(H2Database.java:93)
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:364)
at org.briarproject.bramble.db.JdbcDatabase.open(JdbcDatabase.java:271)
at org.briarproject.bramble.db.H2Database.open(H2Database.java:46)
at org.briarproject.bramble.db.DatabaseComponentImpl.open(DatabaseComponentImpl.java:117)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.java:122)
at org.briarproject.briar.android.BriarService$1.run(BriarService.java:98)
```
It looks like the recent H2 upgrade has introduce a dependency on a newer version of Java.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/967Tap target didn't fully expand2018-06-11T11:29:59ZakwizgranTap target didn't fully expandThe tap target failed to expand to its full size, causing the text to be overlayed on other elements. This happened on a Galaxy Nexus running Android 6.0.1/LineageOS 13.0.The tap target failed to expand to its full size, causing the text to be overlayed on other elements. This happened on a Galaxy Nexus running Android 6.0.1/LineageOS 13.0.https://code.briarproject.org/briar/briar/-/issues/966Sharing contact's blog fails with DbException2017-07-07T14:23:49ZakwizgranSharing contact's blog fails with DbExceptionLooks like this may have the same cause as #962.
```
06-01 02:02:06.140 25336-25418/org.briarproject.briar W/tSelectorControllerImpl: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at...Looks like this may have the same cause as #962.
```
06-01 02:02:06.140 25336-25418/org.briarproject.briar W/tSelectorControllerImpl: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:162)
at org.briarproject.briar.sharing.SharingManagerImpl.canBeShared(SharingManagerImpl.java:433)
at org.briarproject.briar.sharing.SharingManagerImpl.canBeShared(SharingManagerImpl.java:420)
at org.briarproject.briar.android.sharing.ShareBlogControllerImpl.isDisabled(ShareBlogControllerImpl.java:54)
at org.briarproject.briar.android.contactselection.ContactSelectorControllerImpl$1.run(ContactSelectorControllerImpl.java:54)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
```Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/965Forum empty state message still refers to pen icon2018-03-28T11:39:17ZakwizgranForum empty state message still refers to pen iconThe forum empty state message says "Use the pen icon at the top to compose the first post". The pen icon no longer exists so this text should be removed.The forum empty state message says "Use the pen icon at the top to compose the first post". The pen icon no longer exists so this text should be removed.Android Beta 2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/964Buttons on private group messages are cropped2018-11-15T11:39:12ZakwizgranButtons on private group messages are croppedOn the Galaxy Nexus, but not on the Moto G 4G or Moto E3, the buttons on private group messages are cropped so the text isn't fully visible:
![Screenshot_2017-05-31-23-50-57](/uploads/34f209c7540486a337fb144dc59b4c1a/Screenshot_2017-05-...On the Galaxy Nexus, but not on the Moto G 4G or Moto E3, the buttons on private group messages are cropped so the text isn't fully visible:
![Screenshot_2017-05-31-23-50-57](/uploads/34f209c7540486a337fb144dc59b4c1a/Screenshot_2017-05-31-23-50-57.png)Sponsor 2.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/963Threaded Conversation: No Unread Button when new message partly visible2020-11-19T15:13:36ZakwizgranThreaded Conversation: No Unread Button when new message partly visibleIf a message is received in a private group while the group is open, the message doesn't appear until the screen is rotated.
This may be device-dependent: it happens on the Moto G 4G and the Moto E3, but not on the Galaxy Nexus.If a message is received in a private group while the group is open, the message doesn't appear until the screen is rotated.
This may be device-dependent: it happens on the Moto G 4G and the Moto E3, but not on the Galaxy Nexus.https://code.briarproject.org/briar/briar/-/issues/962Removing contact fails with DbException2017-07-04T15:19:30ZakwizgranRemoving contact fails with DbExceptionWith a fresh install of Briar, I added and removed a contact. Removing the contact succeeded on one device, but failed repeatedly on the other device with the following exception:
```
05-31 18:13:01.426 2390-2584/org.briarproject.briar ...With a fresh install of Briar, I added and removed a contact. Removing the contact succeeded on one device, but failed repeatedly on the other device with the following exception:
```
05-31 18:13:01.426 2390-2584/org.briarproject.briar W/ConversationActivity: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:162)
at org.briarproject.briar.sharing.SharingManagerImpl.removingShareable(SharingManagerImpl.java:453)
at org.briarproject.briar.sharing.BlogSharingManagerImpl.removingBlog(BlogSharingManagerImpl.java:70)
at org.briarproject.briar.blog.BlogManagerImpl.removeBlog(BlogManagerImpl.java:224)
at org.briarproject.briar.blog.BlogManagerImpl.removingContact(BlogManagerImpl.java:119)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:175)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:137)
at org.briarproject.briar.android.contact.ConversationActivity$19.run(ConversationActivity.java:810)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
```
From the stacktrace, it looks like more than one session has somehow been created for sharing the contact's blog. (I didn't share the blog manually.)Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/961Minor UX issue with reblogs and contact messaging2019-02-27T10:25:16ZErnir ErlingssonMinor UX issue with reblogs and contact messagingMargins are missing in the bottom area between the screen border and between the input area and button. Button also seems wider than the input area which is probably missing a shadow due to elevation
See screenshots:
![Screenshot_2...Margins are missing in the bottom area between the screen border and between the input area and button. Button also seems wider than the input area which is probably missing a shadow due to elevation
See screenshots:
![Screenshot_2017-05-31-11-14-05](/uploads/4bb202defb5e3589d521318eb200d48a/Screenshot_2017-05-31-11-14-05.png)
![Screenshot_2017-05-31-11-22-04](/uploads/d37e09cf19b5ad2bc194c7a561289039/Screenshot_2017-05-31-11-22-04.png)https://code.briarproject.org/briar/briar/-/issues/960Contact Introduction confusions and redundancies2019-04-16T13:38:29ZErnir ErlingssonContact Introduction confusions and redundancies***Background***
This ticket lists all the issues observed during contact introduction during user testing and a robust internal test. Some of these might be "features" or already listed as issues in other tickets.
***Results***
...***Background***
This ticket lists all the issues observed during contact introduction during user testing and a robust internal test. Some of these might be "features" or already listed as issues in other tickets.
***Results***
1 Some testers were confused why nothing happened after accepting the introduction, confirming #923 .
2 It's possible for the same user to introduce the same two contacts as in a previous introduction even when the two contact's have not yet responded to the initial introduction. Multiple simultaneous introductions, with the same pair of contacts, were confusing for the introduction recipients.
3 If A has declined the introduction that information is not displayed for B until he/she has selected decline/accept introduction. I wonder if it would not be simplest just to display the rejection immediately before B answers ?
4 If two contact's are introduced to one-another that are already contacts, unbeknown to the introducer, there is no need to propagate rejections between the two contacts.
Ex. User's A and B are already connected. User C introduces A and B to one another, A decides to reject. B receives introduction from C but also the rejection from A, which caused confusion. In this case it would have been best to skip displaying the rejection entirely because it is completely irrelevant.https://code.briarproject.org/briar/briar/-/issues/959Large RSS imports take over the feed2017-08-01T15:42:01ZErnir ErlingssonLarge RSS imports take over the feedWhen testers imported RSS feeds, they complained that user blogs were too hard to find.
One suggested using two feeds: one for user blogs and the other for imported RSS feeds. User's could then switch between them with tabs.When testers imported RSS feeds, they complained that user blogs were too hard to find.
One suggested using two feeds: one for user blogs and the other for imported RSS feeds. User's could then switch between them with tabs.https://code.briarproject.org/briar/briar/-/issues/958Importing RSS Feed, UX considerations2020-11-19T15:15:13ZErnir ErlingssonImporting RSS Feed, UX considerations1. We should close the keyboard after the user has pressed the import button
2. One user imported a large RSS feed and before it finished his screen turned off, he had a short setting for an active screen but we should maybe consider met...1. We should close the keyboard after the user has pressed the import button
2. One user imported a large RSS feed and before it finished his screen turned off, he had a short setting for an active screen but we should maybe consider methods to keep the screen on while something is loading, there the device is usually not really idle but the user is simply waiting for the loading to finish before continuing.