Closed FunkMonkey closed 14 years ago
Yeah, this is kind of what I have in mind for where I want to get it eventually... part of the problem is the rate limiting on the Twitter API. If you have four or five accounts feeding into this thing, you'll start cranking up your API rate pretty quickly. But I agree w/ the concept.
well. every twitter client kinda has this problem i guess. is the rate limit per IP or per account? would be kinda weird if it is per IP as there could be plenty computers behind the same.
I made up my mind a little about how I imagine Buzzbird should work when it comes to multiple accounts, services and topics the user is interested in.
In my opinion the data should be seen as streams coming from different sources merging into user-defined (filtered) output streams. In the end it shouldn't matter where the information comes from. The user can set up streams that merge different sources or that filter the tweets (information) based on tags, sender or whatever.
An output stream (the resulting data) will be displayed in an output-view and Buzzbird should be able to display multiple views at the same time, be it in tabs or side by side so the user can look at multiple data-streams.