The use of unicode in the source is interesting. ← and ⇒
Show HN: Actor Messaging platform
31–40 of 40 posts
Re: Show HN: Actor Messaging platform
#32The use of unicode in the source is interesting. ← and ⇒
Could you link to the sources you're talking about? That sounds interesting.
Re: Show HN: Actor Messaging platform
#33Earlier quoted context omitted.
You're free to re-implement the public-domain protocol[1] under your own license. Pond has a 3-clause BSD licensed Golang implementation[2] that Moxie even references in the Axolotl announcement blog post. 1: https://github.com/trevp/axolotl/wiki 2: https://github.com/agl/pond/tree/master/client/ratchet
Re-Implementing cryptography is VERY costly operation that we cannot afford now. 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.
Re: Show HN: Actor Messaging platform
#34Earlier quoted context omitted.
Thank you for sharing the code! I read through your documentation and noticed there is documentation of server-client but not server-server. How do you achieve a multi-server architecture? Is it simply to scale the Postgre database and connect more server frontend to it and load balance over those frontends? Or is there some inter server protocol as well?
Actor is built on top of Akka that have built-in support for node-to-node communication. When our CTO will wake up, he will answer in details how it works.
Re: Show HN: Actor Messaging platform
#35Re: Show HN: Actor Messaging platform
#36This is great! Any chance of making it so that it can use email instead of SMS in the mobile app though? SMS gets expensive really quickly in Australia. Thanks again! :)
But we have email authentication now and we just not implemented it apps. We also can to do OAuth2 authentication.
Re: Show HN: Actor Messaging platform
#37This is great! Any chance of making it so that it can use email instead of SMS in the mobile app though? SMS gets expensive really quickly in Australia. Thanks again! :)
We provide SMS authentication for free. If it will be costly for us, then we will switch to Twitter's free sms authentication solution. But we have email authentication now and we just not implemented it apps. We also can to do OAuth2 authentication.
Thanks!
Re: Show HN: Actor Messaging platform
#38Earlier quoted context omitted.
Thanks for opening the source. You might want to contact the EFF to see if they will add you to their "scorecard" for secure messaging programs: https://www.eff.org/secure-messaging-scorecard
I want to implement full e2e encryption with Moxie's encryption and I can't because it is GPL( GPL is not comparable with mobile apps at all. Also I think that implementing encryption by ourselves will be mistake. May be some one can contribute?
Re: Show HN: Actor Messaging platform
#39Earlier quoted context omitted.
Could you link to the sources you're talking about? That sounds interesting.
https://github.com/actorapp/actor-platform/blob/master/actor...
Re: Show HN: Actor Messaging platform
#40Earlier quoted context omitted.
I want to implement full e2e encryption with Moxie's encryption and I can't because it is GPL( GPL is not comparable with mobile apps at all. Also I think that implementing encryption by ourselves will be mistake. May be some one can contribute?
I don't like the way you've framed the debate. As I said below, the reason you aren't allowed to publish applications containing GPL'd source code in the Apple Store isn't because the GPL forbids it, it's because Apple forbids it; they have an unnatural hatred for the GPL. Whether you like copyleft licenses or not is irrelevant. They are the wishes of the person who developed the original code.