Briar GTK issueshttps://code.briarproject.org/briar/briar-gtk/-/issues2021-04-20T23:36:56Zhttps://code.briarproject.org/briar/briar-gtk/-/issues/100RuntimeError: Requests dependency 'chardet' must be version >= 3.0.2, < 3.1.0!2021-04-20T23:36:56ZJohn KennedyRuntimeError: Requests dependency 'chardet' must be version >= 3.0.2, < 3.1.0!I've been getting this error for a couple of weeks while trying to build on Arch (both stable and git).
`RuntimeError: Requests dependency 'chardet' must be version >= 3.0.2, < 3.1.0!`I've been getting this error for a couple of weeks while trying to build on Arch (both stable and git).
`RuntimeError: Requests dependency 'chardet' must be version >= 3.0.2, < 3.1.0!`https://code.briarproject.org/briar/briar-gtk/-/issues/97Accessibility User Testing2021-02-08T12:12:33ZNicoAccessibility User TestingWe should test whether Briar GTK is accessible to users with [different types of disability](https://developer.gnome.org/accessibility-devel-guide/stable/idm140487279365936.html.en) by using tools like [Orca](https://wiki.gnome.org/Proje...We should test whether Briar GTK is accessible to users with [different types of disability](https://developer.gnome.org/accessibility-devel-guide/stable/idm140487279365936.html.en) by using tools like [Orca](https://wiki.gnome.org/Projects/Orca).
Relevant links:
* [GNOME Accessibility Developers Guid](https://developer.gnome.org/accessibility-devel-guide/stable/index.html.en)
* [Accessibility in GTK 4](https://blog.gtk.org/2020/10/21/accessibility-in-gtk-4/)GTK 0.2.0-beta1https://code.briarproject.org/briar/briar-gtk/-/issues/87Port to GTK 4.02021-02-01T11:52:09ZNicoPort to GTK 4.0GTK 4.0 got released some days ago: https://blog.gtk.org/2020/12/16/gtk-4-0/
There are some cool new things in there that are all mentioned in the blog post. However, I marked this issues as blocked for now because I don't want to trans...GTK 4.0 got released some days ago: https://blog.gtk.org/2020/12/16/gtk-4-0/
There are some cool new things in there that are all mentioned in the blog post. However, I marked this issues as blocked for now because I don't want to transition to GTK 4.0 before [Debian stable ships it](https://packages.debian.org/experimental/libgtk-4-0). I think we have good chances to have it in the next Debian release coming in 2021. If we focused only on Flatpak, we could transition to GTK 4.0 today, though.
Related issues: https://code.briarproject.org/briar/briar-gtk/-/issues/80 and all the issues linked in there.
Related links:
* [Migrating from GTK 3.x to GTK 4 - GTK documentation](https://developer.gnome.org/gtk4/4.0/gtk-migrating-3-to-4.html)GTK 0.2.0-beta1https://code.briarproject.org/briar/briar-gtk/-/issues/86Provide firejail profile2020-11-20T16:52:36ZNicoProvide firejail profileA user of Briar GTK said:
> Contributing a firejail profile would also help [with getting Briar GTK into Debian]!A user of Briar GTK said:
> Contributing a firejail profile would also help [with getting Briar GTK into Debian]!https://code.briarproject.org/briar/briar-gtk/-/issues/84Use Briar blue instead of theme selected color2020-12-16T14:02:59ZNicoUse Briar blue instead of theme selected colorCurrently we use [`@theme_selected_bg_color`](https://code.briarproject.org/briar/briar-gtk/-/blob/154be3dcfe2c93f5cf66f25f1b356e54653175a1/briar-gtk/data/ui/application.css#L67) for things like usernames. This is mostly blue, but on e.g...Currently we use [`@theme_selected_bg_color`](https://code.briarproject.org/briar/briar-gtk/-/blob/154be3dcfe2c93f5cf66f25f1b356e54653175a1/briar-gtk/data/ui/application.css#L67) for things like usernames. This is mostly blue, but on e.g. Linux Mint it's green. There, the difference between own and their usernames is not visible that much, because both names are colored in green. We should use the Briar blue code instead, so that we have blue-green on all platforms.GTK 0.1.0-beta3x0lootsx0lootshttps://code.briarproject.org/briar/briar-gtk/-/issues/81Improve line wrapping in messages2021-01-06T14:41:28ZNicoImprove line wrapping in messagesA user reported a bug I had in mind once but forgot about: messages consisting of one very large "word" don't get wrapped in the chat history. By sending a very large sequence of characters without spaces etc. you can essentially explode...A user reported a bug I had in mind once but forgot about: messages consisting of one very large "word" don't get wrapped in the chat history. By sending a very large sequence of characters without spaces etc. you can essentially explode your window width.
Seems like this is really easy to fix: in [_briar-gtk/briar_gtk/widgets/private_message.py#L121_](https://code.briarproject.org/briar/briar-gtk/-/blob/154be3dcfe2c93f5cf66f25f1b356e54653175a1/briar-gtk/briar_gtk/widgets/private_message.py#L121) all we have to do is to add a new code line calling [`body_content.set_line_wrap_mode()`](https://lazka.github.io/pgi-docs/#Gtk-3.0/classes/Label.html#Gtk.Label.set_line_wrap_mode) with [`Pango.WrapMode.WORD_CHAR `](https://lazka.github.io/pgi-docs/#Pango-1.0/enums.html#Pango.WrapMode.WORD_CHAR).GTK 0.1.0-beta3https://code.briarproject.org/briar/briar-gtk/-/issues/73Redesign contact list2022-01-28T10:54:10ZNicoRedesign contact listInspiration by the GNOME Project:
![mobile-shell-convergence](/uploads/c7c585bd2133b1e37cd70487b7baf6a5/mobile-shell-convergence.png)
Source: https://gitlab.gnome.org/Teams/Design/os-mockups/-/blob/f69fa82f8676582d900af8716522a27ddd77d...Inspiration by the GNOME Project:
![mobile-shell-convergence](/uploads/c7c585bd2133b1e37cd70487b7baf6a5/mobile-shell-convergence.png)
Source: https://gitlab.gnome.org/Teams/Design/os-mockups/-/blob/f69fa82f8676582d900af8716522a27ddd77d87f/mobile-shell/mobile-shell-convergence.png