Talk:Wire Swiss
Latest comment: 6 years ago by Dodi 8238 in topic Leadership changes, open source server
| This is the talk page for discussing improvements to the Wire Swiss article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
 | The following Wikipedia contributors may be personally or professionally connected to the subject of this article. Relevant policies and guidelines may include conflict of interest, autobiography, and neutral point of view.
|
GPL Licensing
editThe GPL license (and other open source licenses) seem to apply to client software only. The client applications still need to connect to a server but none is available under an open source license currently. Therefore an end-to-end communication does not appear to be possible using solely open source software. Should this be made more clear in the article's license section?
Tunkki-1970 (talk) 12:29, 28 July 2016 (UTC)
- Could you elaborate? By "end-to-end communication", I assume you mean "peer-to-peer communication". Wire is not based on the peer-to-peer communication model, but on the client–server model. Even if Wire Swiss GmbH open-sourced their servers, that would still not make Wire peer-to-peer. If you mean end-to-end encryption, then you are mistaken. The encryption is based entirely on open-source software because the keys that are necessary to decrypt the communications are generated and stored at the endpoints (i.e. by users, not by servers). The keys never leave the clients except with explicit user action, such as to backup a key or synchronize keys between devices. Using centralized servers for the relaying of communications and storing of public key material does affect the end-to-end encryption. --Dodi 8238 (talk) 13:50, 28 July 2016 (UTC)
- I do not mean peer-to-peer communication. As you said, Wire uses client-server model. Therefore, an open sourced client by itself does not function as a communication tool. You cannot communicate without using the server. There's only a proprietary server available for Wire communications. There are no open source servers that can be used with Wire currently.
- By stating on the article that Wire is GPL/open source software, an impression is given that anyone can use Wire communication with an open sourced technology stack. This is currently not possible.
- The question then is should the article be more clear about this limitation of Wire software -- that it requires proprietary components to function -- and how should this information be presented on the article? Tunkki-1970 (talk) 15:05, 28 July 2016 (UTC)
- Thanks for clarifying. I have now made some changes. Hopefully this makes it clearer that the service is centralized and that the servers are proprietary. --Dodi 8238 (talk) 16:05, 28 July 2016 (UTC)
The company seems to have changed their postion on partial end2end encryption.
edit"All Wire applications across all platforms uniformly use state-of-the-art encryption mechanisms that are recognized as reliable by experts and the community.
"Text, voice, video and media on Wire are always end-to-end encrypted 1:1 and in groups, so all your conversations are secure and private. Conversations are available on multiple devices and platforms without weakening security." — Preceding unsigned comment added by 2607:FB90:A509:B147:60E5:2BFE:53AC:9F42 (talk) 13:00, 20 November 2016 (UTC)
- That is already made clear in the article, both in the lead and history sections. This is not a forum for general discussion of the article's subject. Please suggest exact changes and provide reliable sources. Thank you. --Dodi 8238 (talk) 21:51, 21 November 2016 (UTC)
German and Spanish Wikipedia articles
editWhats the best way to refer to these related articles in the German and Spanish Wikipedia!?
--ColAflash (talk) 13:05, 24 November 2016 (UTC)
- Both of those articles are about the Wire application. This article is about Wire Swiss GmbH, the company that is behind the application. If an article is written here on the English language Wikipedia about the Wire application, then that article can be added to the same Wikidata item as the German and Spanish articles: wikidata:Q26934461. If articles are written at the German and/or Spanish language Wikipedias about Wire Swiss GmbH, then those articles can be added to the same Wikidata item as this article: wikidata:Q18712630. --Dodi 8238 (talk) 13:51, 24 November 2016 (UTC)
Leadership changes, open source server
edit | This edit request by an editor with a conflict of interest has now been answered. |
Leadership:
- Alan Duric is now CTO/COO
- Morten Brøgger is the new CEO (former CEO of Huddle)
- Source: http://www.businessinsider.de/huddles-ceo-coo-quit-3-months-acquisition-2017-12?r=US&IR=T
Server open source:
- Wire announced on September 19, 2017 that 100% of its server code is open source
- AGPL license
- Source: https://www.networkworld.com/article/3188972/open-source-tools/instant-messaging-service-wire-open-sources-its-server-code.html
— Preceding unsigned comment added by Siimteller (talk • contribs) 13:48, 21 December 2017 (UTC)
Done. The Network World article that you provided was published in April, so it can only be used support the claim that Wire Swiss started open sourcing Wire's server code around that time. I have now used the Medium article that Wire Swiss published in September instead. --Dodi 8238 (talk) 22:58, 21 December 2017 (UTC)
