So now it isn't listed in plugin list even if its dll files are still located in plugins directory. Fine! So how do you propose to use this plugin now?
AFAIK Skype plugin (with Skypekit) ceased to work due to Microsoft blocked login from such clients. Only way was to patching our plugin and replacing "certificate" and/or whole skypekit binary with older/patched version.
Why should we distribute completely broken plugin that wouldn't work for 99.99 % people? (unless they use untrusted binaries and/or play with hex editor etc.)
If you're advanced enough to patch skype and skypekit binaries then you're probably advanced enough to stop whining and compile your own Miranda core without condition that blocks skype from being loaded... But probably it will cause you crashes as this plugin hasn't been updated for new core.
Do you force users interested in it to stay on previous Miranda-NG version and never updade again?
Looks like there's simply no tracks of 0.95.2 anymore. Are you kidding?
You can always compile virtually any version by yourself - all sources are in SVN/Git repository. But I agree it would be better to keep at least one older released version for download.
Yes, it is clearly fine that you mark that plugin as deprecated and won't make any changes or updates to it etc. It's ok.
But why the hell do you think that you are allowed to completely disable it for every user who has it installed?
You answered yourself in first sentence. If we won't update (and release new builds) some plugin, it can't be used with new version of core and other plugins as watcher mentioned. It will work only if there are no bigger api changes in core (or other plugins) anymore.