3 ms·
It's not obvious to me how to automatically classify stories as (a)temporal. My understanding of the way submissions work is that if Bob submits something that
by rflrob 15y ago
It's not obvious to me how to automatically classify stories as (a)temporal. My understanding of the way submissions work is that if Bob submits something that Alice also recently[1] submitted, then it just gets counted as an upvote for Alice's story.
Then, of course, there are the "this happened recently, which inspired me to think about some broader trend". For example, during the AWS outage, Coding Horror had a story about Netflix's Chaos Monkey[2], which one could easily classify as both temporal and atemporal.
[1] For some definition of "recently" that I haven't yet figured out.
[2] http://www.codinghorror.com/blog/2011/04/working-with-the-chaos-monkey.html http://www.codinghorror.com/blog/2011/04/working-with-the-ch...
- JoachimSchipper 15y agoAnything that has been re-submitted is atemporal. That doesn't catch nearly everything, but...
- lt 15y agoI believe your understanding is right, recently being a month, provided it's the exact same URL. Popular news are usually submitted from different sources so there are actual duplicates. I agree that it's certainly not easy to automate the classification. The Coding Horror example is a very good one. Jeff write very atemporal stories, I'm pretty sure that happens intentionally. It's not unusual to see one of his posts from several years ago pop in the front page every now and then. Same with Joel's. It may be inspired by a recent event, but the lesson is meant to stand. I think a good heuristic would be: given a random, highly voted story from the archives, would it get upvoted if reposted today?