the idea that it's a skype replacement while simultaneously warning the reader about avoiding NAT is funny, 50% of the skype secret sauce is the NAT traversal.
The real secret sauce is their dead-simple way to sign up and use the client. As you can see in the post, the setup process with the Jitsi client is still a bit awkward, because it is supposed to be a provider-agnostic multi-protocol client. There is still a huge potential in stream-lining this process to get a broad end-user adoption. Flexibility really isn't key in this case, rather than proper UX.
Comments
the idea that it's a skype replacement while simultaneously warning the reader about avoiding NAT is funny, 50% of the skype secret sauce is the NAT traversal.
> 50% of the skype secret sauce is the NAT traversal
And the other 50% is the network effect.
The real secret sauce is their dead-simple way to sign up and use the client. As you can see in the post, the setup process with the Jitsi client is still a bit awkward, because it is supposed to be a provider-agnostic multi-protocol client. There is still a huge potential in stream-lining this process to get a broad end-user adoption. Flexibility really isn't key in this case, rather than proper UX.
The post warns about NAT on the server-side (like Amazon EC2 does). Client-side NAT works just fine.
Oh so that's how it loses my messages or doesn't send them to the intended recipient until 4-5 days laster. Sweet.
It's not a very secretive sauce, especially since they simplified the directory/routing service a few months ago.