Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

what types of features do you think would make it more useful for this use case?


Better threading for sure. The current interface is pretty good, but it makes it hard to keep track of multiple back-and-forths and oftentimes drops tweets from threads.


Indeed, navigating any discussion on Twitter feels like a complete mess. Imho some quirks it has in a browser are really annoying, like closing the conversation you are looking at when you click somewhere outside of it.

Happened to me plenty of times that I misclicked and closed a discussion which I had been very deep in, so I had to open it again and scroll&click my way back to where it originally closed, way too much wasted time over a simple wrong click.


- going back to a 'reproducible timeline', I want to see each tweet by each person I'm following, in the right order

- I don't want to see tweets by persons I'm not following, unless they are retweeded or part of a thread

- navigating the time line is a mess, sometimes the timeline scrolls to the top, and it's generally very hard to continue where you left

- better thread visualization

- clear distinction between tweets I've already seen vs 'unread tweets'

- some sort of bookmarking or 'read later' for tweets

- let me add tags to tweets and persons (I mainly want to add company or topic tags to people, for instance 'this is the WebGL guy at Apple')

[edit: formatting]




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: