Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 2 days, 14 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 3 days, 13 hrs ago - more...
|
2016-05-17
, 11:02
|
|
Posts: 201 |
Thanked: 410 times |
Joined on Dec 2013
|
#42
|
Originally Posted by llelectronics
For me, bot the version on Harbor and the one posted here, are crashing when entering the verification code. No clue why.
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.
 |
|
2016-05-18
, 09:03
|
|
Posts: 237 |
Thanked: 502 times |
Joined on May 2010
@ Mittelfranken, Germany
|
#43
|
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...
|
|
2016-05-18
, 21:23
|
|
Posts: 426 |
Thanked: 1,812 times |
Joined on Dec 2013
|
#44
|
Originally Posted by gaelic
Its trying to restart. If you click on it however it should start normally.
For me, bot the version on Harbor and the one posted here, are crashing when entering the verification code. No clue why.
|
|
2016-05-19
, 07:26
|
|
Posts: 201 |
Thanked: 410 times |
Joined on Dec 2013
|
#45
|
Originally Posted by llelectronics
Then it asks for the verification code again and restarts again and ...
Its trying to restart. If you click on it however it should start normally.
|
|
2016-05-19
, 08:20
|
|
Posts: 426 |
Thanked: 1,812 times |
Joined on Dec 2013
|
#46
|
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.
Do you by chance have setup that Android Apps can't access the addressbook? That might be the cause. It needs access to it.
|
|
2016-05-19
, 09:31
|
|
Posts: 201 |
Thanked: 410 times |
Joined on Dec 2013
|
#47
|
Originally Posted by llelectronics
Thx, this is it, it crashes when it cannot access the contact data.
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.
 |
|
2016-06-08
, 22:15
|
|
Posts: 764 |
Thanked: 2,888 times |
Joined on Jun 2014
|
#48
|
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
Alternatives:
- Whisperfish: https://github.com/aebruno/whisperfish/releases
- Sailsecure: https://openrepos.net/content/schorsch/sailsecure
|
|
2016-06-09
, 08:20
|
|
Posts: 752 |
Thanked: 2,808 times |
Joined on Jan 2011
@ Czech Republic
|
#49
|
Originally Posted by nthn
Thanks for the heads up.
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
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:
Originally Posted by moxie0
I'm not OK with LibreSignal using our servers, and I'm not OK with LibreSignal using the name "Signal." You're free to use our source code for whatever you would like under the terms of the license, but you're not entitled to use our name or the service that we run.
Last edited by nodevel; 2016-06-09 at 09:17.
|
|
2016-06-09
, 21:46
|
|
Posts: 764 |
Thanked: 2,888 times |
Joined on Jun 2014
|
#50
|
Originally Posted by nodevel
Totally agreed, but so far this is the best we have, and we can hope 'unofficial' clients are not banned in the near future, or even that moxie has a change of heart. XMPP is getting there thanks to the Conversations people, but it needs some more tweaks to be really straightforward for people who just want to talk to their friends - and that stuff needs to be implemented on Sailfish as well, unless everyone intends on specifically using Conversations with the Android layer. As far as I know, no other messaging application/protocol even comes close.
Thanks for the heads up.
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:
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.
I had more reports on that and it seems to be related to a harbour/Jolla Store problem.
Donation for my sailfish apps via PayPal
Donate using Liberapay