It's common for larger blogs to syndicate content, but they will always credit the original author with a link back. Even then they ask for your permission. Looks like they didn't do that. Email the editors to state your case.
Firstly grab a copy of the offending pages and save it out as a PDF or whatnot.
secondly, this chap's editors will be greatly displeased. Contact them. Don't start shouting about lawyers, but point out the infringement and ask for remedy.
The simplest thing to do is to simply ask them to take it down.
He wrote about the same subject, but near as I can tell he wrote with his own words and near as I can tell even his own data points (for example, he talks about the Commodore 64, and WIN.INI, and I see no reference to either in your much longer article).
I've got news for you, you aren't the first person to write about the fact that younger folks aren't learning computers like their predecessors. Nothing wrong here.
I love the submitter's article, but I have to agree - while the thesis is similar, it's told from such a different viewpoint that I wouldn't have even made a connection between the two.
Disclaimer: I am not a lawyer, and this is business manners advice, not legal advice.
Step 1: Start with a very friendly letter noting the similarities, and asking for citation with a link. If it's a friendly error, or you give them an out making it seem like a friendly error, they'll cite you and it's done.
Step 2: If you aren't cited, write a firm but polite letter saying, "I'd prefer to keep this between professionals. I notice the similarities. Please cite my work. Let's resolve this amongst ourselves before involving editors."
Step 3: If it's not resolved, then send a nice letter, along with the correspondence chain to the editor. Explain that you worked a long time at the article, that you respect Forbes, and that you are looking for a citation, and not shaking them down for money.
Whatever you do, don't lose your composure. If you lose your composure, you lose the negotiation.
This should resolve 80% of the issues, without making any enemies. The last 20% just aren't worth fighting on your own dollar. Plagiarism happens, but it's best to let big companies sue big companies. The upside isn't worth involving lawyers.
Accusing someone of plagiarism is a VERY big deal. It is potentially a career ruiner.
Consequently, before you accuse someone of plagiarism, you should be extremely certain that he has actually committed the offense.
Here's what plagiarism is:
Lifting, word for word (or very nearly word for word), passages from somebody else's work and passing it off as your own, without attributing the source.
Here's what plagiarism isn't:
Writing about the same topic.
Making the same argument, using different language.
Citing the same quotes from the same sources, but otherwise using different language.
I don't see anything in Mike Elgan's piece that qualifies as plagiarism of your piece, as I've defined it above.
What needs to be impressed upon you is that falsely accusing someone of plagiarism is a legally actionable offense. It's called libel, and you can find yourself with a lawsuit on your hands.
I'm not a lawyer, but I would strongly urge you to retract this post.
Disclaimer: I'm a former Forbes.com employee but no longer have any ties to the company.
21 comments
[ 2.5 ms ] story [ 66.3 ms ] threadsecondly, this chap's editors will be greatly displeased. Contact them. Don't start shouting about lawyers, but point out the infringement and ask for remedy.
The simplest thing to do is to simply ask them to take it down.
He wrote about the same subject, but near as I can tell he wrote with his own words and near as I can tell even his own data points (for example, he talks about the Commodore 64, and WIN.INI, and I see no reference to either in your much longer article).
I've got news for you, you aren't the first person to write about the fact that younger folks aren't learning computers like their predecessors. Nothing wrong here.
What are the specific similarities you have issues with ?
I would not be surprised in the slightest if your article served as inspiration for this one, but that is completely allowed.
Step 1: Start with a very friendly letter noting the similarities, and asking for citation with a link. If it's a friendly error, or you give them an out making it seem like a friendly error, they'll cite you and it's done.
Step 2: If you aren't cited, write a firm but polite letter saying, "I'd prefer to keep this between professionals. I notice the similarities. Please cite my work. Let's resolve this amongst ourselves before involving editors."
Step 3: If it's not resolved, then send a nice letter, along with the correspondence chain to the editor. Explain that you worked a long time at the article, that you respect Forbes, and that you are looking for a citation, and not shaking them down for money.
Whatever you do, don't lose your composure. If you lose your composure, you lose the negotiation.
This should resolve 80% of the issues, without making any enemies. The last 20% just aren't worth fighting on your own dollar. Plagiarism happens, but it's best to let big companies sue big companies. The upside isn't worth involving lawyers.
Accusing someone of plagiarism is a VERY big deal. It is potentially a career ruiner.
Consequently, before you accuse someone of plagiarism, you should be extremely certain that he has actually committed the offense.
Here's what plagiarism is:
Lifting, word for word (or very nearly word for word), passages from somebody else's work and passing it off as your own, without attributing the source.
Here's what plagiarism isn't:
Writing about the same topic.
Making the same argument, using different language.
Citing the same quotes from the same sources, but otherwise using different language.
I don't see anything in Mike Elgan's piece that qualifies as plagiarism of your piece, as I've defined it above.
What needs to be impressed upon you is that falsely accusing someone of plagiarism is a legally actionable offense. It's called libel, and you can find yourself with a lawsuit on your hands.
I'm not a lawyer, but I would strongly urge you to retract this post.
Disclaimer: I'm a former Forbes.com employee but no longer have any ties to the company.