Fixed
- A boolean flag with a value other than
trueorfalse(--silent=noand--silent=0,
which ran as--silent) isINVALID_ARGSinstead of being read as set (#217). tg send,tg messages readandtg apiwrite methods resolve an@usernamethrough
Telegram, not the cache, so a username that moved never sends to its previous owner. The
allowedChatscheck of a write resolves the list's@usernameentries the same way: an entry
allows the chat that holds the username now, not its previous owner by ID. Reads take the
latest fetched owner of a username (#217).- The daemon no longer deletes an account when two accounts sign in as the same Telegram user.
It picked the one to keep by the kind of phone, so it could delete the account with the cache,
label and active choice, or the one with the only working session. Now it leaves both and
doesn't sync the second; its error says to log in again or remove it.