Please give proper attribution - your project is a packaged version of a stackoverflow.com answer of mine.

[mklement0]

As I've said in a comment on my stackoverflow.com answer where you got the code from:

It's great that you've packaged it for npm, but you need to give proper attribution:

• mention the source in README.md
• add me to the contributors key in package.json

If this were a one-liner, I wouldn't ask for this, but given that the entire functionality of your package is my code verbatim, and the contents of your read-me are the comments from my code verbatim, I think it's only fair that you publicly acknowledge where it came from.

[mklement0]

I was hoping that my informal request for attribution would be enough, but just in case you're unaware of the legal situation:

As noted in the Stack Exchange Terms of Service and in the footer of every page, all user contributions are licensed under Creative Commons Attribution-Share Alike. Proper attribution is required if you republish any Stack Exchange content.

http://stackoverflow.com/help/licensing

If I don't hear from you in the coming days, I will report you for abuse.

[mklement0]

I have just filed a DCMA takedown request. You can learn about the process here.

[caseyWebb]

jfc... I get it, but damn.

@mklement0, @barsh is/was on vacation. I'll submit a PR before you have an aneurysm, but more importantly break our build process.

[mklement0]

Hey, thanks for letting me know.

Just to be clear: I want the repository to remain in place, and I think it's great that @barsh packaged it up, as I've stated.

I do, however, think that just republishing other people's work verbatim without attribution is not acceptable, and since I hadn't received any feedback in 11 days I decided to take action.

But if that's getting resolved now, that's great.

I'm asking this innocently (I'm really interested in the answer): how long would you have waited?

[barsh]

I was out of the country... this is my first day back, but I get so many messages from Github that I might have overlooked this anyway. I have made the requested changes. As @caseyWebb suggested, feel free to submit a pull request if you want more cred.

[mklement0]

I'm glad to hear that this was just a case of crossed wires - thanks for fixing the problem. As I've stated in my response on stackoverflow.com, I am glad that you took the time to package up my code for easy reuse via npm.

[Qix-]

@mklement0 Lol, seriously though. You wrote 5 generic SLOC on Stack Overflow and DMCA'd him over it due to no responses in a week or so. Just pointing out a bit of absurdity with that.

[mklement0]

@Qix- You've read the exchange. You know what happened. You've made yourself feel superior. I respectfully opt out of this conversation you're having with yourself.

[Qix-]

@mklement0 Mmk. :)