> Moxie has threatened to shut LibreSignal down if they allow LibreSignal users to message normal Signal users, and refused to even discuss alternative solutions.
Please cite this. To my knowledge I never threatened anything, and your comment is a response to a quote from the discussion about LibreSignal, where I suggest that they submit a PR with the functionality they desire to Signal. Is that not an alternative?
> He also uses the GCM library from Google, which pulls in several analytics libraries into the APK
Could you cite this as well? Here's the entire POM file for the version of the GCM library we use:
A single dependency. If you follow it, the only transitive dependency is the supportv4 library. Where are the "several" analytics libraries?
> (And in addition to that, Moxie even refuses to allow any distribution that doesn’t come with full analytics, which is extremely user hostile.)
What do you mean by "full analytics?" Is there something user hostile about having an aggregate count of the number of users you have on what platforms, so that you can develop and deploy software accordingly? About being able to receive crash reports when users choose to submit them so that you can fix their problems?
If they can’t fork it while still using your servers, and you refuse to allow federation, how the FUCK is it open in any way?
How are users supposed to be able to verify the software running on their own systems when you only allow binaries compiled by yourself to communicate with your users, abusing the lock-in effect?
> Could you cite this as well?
Have you actually read the code that gets compiled in when you depend on play-services-base and play-services-gcm?
As I happen to have reversed all of it to write an open source library for GCM, I have. And let me tell you, most of the code in there is "measurement"-code.
> What do you mean by "full analytics?"
Distributing through any means where the user can get the app without being required to be fully tracked by the Google Play Services?
You only distribute through the Play Store, which doesn’t fully work with microG at the moment, requiring users to install spyware on their devices.
> If they can’t fork it while still using your servers, and you refuse to allow federation, how the FUCK is it open in any way?
What makes you think you have a right to demand federation? Run your own server if you don't like how they're doing it. You have access to the source under a Free Software license https://github.com/WhisperSystems but of course you don't want to actually do any work, you want to complain about what other people do because they don't do it in the exact way you want it done for free.
> How are users supposed to be able to verify the software running on their own systems when you only allow binaries compiled by yourself to communicate with your users, abusing the lock-in effect?
> but of course you don't want to actually do any work, you want to complain about what other people do because they don't do it in the exact way you want it done for free.
Nah, I don't spend months of my own free time maintaining an open source IRC app, and working on creating tools to make IRC easier for users to use.
I don't actually spend time making open chat systems more useable to users, sure.
That accusation from you doesn't belong at all on HN, and is not only a personal attack, but also wrong.
I could just run a Signal fork with my own servers tomorrow, but one of my goals is to allow users to have one single place where they can send a message to a user, and it will arrive. No matter what service the other user uses, what app, what chat system, if they're on an obscure 20 people IRC network, on Signal, WhatsApp, etc.
My ideal goal would be a universal, federated protocol, but even having libraries for each protocol with a unified API would make things already easier.
And Moxie is fighting for the opposite.
He fights against any compatibility, and suggests I tell my mother to install yet another chat app, ignoring that her phone can't even install Signal in the first place because it only has 3MB of useable memory, left.
You and Moxie actively tell people to create more, and less interconnected, chat networks.
How the fuck is that going to help?
If everyone uses a different secure app, that doesn't help at all! People will just use the systems everyone has (case in point: usage of SMS in the US, or WhatsApp everywhere else), and thereby you ensure no one gets any security.
So stop insulting people you don't know, and claiming untrue motives to be theirs, just so you can justify your actions.
> My ideal goal would be a universal, federated protocol, but even having libraries for each protocol with a unified API would make things already easier.
And Moxie is fighting for the opposite.
Yet here you are, pissed off that your goals don't align with someone elses. Use your open source IRC app to talk to your mom and I'll use Signal to talk with mine. No one is forcing you to do anything. Considering your goals and ideas are superior surely whatever you're suggesting will become the one service everyone uses, problem solved.
> If they can’t fork it while still using your servers, and you refuse to allow federation, how the FUCK is it open in any way?
"Open" doesn't mean you get to use someone else's servers. It just means that the code is there and you can make use of it in your app. There are a ton of things in that code that are valuable and useful as open source beyond the line that lists the URL of their servers.
I don't disagree with you, but the reality of running an API service in the cloud means it's tough to support more than just your own clients if you don't have a large budget. And it's easier to coordinate breaking changes if you have control over both the client and server.
Please cite this. To my knowledge I never threatened anything, and your comment is a response to a quote from the discussion about LibreSignal, where I suggest that they submit a PR with the functionality they desire to Signal. Is that not an alternative?
> He also uses the GCM library from Google, which pulls in several analytics libraries into the APK
Could you cite this as well? Here's the entire POM file for the version of the GCM library we use:
<?xml version="1.0" encoding="UTF-8"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelVersion>4.0.0</modelVersion> <groupId>com.google.android.gms</groupId> <artifactId>play-services-gcm</artifactId> <version>8.1.0</version> <packaging>aar</packaging> <dependencies> <dependency> <groupId>com.google.android.gms</groupId> <artifactId>play-services-base</artifactId> <version>8.1.0</version> <scope>compile</scope> <type>aar</type> </dependency> </dependencies> </project>
A single dependency. If you follow it, the only transitive dependency is the supportv4 library. Where are the "several" analytics libraries?
> (And in addition to that, Moxie even refuses to allow any distribution that doesn’t come with full analytics, which is extremely user hostile.)
What do you mean by "full analytics?" Is there something user hostile about having an aggregate count of the number of users you have on what platforms, so that you can develop and deploy software accordingly? About being able to receive crash reports when users choose to submit them so that you can fix their problems?