All these shitheel sites do the same thing. BusinessInsider often doesn't even do the work of lightly rewriting paragraphs, they just rip content off wholesale. It's a dirty game, but I dunno if much can be done to stop it. The CEO's reaction is a disaster unto itself. Shameful.
I kind of disagree on this point. Business Insider has always asked for my permission before syndicating my content.
Plagiarism
291–300 of 326 posts
Re: Plagiarism
#292It's not surprising when your articles have no byline.
Re: Plagiarism
#293TheNextWeb did this to me a while back, if you remember the Only One Cloud meme. http://thenextweb.com/apple/2011/10/16/apples-icloud-icon-it...
I went back and forth with the guy on Twitter and he was nice enough and updated it, but it's still curation, not creation. They are link blogging essentially, but with too much "copy and paraphrase."
Re: Plagiarism
#294Earlier quoted context omitted.
It's our way of voicing very clear disagreement. Anyone who wants to read his words still can.
You think otherwise he might not know people disagree? Voting really shouldn't be punitive to people with unpopular opinions.
Why shouldn't it? The only way to get rid of bad ideas is to shame them out of existence.
Re: Plagiarism
#295Earlier quoted context omitted.
Thanks, but the distance calculation is the work of Alex Martelli from Stack Overflow. It's one of the sources I cited: http://stackoverflow.com/questions/3106994/algorithm-to-calc... I cited. It's simple enough that I probably could have thought of it on my own if I spent more time on it, but then again it was simple enough to find with a Google search.
I could have sworn it was the work of Vladimir Levenshtein: http://en.wikipedia.org/wiki/Vladimir_Levenshtein
The code I referenced measures the difference between strings (percentages), using Levenshtein distance--which states the number of changes between two strings. If you can find a source that states this idea of difference can be attributed to Levenshtein, then by all means I will acknowledge him. Until then, I will refer to Alex Martelli's code.
Re: Plagiarism
#296It makes me wonder what else have they plagiarised. Just saying.
Re: Plagiarism
#297Earlier quoted context omitted.
We do have processes AND policy in place to make sure this doesn't happen. But it can still happen unintentionally and when it does, we react activity and proactively.
Don't be ridiculous, this wasn't "unintentional". Additionally, it's impossible to react proactively.
Excellent point re: reacting proactive-ly. At some point you've taken so many action items on-board, uplifted so much capability and re-purposed to much content that all the corporate buzz-words just start making perfect sense.
Re: Plagiarism
#298omg you got plagarized? omg on the internetz?? omg serialz???
It's the internet shit for brains. Lemme ask you: Ever downloaded a torrent? Ever hotlinked an image?
The content you wrote sits on a web page, written in html and served with the http protocol. Anyone can save your webpage as file on their desktop, copy it, put it in a torrent, whatever.
Getting plagiarized sucks but man up and understand the game you're playing here though you could argue that you do know the game by bitching about it on hacker news and reddit, that's a good place to bitch about such things, the girls here like to get worked about this kinda shit.
Re: Plagiarism
#299Earlier quoted context omitted.
I might have to steal/quote that last line. "Move fast and break things. Edit later." Perfect.
Release early and often. The prolbem ocrcus wehn exprsesd tghins are had to undrestnad, or the idaes pooryl tghought out.
Interestingly enough, most people will be able to understand exactly what you wrote there. People can easily recognize common words "by shape". They only ever have to look at the first and last letters.
I'm not saying people won't notice there's something wrong with what you wrote. They will. But they'll be able to understand you perfectly despite that.
Re: Plagiarism
#300Earlier quoted context omitted.
We do have processes AND policy in place to make sure this doesn't happen. But it can still happen unintentionally and when it does, we react activity and proactively.
Quit using manager-bullshit-speak. Here, let me write your entire "processes AND policy" manual for plagiarism: 1) Don't do it; 2) If it occurs, fire the guy who did it; 3) Apologize and try to make it right; 4) Shut up. You seem to find each one of those steps challenging.
Actually, the boss should carry the can: http://en.wikipedia.org/wiki/Command_responsibility