Make breakpoints in Client::startSyncing() const

Check if it still crashes if we cut off network after opening

The RoomModel in libkazv should remember more than the current text-only localDraft. Should also store the state of e.g. editing or replying.

Pinned messages page: Modify the behaviour so that when the pinned messages action is triggered, the pinned messages page will replace the room page. Then, add an action in pinned messages page to return to the room page. Leave it that way until we refactor PageRow in T182 .

Some pages are left unmodified.

I don't think we want to do this. The benefits of keeping Crypto a value type isn't great. For example, it delays saving of the crypto state, which can cause problems in the case of a crash / kill of the process. A solution might be to make Crypto a dependency of the store instead.

After thinking this is not a good move because it actually adds unnecessary comparisons and is bad for running time

Done in https://iron.lily-is.land/D229

In T75#2565, @tusooa wrote:

@nannanko I cannot seem to reproduce this bug. Is it still a problem for you? My guess is that it is somehow fixed by @apr3vau .

To be resolved altogether with the event store (well, if we aren't displaying all of the events then we should be fine)

@nannanko I cannot seem to reproduce this bug. Is it still a problem for you? My guess is that it is somehow fixed by @apr3vau .

Upstream bug fixed, closing because I can no longer reproduce.

Resolved by https://iron.lily-is.land/D238 https://iron.lily-is.land/D240

Instead of sync forever in Client, we can do one sync cycle in the function, and give control to the user of libkazv. Then, in kazv we can implement the retry logic.

FileHandler analyzes eventContent, checks whether it is encrypted and contains thumbnails, and performs download/cache.