Currently we build telegram with API_TEST creds and it may limit connectivity to telegram API servers for users. Users also have a way to override the API at build time, but this is not great UX. debian has their own creds publushed here https://salsa.debian.org/debian/telegram-desktop/blob/debian/master/debian/rules#L23 our chromium ebuilds also contains similar api key for google services. I've sent an email to telegram API guys and requested our DISTRO API creds. for obvious reasons I do not wish to attach api creds to my personal telegram account.
after some research and chatting with other maintainers and contributors it seems it's impossible to obtain distro-specific creds. but we can use same creds telegram uses to build snaps https://github.com/telegramdesktop/tdesktop/blob/dev/snap/snapcraft.yaml will switch to that (but will still leave specifying custom ID possible)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b874bcd2d812eca72729978b20a778b6d7e20738 commit b874bcd2d812eca72729978b20a778b6d7e20738 Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2020-02-14 07:22:19 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2020-02-14 07:30:35 +0000 net-im/telegram-desktop: use snapcraft api creds Closes: https://bugs.gentoo.org/706386 Package-Manager: Portage-2.3.88, Repoman-2.3.20 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> ...13.ebuild => telegram-desktop-1.9.13-r1.ebuild} | 27 +++++++++++----------- 1 file changed, 14 insertions(+), 13 deletions(-)
