[killwhitey]

Author here: In developing this I discovered that Twitter really doesn't care about lists. The limits on API usage and aggressive following are well documented, but anything about lists is minor.

Also, if anyone from Twitter is reading: it would be nice if Twitter implemented a way to subscribe to someone's timeline instead of having to resort to this method.

[danso]

Still befuddles me how badly Twitter has neglected list functionality. On every device/platform, there's a differently-obfuscated way to just see the damn lists you've created, nevermind create them. I get that making lists isn't fun, but they never seemed to try to make them easy to make. The end result is that new users who enthusiastically follow others see a stream of unfiltered shit and end up either just quitting, or obsessively pruning their follow list.

[huskyr]

I don't get this as well. The only reason i use Tweetbot instead of the official client is because it allows me to set a list as a custom timeline. This is such a wonderful functionality: i can easily switch between the 'firehose' of everyone i follow (around 700 accounts or so) and a custom timeline that has around 50-100 accounts that i don't want to miss. You get the feeling that the only thing Twitter cares about is building new features (e.g. moments) instead of improving existing features.

[joshkpeterson]

I moved to a new city and I wanted to see who I followed that lived there. I had to spend 8 hours learning the API and writing a script to put those people into a list. I shouldn't have to do that.

[sulam]

This feature used to exist in the web client and was removed. I am loathe to say why because my memory is faulty and I wasn't directly involved with it, but IIRC there were (odd to me) privacy concerns and the usage wasn't high.

[cocotino]

I am sure there's an endpoint to get the timeline of someone else because tweetdeck had such a feature some time ago.

If you're concerned about API usage limits, just use the API keys of any official client (google them) and enjoy.

[mayneack]

Did tweetdeck remove this feature? I can't seem to figure out how to do it there.

[cocotino]

Yes they did remove it.

[andreasklinger]

Imo they realized it doesnt work for their users core usecases that well. Therefore they removed efforts.

The problem here is in the end that there isnt a easy way for a company to communicate it's product strategy to api users and people are left to reverse engineer it.

[theli0nheart]

It doesn't work for their users' core use-cases because they never made it usable in their core web and mobile products. They don't spend engineering time on making it useful in their core web and mobile products because their users don't use it. See the problem here?

It's like they gauged interest on half-an-MVP of a feature and never bothered to truly complete it and make it actually useful.