Hacker News new | comments | show | ask | jobs | submit login

Looks like whoever posted this got around the repost limit by appending a '?' to the end of the url. Someone should fix that.



Looks like whoever posted this got around the repost limit by appending a '?' to the end of the url. Someone should fix that.

Yeah, because we should never, ever be subjected to the same content twice. After all, this is Hacker News, not Hacker Olds, amirite?

(Sorry for the snark. I have been reading Hacker News for several years, and I don't recollect having read this article before. I enjoyed it, I upvoted it, and I'm glad it was reposted.)


Y'know, if I'd known it was an evergreen I'd have posted it myself, for the link karma.

Humph.


Come on, surely you already have far more internet points than any one man needs. Share the wealth a little!


I have vague recollection of reading it on HN before, but meh, it's not like we're wading through a swamp of reposts. My scrollwheel still works.


And sometimes the page changes but the url stays the same


Whew, that was a close call. Still shaking. I can't believe I almost read the same thing twice.


You can resubmit a link after a year, I think?

In any event, there's no way to block resubmissions programatically: the site owner could just change the name of the file.


Or people could append random query parameters, HN would have no way of detecting that http://example.com/?foo, http://example.com/?bar and http://example.com/?baz points to the same article.

No need to change anything on the webpage.


The page content's hash or any other blueprint (an arbitrary regex match) could be checked against for resubmissions. For convenience, if resubmission should be detected, the original post could be topped on the frontpage nevertheless, because old material may as well be worth revisiting for several reasons -- I for one had missed this article before, and enjoyed it reading greatly now.


  page content hash
Change one byte.

  regex match
Now we get into ship-of-theseus arguments. What counts as the "same" article? 99 percent? 51 percent?

What if you resubmit a blog post that's picked up 150 more comments since it was last posted? How would HN tell the comments apart from the article text?

What if someone submits a blog post that heavily quotes another article that's been submitted, in the process of rebutting it, and ends up being a 80% match?

What if you include the full text of moby dick, in a display:none <div>? What if the page loads the text of the article with javascript? Would the HN submissionbot have to render CSS and javascript?


> Change one byte.

Most resubmissions are submitted by people other than their authors, who are typically not in a position to change any bytes of the content.

In the present case, speaking as the last person to submit this one (more than two years ago), I don't see that there's any harm in it at all. If this is still interesting two years since it was last discussed on HN -- which clearly it is -- then good for the submitter, who has provided the HN audience with something interesting to read.


The slightest spec of dynamic content makes this approach brittle at best, author or not.


You probably meant "speck", not "spec".


I disagree. I — and others — have used query parameters to submit links to Humble Bundles, for example. New Bundles are launched regularly, and the broader HN community tends to have useful things to say about the titles in any given Bundle, and to appreciate the heads-up to their existence.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: