Please remove the user confirmation so we are able to create real "naked" Skype apps.

I understand the user confirmation is used to ensure a rogue app doesn't take over Skype - much like Outlook has a security popup (although can be overridden with third party controls).

If I may recommend, some how authorize vendors that pass a certification/enrollment to have an access key binded to a strong key - to permit approved apps the ability to go completely naked. The strong key will eliminate the worry of distributing keys for other apps.

I just don't know why you people at skype don't get this. This in not 1/2 naked skype, it's not even close to 1/100th naked. If anyone of us programmers tries to make a client-server application with skype, we can't because you still need some bozo that clicks the OK button.

Why in gods name do I have to manually allow my program to turn on silent mode. I wrote a program thats controlling skype so why would I be afraid of doing something bad with this combination. I (and many other) are trying to extend skypes functionality and god forbid make some money while we're at it. But you people are suffocating us with your stupid security policies.

I mean just hold for a second and see this from our programmers point of view. C'mon is it really so hard to add one check box or applications white list that allows external programs to turn on silent mode without conformation.

Sorry but I had to get it out of my system without any sugar coating.

Personally, I don't think it was a serious statement about being close to being Naked Skype. However, at the moment it is as close as it gets.

Personally, I think Silent Mode is a method that places the client GUI to sleep and since it does this, it really should NOT be up to a program or based on some, I am a "Good Person" so let me bypass what the user wants concept.

Security is NOT based on a test of the past, good people go bad.

If done correctly, Silent Mode only needs to be approved once during the life of the user session. If it needs to be done more than once, then you need to add whatever logic is neeeded to your application so that the Skype user has no need to use the client while using your application.

If you don't want to client to use the Skype GUI, then it is your responsibility to provide the interface the Skype user needs to not need the Skype client. If you can't do that, then your application should not be using Slient Mode. It is the lack of features that is causing the user to require the need for the Skype GUI, not Silent Mode itself.

Naked Skype would be the equal of Silent Mode without the need of user approval, and as you say, Silent Mode is NOT naked Skype

In a nutshell here is what you are saying:

Listen, I am a good person, my application only deals with Skype Calls ("Just an Example").

So, I could care less about all the other rich features the Skype client GUI offers the user, or what trouble I may cause by placing them all in sleep mode, so when my application is around, I want to disable ALL the other rich features of the Skype client GUI, and without user permission.

I don't care what I disable for this Skype user, and anytime they TRY to come out of "Silent Mode" I want to put them back, because my program has things to do.

Lastly, God help the Skype user who would be using say 3 or more "Good People" applications, that any one of them could be using "Silent Mode" without permission, and at any given moment.

When they become totally frustrated trying to answer calls, chats, and do normal things, like they could before, which "Good People" application(s) do they stop, so they can continue to do the things they enjoyed before when using Skype?

I know silent mode is not naked skype
If naked skype would be out we wouldn't have this conversation. And I would be rich on some beach somewhere with a smile from ear to ear

My app. is very specific to clients need. So this is not something that every skype user can download somewhere and install to his PC.
There is going to be a dedicated server for this app to work with skype. I'm developing some sort of automated call-center/answering machine. And what now? All I can do is hire one person that sits in server room and clicks notifications when server restarts or app. restarts.

You see my problem? I'm trying to make an app. that runs only on servers. No person is going to use that skype client. All automated except that notification window

It's like you would make a great answering machine for ordinary phone but since your phone service provider doesn't allow automatic answering you have to be at home to push a button to record calls, sorry but thats a bit stupid if you ask me.

Besides, thats a lame excuse you stated in last post.
If I have in skype->options menu check box "warn before entering silent mode". If user unchecks this and some program is giving him problems he just enables this back. Exits skype and runs it again. When asked for silent mode it denies access.

Oh, and why I need silent mode.

There are going to be 8 skype client or more on one machine. All running under same skype user and different windows user. And if not in silent mode you can imagine all the popup windows from chats, calls and so on...

In your case then, run these Skype clients as system services, don't allow any GUI interface with the desktop, set them up to auto logon, problem solved. Not even a need to worry about "Silent Mode" then, because the client can't even be seen, More here:

http://testing.onlytherightanswers.com/modules.php?name=News&file=article&sid=46

If you don't mind can we move this into the API forum, this has turned into a debate, lol.

And one Harry Potter that will install all this when finished

I don't mind.