like, precisely. pidgin is an insecure piece of shit. signal desktop is an unusable piece of shit. when did we collectively forget how to write desktop apps that are minimally functional twitter.com/rqu45/status/1
Conversation
signal is the one electron app i do not outright refuse to use and i regret it almost every day
5
3
51
Replying to
Maybe signal-cli? github.com/AsamK/signal-c Or is there a libpurple implementation you could use from Bitlbee?
1
1
Replying to
i've seriously considered using signald but it seems like that'd also be kind of a nightmare
1
1
It's also quite possible that it will break because Signal makes backwards incompatible changes and forces updating the client. It regularly phases out support for older client versions and forces people to upgrade so they don't need to worry about older protocol versions.
1
It requires an ongoing commitment to quickly adapting to any of the upstream changes. I don't think it can really be relied upon to continue working. The upstream project also doesn't like that it exists and doesn't want people using their server with alternate clients.
2
It uses a very lightly modified fork and is currently missing the most recent minor bug fix release from a few days ago. The library doesn't completely abstract it though so it still has to adapt to various changes. The library doesn't offer any guarantee of a stable API.
1
It's also completely possible that they'll do things like migrating their code to Kotlin similar to how they started replacing Objective-C with Swift in their iOS app. It can definitely work long-term, but it depends on keeping up with everything that ends up changing in Signal.
1
1
I think that's a lower-level component than libsignal-service-java equivalent to github.com/signalapp/libs. It's the cryptographic protocol rather than the higher level messaging protocol. They use the C code in the iOS app and the Android app and server both use the Java code.
yeah, I mean, what do you think about building something on top of it? because i'm annoyed with Signal Desktop badly enough i want to do that.
2
2
I'm wary of building anything on their code or forking anything to make changes because of their hostility towards alternate clients using their servers and their lack of need to preserve any backwards compatibility due to forcing upgrades, which is an overall positive thing.
1
2
Show replies
I really wouldn't assume that the C libraries are going to continue to exist since they're migrating code to Swift and I don't think it's any less suitable than C for that kind of code. They'll probably replace all the Objective-C code first though: github.com/signalapp/Sign.