Remix.run Logo
▲ codedokode a day ago

Yes it is awful. I do not even understand how I can "verify" a temporary browser session which gets destroyed after a log out.

Reminds me of WhatsApp vs Telegram. In Telegram to log in from a new device, you just enter the phone number and the code. In WhatsApp you need to scan some codes, do other things, overcomplicated.

▲danelski a day ago | parent | next [-]

Telegram doesn't have the E2E encryption apart from the private chats bound to a single device. No wonder their process can be simpler.

▲tomstockmail a day ago | parent | prev | next [-]

In the Element client, Element X on android, you scan the QR code and enter a series of emojis. It's slightly more involved than telegram/Whatsapp, but I would not be surprised if they do something similar in the future.

What is slow is the syncing after that, which I understand depends on a variety of factors.

▲codedokode a day ago | parent | next [-]

By the way I do not really need the history and I believe it should be disabled by default - like in real life conversations where there is no history - so I do not understand why syncing needs to be slow. Cannot you just fetch last 10 messages when the user opens a room?

▲tomstockmail a day ago | parent [-]

Sure, there's retention policies you can set for the synapse server. Not sure on other implementations.

▲wolvoleo a day ago | parent | prev [-]

You don't have to enter the emoji. You just have to verify that they're the same at both ends.

▲tcfhgj a day ago | parent | prev | next [-]

> I do not even understand how I can "verify" a temporary browser session which gets destroyed after a log out.

why shouldnt you be able to do that? Even WhatsApp does it

▲pbmonster a day ago | parent | prev [-]

You do realize that in both those cases, private crypto keys are being transferred to the new/temporary device?

There's really only so many ways you can do that securely.

▲rwmj a day ago | parent [-]

[dead]