4 ms·

Empty promises and no screenshots. When I click through on one of the blog posts I see: "Advanced users can also help to correct problems: we welcome contribu

Empty promises and no screenshots. When I click through on one of the blog posts I see: "Advanced users can also help to correct problems: we welcome contributions. We expect people to tell us what needs to be corrected, but they can also do it and submit their patches. This is the way it worked with SFLphone and it works pretty well." So you have no idea IF there are any problems, or do you know that there ARE problems, but you assume they will be corrected soon? If any of the above then how can you state "Ring gives you a ... an unmatched level of privacy."? I am sorry to be negative about something that seems like it has our privacy at heart, but promising privacy when it might not be there at all is reckless. We in the first world have issues like "I don't want my e-mails scanned by companies" or "I don't want companies to see what I write", but in other parts of the worlds you can be killed if the wrong piece of communication falls in certain hands. So it is pretty important to get it right. You (Ring) provide no information on the site about the state of the code, reviews being done, etc.

desdiv 12y ago
I think this is their code: GNOME client: https://github.com/max3903/SFLphone https://github.com/max3903/SFLphone KDE client: https://github.com/Elv13/sflphone-kde https://github.com/Elv13/sflphone-kde Sounds like they recently relocated from their old homepage at http://sflphone.org http://sflphone.org to this new domain and just don't have everything in order yet.
- leni536 12y ago
  Their wiki: https://projects.savoirfairelinux.com/projects/ring/wiki https://projects.savoirfairelinux.com/projects/ring/wiki According to this their code repos: Daemon: https://gerrit-ring.savoirfairelinux.com/ring-daemon https://gerrit-ring.savoirfairelinux.com/ring-daemon Client library: git://anongit.kde.org/libringclient Clients: https://gerrit-ring.savoirfairelinux.com/ring-client-gnome https://gerrit-ring.savoirfairelinux.com/ring-client-gnome git://anongit.kde.org/ring-kde https://gerrit-ring.savoirfairelinux.com/ring-client-macosx https://gerrit-ring.savoirfairelinux.com/ring-client-macosx Not really well organized.
jordigh 12y ago
Savoir-Faire Linux are a local Montréal company with a lot of clout. I don't consider their promises empty, and I'm excited to see them working on this.
Elv13 12y ago
Ring-KDE announcment: https://elv13.wordpress.com/2015/05/07/announcing-ring-a-distributed-and-secure-multimedia-communication-platform/ https://elv13.wordpress.com/2015/05/07/announcing-ring-a-dis... (I am one of the developer, ask me anything) EDIT: There is screenshots on that page
- madez 12y ago
  As I asked in my direct comment on this submission: What are the advantages compared to Tox? I see one advantage of Tox compared to Jitsi. Account management is decentralized on Tox and federated on the protocols Jitsi supports. Are there plans to support Tox as a backend?
  - Elv13 12y ago
    As of now we have no plan to support Tox. We initially evaluated this and decided against. Ring is based on open standards such as SIP (rfc3261), TLSv1.2 (rfc5246), SRTP (rfc3711), vCards (rfc6350) and many more. We are also inter-operable with existing SIP infrastructure such as corporate phone system and classical phone provider with optional SIP accounts. We will continue to be as standard compliant as we can rather than create/support yet another custom communication protocol. What Ring bring to this existing mesh of technologies is the ability to connect people using a decentralized peer-to-peer network.
    - madez 12y ago
      Support for non-obsolete and secure standardized protocols seems to me to be a good thing. As of now we have no plan to support Tox. We initially evaluated this and decided against. I'm rather interested in the reasons of this decision. Ring is based on open standards (...). Tox is open as well. However, I see a difference between the protocols you've given and Tox: Tox is not standardized. What Ring bring to this existing mesh of technologies is the ability to connect people using a decentralized peer-to-peer network. This technology for peer-to-peer discovery is also not standardized, I assume. So, why creating your own protocol instead of using Tox for this?

desdiv 12y ago

I think this is their code: GNOME client: https://github.com/max3903/SFLphone https://github.com/max3903/SFLphone KDE client: https://github.com/Elv13/sflphone-kde https://github.com/Elv13/sflphone-kde Sounds like they recently relocated from their old homepage at http://sflphone.org http://sflphone.org to this new domain and just don't have everything in order yet.

leni536 12y ago
Their wiki: https://projects.savoirfairelinux.com/projects/ring/wiki https://projects.savoirfairelinux.com/projects/ring/wiki According to this their code repos: Daemon: https://gerrit-ring.savoirfairelinux.com/ring-daemon https://gerrit-ring.savoirfairelinux.com/ring-daemon Client library: git://anongit.kde.org/libringclient Clients: https://gerrit-ring.savoirfairelinux.com/ring-client-gnome https://gerrit-ring.savoirfairelinux.com/ring-client-gnome git://anongit.kde.org/ring-kde https://gerrit-ring.savoirfairelinux.com/ring-client-macosx https://gerrit-ring.savoirfairelinux.com/ring-client-macosx Not really well organized.

jordigh 12y ago

Savoir-Faire Linux are a local Montréal company with a lot of clout. I don't consider their promises empty, and I'm excited to see them working on this.

Elv13 12y ago

Ring-KDE announcment: https://elv13.wordpress.com/2015/05/07/announcing-ring-a-distributed-and-secure-multimedia-communication-platform/ https://elv13.wordpress.com/2015/05/07/announcing-ring-a-dis... (I am one of the developer, ask me anything) EDIT: There is screenshots on that page

madez 12y ago
As I asked in my direct comment on this submission: What are the advantages compared to Tox? I see one advantage of Tox compared to Jitsi. Account management is decentralized on Tox and federated on the protocols Jitsi supports. Are there plans to support Tox as a backend?
- Elv13 12y ago
  As of now we have no plan to support Tox. We initially evaluated this and decided against. Ring is based on open standards such as SIP (rfc3261), TLSv1.2 (rfc5246), SRTP (rfc3711), vCards (rfc6350) and many more. We are also inter-operable with existing SIP infrastructure such as corporate phone system and classical phone provider with optional SIP accounts. We will continue to be as standard compliant as we can rather than create/support yet another custom communication protocol. What Ring bring to this existing mesh of technologies is the ability to connect people using a decentralized peer-to-peer network.
  - madez 12y ago
    Support for non-obsolete and secure standardized protocols seems to me to be a good thing. As of now we have no plan to support Tox. We initially evaluated this and decided against. I'm rather interested in the reasons of this decision. Ring is based on open standards (...). Tox is open as well. However, I see a difference between the protocols you've given and Tox: Tox is not standardized. What Ring bring to this existing mesh of technologies is the ability to connect people using a decentralized peer-to-peer network. This technology for peer-to-peer discovery is also not standardized, I assume. So, why creating your own protocol instead of using Tox for this?