briar issueshttps://code.briarproject.org/groups/briar/-/issues2023-08-28T16:00:12Zhttps://code.briarproject.org/briar/briar-mailbox/-/issues/82User feedback / bug / crash-log reporting mechanism2023-08-28T16:00:12ZSebastianUser feedback / bug / crash-log reporting mechanismIn briar, users can report general feedback and get promted to do so if the app crashes. That's very useful for us as developers, so it would make a lot of sense to have something like this in the mailbox app as well.In briar, users can report general feedback and get promted to do so if the app crashes. That's very useful for us as developers, so it would make a lot of sense to have something like this in the mailbox app as well.https://code.briarproject.org/briar/briar/-/issues/2212Comply with Google emoji policy2023-07-31T15:02:31ZakwizgranComply with Google emoji policyGoogle has created a new policy that requires apps to support the latest emoji version within four months of its release.
https://support.google.com/googleplay/android-developer/answer/11190649#emoji_preview
To do this, we may need to ...Google has created a new policy that requires apps to support the latest emoji version within four months of its release.
https://support.google.com/googleplay/android-developer/answer/11190649#emoji_preview
To do this, we may need to replace our current emoji implementation with Google's emoji2 library, which can be used directly or via AppCompat.
https://developer.android.com/guide/topics/ui/look-and-feel/emoji2
By default this uses a downloadable font and requires a downloadable font provider such as Google Play Services. In order to work offline, avoid depending on Play Services and protect users' privacy, we would need to bundle the 10 MB emoji font in our APK.
https://developer.android.com/guide/topics/ui/look-and-feel/emoji2#support-bundled-fonts
The policy becomes effective on 2 February 2022.https://code.briarproject.org/briar/briar-desktop/-/issues/290More settings2022-11-09T13:40:23ZSebastianMore settingsI think we should create individual tickets for the items below.
## General
* Profile image
## Display
* ~~Theme switch as already in the first proof of concept~~
* ~~Language switch~~
## Connections
* Transport option: use direct con...I think we should create individual tickets for the items below.
## General
* Profile image
## Display
* ~~Theme switch as already in the first proof of concept~~
* ~~Language switch~~
## Connections
* Transport option: use direct connections with contacts on the same Wifi? yes/no
* connect via Internet?
* connect directly or via bridges to Tor?
## Security
* ~~Change password (#289)~~
## Notifications
* ~~Notifications (show desktop notifications in general)~~
* Specific notifications per category (show notifications for private messages, groups, forums, blogs)
## Actions
* Feedback button triggering some mechanism for sending some feedback to developers (#272)https://code.briarproject.org/briar/briar-desktop/-/issues/41Investigate Bluetooth for desktop systems2022-10-31T17:07:58ZMikolai GütschowInvestigate Bluetooth for desktop systemshttps://code.briarproject.org/briar/briar-desktop/-/issues/15Blogs2022-04-03T10:47:51ZMikolai GütschowBlogsDesktop 1.0.0https://code.briarproject.org/briar/briar-desktop/-/issues/14RSS2022-04-03T10:36:55ZMikolai GütschowRSSDesktop 1.0.0https://code.briarproject.org/briar/briar-desktop/-/issues/16Installers2022-04-03T10:36:55ZMikolai GütschowInstallershttps://code.briarproject.org/briar/briar-desktop/-/issues/17Update mechanism2022-04-03T10:36:54ZMikolai GütschowUpdate mechanism- updates also through Tor network
- binary diffs?
- might enable estimation of number of Briar (Desktop) users- updates also through Tor network
- binary diffs?
- might enable estimation of number of Briar (Desktop) usershttps://code.briarproject.org/briar/briar-desktop/-/issues/25Investigate Decompose2022-04-03T10:36:53ZMikolai GütschowInvestigate Decomposehttps://arkivanov.github.io/Decompose/https://arkivanov.github.io/Decompose/https://code.briarproject.org/briar/briar-desktop/-/issues/52Responsive Design2022-04-03T10:36:49ZpaulResponsive DesignThe current views are responsive for medium size screens, this ticket looks to add support for:
- [Phone Constraints](https://developer.puri.sm/Librem5/Apps/Guides/Design/Constraints.html)
- Large fullscreen desktop widthsThe current views are responsive for medium size screens, this ticket looks to add support for:
- [Phone Constraints](https://developer.puri.sm/Librem5/Apps/Guides/Design/Constraints.html)
- Large fullscreen desktop widthshttps://code.briarproject.org/briar/briar-desktop/-/issues/72Allow configuration of transports2022-04-03T10:36:48ZNicoAllow configuration of transportsUsers may want to
* turn on/off Tor
* turn on/off local network (https://code.briarproject.org/briar/briar-desktop/-/issues/71)
* use Tor only via bridges
* ?Users may want to
* turn on/off Tor
* turn on/off local network (https://code.briarproject.org/briar/briar-desktop/-/issues/71)
* use Tor only via bridges
* ?https://code.briarproject.org/briar/briar-desktop/-/issues/242Improve test data creator2022-04-03T10:36:24ZSebastianImprove test data creatorThis can be broken down into smaller tickets for individual improvements of the test data creator.
* It would be nice to have not only readily added contacts, but also a bunch of pending contacts.
* Also it would be good if we can make ...This can be broken down into smaller tickets for individual improvements of the test data creator.
* It would be nice to have not only readily added contacts, but also a bunch of pending contacts.
* Also it would be good if we can make the `briar://`-links of both regular and pending contacts available for further interactive testing, for example by printing them on stdout. That would allow for easy testing of contact-readding etc.
* However, testing contacts don't currently have a handshake key from which the briar:// link gets derived. We can generated one, but apparently we need to go through the process of first adding our testing contacts as pending contacts and then making them proper contacts. See this message and the conversation shortly before and after for details: https://chat.briarproject.org/briar/pl/7tcobcx5qfb5mjkto3cj33kw8r
* Support for aliases
* Support for introductionshttps://code.briarproject.org/briar/briar/-/issues/1823ViewModel migration2021-07-06T09:59:04ZakwizgranViewModel migration