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

yeah, unfortunately it is. At present it uses the same threading algorithm as twitter does, namely: if there's an @username in a tweet, assume it's responding to the last tweet of that user. I may look to do something smarter down the road.. we'll see.

here's an idea. Make a message to @B from A be a reply to the last message from B to @A if any.

the issue is time decay. The last point in that conversation shouldn't be the parent of a new conversation N hours later.

Time decay might be a factor, but I think you'll get better results than making everything be a reply to the last update from that user. Once you find out what the magical N number is you can throw that in as well.

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