Doesn't it make more sense to have a WhatsApp backup file to Signal backup file converter rather than forking the whole app. This fork would end up being a significant maintenance overhead for something that could be done more simply.
Signal Fork with WhatsApp Migration
11–20 of 158 posts
Re: Signal Fork with WhatsApp Migration
#12Earlier quoted context omitted.
I might have the wrong impression but Signal has always seemed to me to be uninterested in user requests. They are privicy first & user experience second. There have been lots of Signal forks with a variety of features the official client refuses to add or merge.
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
But yeah, Telegram can't be trusted either. I hope matrix/element will replace both soon.
Re: Signal Fork with WhatsApp Migration
#13Anyone know how to get their elderly parents to switch? Whatsapp has us cornered and they know it.
So, get better parents?
Re: Signal Fork with WhatsApp Migration
#14Why a fork? Why not a pull request?
I might have the wrong impression but Signal has always seemed to me to be uninterested in user requests. They are privicy first & user experience second. There have been lots of Signal forks with a variety of features the official client refuses to add or merge.
FWIW I've had one (very small thing) accepted and another not. That second wasn't a net positive if "security for the masses" is the only important goal.
Re: Signal Fork with WhatsApp Migration
#15Re: Signal Fork with WhatsApp Migration
#16Does Signal do group chats like Telegram does?
Re: Signal Fork with WhatsApp Migration
#17Re: Signal Fork with WhatsApp Migration
#18Does Signal do group chats like Telegram does?