Hi André and Ludovic, André A. Gomes <andremegaf...@gmail.com> writes:
[...] > It's working for me too, following your steps! Fine, so we have an easy procedure to "roll back" the telega-server status folder; this means a new desktop application authentication that will appear as a new "device" (probably followed by old "device" deletion, for security) in Telegram, but AFAIU this is not a problem for most of the users > So, I believe we're agreeing that the commit we referred to should be > reverted. Correct? IMHO yes, we should revert the tdlib upgrade /or/ keep a packaged tdlib@1.8.0 used by emacs-telega v. 0.8.3 AFAIU soon (TM) a new release of emacs-telega should be published (tagged) so eventually the next step could be to upgrade emacs-telega (as soon as it is released) Anyway, IMHO both tdlib and emacs-telega should be built from official releases and not from specific commits, for users who wish to run emacs-telega/tdlib from specific commits more recent than current "stable", I propose to create tdlib-next and emacs-telega-next [...] If I don't get it wrong, I still have commit access to the guis repo so I could revert the commit on tdlib, but I'd like to have an OK. Ludo' WDYT please? Thanks, Gio' -- Giovanni Biscuolo Xelera IT Infrastructures
signature.asc
Description: PGP signature
