Live data from Hacker News

Signal Fork with WhatsApp Migration

github.com

11–20 of 158 posts

Re: Signal Fork with WhatsApp Migration

#11
post #3

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.

If the backup restore is a merge rather than a nuke and pave it might make sense to do whatever Molly[1][2] does to allow it to be installed alongside Signal, so it's install this, import from WhatsApp, then backup/restore without having to do the uninstall/reinstall dance.

[1] https://github.com/mollyim/mollyim-android

[2] https://news.ycombinator.com/item?id=25743852

Re: Signal Fork with WhatsApp Migration

#12

Earlier 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

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

#13

Anyone know how to get their elderly parents to switch? Whatsapp has us cornered and they know it.

I sent the link to my elderly parents. They both installed it on their Android without a problem. Then I received a video call from my mum - she'd installed the desktop app by herself.

So, get better parents?

Re: Signal Fork with WhatsApp Migration

#14

Why 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.

Well, sort of. They have their idea of what they want (approximately "security for the masses"), and if your pull request doesn't go in the same general direction they don't care about it. If it does, they're positivish but they still aren't eager about fixing your code.

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.

Post reply on HN