7mo ago

What do you think about using Beeper just for SMS?

It would be nice if I could get SMS 2FA-type notifcations on my desktop without having to use my phone.

I probably wouldn't use Signal with it, since Beeper's own page seems to suggest that sending Signal messages with it would be less secure! And, I guess, SMS isn't secure to begin with . . .

If I download and install Element, and then look at the SMS bridges available on Matrix's website, the recommended bridge instructions sends me over to Beeper, since I don't have my own server. Old and confused here . . .

14 comments

What OS are you using? Microsoft has a proprietary and data-sucking app that can allow you to send messages from desktop. I can understand wanting to avoid using it.
On Linux there's KDE Connect and a litany of other options as well (KDE Connect breaks a lot in my personal experience, although it has been more stable lately).
Jumping to Beeper for this seems like a bunch of extra steps to mimic things that already exist.
- Sorry, on Linux Mint 22.1. I'm not a big fan of KDE stuff in general, since it seems like you have to download tons of other stuff just to use one of their apps, but I suppose I could give it a look . . .
  
  There's also GSconnect, a gnome implementation. There's also Zorin Connect from Zorin OS.
  There is also scrcpy
  https://github.com/Genymobile/scrcpy
  Scrcpy literally copies the screen of your android device into a Window on your desktop
  Anyway, I found those by searching "kde connect alternatives."
  
  I guess that is one of the issues with reuse of frameworks and things. The first one takes a lot of new stuff. Subsequent KDE software doesn't
  I guess there are pro's and cons to all things.
It's definitely an option. It will do the things that you want (as long as your phone is online, but that is the same for any other solution).
sending Signal messages with it would be less secure
Yes, this is because Beeper converts the Signal protocol to the Matrix protocol and vice versa. In order to do this it needs to access the messages. So it needs to decrypt the messages, then re-encrypt them on the other side. This means that the bridge (in this case operated by Beeper) has access to your messages. This is often referred to as "end-to-bridge" encryption, as it isn't end-to-end anymore.
This is going to be true of any bridge you use that is hosted by a third party. You are always adding one additional trusted party into your communication.
the recommended bridge instructions sends me over to Beeper, since I don’t have my own server
Yes, to practically operate a bridge you need your own Matrix server. This is because the bridge will create a new Matrix user for every remote participant (every phone number you communicate with in this case). Doing this with regular mechanisms would be difficult (as signup is likely restricted in some ways) and inefficient (as each account would need to be checked for new messages separately). Beeper runs their own homeserver so that they can operate their bridges. However Beeper's bridges are only available to users on the same homeserver (this is not a protocol limitation, just their choice). So in order to use their bridges you need to make an account with them (which you can, it is free IIUC). Beeper also offers custom clients which have special features for interacting with their bridges (for example making it easier to start a conversation with a new phone number).
The alternative would be to run your own server and bridge (or hire someone to it on your behalf).

14 comments