![]() |
Re: TextSecure Jolla Edition (APK)
Then try manually installing the apk from my link and see if it works.
I had more reports on that and it seems to be related to a harbour/Jolla Store problem. |
Re: TextSecure Jolla Edition (APK)
Quote:
|
Re: TextSecure Jolla Edition (APK)
the one from the link worked alright. It starts LibreSignal. Now that I think about it, when updating from harbour it got stuck afterwards. maybe it didn't finish, but somehow harbour thinks it did...
|
Re: TextSecure Jolla Edition (APK)
Quote:
|
Re: TextSecure Jolla Edition (APK)
Quote:
|
Re: TextSecure Jolla Edition (APK)
This is strange then. It works here without a problem and apparebtly for others aswell.
Do you by chance have setup that Android Apps can't access the addressbook? That might be the cause. It needs access to it. |
Re: TextSecure Jolla Edition (APK)
Quote:
|
Re: TextSecure Jolla Edition (APK)
LibreSignal was abandoned: https://github.com/LibreSignal/Libre...ment-217211165
Alternatives: - Whisperfish: https://github.com/aebruno/whisperfish/releases - Sailsecure: https://openrepos.net/content/schorsch/sailsecure |
Re: TextSecure Jolla Edition (APK)
Quote:
It's worth reading the linked discussion as well and maybe reconsider if a messenger with such a hostile developer team is the one to use. IMHO the fact that its identification is based on phone numbers, that they are against IM federation, that their priority is to have control over the clients and most of all that they rely on Google's proprietary libraries (even though they can be easily replaced by WebSockets like in LibreSignal) pretty much nullifies their privacy aims. It is understandable that they do not have an infinite amount of funding, but if their mission is to bring a secure, privacy oriented messenger, then LibreSignal was, as a client, doing a better job than they were, and therefore the hostility towards it makes their intentions questionable. Also, judging from the linked discussion, if they find a way to ban clients like LibreSignal (they didn't have to, as they pushed the developer team to stop the client before any ban was needed), then nothing stops them from trying to be hostile towards Whisperfish and Sailsecure as well - and it's also good to mention that the developers of LibreSignal abandoned it mostly to find a new messaging service to support, as Signal turned out to be the way it did. This applies to SailfishOS clients as well after all: Quote:
|
Re: TextSecure Jolla Edition (APK)
Quote:
I must say moxie has a point, with control over the clients it's a lot easier to make sure that any bugs encountered are the fault of the Signal developers and not of a third party (who could be malicious, but also just lazy), and they can fix those bugs themselves and get everyone on the fixed version asap. The problem is that the solution of just not allowing any third party clients is the easy way out. Luckily taking the easy way out was not the underlying thought when they developed the protocol. |
All times are GMT. The time now is 12:06. |
vBulletin® Version 3.8.8