fix/app-issues-25-28 #37
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/app-issues-25-28"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
message <Expired>(sent instead of<Retracted>since the app keeps no history,preserve_history0) was not mapped and became.other, so the transcript kept the row until the chat was opened again (#27). It is handled asRemovedof its timestamp, as TackyWire says. The chat list's preview of it stays until the list's next update; that is libtacky's chatlist, which does not follow<Expired>. 0a6073fdearoster accept_invite, which makes us mutual contacts at once, while a link from outside asked first (#18); it now keeps the code asinvitation, andaccepttakes it once the user says Add. The question is one view modifier,invitationPromptin ComposeUI, used by AppShell for links and by Add Contact for codes, with its strings moved to ComposeUI's catalog. Its message now says that Add asks them to share their status and approves their request to see ours without asking again if it comes within 7 days, libtacky's EXPECT_TTL (roster.tcl), which is where that approval happens; ru/uk/et/es with it. A notice when such an approval happens needs libtacky to say why a subscribe came pre-approved, and is moved there. ed0d2375cc.task, so a cancel (the screen rebuilt as the chat list changes on open, by the look of it) left a stranger's header, since the live header reads the roster and OMEMO state withtry?, and an empty window that nothing asked again, until Info and Back ran the task anew. The loads now run in tasks of their own; only the following of the chat's events ends with the screen's. TackyBackend logs a request its task cancelled (debug), so the next diagnostics say what came before "reply to an unknown token". fe1bacf0a1