1) The firewall on your computer, router or corporate network doesn't allow outbound UDP traffic. You can go to this site to get an analysis by adobe of your connectability: http://cc.rtmfp.net/
(post a screenshot if you can't make sense of the analysis yourself)
Knows public IP address of self (no NAT): NO
Public UDP port number same as local UDP port number: YES
Can receive from same IP address, same UDP port number: YES
Can receive from same IP address, different UDP port number: NO
Can receive from different IP address, different UDP port number: NO
Can send to different IP address after server introduction: YES
Source IP address is preserved from original connection: YES
Source UDP port number is preserved from original connection: YES
Everything looks good to me, except for the fact that I'm behind a NAT. Please tell me that doesn't mean I don't get to see boobies.
EDIT: Never mind, it's working now. Rendez Vous server must have gone down temporarily. Also, some way to adjust the quality would be preferable. Right now it's more than what my connection can handle, and decompression errors are a real turn-off.
Also, in the login screen it used to trow a popup telling the user it failed top connect. I changed that to not do this this but instead attempt to reconnect on every failed attempt (so basically indefinitely) without giving user feedback. What do you think of this choice? Would you prefer to be notified of this and if so how?
To be honest, I think it's a stupid choice. It should only attempt to reconnect N number of times before giving up and displaying an error message. Sure, dropped packets might cause it to fail to connect one or two times, but if it keeps failing to connect several times in a row, that's a pretty clear sign that something is seriously wrong and it's never going to connect.