I'm impressed by #wire - Its apps are all open source and well-polished. The **server-side** code is open source as well. They are pursuing a legitimate end-to-end encryption standard, rather than just building a closed ecosystem. And federation is supposedly on the to-do list.
I still haven't found my perfect messaging app yet, but this one has really differentiated itself from the other proprietary, insecure, or user-unfriendly apps out there.
long text, quoted verbatim
@pcrock Here's the direct link to their README: https://github.com/wireapp/wire/blob/master/README.md#open-source
```
Additionally, if you choose to build an Open Source App, certain restrictions apply, as follows:
a. You agree not to change the way the Open Source App connects and interacts with our servers; b. You agree not to weaken any of the security features of the Open Source App; c. You agree not to use our servers to store data for purposes other than the intended and original functionality of the Open Source App; d. You acknowledge that you are solely responsible for any and all updates to your Open Source App.
For clarity, if you compile the open source software that we make available from time to time to develop your own mobile, desktop or web application, and do not cause that application to connect to our servers for any purposes, then that application will not be deemed an Open Source App and the foregoing will not apply to that application.
```
long text, quoted verbatim
@illandan Aha, thanks!
So reading the full thing, it looks like you _can_ self-host and change it however you like (as the license is AGPL), but you aren't necessarily allowed to connect to Wire's own servers because that could violate their terms of use.
long text
@pcrock Yes, that is correct. You are technically allowed to make changes to code but without connectivity to Wire's servers, it would cease to be a Wire app. I don't really understand the motivation behind such a clause because:
1. I change the code, but no changes to the protocol that Wire uses for server interaction so, Wire servers can still understand the protocol.
2. I change the code, changing the communication protocol too
I can understand Wire blocking the usecase for (2), but doing it for (1) too would be overly broad IMHO.
*shrug* It's Wire's code, Wire's rules.
@illandan I didn't see that, do you have a link?