Sav, she's not singling you out. You just happened to be in the wrong place at the wrong time. There's a LOT of people disregarding licenses, etc, that shouldn't be. She's been fighting this for a long time, as she's said.
all i have to say is WOW talk about acting like a spoiled child !
Or maybe she's just a frustrated author/owner? Read all of the posts before you run your mouth.
someone made a simple mistake and you make a post about it pretty freaking sad PM would have done the job .
Learn to read. She's been PMing people for months.
ive used your addons for a while .. sadly as of today i will not use your chat addon any longer
I'll make sure to loan her a tissue.
your "i am better than most god complex" is what will in the long run drive a lot of people off
your "i am better than most god complex" is what will in the long run drive a lot of people off
You'd be surpized how many people it dosn't, IE tekkub, clad .. both very picky authors as well.. and also have similar stances. Thing is that a good mod that works EXACTLY like you want it to is hard to replace.
... the first version I found with the change to the README stating the license was in mid October. Ignorance is no excuse and obviously there was a change in how she wanted this mod handled so that was my fault for not noticing.
Wrong. This is the same misconception I keep hearing from people. This is not how it works. If an addon does not explicitly state any license terms, full copyright protections apply. If an addon does not explicitly grant you a right, you do not have that right. If that weren't the case, if having no license terms meant you had all the rights you could dream up, I would not push this so hard, because for a long time I didn't state any license terms, and it would be my own fault. However, that's not the case. Adding license terms to my distribution is actually a change in the direction of "less restrictive", as my license (and any license, really) grants you rights above and beyond those granted by copyright.
I have a solution. change the name, give phanx credit for the code, and then distribute it. Then she shouldnt be getting any bug reports etc.
I don't even care if I get credit. If you want to distribute my code in your compilation or your addon, that is 100% okay with me, as long as it does not have my name attached. Change the name of the addon, including the name as used in the code, and don't use my addon's name to advertise yours, and you can distribute it in a compilation, encrypt it and charge money for it, or do anything else you want with it and I won't bat an eye.
That's really what I find so baffling, is that people would rather deal with this than read a few lines in a text file, perform a simple search-and-replace, and rename a few files.
Sorry for your frustration Phanx, I do understand when you say it like that. I like that fact that we are allowed to ask for permission to use your addons, and as the addon author that is entirely up to you to make that decision. I do see Tapestry's side because I've made that mistake also, but I'm not going to stop using your addons just because I have to ask permission. I don't mind doing that at all.
Maybe you could make Phanx chat like have a pop up when you first log in that says if you want to redistribute, please ask permission first or risk having your (body part here) removed :P Has to be something funny of course :D
// Warning this is a Joke //
how bout this.. it's an awesome solution..
When you make a compliation, DO NOT Include addons at all, Just your WTF Files.
Then List all the addons your going to need.
There Solves 2 problems with one stone. Now no more random updates or lack of and 2 it dosn't step on anyone that dosn't want their stuff distributed. Granted this does create that problem that the Vast Majority of wow players will not actualy take the time and effort to download those mods on their onw... But that's their problem :P
When you make a compliation, DO NOT Include addons at all, Just your WTF Files.
Then List all the addons your going to need.
That's actually a REALLY good idea. I mean, think of how much extra bandwidth sites like WoWI are using because of hundreds of copies of the same exact files. Not to mention that it solves all of the arguments in a fell swoop.
Honestly, I'm surprised that the WoWI mods haven't devised a system that allows compilation authors to upload their SV files and then select, from a list, all of the addons used in that compilation.
Education, Ease of Distribution, Proper Practices, Ease of Support > convince for stupid people who are unwilling or stuburn about figuring it out properly.
When you cater to the lazy people you complicate your life for the simplifaction in theirs. When no money is exchanged in this proccess you create a feeling of Entitlement in that user base, this is inherantly bad for EVERYONE including the ones bennifiting from the simplification.
When you make a compliation, DO NOT Include addons at all, Just your WTF Files.
Then List all the addons your going to need.
There are a few "compilations" on WoWI that work like this; one of them "includes" my addon. Unfortunately this idea will never take off unless the major UI sites stop allowing everyone and their brother to upload 40mb zips that contain other people's copyrighted work without permission. Curse already has something similar planned (though not yet implemented); we'll see how it pans out. Hopefully it goes well, and the other sites will follow suit.
That would be my preference as well. I've never downloaded a compilation, and I've never responded to any of the requests to upload my UI as a compilation I've gotten when posting screenshots of my UI. It's just not that hard to set up addons in a way that works for you. If an addon is too complicated for you to set up, that's probably a good sign that it's also too complicated for you to use effectively on a daily basis, and you should look for a simpler addon, or not use an addon at all.
This thread is a waste of e-space. Which is saying something because the internet is infinite.
I read this whole thread and what I gathered is this:
Phanx = mad b/c people redistribute her addons, which may (or may not) be out of date. Then when down-loaders receive said "outdated addons" from a compilation, they report bugs to her which may be false reports which then create time consuming issues for her.
Phanx = mad because Ui designers don't ask her before including an addon in their compilation.
Lets break it down. To say it and get it out of the way... yes, Phanx, you do have all the right in the world to demand people ask permission before redistributing your addon and making your work known to thousands more people in the process. And yes, you even put the request in red lettering in some of your download pages. Although honestly, it could be a bit bigger font size and could be included on every addon page. I think both of those changes would help. I am a compilation designer myself and here is my question to you. How exactly is me asking you for permission to use your addon keeping people from reporting false bugs to you? I don't really see where your problem and request are connecting. And honestly, I really think the whole false bug thing is a load of panda poop. AND I think it was really disrespectful to point out Tapestry like that. I recently had an issue with an author on WoWInterface and I no longer support any of his addons in my Ui's. That is now thousands of people who aren't looking him up on WowInterface or telling their friends about his addons. And lets be honest, when you spend as much time on something as authors and designers do, it really is about getting your work out there to people. Anyway, back to the panda poop. People that download a compilation don't just go and randomly report bug issues they are having. Like you said yourself, you have never uploaded a compilation. Let me let you in on a little secret. When a downloader has an issue with something in a compilation, guess who they come running to first? You guessed it...the uploader they downloaded from...and what is that uploader going to tell them? Probably something along the lines of "make sure you have the latest version of the addon you are having trouble with."
Anyway, this has become entirely too big a wall-o-text. My point is, yes people should ask if you want them to ask. Will that solve the problem you are saying is your reasoning for asking people to ask, no. Should you make it a bit more obvious on each download page that you want people to ask, yes. Lets face it, people don't read readme files. They just don't, should they, yes. Life is full of should's and just not as many do's. So, help yourself out and put big ol' letters up there on your download pages.
Gl with your endeavor, and try not to snap at the designers, they are the ones making your coding look good and putting your work out there.
And yes, you even put the request in red lettering in some of your download pages. Although honestly, it could be a bit bigger font size and could be included on every addon page. I think both of those changes would help.
It's already on every one of my addon pages. But since 99.99% of people viewing my addon page aren't going to redistribute it, I felt that it should be enough to put the notice at the bottom of my page. I have now moved it to the top and colored it red for the two addons that are most commonly redistributed. But you know what -- the law says I don't need to put that notice anywhere. The law says I don't even need to include it with my addon. People who want to distribute bundles of other people's original work should be responsible for educating themselves about the relevant laws. It should not be my responsibility to chase them down and beat them over the head with this knowledge.
How exactly is me asking you for permission to use your addon keeping people from reporting false bugs to you? I don't really see where your problem and request are connecting.
If you ask first, I can look at your history of updating your compilations, look at your history of providing support for your compilations, and make a basic assessment of your intelligence. If you've uploaded 5 compilations and never posted a new version of any of them, I can say no. If you've uploaded 5 compilations and have dozens of comments on each one asking for help that you haven't ever responded to, I can say no. If u tyep liek dis n cant speel 2 sav ur lyfe m8, I can say no. I've consented to a grand total of two people redistributing my work. Both were able to present themselves intelligently, had a clear history of providing support and keeping things updated. If ever they let their compilations lapse into disrepair to the point that the version of my addons in them require an update just to function, I will ask them to remove them, or ask the addon site to remove them if the uploader has disappeared.
I recently had an issue with an author on WoWInterface and I no longer support any of his addons in my Ui's. That is now thousands of people who aren't looking him up on WowInterface or telling their friends about his addons.
Great. Tell your friends to not use my addons. I don't write addons to win some imaginary popularity contest. I would much rather have only three people use my addon, than have ten thousand people find my addon through a compilation I didn't want it included in.
People that download a compilation don't just go and randomly report bug issues they are having. Like you said yourself, you have never uploaded a compilation. Let me let you in on a little secret. When a downloader has an issue with something in a compilation, guess who they come running to first? You guessed it...the uploader they downloaded from...and what is that uploader going to tell them? Probably something along the lines of "make sure you have the latest version of the addon you are having trouble with."
What about the many compilations whose authors don't provide support? What about the compilations whose download pages feature an "I won't provide any support for this" notice? What about the many compilations whose comment sections are full of requests for help with this, that, and the other with no response from the uploader? What about the many compilations whose authors' last login date to the site was the day they uploaded the compilation, even six months later? Go browse through the compilation categories on WoWInterface if you don't believe this happens.
Should you make it a bit more obvious on each download page that you want people to ask, yes.
Like I said above, no, I shouldn't have to make it obvious at all on any download page. People who want to redistribute my copyrighted work should take the time to learn about the laws involved beforehand. If they can't be bothered to do this, then I can't be bothered to be remotely polite to them when I have to contact them telling them to stop violating laws and licenses and taking a steaming crap on common courtesy.
You're welcome to hold your own opinion, but the law is very clear, and your opinion cannot change that fact, and that is really all there is to it.
You're right. Her addons have restrictions. Someone broke them, she responded. Posts like yours are pointless and irrelevant as the thread ended with post #1.
There are a few "compilations" on WoWI that work like this; one of them "includes" my addon. Unfortunately this idea will never take off unless the major UI sites stop allowing everyone and their brother to upload 40mb zips that contain other people's copyrighted work without permission. Curse already has something similar planned (though not yet implemented); we'll see how it pans out. Hopefully it goes well, and the other sites will follow suit.
This is problematic as well... Let's say, we allow users to create list of addons (which would be automatically updated) and to add WTF folder with settings (SavedVariables). After some time new version of the addon is released with different SavedVariables format and the problems arises:
- Your addon doesn't look as good as on the compilation screenshot, because it has new features, which are not "configured" properly for the compilation
- Your addon lost all the UI settings because of the UI change with no way to update old settings to the new one (eg. how do you update window position for one small window to new format with two windows and one popup?)
- Your addon settings were created with bugged addon version and even when your addon was fixed, the SavedVariables are corrupted throwing errors in the compilation or losing its settings.
- Your new version of addon (released months after the compilation was created) has completely changed your SavedVariables DB format with no or impossible update path. This can lead to errors or lost settings as well...
Wrong. This is the same misconception I keep hearing from people. This is not how it works. If an addon does not explicitly state any license terms, full copyright protections apply. If an addon does not explicitly grant you a right, you do not have that right. If that weren't the case, if having no license terms meant you had all the rights you could dream up, I would not push this so hard, because for a long time I didn't state any license terms, and it would be my own fault. However, that's not the case. Adding license terms to my distribution is actually a change in the direction of "less restrictive", as my license (and any license, really) grants you rights above and beyond those granted by copyright.
It actually depends on where and when the work was authored and distributed. In the US for example, before they signed the International Berne convention a work with no license terms and copyright notice was indeed considered to be in the public domain.
I don't even care if I get credit. If you want to distribute my code in your compilation or your addon, that is 100% okay with me, as long as it does not have my name attached. Change the name of the addon, including the name as used in the code, and don't use my addon's name to advertise yours, and you can distribute it in a compilation, encrypt it and charge money for it, or do anything else you want with it and I won't bat an eye.
That's really what I find so baffling, is that people would rather deal with this than read a few lines in a text file, perform a simple search-and-replace, and rename a few files.
Seems to me you may be better served saying your code is pd and you have a protected trademark for the use of the name from a legal perspective anyway. You would never be able to claim damages to enforce the copyright in a meaningful way, and I doubt you have registered it with the library of congress to enforce them without damages, however you can enforce mark usage without this need.
// Warning this is a Joke //
how bout this.. it's an awesome solution..
When you make a compliation, DO NOT Include addons at all, Just your WTF Files.
Then List all the addons your going to need.
There Solves 2 problems with one stone. Now no more random updates or lack of and 2 it dosn't step on anyone that dosn't want their stuff distributed. Granted this does create that problem that the Vast Majority of wow players will not actualy take the time and effort to download those mods on their onw... But that's their problem :P
OR
Not do compliations at all. I vote for this one.
Actually what I did was write an installer for friends that wanted me to make a compilation for them, what it does it check a master list that is kept in version sync with what I am running and then installs/updates the mods they use to that version... works well enough to keep them in sync with version that I know are running well, but would run into wowmatrix like issues if let into the wild as is I guess.... it is a case of damed if you do and damned if you dont here... if you include/host the files some authors get annoyed, and if you don't you leech bandwidth from the sites....
When a downloader has an issue with something in a compilation, guess who they come running to first? You guessed it...the uploader they downloaded from...and what is that uploader going to tell them? Probably something along the lines of "make sure you have the latest version of the addon you are having trouble with."
This is down right WRONG. Speaking as somebody who has probably read through more code, found and fixed more bugs in more addons (99% of which I am not listed in the credits for) than over half of the 'authors' on the main addon sites, I can say right now that most users are FUCKING STUPID. They see an error message and they don't even fully read it, they read it until they find the first name that stands out as an addon and go post a comment saying 'its broken halp'. Or even worse they see the word Ace and come saying 'somebody fix ace plx i get error'. But the absolute worst thing is when they goto the page for addon A because they get an error message caused by addon B and both addons are using and embed library C but addon A loads first and is the first addon name in the error message but the rest of the error is clearly talking about addon B.
By saying you can include the addon as long as you rename it and don't use the original name anywhere at all including the code it insures the idiots don't come crawling in when they have an older version and a new fixed one is clearly listed on the page they are crying on.
Most of those bugs I said I've found earlier, I found when somebody claimed they were getting errors from an addon or library I do care about but it turned out to be a problem with some other addon the person was using that I don't give a damn about but didn't want people to report false errors.
It actually depends on where and when the work was authored and distributed. In the US for example, before they signed the International Berne convention a work with no license terms and copyright notice was indeed considered to be in the public domain.
And that happened in 1989, over a decade before WoW was even a twinkle in Blizzard's eye, and is therefore completely irrelevant to this discussion. And since I live in the US, and my addons are written in the US, they are protected by US copyright law; this is quite plainly stated in my license, if you or anyone else would ever bother to take the 30 seconds to read it.
Seems to me you may be better served saying your code is pd and you have a protected trademark for the use of the name from a legal perspective anyway. You would never be able to claim damages to enforce the copyright in a meaningful way, and I doubt you have registered it with the library of congress to enforce them without damages, however you can enforce mark usage without this need.
I hope it never comes to the point where I have to think about filing legal claims, since the major UI sites actually respect authors' rights and wishes and will remove compilations that redistribute addons without the author's consent. That said, though, I could wrap my addon in 50 pages of legalese and it still wouldn't help, because 99.99% of the issue is that people do not read anything, as evidenced by the fact that every uploader I've contacted who has responded (and I'm guessing the others simply never got the message) has promptly removed my addon and said "sorry I didn't know". Nobody argues that copyright and my license aren't valid; they just don't think and don't read, and believe that "not knowing" excuses any wrongdoing they might do in their ignorance.
- Your addon doesn't look as good as on the compilation screenshot, because it has new features, which are not "configured" properly for the compilation
This is hardly a problem specific to the "settings only" kind of compilation; the uploader should release a new version of the compilation regardless. If he isn't posting updates for major new addon features, which don't really come along that frequently in stable addons, how likely is it that he's posting updates necessary for WoW patches, or providing any support for users?
- Your addon lost all the UI settings because of the UI change with no way to update old settings to the new one (eg. how do you update window position for one small window to new format with two windows and one popup?)
Again, this isn't a problem specific to a settings-only compilation, or to compilations in general. Any user of any addon that makes major changes in the way it stores its settings will face this issue when upgrading, regardless of how they got the addon originally or how they configured it.
- Your addon settings were created with bugged addon version and even when your addon was fixed, the SavedVariables are corrupted throwing errors in the compilation or losing its settings.
Again, not compilation-specific, and should be addressed by the compilation uploader uploading an update.
- Your new version of addon (released months after the compilation was created) has completely changed your SavedVariables DB format with no or impossible update path. This can lead to errors or lost settings as well...
Again, not compilation-specific. Any user who updates to a new version of an addon without an automatic upgrade path will lose their settings or get errors. It is the responsibility of the compilation uploader to keep his compilation up to date. If you aren't willing to post an update once a month (or less frequently if nothing major changes) don't upload your compilation.
None of these things have anything to do with an author's right to control how their work is distributed, or are in any way arguments in favor of the existence of compilations. They are all issues that all addon users face when an addon undergoes the kind of changes you describe.
it is a case of damed if you do and damned if you dont here... if you include/host the files some authors get annoyed, and if you don't you leech bandwidth from the sites....
Not really. Give users a list of links to authors' download pages, and let them download and update their addons like everyone else. Having updated addons is not some divine right of which all mankind is possessed. Neither you nor anyone else is entitled to the use any addon. If updating addons once a month is too hard (believe it or not, you don't really need to download every update that comes along), then don't use addons.
I can say right now that most users are FUCKING STUPID. They see an error message and they don't even fully read it, they read it until they find the first name that stands out as an addon and go post a comment saying 'its broken halp'.
This. Go look at any addon's download page comments. Go look at any addon's forum thread. Go look at any place anywhere where users report bugs for WoW addons. Look at the percent of reports that make any sense at all, let alone are detailed enough to be of any use. If you provide support for your compilation and are willing to hold hands and gently explain to users over and over again that they need to update their addons, that's great, but you are a very, very, very small minority.
Or maybe she's just a frustrated author/owner? Read all of the posts before you run your mouth.
Learn to read. She's been PMing people for months.
I'll make sure to loan her a tissue.
And your exaggeration makes you look stupid.
You'd be surpized how many people it dosn't, IE tekkub, clad .. both very picky authors as well.. and also have similar stances. Thing is that a good mod that works EXACTLY like you want it to is hard to replace.
Wrong. This is the same misconception I keep hearing from people. This is not how it works. If an addon does not explicitly state any license terms, full copyright protections apply. If an addon does not explicitly grant you a right, you do not have that right. If that weren't the case, if having no license terms meant you had all the rights you could dream up, I would not push this so hard, because for a long time I didn't state any license terms, and it would be my own fault. However, that's not the case. Adding license terms to my distribution is actually a change in the direction of "less restrictive", as my license (and any license, really) grants you rights above and beyond those granted by copyright.
I don't even care if I get credit. If you want to distribute my code in your compilation or your addon, that is 100% okay with me, as long as it does not have my name attached. Change the name of the addon, including the name as used in the code, and don't use my addon's name to advertise yours, and you can distribute it in a compilation, encrypt it and charge money for it, or do anything else you want with it and I won't bat an eye.
That's really what I find so baffling, is that people would rather deal with this than read a few lines in a text file, perform a simple search-and-replace, and rename a few files.
Maybe you could make Phanx chat like have a pop up when you first log in that says if you want to redistribute, please ask permission first or risk having your (body part here) removed :P Has to be something funny of course :D
how bout this.. it's an awesome solution..
When you make a compliation, DO NOT Include addons at all, Just your WTF Files.
Then List all the addons your going to need.
There Solves 2 problems with one stone. Now no more random updates or lack of and 2 it dosn't step on anyone that dosn't want their stuff distributed. Granted this does create that problem that the Vast Majority of wow players will not actualy take the time and effort to download those mods on their onw... But that's their problem :P
OR
Not do compliations at all. I vote for this one.
That's actually a REALLY good idea. I mean, think of how much extra bandwidth sites like WoWI are using because of hundreds of copies of the same exact files. Not to mention that it solves all of the arguments in a fell swoop.
Honestly, I'm surprised that the WoWI mods haven't devised a system that allows compilation authors to upload their SV files and then select, from a list, all of the addons used in that compilation.
Education, Ease of Distribution, Proper Practices, Ease of Support > convince for stupid people who are unwilling or stuburn about figuring it out properly.
When you cater to the lazy people you complicate your life for the simplifaction in theirs. When no money is exchanged in this proccess you create a feeling of Entitlement in that user base, this is inherantly bad for EVERYONE including the ones bennifiting from the simplification.
.../end-soapbox
There are a few "compilations" on WoWI that work like this; one of them "includes" my addon. Unfortunately this idea will never take off unless the major UI sites stop allowing everyone and their brother to upload 40mb zips that contain other people's copyrighted work without permission. Curse already has something similar planned (though not yet implemented); we'll see how it pans out. Hopefully it goes well, and the other sites will follow suit.
That would be my preference as well. I've never downloaded a compilation, and I've never responded to any of the requests to upload my UI as a compilation I've gotten when posting screenshots of my UI. It's just not that hard to set up addons in a way that works for you. If an addon is too complicated for you to set up, that's probably a good sign that it's also too complicated for you to use effectively on a daily basis, and you should look for a simpler addon, or not use an addon at all.
I read this whole thread and what I gathered is this:
Phanx = mad b/c people redistribute her addons, which may (or may not) be out of date. Then when down-loaders receive said "outdated addons" from a compilation, they report bugs to her which may be false reports which then create time consuming issues for her.
Phanx = mad because Ui designers don't ask her before including an addon in their compilation.
Lets break it down. To say it and get it out of the way... yes, Phanx, you do have all the right in the world to demand people ask permission before redistributing your addon and making your work known to thousands more people in the process. And yes, you even put the request in red lettering in some of your download pages. Although honestly, it could be a bit bigger font size and could be included on every addon page. I think both of those changes would help. I am a compilation designer myself and here is my question to you. How exactly is me asking you for permission to use your addon keeping people from reporting false bugs to you? I don't really see where your problem and request are connecting. And honestly, I really think the whole false bug thing is a load of panda poop. AND I think it was really disrespectful to point out Tapestry like that. I recently had an issue with an author on WoWInterface and I no longer support any of his addons in my Ui's. That is now thousands of people who aren't looking him up on WowInterface or telling their friends about his addons. And lets be honest, when you spend as much time on something as authors and designers do, it really is about getting your work out there to people. Anyway, back to the panda poop. People that download a compilation don't just go and randomly report bug issues they are having. Like you said yourself, you have never uploaded a compilation. Let me let you in on a little secret. When a downloader has an issue with something in a compilation, guess who they come running to first? You guessed it...the uploader they downloaded from...and what is that uploader going to tell them? Probably something along the lines of "make sure you have the latest version of the addon you are having trouble with."
Anyway, this has become entirely too big a wall-o-text. My point is, yes people should ask if you want them to ask. Will that solve the problem you are saying is your reasoning for asking people to ask, no. Should you make it a bit more obvious on each download page that you want people to ask, yes. Lets face it, people don't read readme files. They just don't, should they, yes. Life is full of should's and just not as many do's. So, help yourself out and put big ol' letters up there on your download pages.
Gl with your endeavor, and try not to snap at the designers, they are the ones making your coding look good and putting your work out there.
<3
Ish
It's already on every one of my addon pages. But since 99.99% of people viewing my addon page aren't going to redistribute it, I felt that it should be enough to put the notice at the bottom of my page. I have now moved it to the top and colored it red for the two addons that are most commonly redistributed. But you know what -- the law says I don't need to put that notice anywhere. The law says I don't even need to include it with my addon. People who want to distribute bundles of other people's original work should be responsible for educating themselves about the relevant laws. It should not be my responsibility to chase them down and beat them over the head with this knowledge.
If you ask first, I can look at your history of updating your compilations, look at your history of providing support for your compilations, and make a basic assessment of your intelligence. If you've uploaded 5 compilations and never posted a new version of any of them, I can say no. If you've uploaded 5 compilations and have dozens of comments on each one asking for help that you haven't ever responded to, I can say no. If u tyep liek dis n cant speel 2 sav ur lyfe m8, I can say no. I've consented to a grand total of two people redistributing my work. Both were able to present themselves intelligently, had a clear history of providing support and keeping things updated. If ever they let their compilations lapse into disrepair to the point that the version of my addons in them require an update just to function, I will ask them to remove them, or ask the addon site to remove them if the uploader has disappeared.
Great. Tell your friends to not use my addons. I don't write addons to win some imaginary popularity contest. I would much rather have only three people use my addon, than have ten thousand people find my addon through a compilation I didn't want it included in.
What about the many compilations whose authors don't provide support? What about the compilations whose download pages feature an "I won't provide any support for this" notice? What about the many compilations whose comment sections are full of requests for help with this, that, and the other with no response from the uploader? What about the many compilations whose authors' last login date to the site was the day they uploaded the compilation, even six months later? Go browse through the compilation categories on WoWInterface if you don't believe this happens.
Like I said above, no, I shouldn't have to make it obvious at all on any download page. People who want to redistribute my copyrighted work should take the time to learn about the laws involved beforehand. If they can't be bothered to do this, then I can't be bothered to be remotely polite to them when I have to contact them telling them to stop violating laws and licenses and taking a steaming crap on common courtesy.
You're welcome to hold your own opinion, but the law is very clear, and your opinion cannot change that fact, and that is really all there is to it.
You're right. Her addons have restrictions. Someone broke them, she responded. Posts like yours are pointless and irrelevant as the thread ended with post #1.
This is problematic as well... Let's say, we allow users to create list of addons (which would be automatically updated) and to add WTF folder with settings (SavedVariables). After some time new version of the addon is released with different SavedVariables format and the problems arises:
- Your addon doesn't look as good as on the compilation screenshot, because it has new features, which are not "configured" properly for the compilation
- Your addon lost all the UI settings because of the UI change with no way to update old settings to the new one (eg. how do you update window position for one small window to new format with two windows and one popup?)
- Your addon settings were created with bugged addon version and even when your addon was fixed, the SavedVariables are corrupted throwing errors in the compilation or losing its settings.
- Your new version of addon (released months after the compilation was created) has completely changed your SavedVariables DB format with no or impossible update path. This can lead to errors or lost settings as well...
It actually depends on where and when the work was authored and distributed. In the US for example, before they signed the International Berne convention a work with no license terms and copyright notice was indeed considered to be in the public domain.
Seems to me you may be better served saying your code is pd and you have a protected trademark for the use of the name from a legal perspective anyway. You would never be able to claim damages to enforce the copyright in a meaningful way, and I doubt you have registered it with the library of congress to enforce them without damages, however you can enforce mark usage without this need.
Actually what I did was write an installer for friends that wanted me to make a compilation for them, what it does it check a master list that is kept in version sync with what I am running and then installs/updates the mods they use to that version... works well enough to keep them in sync with version that I know are running well, but would run into wowmatrix like issues if let into the wild as is I guess.... it is a case of damed if you do and damned if you dont here... if you include/host the files some authors get annoyed, and if you don't you leech bandwidth from the sites....
no compilations fails, i love DLing them to see how they made certain bits etc.
very elitist coders!
This is down right WRONG. Speaking as somebody who has probably read through more code, found and fixed more bugs in more addons (99% of which I am not listed in the credits for) than over half of the 'authors' on the main addon sites, I can say right now that most users are FUCKING STUPID. They see an error message and they don't even fully read it, they read it until they find the first name that stands out as an addon and go post a comment saying 'its broken halp'. Or even worse they see the word Ace and come saying 'somebody fix ace plx i get error'. But the absolute worst thing is when they goto the page for addon A because they get an error message caused by addon B and both addons are using and embed library C but addon A loads first and is the first addon name in the error message but the rest of the error is clearly talking about addon B.
By saying you can include the addon as long as you rename it and don't use the original name anywhere at all including the code it insures the idiots don't come crawling in when they have an older version and a new fixed one is clearly listed on the page they are crying on.
Most of those bugs I said I've found earlier, I found when somebody claimed they were getting errors from an addon or library I do care about but it turned out to be a problem with some other addon the person was using that I don't give a damn about but didn't want people to report false errors.
And that happened in 1989, over a decade before WoW was even a twinkle in Blizzard's eye, and is therefore completely irrelevant to this discussion. And since I live in the US, and my addons are written in the US, they are protected by US copyright law; this is quite plainly stated in my license, if you or anyone else would ever bother to take the 30 seconds to read it.
I hope it never comes to the point where I have to think about filing legal claims, since the major UI sites actually respect authors' rights and wishes and will remove compilations that redistribute addons without the author's consent. That said, though, I could wrap my addon in 50 pages of legalese and it still wouldn't help, because 99.99% of the issue is that people do not read anything, as evidenced by the fact that every uploader I've contacted who has responded (and I'm guessing the others simply never got the message) has promptly removed my addon and said "sorry I didn't know". Nobody argues that copyright and my license aren't valid; they just don't think and don't read, and believe that "not knowing" excuses any wrongdoing they might do in their ignorance.
This is hardly a problem specific to the "settings only" kind of compilation; the uploader should release a new version of the compilation regardless. If he isn't posting updates for major new addon features, which don't really come along that frequently in stable addons, how likely is it that he's posting updates necessary for WoW patches, or providing any support for users?
Again, this isn't a problem specific to a settings-only compilation, or to compilations in general. Any user of any addon that makes major changes in the way it stores its settings will face this issue when upgrading, regardless of how they got the addon originally or how they configured it.
Again, not compilation-specific, and should be addressed by the compilation uploader uploading an update.
Again, not compilation-specific. Any user who updates to a new version of an addon without an automatic upgrade path will lose their settings or get errors. It is the responsibility of the compilation uploader to keep his compilation up to date. If you aren't willing to post an update once a month (or less frequently if nothing major changes) don't upload your compilation.
None of these things have anything to do with an author's right to control how their work is distributed, or are in any way arguments in favor of the existence of compilations. They are all issues that all addon users face when an addon undergoes the kind of changes you describe.
Not really. Give users a list of links to authors' download pages, and let them download and update their addons like everyone else. Having updated addons is not some divine right of which all mankind is possessed. Neither you nor anyone else is entitled to the use any addon. If updating addons once a month is too hard (believe it or not, you don't really need to download every update that comes along), then don't use addons.
It is freeware. There's a difference between "freeware" and "public domain". Educate yourself before you post things that don't make sense.
This. Go look at any addon's download page comments. Go look at any addon's forum thread. Go look at any place anywhere where users report bugs for WoW addons. Look at the percent of reports that make any sense at all, let alone are detailed enough to be of any use. If you provide support for your compilation and are willing to hold hands and gently explain to users over and over again that they need to update their addons, that's great, but you are a very, very, very small minority.