Skip to main content

Story about plagiarism by means of time machine


I can't remember the name of the story, and couldn't find anything on Google searches either.


The story is about a science fiction writer whose story gets rejected by the publisher because it's word-by-word identical to another story published years ago. The writer then writes another story only to find out that the same author also published this story around the same time as the other one.


Our writer then writes a story about a man who uses a time machine to read other people's work in the future and then publishes it in his time. Only to find out that this story was also published by the same guy years ago.


The story I'm trying to find out was in the form of letter correspondence between the writer and the publisher.


So, does anyone know its title?




Answer



Looks like Who's Cribbing by Jack Lewis. From this Usenet thread:



There's a story, which I really wish I could remember the details of, which consists of a series of letters between the author and various SF magazines. All the letters from the magazines are along the lines of "Thank you for your contribution, but we already published exactly this story 20 years ago". The author, in his various letters to the magazines, gets more and more defensive, pleading with the editors not tell him that some guy his never heard of has already written the story. Eventually, he bundles all these letters together and sends them to one last magazine with a cover note saying that he's done some research into this guy he's supposedly plagiarising, and thinks it was the other way around - Mr X was apparently a bit of a backyard tinkerer, and suppose he invented some machine for seeing into the future...? "Thank you for your contribution. It's an intriguing premise, and we certainly would have accepted it for publication, had [Mr X] not submitted exactly this story 20 years ago..."



Your description reminded me of something I'd read, but I haven't read Who's Cribbing, so I must have misremembered some other plagiarism-related story.


Comments

Popular posts from this blog

languages - Do we ever see written English in the Star Wars films?

In Empire Strikes Back , we see a transcription of what R2's beeps and bloops mean, but it's not English (sorry for the low quality, it's from the 2004 DVDs): I'd assume it's what Basic looks like when written, but is there some point in the the Star Wars films we see written English instead? (This sort of spun off from a discussion in How do people understand astromech droids? .) Answer At one point there was English but it has been phased out in subsequent versions of the films. Chris Gould at DVD Active did a comparison of all versions of each of the Star Wars films, and in his comparison of Episode 4 , there are a couple of screenshots showing how the power gauge for the Death Star tractor beam was changed. I imagine there are probably more to be found in his other comparisons but I haven't got around to reading those yet.

Was the "pure soul" of Harry's what had really hurt Voldemort?

In the Order of the Phoenix, Voldemort possesses Harry, and it hurts. Greatly. I think that Dumbledore explained that it was because Voldemort's rotten soul was incapable of assimilating Harry's pure soul, that Voldemort didn't understand the love and friendship etc that Harry has in his heart. But, I think it was a lie. Remember that in Deathly Hallows, while looking for information regarding Horcruxes, it is discovered that it is in fact possible to merge a soul fragment back, but that the process was extremely painful. Now then, if Voldemort tried to possess Harry, and Harry had a fragment of Voldemort's soul, I think that it could have been the true cause of Voldemort's pain: the fact of having his soul so close of another fragment. I think that Dumbledore knew that fact, but had to lie to Harry because it was inappropriate to let him know that he had one of Voldemort's soul fragments at the moment. Is that right? Or was it truly the pure soul of Harry's...

star wars - What "exactly" happens when someone turns to the Dark Side?

When I saw the original Star Wars saga as a kid, the concept of the Dark Side imprinted in me was quite simple. You did a bad thing, so you're a bad person so you go to the Dark Side and keep doing bad things. Now, obviously this doesn't hold true in reality. In my mind it is perfectly reasonable for Luke to kill the Emperor and Vader and then just flee the Death Star and rejoin the Alliance. After all they are at war, those are enemy officers that have captured him and are taunting him by threatening with death of all loved ones and the whole operation was intended to kill the Emperor anyway. The same would hold true for Anakin. He could have killed Mace Windu to save the Chancellor and Padme but that doesn't mean he's going to then go mad and kill all Jedis including children. It doesn't add up from a merely psychological point of view. He had a set of objectives and that made him want to keep the Chancellor alive (quite valid by the way, Mace Windu is quite clums...

star trek - Warning regarding forward saucer section in Nemesis?

In Star Trek: Nemesis , just before the Enterprise rams into the Scimitar, Picard sends a text message from his captain's chair arm pad to Troi — who is manning the helm in lieu of the crewman who was just blown out through what was once the view screen — indicating that she should put full impulse on standby. (Literally, if you watch the scene closely, Troi's console prefaces the order with "TXT MSG" !) My question is: Did Picard also somehow warn crew members in the forward saucer section about what was about to happen? The ramming of the Scimitar was a heat of the moment decision. Considering that he also resorted to calling the auto-destruct sequence shortly after (which ended up being offline), he probably was of the mindset that any losses would be acceptable in order to hault Shinzon's march to Earth. Still, I'm curious. Answer The original script indicates that he called for the crew to " brace for impact ". Whether that call (or the comma...