Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Signal Fork with WhatsApp Migration

github.com

Post reply on HN
Print view View original

1–10 of 158 posts

Re: Signal Fork with WhatsApp Migration

#3

Post by robjan »

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.

Re: Signal Fork with WhatsApp Migration

#4

Post by teruakohatu »

blackbear_ wrote: post #2

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.

Re: Signal Fork with WhatsApp Migration

#5

Post by theshrike79 »

teruakohatu wrote: post #4
blackbear_ wrote: post #2

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.

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

Re: Signal Fork with WhatsApp Migration

#6

Post by Semaphor »

robjan wrote: 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.

That’s essentially what this is. You install it to migrate, then you remove it again and install the original Signal app, as per the steps in the repo.

I would guess it was easier (or even only possible) this way.

Re: Signal Fork with WhatsApp Migration

#7

Post by vmception »

theshrike79 wrote: post #5
teruakohatu wrote: post #4

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

People only ever mention Signal because of the security by default. Telegram does not have that, their encrypted rooms are something you have to go out of your way to create.

Re: Signal Fork with WhatsApp Migration

#8

Post by carlos22 »

theshrike79 wrote: post #5
teruakohatu wrote: post #4

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

Thats true, Telegram has very good UX. But bullshit crypto with a closed server etc. :-(

Re: Signal Fork with WhatsApp Migration

#10

Post by eloisant »

telesilla wrote: post #9

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

It isn't harder to use than Whatsapp. It's actually simpler, because it has less useless bells and whistles.

All you need to do is convince them that it's for their good, if they can agree on that then the technicality isn't difficult.

Post reply on HN