Download Telegram App For Desktop
Hope Yelvington
- I installed Qt bindings local/telegram-qt 0.1.0-4 above, although I don't imagine that the issue is related to absent bindings for the telegram protocol.
- I also went to the home page and to the GNOME project home page to consult the Gnome discourse bbs for any similar looking issue. However telegram-desktop not being a Gnome app, it is out of scope for the Gnome team.
@progandy:
Tx. Did that. No qt.svg at those queried locations.
Made a legit svg file file up and placed it at /usr/share/icons/hicolor/scalable/apps/qt.svg. Rebooted. Same behavior. Systemd Journal log still gets spammed as soon as telegram-desktop is launched and everytime the first time the Telegram client sends or receives a message.
Something curious and I did not mention is the regularity and predictability of the error entry in the log.
Essentially at boot only 2 identical entries appear, just at the end of the journal log for the current boot and after the login session starts. That's when the autostarting of telegram-desktop occurs.
Then the first time a message is sent from telegram-desktop the same line, only replicated 158 times (that's 159 lines in total), are logged. No error entry is logged for received messages
On subsequent message sends and receives, no error entry is logged. So when I mentioned in post#1 that the systemd boot log showed well over 200 messages (in fact well other 600 for certain past sessions during which I spent time making sense of this), it was only because in order to troubleshoot the issue, I was manually killing and restarting the telegram-desktop app within the same OS session, thus generating new journal log entries.
It would suggest that telegram-desktop uses Qt as framework for the app codebase and that Qt in turn tries (unsuccessfully?) to use the SVG icon theme ? I've been looking in that general direction, unsuccessfully so far. The curious thing is this only ever happens with telegram-desktop .
Sorry, qt.svg is not a filename, but the logging category. qt.svg means it comes from the qtsvg package. The specific error message results from the function qt_inflateSvgzDataFrom. That function is called from QSvgTinyDocument::load, so I'd guess telegram might contain some compressed svg file that cannot be decompressed by qt.
@progandy:
Yes, most probably cannot read that svg file, but I had to try it.
Yes, telegram-desktop use themes and is customizable in that sense, but I just use the package from Arch local/ repo as is. No tweak whatsoever.
After updating the looks of GNOME installation as described here, telegram-desktop (installed from Official repos, not from AUR) got some borders.If I use Style: kvantum or kvantum-dark I get borders, if I switch to anything else - borders are gone.
Im having telegram on my windows 7 desktop machine.
I wanted to know is there a way to disable the "automatic media download" option that exists in telegram desktop? which causes the app to download all photoes and voices at the moment that the screen reaches them.
The telegram which is on android platform has an option in its settings in which you can untick photo and audio inorder to prevent it from auto downloading such media, but there is no such option in the settings of the desktop version.
Any help would be appreciated.
unlike the older versions of telegram, the newer version has automatic media downloads in advanced setting and not in chat settings. thussFIRST open SETTINGS then click on ADVANCED then look for AUTOMATIC MEDIA DOWNLOADS. under it you will see ( in private charts, in groups, in channels) click on them to set your automatic download preferences for each of them
a workaround would be to copy /var/lib/flatpak/app/org.telegram.desktop/current/active/export/share/applications/org.telegram.desktop.desktop to /.local/share/applications/. and removing the line DBusActivatable=true from it
I saw there are various UDF libs for Telegram already (to my pleasure, I must say), but looks like they're for direct interaction with telegram API, so kinda to use them with a bot.
Unfortunately bot file management is severely limited in size of files (20mb compared to 4gb on premium normal user) and other aspects.
Therefore my last choice was to automate in some way telegram desktop in a way that directly interacts with the window (WinGetHandle, WinExists, etc etc.).
Unfortunately, probably due to the fact that as I understood telegram is packed with electron, and electron AFAIK just displays a webapp into an exe,, trying to use Window Info tool doesn't give any result beside a main window, which has the current chat name and a random number.
The only way to grab it is by classname like this:
But I'm unable to catch any other button/UI element info with the telegram application. They all give the same handle info of the main page.
I tried to disable/enable Spy++ detection logic but nothing changed.
This leaves me to 3 roads:
1) Maybe there is another way to detect the handles and I don't know?
2) Trying some injector ( -injector for example) to inject html/js directly and interact with it
So, the I wanted a version that was generated from upstream code potentially without modifications. tdesktop also has a quite complex build system which needs various upstream libraries (some of them in static form) with specific versions including slightly patched Qt 5.6.2 and gyp, so it was fun to test it with the power of snapcraft.
Since I was there I also fixed telegram to compile properly in armhf (I hated the red light on b.s.i!), and then if you have any hardware with such arch handy and a graphic session, please test it too.
PS: unity launcher / GNOME dock integration works, but having other .desktop files around in your systems (like the ones that the official build generates) could cause a wrong matching, so in that case, just get rid of /.local/share/applications/telegramdesktop.desktop
I had previously installed Telegram but recently it notified me that unless I updated the app it would stop working, so I removed it completely. Ready to reinstall. First I tried with synaptic, telegram said it's old version. Same for apt. What works is only the direct executable file downloaded from official site. Don't get me wrong I have no problem with using that. But the problem is that the executable file cannot be placed inside /opt because then it won't show up in the menu bar. It has to be somewhere out. I think it'd be better if apps were installed inside /opt else I might delete the file by mistake
The desktop clients (excluding the macOS client) do not feature options for end-to-end encrypted messages. When the user assigns a local password in the desktop application, data is locally encrypted also. Telegram has defended the lack of ubiquitous end-to-end encryption by claiming the online-backups that do not use client-side encryption are "the most secure solution currently possible".[305]
In March 2014, Telegram promised that "all code will be released eventually", including all the various client applications (Android, iOS, desktop, etc.) and the server-side code.[322] As of May 2021, Telegram had not published their server-side source code.[323] In January 2021, Durov explained his rationale for not releasing server-side code, citing reasons such as inability for end-users to verify that the released code is the same code run on servers, and a government that wanted to acquire the server code and make a messaging app that would end competitors.[324]
The search service can find package by either name (apache),provides(webserver), absolute file names (/usr/bin/apache),binaries (gprof) or shared libraries (libXm.so.2) instandard path. It does not support multiple arguments yet... The System and Arch are optional added filters, for exampleSystem could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system. System Arch RPM resource telegram-desktopTelegram is a non-profit cloud-based instant messaging service.Users can send messages and exchange photos, videos, stickers, audio and files of any type.Its client-side code is open-source software but the source code for recent versions is notalways immediately published, whereas its server-side code is closed-source and proprietary.The service also provides APIs to independent developers.
Telegram version 3.7.1 does not allow to select the web camera to use in video conference. If you want to force telegram to use a different camera, as a workaround you can disable the unwanted camera device as described in [1].
Telegram-desktop is built against Qt 6 since 3.4.2-2. Users upgrading from an older version might notice Fcitx stop working for this application. To make it work again, install fcitx-qt6 or the fcitx-im group. If using Fcitx5, install fcitx5-im.
Fiddler Everywhere and Fiddler Classic are HTTPS proxies, and as such they can capture application traffic that utilizes HTTP, HTTPS, WebSocket, or gRPC protocols. While some basic operations in the Telegram desktop application use HTTP (pre-handshake requests), all communication is end-to-end encrypted. The encryption is not using the TLS protocol that is widely used with HTTP, but instead, Telegram created its encryption protocol called MTProto. The creators of Telegram started this protocol with the sole idea of preventing traffic decryption from the intermediate.
One of the important things to understand about desktop versions of messengers is that the vast majority of them are built on the Electron framework. What this basically means is that such a program, on the inside, is a web application that opens in an embedded Chromium browser.
356178063d