Similar open source solutions exist like:
How does this compare?
Similar open source solutions exist like:
How does this compare?
- FileBrowser (https://filebrowser.org/features)
- Syncthing (https://syncthing.net/)
Run both as Docker containers on a server at home. Syncthing keeps the files on your PC, Mac, and BSD systems in sync, and FileBrowser can point to the sync share and supply a convenient web UI for phones, etc. It works for me, it's kind of like a local Dropbox.
Syncthing + KDE connect does a lot.
The only issues I have had is that I cannot ensure that both are always running on android.
For example, imagine you save a file on your laptop then put it to sleep. You turn on your desktop and the file isn't there because the laptop is now asleep. Having a central 24/7 Syncthing server allows the share to always be available.
[0](https://github.com/psanford/wormhole-william)
[1](https://f-droid.org/en/packages/com.pavelsof.wormhole/)
[2](https://f-droid.org/en/packages/com.leastauthority.destiny/)
kdeconnect-cli --share [url|path/to/file] --device [device_id]For CLI stuff, I usually just run the python http server or woof and make a QR code with the URL.
Secret chats don’t work between the desktop client and the app, so I would suspect that, like the rest of the messages, everything is saved on telegram’s servers in the clear.
Or am I missing something?
They hold the keys, irrespective of how many proprietary protocols they wrap over the message.
A great product tho! I used saved messages extensively!
Not just plain-old HTTPs. MTProto 2.0 is a whole encryption algorithm for Cloud chats: https://core.telegram.org/mtproto/AJiEAwIYFoAsBGJBjZwYoQIwFM...
I do not feel it is any different from Google Chat, Twitter DMs, etc. They do have a lot of censorship resistant and anti-MITM attack features in between, but they hold the keys by default
I use it for convenience and amazing features, not for security!
Telegram doesn't support markdown though, that's why I decided to build writedown.app
You can found more in depth details in this article: https://telnyx.com/resources/webrtc-encryption-and-security
And sorry for not replying I was not on the platform lately
Are you employing E2E on the client side? Encryption during transit shouldn't be claimed as E2E. Please correct me if I'm wrong.