Let's make sure we put a few items on the table that are key to remember:
Stardock != Microsoft. That means that changes in WinStyles and how it works are on the table. So if users or website admins or skin authors object to certain ways it works, we can alter it.
Let's break down the major issues at hand:
(1) WinStyles takes away from skin author credit.
Response:
https://www.stardock.com/temp/ws.jpg
You can't even create a .suite file without including credit for who did what. There are two formats that WinStyles supports - .xptheme and .suite. .XPTheme should be pretty straight forward good for users and skin authors. No respecting skin site is going to accept .xpthemes that contain rips. Just as they won't tolerate rips of wallpapers and skins. This is no different. A .xptheme is just a ZIP file renamed that contains teh various app skins.
.SUITE can be a bit scarier though and it's open for discussion. A .SUITE is less than 1K in size. It is, in effect, a portable skin site.

When you apply a .SUITE file, it goes out and downloads the skins from the place the .SUITE maker tells it to and WinStyles then grabs them and applies them. I uploaded the Beige .SUITE file here today for instance even though I created none of the skins. My submission doesn't include any skins or themes, it just points to the URL where users can get them (no different than a screenshot that manually states where you can get them except that a .SUITE file requires the user to list who made each part).
2) WinStyles hurts skin sites.
Response: THIS I have to agree with to an extent. .XPThemes don't hurt skin sites. But .SUITEs could because the site doesn't get a page view. However, the download count on components IS increased of the individual components on .suites.
What can we do about this? We could require that they only use WInCustomize. But then the "Stardock is the devil" crowd will say we're trying to lock people into WinCustomize which was the reason we made it so that any URL could be used (we had thought about tying it directly to our skin database to make it even easier to use but that would have required it to tie only to Stardock's database).
We're open to suggestions. However, this sort of thing happens already. The popular shell program, Talisman has no actual skin library of its own. It links purely to other people's skin sites (that's why Talisman skins are alwas highly ranked on skinz.org - Lightek links to them from their site). ICQPlus is doing the same thing to Deskmod as I type this. WinStyles .suites are the same sort of thing.
3) About not appreciating the applications.
Response: This I just totally disagree with. I would say it's just the opposite because each application is very highlighted in it and it increases awareness of these applications. The user does, afterall, have to go out and download these programs to use them.
We originally were ONLY going to support Stardock apps but once again we knew that the "Stardock is the devil" crowd would accuse us of trying to lock users into Stardock software so we put in the effort to support third party applications as well (including quite a bit of work to support Hoverdesk).
I would argue that WinStyles is the best thing to happen for skinnable application developers. If they maek a good app, now they get exposure by being able to leverage the strength of better known skinnable programs. Example: If Hoverdesk is felt to be better than say ObjectBar, then people will use WInStyles to include Hoverdesk themes with their WindowBlinds skin and Icon package. That will in turn get a lot of new users interested in Hoverdesk (which is one reason why we wanted to only support Stardock apps in the first place but we're trying to be fair here).
4) Decreases author interaction with users.
Response: Disagree again here. This could actually be increased. If we were somehow to switch it to be a WinCustomize only file solution, then we could let people comment on components directly from the program. But again, this would get a different group upset.
Another solution might be for the suite creator to be required to put a link to the comments field. For instance, on Beige, I could just add:
https://www.wincustomize.com/comments.asp?SkinID=2158&Lib=1
Or this could just be optional.
5) In General - good or bad:
Response:
Most of you knwo I'm a statistics nut. But it is with good reason. We all tend to forget how big the "community" is. It's not 60 guys on #skinnerz anymore. On WinCustomize alone there are 40,000 people who visit this site nearly every day. There are something like 10,000 peole who visit this site more than 3 times per day. I suspect the stats at DeviantART and Deskmod aren't much different.
It's for those people that we want to serve too. When I upload a screenshot of my desktop, I want to be able to say "You like this? Here's a 1K file you can apply and you can have the same desktop. Isn't skinnign cool? Wouldn't you like to make some skins? Wouldn't you like to try out more apps?" WinStyles makes customization much more accessible to those 40,000 people who visit daily let alone the other 700,000 who visit at least 1 time per month.