1–10 of 15 posts
This morning, I wanted to share that I released the FULL course (same URL) but every time I hit submit, it redirects me to my previous submission.
Is this some anti-duplication protection in action? Does my account not have posting privileges?
Solution: write a separate release announcement (there's certainly more to tell than just "done"?), link to the course from there, and submit the announcement.
But, if the system is stopping you submitting the same URL again, why not why not just put a meaningless query string on the URL so it's different from last time. eg:
https://www.nlpdemystified.org/?blah
BTW. I don't know if that will work. Just a thought.
Yes. The former submission got enough attention, so it shouldn't be submitted for a year. Solution: write a separate release announcement (there's certainly more to tell than just "done"?), link to the course from there, and submit the announcement.
>Yes. The former submission got enough attention, so it shouldn't be submitted for a year.
Yes. The former submission got enough attention, so it shouldn't be submitted for a year. Solution: write a separate release announcement (there's certainly more to tell than just "done"?), link to the course from there, and submit the announcement.
>Yes. The former submission got enough attention, so it shouldn't be submitted for a year. If this is official policy, it's kind of laughable to single out 'Show HN' posts for this treatement, given how any major techie news story gets submitted over and over and over again for days on end. I've complained about this so many times in the past, to no avail. Anyone who uses the 'Newest' page as their HN landing page wi…
Yes. The former submission got enough attention, so it shouldn't be submitted for a year. Solution: write a separate release announcement (there's certainly more to tell than just "done"?), link to the course from there, and submit the announcement.
>Yes. The former submission got enough attention, so it shouldn't be submitted for a year. If this is official policy, it's kind of laughable to single out 'Show HN' posts for this treatement, given how any major techie news story gets submitted over and over and over again for days on end. I've complained about this so many times in the past, to no avail. Anyone who uses the 'Newest' page as their HN landing page wi…
The mods somehow try to keep only one, if they are too similar, but sometimes it's difficult. And in some cases each day there is a new part of the story that appears, and that sometimes make the new post interesting.
Yes. The former submission got enough attention, so it shouldn't be submitted for a year. Solution: write a separate release announcement (there's certainly more to tell than just "done"?), link to the course from there, and submit the announcement.
That said, the anti-dupe mechanism doesn't catch all dupes, and from what I can recall of things said by dang, pg, etc in the past, I think that is intentional. In particular, dupes are explicitly considered OK after a certain period of time. You can see this by noting that certain links have been submitted to HN, and sometimes discussed in detail, on 5, 10, or even 15 unique occasions.
I believe it is the case that whatever automatic anti-duplicate detection they have doesn't do much besides look for an exact match on the URL though. It was known at one time that you could submit a dupe and get it to go through by just adding some extra stuff to the query string for example. What I can't speak to at all, is how much effort (if any) the mods put into manually detecting and remediating dupes. I can't recall any of the mods ever addressing that point explicitly, but my suspicion is that they do spend at least some cycles on doing that, but I can't prove it. And I may very well be wrong.
All this is totally unofficial mind you. It's just based on my recollections from various times this topic has been discussed in the past, and my own empirical observations. YMMV.