NAVDEEP BAINS  @RUDHY I don't understand it either. I should also add that I can't reproduce the firewall issues being reported on any of my machines. There's only one way to bind a socket to a port, so in that respect, Playback and Rivet are exactly the same. There's no special technique to employ; no magic trick that I'm aware of at least.

Take a look at the Rivet forums and you'll see that Rivet users are also having problems with the Snow Leopard firewall. Both Yazsoft and Cynical Peak are being blamed for Apple's buggy code.

It's not Yazsoft's fault that the Mac OS X firewall implementation is flaky. It's not Cynical Peak's fault either. There really is absolutely nothing we can do to solve these issues on our end.

Thanks,

Navdeep Bains

Playback Developer  
(Version 1.2)

NAVDEEP BAINS  Hello,

Customers seem to be under the impression that there's some Firewall API for developers to interface with -- there's not. Applications are not supposed to know that the firewall exists and there are no special calls for requesting permission.

The only guideline offered by Apple is to not to self-modify the application package. Playback doesn't. As far as I know, there's nothing else we can do on our end. If I'm wrong or if anyone has any suggestions, please email playback@yazsoft.com or post on the forums.

@Rustman: Playback doesn't attempt any outgoing connections aside from the Sparkle updates.Also, since you have a router, you won't be opening up your computer to the world -- just to your local network. No one can connect to your computer from the outside unless you specifically open a port on your router.

Thanks,

Navdeep Bains

Playback Developer  
(Version 1.1)

NAVDEEP BAINS  Hello,

If you have a feature you would like to see, we're listening. However, if Playback's mere existence offends your sensibilities, there's not a whole lot we can do about that.

This is not an appropriate forum for a debate and I have no interest in engaging in one. This will be my last interaction with you. Have a nice day!

Thanks,

Navdeep Bains

Playback Developer  
(Version 1.0.2)

NAVDEEP BAINS  Hello,

I have to say that the tone of your posts is confusing to me. If you don't find Playback's feature set compelling, that's fine. We're offering an alternative to the choices already available. We're not accosting you at gun point. If we've said something rude or offensive, I'm not aware of it.

I requested that you email us on the assumption that you were considering Playback as a user. In that case, there would be an obvious benefit to you. However, it appears that my assumption was incorrect. You clearly have no interest in using Playback.

Thanks,

Navdeep Bains

Playback Developer  
(Version 1.0.2)

NAVDEEP BAINS  Hello,

Sure, the data is fine. I just don't see the part where we look bad in comparison to Rivet.

QuickLook will take the same amount of time to generate a thumbnail regardless of what application is calling it. You can turn the thumbnails off if you prefer. If I'm reading your message correctly, Playback listed the same directory *faster* than Rivet once the thumbnails were cached.

Yes, the download is larger. The memory usage will be close to equal. Playback Menu is taking a much larger chunk on your system than it does on mine, which is strange. If you send us an email, we would be interested in finding out why that is.

Thanks,

Navdeep Bains

Playback Developer  
(Version 1.0.2)