Why migrating to Signal when there is a much better alternative as Telegram?
About twice as many people express a preference for Signal as Telegram here: https://news.ycombinator.com/item?id=25669864
Signal Fork with WhatsApp Migration
151–158 of 158 posts
Re: Signal Fork with WhatsApp Migration
#152Earlier quoted context omitted.
On mobile you can do this via backups and use https://github.com/xeals/signal-back On desktop you can copy the appdata folder over to the new device. (warning: this is not officially supported) Note that you must close the app on desktop from the host computer before copying the files over, otherwise the forward secrecy stuff breaks and you'll have to reset the sessions on the migrated computer.
Is there an equivalent for iOS?
Re: Signal Fork with WhatsApp Migration
#153The repository mentions [0] the Wassenaar agreement, and that I must consult with the laws of my country on whether I am allowed to import/use software which includes encryption algorithms developed in other countries. Wat? In this day and age 99% (OK, this number is exaggerated, but you get my point) of software includes some sort of encryption. For one, think about all the libs/apps which communicate over the Inter…
Re: Signal Fork with WhatsApp Migration
#154Earlier quoted context omitted.
About twice as many people express a preference for Signal as Telegram here: https://news.ycombinator.com/item?id=25669864
Uses Approval voting. That poll doesn't show a negative preference (as in: what do you really not want to run).
Re: Signal Fork with WhatsApp Migration
#155The repository mentions [0] the Wassenaar agreement, and that I must consult with the laws of my country on whether I am allowed to import/use software which includes encryption algorithms developed in other countries. Wat? In this day and age 99% (OK, this number is exaggerated, but you get my point) of software includes some sort of encryption. For one, think about all the libs/apps which communicate over the Inter…
> Wat?
> In this day and age 99% (OK, this number is exaggerated, but you get my point) of software includes some sort of encryption. For one, think about all the libs/apps which communicate over the Internet and use encryption libs to talk via HTTPs. Is mentioning The Wassenaar Arrangement [1] in terms of software even necessary nowadays?
> Linux, Windows, MacOS - all have encryption libs built in (at least on the kernel level). They have been made in various countries, yet they are used all over the world. Do they fall under the terms of The Wassenaar Arrangement?
> --------
> [0] https://github.com/jukefoxer/Signal-Android/tree/feature/wa-...
> [1] https://www.wassenaar.org
It's also mentioned in the original signal repo.I guess they have their reasons to include it and the fork just left it there.
Re: Signal Fork with WhatsApp Migration
#156Earlier quoted context omitted.
Indeed: signal proves that good UX and good security can coexist. Telegram proves that to have even better UX, you need to sacrifice security (and privacy).
I don't think the latter is true. It feels like the Signal team just isn't interested in taking on work (even work done by others) to improve the UX. I can understand that they have limited funding and want to focus on the security features first and foremost, but that makes it really hard for me to get some of my friends to use it. Having said that, I agree that Signal's UX is not bad , just that it could be better.
Telegram went UX first and turned down the crypto so that I can install Telegram on a fresh laptop and I've instantly got the same chats, with history, as I do on my phone.
Re: Signal Fork with WhatsApp Migration
#157Earlier quoted context omitted.
And this is why I use Telegram, for them UX matters. Yes MTProto is not audited blah blah. I use IRC too and that has exactly butkus for encryption :D
In signal you cant delete/forget contacts... And groups will haunt you to the end of days too. I started to strongly distrust signal after I learned that. It's meta information nonetheless and invites for identity fraud. But yeah, Telegram can't be trusted either. I hope matrix/element will replace both soon.
Re: Signal Fork with WhatsApp Migration
#158Earlier quoted context omitted.
I don't think the latter is true. It feels like the Signal team just isn't interested in taking on work (even work done by others) to improve the UX. I can understand that they have limited funding and want to focus on the security features first and foremost, but that makes it really hard for me to get some of my friends to use it. Having said that, I agree that Signal's UX is not bad , just that it could be better.
Stuff like multiple clients with shared chat history is a huge pain in the ass for full proper end to end encrypted chats. This is why whatsapp web uses your phone as a proxy and signal does some janky shit to work on multiple devices. Telegram went UX first and turned down the crypto so that I can install Telegram on a fresh laptop and I've instantly got the same chats, with history, as I do on my phone.