[Call for action] Native Signal app. [not relevant]
A Signal app is something that just should exist for Sailfish, I want to make it so. I could perhaps pull it off... but not with the quality and features it deserves and in a reasonable time frame, therefore i'm looking for collaborators. I can throw time, some money and phones at the project, but not enough for what i'd like to achieve.
I think 3-5 active developers should be enough to make it happen, but it's not like i'd turn people away for wanting to contribute. Not being a one-man-show also significantly increases the chances for the project surviving. I'm not even saying it needs to be me running the show. Other contributors, like beta-testers would also be appreciated, but later.
Plan of attack:
- Use official C library from C++
- Rely on sailfish-secrets for (key) storage
- Look in to ways of using reproducible builds and verifying the integrity of the running application
- < your suggestion here >
Any takers?
Hmm wasnt there an abandoned SFOS app somewhere on github? Edit : Whisperfish?
tortoisedoc ( 2019-04-25 22:37:01 +0200 )edit@tortoisedoc Yes, it has gone unmaintained. The app is written in go, which is not accepted in harbour afaik and a bit of an oddball choice imo. I assume it's also not all that fun to work with an old, unofficial, seemingly unmaintained, client library written in go.
attah ( 2019-04-25 22:48:09 +0200 )editIf you need, I can help on using sailfish-secrets, either from C++ or C.
Damien Caliste ( 2019-04-26 11:36:13 +0200 )editso apart of the c library; we would mainly need a qml frontend
tortoisedoc ( 2019-04-26 12:24:56 +0200 )editAs far as I know, Signal does not accept third-party clients connect to their server. (Might be technically possible, but they don't allow it.) It's not an open system as, for example, XMPP/Jabber.
Mario ( 2019-04-26 14:46:06 +0200 )edit