Woah, how did you do that?
Can you provide a log when you do that? It might be a new style of V2 group that uses sender keys instead of classic Signal protocol. Group V2v3, so to speak…
It was as simple as opening a conversation view, tapping on a UUID to open its detail view, pulling down to “Link” it to a contact. I was quite surprised because this felt so … intuitive 
As for the “V2v3” group message log, I’ll do my best and if it yields something readable, I’ll file a bug report.
1 Like
So you now have contacts that have UUIDs for phone numbers? 
Indeed, you are right, I didn’t notice so far, and for some reason, those UUIDs don’t propagate upstream (via CardDAV), so I also didn’t notice it there. Hrm … this is not what I intended. It works, though.
1 Like
That does inspire me to look whether there’s a custom field that I can use to store the UUID. That would make a lot of sense.
3 Likes
Well, vcard does have a instant messaging field, I guess that would be suitable.
Not widely supported (as in not really at all), but if it works only on sfos, but does sync the information it may be good enough.
1 Like
… and given that Sailfish stores information for XMPP and the like, it makes sense that it’ll work!
I have an even more stupider workaround: copy the UUID from the contact card and add it as a phone number in the People app for desired contact 
I can’t open the contact page for single-person conversations.
Very odd, but correct: 1:1 conversations don’t even offer this!
Unfortunately, cannot reproduce, which is nice. It will reappear when I stop logging in debug mode, of course.
1 Like
Hi. Yesterday friends of me tried to send me a message via their Android Signal app. But it was not possible. But they could not see me in their app as known contact and I could not send them any message via my whisperfish v 060 beta 11. Each message was blocked. Are there any problems with new Signal members?
Oh, dear. Beside having support conversations with UUIDs and not knowing who I’m talking to (which is amusing and leads me to reflect), I keep getting invitations of the form: Signal Group… which I can’t seem to join. How do I join a group?
As mentioned in first post, the other person must add you to the group instead of inviting you.
2 Likes
Thanks! I’ll see if I can get them to do so! (that was a long way to scroll!)
EDIT, and that works! Yeah.
Hi! Sorry to hear this. I fear this is a new bug, and will need quite some work to get everything working up to speed there. This is related to Signal removing phone numbers as mandatory registration mechanism, but this complicates the registration and initial contact procedures by a lot.
1 Like
Since a few hours Whisperfish is in disconnected state.
Has something critical changed with Signal?
[2022-10-26T21:36:13Z ERROR harbour_whisperfish::worker::client] Refresh pre keys failed: Error sending req
uest: Failed to connect to host: invalid peer certificate contents: invalid peer certificate: UnknownIssuer
[2022-10-26T21:36:13Z ERROR harbour_whisperfish::worker::client] Error starting stream: ServiceError
[2022-10-26T21:36:13Z INFO harbour_whisperfish::worker::client] Retrying in 10
The unknown issuer is apparently Signal itself (openssl s_client -connect chat.signal.org:443 shows a self-signed cert).
Is that related?
1 Like
Thanks for reporting!
Certificate error is sure enough to render Whisperfish useless… 
It shouldn’t be a big thing to fix though.
It has always been self-signed, that’s normal.
Would it suffice to gather the CA certificate and add it to the system trust list, or does WP have its own store to verify?
Whisperfish has its own pinned certificate. Update should be out in some hours that fixes this. Sorry for the inconvenience!
To ease the waiting time, you can watch me babble about Signal, Whisperfish and secure messengers, in a talk that I gave in Lausanne last weekend:
9 Likes