~nicoco/slidgnal#4: 
'register' is broken

Trying to set up an account with 'register' -- making it a root account -- instead of 'link' -- making it a subaccount -- fails at the moment due to Signal-Server API changes, which are hitting signald and therefore Slidge.

me> register
slidge> Registration to 'Signal (slidge)'

Fill the form to register a new signal account. If you want to link slidge to an existing signal account, use 'link' (ad-hoc or chat command).
You may need to complete a captcha first, cf https://signald.org/articles/captcha/#getting-a-token

Phone number (ex: +123456789)? (or 'abort')
me> [redacted]

slidge> Your name (or nickname)? (or 'abort')
me> name
slidge> Captcha token? (or 'abort')
me> signal-hcaptcha.<UUID>.registration.<very-long-token>
slidge> Error: InternalError: {'message': 'error registering with server'}
End of command.

If I look through journalctl -u signald I indeed see a 404 as reported in the other issue:

Sep 27 07:48:51 xmpp.example.org signald[39316]: 07:48:51.460 [wt03c1l4jw-register] ERROR register - error while handling request
Sep 27 07:48:51 xmpp.example.org signald[39316]: java.lang.InternalError: error registering with server
Sep 27 07:48:51 xmpp.example.org signald[39316]:         at io.finn.signald.clientprotocol.v1.RegisterRequest.run(RegisterRequest.java:62) ~[signald.jar:?]
Sep 27 07:48:51 xmpp.example.org signald[39316]:         at io.finn.signald.clientprotocol.v1.RegisterRequest.run(RegisterRequest.java:30) ~[signald.jar:?]
Sep 27 07:48:51 xmpp.example.org signald[39316]:         at io.finn.signald.clientprotocol.Request.<init>(Request.java:146) ~[signald.jar:?]
Sep 27 07:48:51 xmpp.example.org signald[39316]:         at io.finn.signald.clientprotocol.ClientConnection$RequestRunner.run(ClientConnection.java:160) ~[signald.jar:?]
Sep 27 07:48:51 xmpp.example.org signald[39316]:         at java.lang.Thread.run(Thread.java:829) ~[?:?]
Sep 27 07:48:51 xmpp.example.org signald[39316]: Caused by: org.whispersystems.signalservice.api.push.exceptions.NotFoundException: [404] Not found

I'm just opening this to pin this before anyone else comes along and thinks this is a bug in slidgnal. It's not. But maybe signald needs some help to get it fixed since it's been open two months and they haven't been able to fix it yet?

Status
REPORTED
Submitter
~kousu
Assigned to
No-one
Submitted
9 months ago
Updated
3 months ago
Labels
signald

~nicoco 9 months ago

Unfortunately it seems signald is in maintenance--- mode, which is the fate of a lot of FLOSS software. :'(

I don't know if it still works, but for a while, reverting to 0.23.0 (not 100% sure about version numer) just to register worked for me.

Keeping this opened as a reference for this is a good idea, thanks.

~kousu 9 months ago*

In the meantime the workaround is to run Signal on a spare phone, or a spare user profile on your phone, or maybe inside of the official android-emulator, or maybe inside of anbox, and then use link.

~kousu 9 months ago

which is the fate of a lot of FLOSS software. :'(

:'(

~nicoco 9 months ago

In the meantime the workaround is to run Signal on a spare phone, or a spare user profile on your phone, or maybe inside of the official android-emulator, or maybe inside of anbox, and then use link.

This workaround is not great because you have to make sure you keep that "signal main device" available somewhere because you can be asked to re-link at some point. The matrix bridges are moving away from signald, so maybe we should consider using their go lib instead. I suffer from engagement bias about signald because this is where slidge started, and I'm pretty happy with the python wrapper I wrote for it.

Register here or Log in to comment, or comment via email.