Authors CurseForge

sorry if that has been alredy request! :D

would be possibile list all addon in CC also the addons not supported by curse and or wowace and have indication that are not already on that comunity so maybe i can search for addons that can substitute them? ;D

i do have probably someting related only wowint :D

Wait, you are asking for an updater made for Curse to show all addons NOT on Curse?

To be honest, I highly doubt that would ever happen, because it requires CC to pull from other sites.

That sort of demonstrates the division between the business aspect of Curse and the community aspect of WoWAce that I've been concerned with.

According to the CC's behavior, "No other community site shall be acknowledged". That same statement, however, is poisonous to a true development community's progress. The third party updaters have always been of a more community mindset than a business mindset, so they tend not to favor a particular community over another. This is very appealing to the end user for obvious reasons.

So my question is, is it possible for a business model, originally based on a community model, to acknowledge, interact, and exchange information and ideas with other communities?

Simple, Curse supports Curse/WowAce addons, because, those are the servers/communities curse pays for. It's quite easy to understand. Should the curse client support say, WoWI, then it would not be any better than WoWMatrix, which is heavily frowned upon by most.

Sleestack, it has absolutely NOTHING do to with not acknowledging other wow sites, in fact, you are completely free to use whichever site you want, but you can not expect Curse to PAY hired programmers to write an application for their concurrents (Curse *is* a business, whether you like it or not). Also, if Curse was to support other addon sites, then they would have 2 possible ways of doing it:
- Blantantly "leech" bandwidth by hotlinking the addons through the client.
- Download the addons from other release sites and host them as well.
- Build in a heuristic layer to parse all toc files etc, compare with others. This would lead to more issues than I care to think about even. There are numerous addons out there with poorly made toc files, comparable toc files but different addons. There is no way an automated process can match addon a with function a on site a with addon b with function b on site b and have it be good. It would at least require user action. Which of course will then lead to a lot of posts "make it automated", which then would lead to "omg it sucks, its wrong". In short, it's not even remotely doable.

I read the OPs request differently. Just a list of all addons with a <not on Curse at this time> next to the ones it can't handle.

Edit: oh . . . someone got it already, should read the thread completely before replying . . . <goes off to get cofee so he can think again>

Quote from gramg

I read the OPs request differently. Just a list of all addons with a <not on Curse at this time> next to the ones it can't handle.

Edit: oh . . . someone got it already, should read the thread completely before replying . . . <goes off to get cofee so he can think again>

yeah that is the point!! :D
would just know waht is not coming from curse / ace so i can search for similar one on curse / ace. :D

Quote from MoonWitch

Sleestack, it has absolutely NOTHING do to with not acknowledging other wow sites, in fact, you are completely free to use whichever site you want, but you can not expect Curse to PAY hired programmers to write an application for their concurrents (Curse *is* a business, whether you like it or not). Also, if Curse was to support other addon sites, then they would have 2 possible ways of doing it:
- Blantantly "leech" bandwidth by hotlinking the addons through the client.
- Download the addons from other release sites and host them as well.
- Build in a heuristic layer to parse all toc files etc, compare with others.

There is a third option. Difficult, insane even, but not impossible.

The current business model appears to be a value-added client, one of the functions being addon updating. Acknowledging that one site does not fit all needs, and that each site can provide it's own extra features and community, why not have the addon sites attempt to get together and produce a common API that exchanges addon information between sites?

Well yeah, the feed. But to just adopt a method like wowmatrix is using, I doubt CC would ever get to that point. But the psyn feed would mean that heads of all distro sites would sit together, which would be a good thing.

I was talking out of a "Curse alone" pov, not if other sites actually got involved :)

Quote from Sleestack

That sort of demonstrates the division between the business aspect of Curse and the community aspect of WoWAce that I've been concerned with.

According to the CC's behavior, "No other community site shall be acknowledged". That same statement, however, is poisonous to a true development community's progress. The third party updaters have always been of a more community mindset than a business mindset, so they tend not to favor a particular community over another. This is very appealing to the end user for obvious reasons.

So my question is, is it possible for a business model, originally based on a community model, to acknowledge, interact, and exchange information and ideas with other communities?

Not as all, as the other's here have pointed out, It is actually a mutual respect that would stop us from leeching bandwidth and addons from other sites. It is a respect to the authors that we won't try to coerce or steal from other sites to boaster our own database.

Quote from Spennig

I -think- what was being asked for is a scan of the addon folder that lists all the addons you're using, then puts "not supported" by the ones Curse doesn't have, so he can switch them to ones curse DOES hold.

I honestly wouldn't mind that, but Kolie said once to me already that they aren't making it work that way. it's working like an addon manager, and only showing mods that it's updated for you at least once, not what you currently have on your system. i'm still waiting to see if anyone will tell me the reason why.

It is more technical than anything else. The client very rarely interacts with the file system. It was an early design decision and in retrospect may not have been the best one, however it is one we have to live with at least for the time being.

Quote from Sleestack

There is a third option. Difficult, insane even, but not impossible.

The current business model appears to be a value-added client, one of the functions being addon updating. Acknowledging that one site does not fit all needs, and that each site can provide it's own extra features and community, why not have the addon sites attempt to get together and produce a common API that exchanges addon information between sites?

I think if you ask around you'd find that I personally do work with the other sites out there.

Also it is *possible* for other sites to adopt the psyn standard and allow the CC to update from them.