-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Threema Web a real desktop client #515
Comments
Hi, thanks for your feedback. The fact that Threema Web connects to your phone is by design. It makes sure that the private key never leaves your phone. It's an extension of your phone, not a standalone client. From what I understand, what you want is not necessarily multi-client functionality, but a standalone Threema client on your computer so that you don't need your phone at all, right? In that case, maybe https://www.openmittsu.de/ could work for you? |
I think this is an interesting topic and I basically agree with Threema's decision here. Most people do instant messaging with the smartphone, now when it comes to using the same ID from multiple devices, it's the best sulution when everything goes through the phone from a security point of view. No duplicated message history, no shared or additional private keys etc. That's a huge advantage when it comes to security because this model is easy to understand and the user can be sure that all the stuff is stored on the phone only. So, I think it's okay to have a web client for the app on the smartphone. My point here is that the web application should be way more stable, efficient and use less battery. That's not the case at the moment and should be fixed as soon as possible. Even if that means a rewrite with other frameworks or technologies. If the web client is working fine then, it's really a good solution for a private messenger. However, when you want to use Threema at the desktop only (it's not about multi-device support), I am with @piegamesde and I'd like to have an officially supported Threema client. One of Threema's strengths is that the account is not dependent on mobile phone numbers. However, Threema does not make advantage of that fact at the moment. Let's see if that changes. |
Closing for now. Feel free to leave further comments. |
You can emulate a standalone app with Google Chrome. You can also change the icon from the default Chrome Icon to Threema's, which you can find by having a look at the source code |
That shouldn't be necessary. Threema Web is a PWA now, see #407. |
This issue is not about a "native" desktop client, it is about a standalone desktop client independent from the phone. Today, I'd maybe call this "multi device support". Nonetheless, the issue description is pretty clear about what I want(ed), so please don't derail it with related issues. I personally don't care about this any more, since I've long moved on to other chat applications (Matrix at the moment, FWIW). But others may still do. |
My response was towards @jeengbe. |
I second this. I only use Threema sparingly because it's not multi-device supported. Please push this |
We've publicly announced that we're working on multi-device and a desktop client. No need to push. 🙂 |
I don't care about Threema on phones, so I don't need multi-device-support. Was there any progress with a desktop-only client? Is there an ETA? |
Interim solution until an official desktop app is released: Threema's progressive web app can be packaged with Electron with little effort. A tutorial or the ready to download app is available on my (german) blog: https://langhard.ch/download-threema-desktop-client-app/ |
One has to be aware that it comes with all the pros and cons of an Electron app. For Threema Web (but not for Threema Desktop), we believe the cons (e.g. potential privilege escalation, potential security vulnerabilities of Electron without an auto-update function) outweigh the pros at the moment. |
Sounds good, as long as this means I don't need a browser on desktop to use Threema when this is released. I'm fine with using a phone to authorise a desktop client to tap into my account, but I want to be able use Threema without opening a browser at all. |
That's what PWAs are for :) |
https://threema.ch/en/blog/posts/md-architectural-overview-intro It's been 6 months since the last update on the blog. I have full trust in your competence and will to make it happen. |
Be assured that we're working on it (quite hard). |
Thank you lots, will buy several more copies of Threema for my friends on the same day it happens. |
As there is now an electron based desktop client, what changed these believes? Or to be more clear, what does the desktop client provide which the PWA doesn't already? |
@bluec0re some people really want to download a standalone application that has its own icon in the dock and in the OS application menu. If you're happy with a PWA, feel free to keep using it. Regarding security, we made sure that Threema Web runs entirely in a sandboxed process and does not have access to the Electron internals. This should solve the concerns regarding privilege escalation. As long as the application is regularly updated (that's why it has an auto-updater built in) it should provide the same level of security as a web browser. Additionally, in a standalone application users cannot install browser extensions, which pose an additional potential for vulnerabilities. So in some sense, while packaging an Electron app poses its challenges, it also provides some security benefits. Version 1.0 of the desktop app is meant as a transitional desktop application while we work on version 2.0, which will be a fully standalone desktop client. |
Thanks for the explanations. Great to hear that you put quite some thoughts into reducing the additional risks, especially reducing the patch gap and inherit sandbox problems. I understand the benefits you can draw from it by having a better control over the handled input (but as usual, with great power comes great responsibility ;-) ). Hopefully https://web.threema.ch will not be discontinued at some point in the future though. |
@bluec0re Edit: as @piegamesde wrote
So, we have just an additional browser to install? Not what i expected to be honest. |
@vulpes9 on their blog they talk about this being temporary.
|
@BlkPingu |
This Arch Linux PKGBUILD may help as a reference: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=threema-desktop |
So, is this forgotten? Do I have to wait until 2023? |
Come on Threema. Publish it |
The development of Desktop 2.0 is ongoing and a preview is available for use in combination with Threema for iOS: https://threema.ch/en/download-md Please refrain from continuously pinging here. When there's something to announce (e.g. a release, support for Android, etc.), it will be done on the usual channels (e.g. subscription to the |
Threema Web is not a real desktop client, it is no more than a web frontend for the app. As someone who almost exclusively uses the laptop for all communication, this is a real pain. All chat applications nowadays have web clients that are completely independent of the phone (except WhatsApp of course), and Threema should have it too.
Expected Behavior
I can use Threema on my Desktop / in my browser independently of my phone. I don't have the phone to be online. I am not required to enter a password or scan a QR code on every connection attempt.
Current Behavior
Threema web is no more than a web frontend for the app. Every thing I do goes through the phone. This is a huge battery drain. Also, every time the connection is lost I need to reconnect it. Sometimes, I don't notice the connection is lost and miss potentially important messages.
Possible Solution
Threema accounts are not tied to a phone number, but to the Threema ID. So there is no real reason why I should be forced to use mobile devices for using it. I don't care if Threema web has to be my only client, or if there is no sync between them.
Your Environment
The text was updated successfully, but these errors were encountered: