News for hackers. Stuff that matters.
Re:Also Out at Twitter: Engineering Head Roetter (and More t... by jay_kyburz on Sunday January 24, 2016 @05:37PM (#10964385)
I think making tweets more readable would help a lot. I think pulling @ addresses, hashtags, and URLS out of the body would give every tweet more breathing room and make more sense to an everyday user.

Then I've read heaps of great ideas here on HN about how they should be leveraging the real-time stream to be the go to place for what is going on for any issue.

What I don't understand is why nothing is changing, I've only been a twitter user for a few years but I've never seen anything change. I think they need to be pumping out lots of little experimental tools for finding, consuming and creating tweets.

Re:Also Out at Twitter: Engineering Head Roetter (and More t... by walterbell on Sunday January 24, 2016 @06:00PM (#10964453)
> they need to be pumping out lots of little experimental tools for finding, consuming and creating tweets

This existed as a thriving third-party ecosystem, before Twitter dismantled it, http://www.mathewingram.com/work/2015/04/30/twitters-multi-b...

"Last year, Twitter effectively admitted that it needed third-party developers ... For anyone who had worked with Twitter in the past, however, this was a little bit like Fox Inc. asking for chicken volunteers to help it build a new hen-house. As far as I can tell, there’s little or no evidence that Twitter’s outreach program is working. What would Twitter be like today if it had embraced its ecosystem and tried to build on it instead of cutting it off at the knees? ... I think it would have a lot more goodwill to spend — both with developers and with users — than it does now, and I think many aspects of the service that it is now trying to build up, including smart recommendations and curation, would be a lot better off with outside input than they are now."

Re:Also Out at Twitter: Engineering Head Roetter (and More t... by jay_kyburz on Sunday January 24, 2016 @06:09PM (#10964486)
Fully agree, but I think they they could at least have some in house talent pumping out experiments.

Would be a dream job for me to be on twitters payroll building experiments and functional prototypes.

Re:Also Out at Twitter: Engineering Head Roetter (and More t... by newman314 on Sunday January 24, 2016 @06:12PM (#10964506)
What I have a hard time with is consuming conversations esp. when there are multiple branches. There is no easy overall thread view.
Re:Also Out at Twitter: Engineering Head Roetter (and More t... by currysausage on Sunday January 24, 2016 @06:43PM (#10964612)
Then go back to the stream and find yourself at the top of the page. Have fun scrolling down to where you were. I get it, pagination is totally 1999. But isn't there some JavaScript solution to this?
Re:Also Out at Twitter: Engineering Head Roetter (and More t... by r721 on Sunday January 24, 2016 @07:53PM (#10964906)
Also scrolling down is not really infinite: on my system it's around 700 tweets (calculated by Ctrl-F "reply").
Re:Also Out at Twitter: Engineering Head Roetter (and More t... by mschuster91 on Sunday January 24, 2016 @11:16PM (#10965526)
It's 800 tweets (per https://dev.twitter.com/rest/reference/get/statuses/home_tim...), and it sucks if you're one of those who want to read every single tweet posted while sleeping.
Re:Also Out at Twitter: Engineering Head Roetter (and More t... by newman314 on Sunday January 24, 2016 @07:22PM (#10964782)
Well, Plurk had something like that but still was not that great of a UX.
Re:Also Out at Twitter: Engineering Head Roetter (and More t... by JoshTriplett on Sunday January 24, 2016 @06:24PM (#10964548)
Agreed; while the current time-ordered view works OK for some purposes, a quick toggle to threaded conversations would help massively when reading a large set of replies.