Here is the original twitter dev blog post if anyone wants to see it [1]. I hope this does not come off an condescending and negative, but my honest reaction is "What took so long"?? It blows my mind that it took 7 years to realize/implement this feature.<p>One of the main reasons I don't regularly use Twitter is because there is too much white noise. It's hard for me to find information of value because the comments are all over the place. Even when I follow a strict set of People specific to an Industry or a Topic, create specific lists, etc; it's still too much white noise (example; interesting post right next to what someone else had for breakfast).<p>I am actually quite frustrated with the entire thing. Being someone interested in Development and Solving Problems, I know this can be better. And on that front, it's great to see that this feature finally exists. But there is so much more that could be done to make it even better. It's frustrating because the issue relates to a core Twitter experience, which (under [2] API v1.1 Developer Rules of the Road section 1.5) cannot be replicated. So the end result, I'll probably just have to wait for the customer feedback loop process to complete (which likely takes a long time). Hopefully in the future I'll see some of the features that I had once hoped to build myself. Until then, I probably won't be a regular Twitter user. Frustrating.<p>If anyone at Twitter reads this, I would be more than happy to describe in detail some of the ways that I think the timeline can become more relevant and valuable. I've talked about it here on HN (project name is InfoStream), and it basically relates to a correlation of GeoLocation Data and Time with relation to Real World Events.<p>[1] <a href="https://dev.twitter.com/blog/introducing-custom-timelines" rel="nofollow">https://dev.twitter.com/blog/introducing-custom-timelines</a><p>[2] <a href="https://dev.twitter.com/terms/api-terms" rel="nofollow">https://dev.twitter.com/terms/api-terms</a>