Live data from Hacker News

Show HN: Actor Messaging platform

github.com

31–40 of 40 posts

Re: Show HN: Actor Messaging platform

#33
post #14
post #11

Earlier 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.

Understandable. Other than that the project looks quite interesting -- good luck!

Re: Show HN: Actor Messaging platform

#34
post #27
post #25

Earlier 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.

I'd be very interested, but I'm sure he has more important stuff to do :)

Re: Show HN: Actor Messaging platform

#36

This 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.

Re: Show HN: Actor Messaging platform

#37
post #36

This 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.

Yeah, that's what I meant. Is it possible to get mobile app authentication working with email?

Thanks!

Re: Show HN: Actor Messaging platform

#38
post #4
post #3

Earlier 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?

Incorporate Moxie's encryption as a module. Distribute this version for those who want it (and have jailbroken phones, where relevant), and use it as a reference implementation when you build an alternative that is more generally available. Meanwhile, criticize Apple's anti-gpl policies for making their users less secure.

Re: Show HN: Actor Messaging platform

#39

Earlier 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...

Those are just Scala unicode operators http://scala-lang.org/files/archive/spec/2.11/01-lexical-syn.... They are equivalent to

Re: Show HN: Actor Messaging platform

#40
post #30
post #4

Earlier 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.

That's not entirely true. They forbid using other people's code licensed under the GPL because it is not possible to meet its conditions[1]. Basically, they don't want to deal with the possible resulting copyright lawsuit. If you own the copyright to all the code used in your app, then there is no issue.

[1]: http://apple.stackexchange.com/a/59495/101602

Post reply on HN