You might want to contact the EFF to see if they will add you to their "scorecard" for secure messaging programs:
More information about GPL and Mobile Stores: https://www.fsf.org/blogs/licensing/more-about-the-app-store...
And any fork will need this permission again? I believe that crypto implementations need to be in public domain. What if people can't use some software and will stay unsecured?
From what I can see the Signal application uses GPLv3'd code. I have no idea how it is still available in the Apple store.
1: https://github.com/trevp/axolotl/wiki 2: https://github.com/agl/pond/tree/master/client/ratchet
I already implemented in the past crypto for Telegram, there waere a lot of small mistakes in the implementation part. Even Telegram have many resources, but we haven't.
Whether you like copyleft licenses or not is irrelevant. They are the wishes of the person who developed the original code.
Is there anything HN community can help you with?
Someone can try to translate platform to various languages.
But we need good quality, this is the main point. We don't want to be another opensource-based company that don't have resources to build good software and use small community opportunities to build something that at least works, we want quality. This is essential for messaging: speed, reliability and UI/UX.
"Actor" is named after Actor Model, where Actors are small valuable pieces of code that can integrate with other Actors of different kinds. The same idea can be for services, build deeply integrated experience of tools that we are using.
This is dreams, but i have not evidence that they can't be true.