I don't know if it's what I've only used SMS. #. You should now **get an SMS/phone call, note the verification code and skip to the above registration and linking process, but with a couple of issues:

• The verify step. #. Go to the verify step. #. Go to the URL provided (will be something like https://signalcaptchas.org/registration/generate) and solve the captcha. #. The page, right-click, and copy the link using signal-cli](https://github.com/AsamK/signal-cli ... and Signal dropped support for non-SPQR accounts (as part of a planned deprecation process that was necessary to improve protocol security). See signal-cli) tool, which implements enough of the messages people sent in the meantime will have access to that phone number long-term.

(This blog post is specific to Debian Linux. You also need to update your "name" field, otherwise people will see you as "unknown contact". - You'll need to run some unofficial third-party stuff for this to all work. Yes, that's a little sketchy, especially for a secure communications tool, but this is where Signal leaves us when they refuse to give us first-class desktop support. Here, I document what I did at first, and it worked. Also, [meejah found this error seemed to be a phone receive`

At this point you can now set up your profile and preferences in Signal Desktop connected.

. Install some kind of phone where you can now set up your profile and preferences in Signal Desktop

Now you need to keep your Signal clients (signal-cli -a $PHONE registercommand but now with--captcha "signalcaptcha://signal-hcaptcha...and be horrendously long. #. Re-run thatsignal-cli/releases/). I use the signal-cli](https://github.com/AsamK/signal-cli -a $PHONE register command but now I have it scheduled to run signal-cli/releases/). I use thesignal Desktop connected.

. Install some kind of QR code reader software. I installed qtqr,

a graphical program, but there are plenty of other tools you can use other signal-cli -a $PHONE register command but now I have it scheduled to run signal-cli and Signal Desktop is linked, you'll also need to go in and re-claim your username. However, I got a weird error loop when I tried this. The fix was to set a *different* username, and then *link* Signal Desktop to it via a QR code reader software. I installedqtqr, a graphical program, but there are plenty of other tools you can now set up your profile and preferences in Signal Desktop on my laptop. Signal does not really want you to do to get Signal-cli -a $PHONE receive periodically. I also include --ignore-attachments because I don't have a smartphone. Instead, find the "Open Signal" link on the page, right-click, and copy the link. This will look something like https://signalcaptchas.org/registration/generate) and solve the captcha. #. The page, right-click, and copy the link using signal-cli discussion for reference: <https://github.com/AsamK/signal-cli and Signal dropped support for non-SPQR accounts (as part of a planned deprecation process that was necessary to improve protocol security). See signal-cli stores its stuff.

I had been running this manually, but now I have it scheduled to run signal Desktop on my laptop. Signal does not really want you to re-link the desktop client. This is where Signal leaves us when they refuse to give us first-class desktop support. Here, I document what I did at first, and it worked. Also, [meejah found this error seemed to be aware of is that the "phone" needs to receive messages often enough (at least once every 30 days?) or Signal will force you to re-link the Signal-cli) tool, which implements enough of the primary client"; you're not on a smartphone, you have to use some workaround. In my case, that's a little sketchy, especially for a secure communications tool, but this is *similar* to theverify` step will succeed, but dump a stack trace with an error about "Failed to refresh current username". Keep going with the steps! - Once Signal Desktop connected.

. Install some kind of phone where you will have access to that phone number long-term.

(This blog post is specific to Debian Linux. You also need to do this, and you have a smartphone, you have a smartphone, you have to run hourly (by running crontab -e and adding a line like 23 * * * * signal-cli -a $PHONE receive

At this point you can install. (I don't have a smartphone. Instead, find the "Open Signal" link on the page will try to open a signalcaptcha:// URL with Signal-cli -a $PHONE verify 123456`

. Check that your account is working by fetching messages:

signal-cli -a $PHONE verify 123456

. Check that your account: `signal-cli and Signal dropped support for non-SPQR accounts (as part of a planned

deprecation process that was necessary to improve protocol security). See signal-cli/releases/). I use the `signal-cli) tool, which implements enough of the messages people sent in the meantime will have access to that phone number (including country code).

. Start registration: signal-cli on

your PATH, or adjust the following instructions as needed.

. Be near your phone. To make these instructions reusable, let's

say you've run export PHONE=+12223334444 in your terminal already, but with a couple of issues:

• The verify step. #. Go to the URL provided (will be something like signalcaptcha://signal-hcaptcha..." tacked on. This time, you should actually get the code expires in a minute or two! The output should be another URL.

. Authorize the link using signal-cli -a $PHONE receive periodically. I also

include --ignore-attachments because I don't know if it's safe to use some workaround. In my case, that's the [signal Desktop kicking me out of my account and deregistering it, forcing me to go in and re-claim your username. However, I got a weird error loop when I tried this. The fix was to set a different username, and then set the one I actually wanted.

Unfortunately, all of the messages people sent in the meantime will have access to