GitLab

We were freeing the hashtable value but we were not passing
a copy of the string, so the same memory location was being
freed multiple times.

Also clear the memory before freeing because we don't want
access token to be in memory after free.

We don't want the access token to stay in memory after the application
is closed

And remove no longer code

Mohammed Sadiq authored Jul 02, 2021 and Mohammed Sadiq committed Jul 02, 2021

Let's eventually move network related methods to a separate class
so that matrix-api won't be much cluttered as more features
are added there.

Instead of blindly emitting 'changed' signal, let it be a property
so that if the changes are reverted, the 'modified' property
can be unset so that we can handle it appropriately

Also adapt to changes in settins-dialog

And adapt to changes.

This is required for matrix accounts as they can be saved only async

This implements the new design

We now handle them in chatty-application.

And adapt to changes

Handling opening chats in chatty-notification seems to result in crash,
which often happens when there are many matrix chats

Loading full room state can be very slow and shall
use too much bandwidth and CPU if the room is large.
So load only the required information.

So that we can improve purple and matrix accounts independently

Otherwise we might end up with duplicate entries on subsequent
requests

Aren Moynihan authored Jun 20, 2021 and Mohammed Sadiq committed Jun 23, 2021

Add timeouts that update the time since the last message so that it
doesn't get too out of date.

We don’t want to skip critical/warnings from GdkPixbuf
regardless of the verbosity.  Also, show GdkPixbuf logs
when the verbosity is set to very high.

and reduce the scope of variable 'server_url'