Earlier quoted context omitted.
Did you see that they implemented CBR for audio calls and submitted patches to both Signal and WebRTC? https://medium.com/@wireapp/call-security-constant-bit-rate-...
In 2017... CBR has been a thing in secure calling apps for ~5 years now.
Wire messenger server code open-sourced
61–70 of 71 posts
Re: Wire messenger server code open-sourced
#62I'm wondering if the clients will allow you to select any server or if you have to rebuild the apps just to do that. Never used Wired, but I am very interested.
Since a lot of the interest for self hosting comes from companies then a nicely packaged version is somewhere in the future.
Re: Wire messenger server code open-sourced
#63Re: Wire messenger server code open-sourced
#64Re: Wire messenger server code open-sourced
#65Earlier quoted context omitted.
Can you recommend some iOS/Android apps which support CBR?
Silent Phone is both Android and iOS compatible, and we have used CBR codecs since we launched (in 2012).
Re: Wire messenger server code open-sourced
#66Earlier quoted context omitted.
That's not accurate at all. If you contribute back changes to it then they have to comply with the license too and publish the source.
At least for contributions you directly submit to their project, they require you to sign a CLA. If I'm reading it right it allows them to use your changes in a private fork as well, as long as they are also included in the public version. https://cla-assistant.io/wireapp/wire-server
Re: Wire messenger server code open-sourced
#67Earlier quoted context omitted.
That's not accurate at all. If you contribute back changes to it then they have to comply with the license too and publish the source.
At least for contributions you directly submit to their project, they require you to sign a CLA. If I'm reading it right it allows them to use your changes in a private fork as well, as long as they are also included in the public version. https://cla-assistant.io/wireapp/wire-server
Re: Wire messenger server code open-sourced
#68Earlier quoted context omitted.
At least for contributions you directly submit to their project, they require you to sign a CLA. If I'm reading it right it allows them to use your changes in a private fork as well, as long as they are also included in the public version. https://cla-assistant.io/wireapp/wire-server
That's a blatant GPL violation. "No additional restrictions"...
Re: Wire messenger server code open-sourced
#69Earlier quoted context omitted.
As a service, what it's provided is consistency for the group of friends I use it with. We've tried XMPP and Matrix on multiple accounts and had trouble on the server and client side. Wire is out of the box a great option with open source ideologies and some feature we liked that weren't available with XMPP or Riot. They could have done the same thing with existing protocols, but I do like the way it was done and how…
It would be great if you could detail what issues you encountered with Matrix (and/or file some bugs to help things improve). Unlike XMPP, Matrix is still considered in beta which gives us a lot of flexibility in addressing shortcomings :)
Re: Wire messenger server code open-sourced
#70there is something i never understood, maybe someone can help me: what makes wire better than xmpp? why do we need yet another protocol for chat?
XMPP is terribly fragmented and the clients all suck.
Be sure to choose a good server: https://gultsch.de/compliance_ranked.html
And a good client: https://omemo.top
Dino is a new Linux client. It's nice and simple.