iequidoo

5 is SQLITE_BUSY, but it indeed should never happen, probably `write_lock()` is forgotten for a write transaction somewhere or so.

> I tried setting `PRAGMA wal_autocheckpoint=0;` next to `busy_timeout = 0` and it did not help, so it is not about some connection doing WAL checkpointing. Still, seems we need...

You're right, but then there's another problem that WAL swells indefinitely. E.g. my WAL now is ~200M which is much more than 1000 pages (SQLITE_DEFAULT_WAL_AUTOCHECKPOINT macro).

My DC Desktop is running since Sep 21, maybe this is the reason?

> With this PR, all encrypted messages are rewritten to the PGP-contact identified by the current autocrypt key. It is not possible to find out which key was actually used...

> Nothing bad can happen if a few old messages are assigned to a slightly-wrong PGP contact, so I think it's fine. And, keeping the complexity low and moving forward....

> * Consideration for naming Maybe `{In,Out}Broadcast`? If we remove the current `Broadcast` lists, these don't conflict with anything. `BroadcastChannel` is quite long and will cause extra line wrapping. OTOH...

> Not sure - then, the name in the code and the name in the UI don't have anything to do with each other. OTOH, it's true that `BroadcastChannel` is...

I guess using seipd_v2 with encryption to a password is possible, but note that the message must be signed with the sender's key first. Signing isn't needed in case of...

"Reply Privately" indeed should work the same way it works for groups, i think it doesn't even need additional development. Reactions (if only shown to the broadcast owner and the...