Live data from Hacker News

PGPfone (1995)

en.wikipedia.org

11–20 of 25 posts

Re: PGPfone (1995)

#11

Earlier quoted context omitted.

Which of the above don't involve a central server? A server is absolutely necessary for VoIP, if only to set up calls (its also the only way to deal with some NATs).

RetroShare is completely decentralized/p2p/OTR. EDIT: @JshWright - Not sure I understand your question, but RS does "real-time voice communication" (besides the other things like chat, messaging, file sharing, forums, channels...)

Isn't the article about a real-time voice communication?

Re: PGPfone (1995)

#14
I've recently given a try to Jitsi [1] and seriously it works great. It really is a Skype drop-in replacement, and is fully open source. Without any need for configuration, I could discuss by text, audio, and video (and also do screen-sharing) all encrypted between my Debian laptop and a Windows PC, using existing XMPP (Jabber) account.

Really I've never seen any other free software do as good as Jitsi in the VoIP field. I've always tried SIP client and it was never perfect. Jitsi can do SIP to, but does wonder over XMPP so I didn't even try SIP.

[1] http://jitsi.org/

Re: PGPfone (1995)

#15
post #9

Earlier quoted context omitted.

Which of the above don't involve a central server? A server is absolutely necessary for VoIP, if only to set up calls (its also the only way to deal with some NATs).

That's Retroshare. It's also the only one as far as I know that has P2P "e-mail", too (besides Bitmessage, which is still quite new and unproven).

BitMessage has already proven to be breakable (as usual, by tricking the user, but still). See https://news.ycombinator.com/item?id=6263850.

Re: PGPfone (1995)

#16

Earlier quoted context omitted.

Personally, I'd stay away from anything that is closed-source (as we don't know what's happening inside) and/or centralized (because it's just one more attack vector and totally unnecessary for VoIP).

Which of the above don't involve a central server? A server is absolutely necessary for VoIP, if only to set up calls (its also the only way to deal with some NATs).

Twelephone gets round that by using twitter for call set up only & transmits media peer-to-peer using WebRTC.

Re: PGPfone (1995)

#17
post #14

I've recently given a try to Jitsi [1] and seriously it works great . It really is a Skype drop-in replacement, and is fully open source. Without any need for configuration, I could discuss by text, audio, and video (and also do screen-sharing) all encrypted between my Debian laptop and a Windows PC, using existing XMPP (Jabber) account. Really I've never seen any other free software do as good as Jitsi in the VoIP f…

Does it encrypt PGP-style?

Re: PGPfone (1995)

#19
post #14

I've recently given a try to Jitsi [1] and seriously it works great . It really is a Skype drop-in replacement, and is fully open source. Without any need for configuration, I could discuss by text, audio, and video (and also do screen-sharing) all encrypted between my Debian laptop and a Windows PC, using existing XMPP (Jabber) account. Really I've never seen any other free software do as good as Jitsi in the VoIP f…

Does it encrypt PGP-style?

More like ZRTP style, also not sure exactly what you mean by PGP-style

Re: PGPfone (1995)

#20
post #16

Earlier quoted context omitted.

Which of the above don't involve a central server? A server is absolutely necessary for VoIP, if only to set up calls (its also the only way to deal with some NATs).

Twelephone gets round that by using twitter for call set up only & transmits media peer-to-peer using WebRTC.

The issue is that behind certain NATs, WebRTC's peer-to-peer component can't work. In these situations, it needs to fall back to using an ICE/STUN server, or some other form of proxy between peers.
Post reply on HN