There are many questions like “why Mixero doesn’t show all the people I’m following on Twitter”.
In this post we’ll try to explain what we think about it currently.
One way to fetch the people you follow to the client is straightforward. The client asks Twitter to give it the list, it does this, in chunks. But there is a catch:
- Twitter allows us to grab maximum 100 of them per API call, ordered by the order in which they were followed.
- Twitter allows us to use 100 API calls each hour. These calls also needed to fetch updates, direct messages and replies, view users’ timelines and their info, etc.
Some of us have thousands or even tens of thousands in their following list. Simple math and we would see that if you follow, say, 5000 people, you’ll need 50 API calls at startup only to fetch all of them. That will cause delays on startup and twice as little API calls for other things (less frequent updates, etc) during the first hour.
If you happen to follow 50000, you’ll have to wait for 5 hours just to fetch them using all the API calls available (you won’t be able to read updates from Twitter using API all that time). And, remember, the most recent friends will be fetched only in the end.
There is another way to get the people followed. When they wake up and write something, they’ll appear in the friends’ timeline. And they’ll appear in the Mixero contacts automatically. So Mixero will show the tweeps that updated recently.
When you do something with a tweep in Contacts, like adding to a group or active list, you tell Mixero that this person matters, and needs to be saved for later. So, this is the moment when a person you follow become your contact in terms of Mixero. From this moment, this person will always be in Contacts and will be synchronized across all the instances of Mixero.
Initially, when we thought of the Contacts feature, we wanted it to be populated only by people that:
- are saved in groups (that means they are matter to you) or
- brought by the timeline update stream (which means that they were active recently).
So, you say, what Mixero can do for me? To fill your contact list initially, just to give you something to play with and to add people to groups, we fetch limited count of people from your follow list, max. 500 by default (you remember, that would be the first 500 people you followed). We suppose this is a reasonable default.
From this point you may:
- Add some people by hand using drag’n’drop from timelines, “Add contact” buttons, follow button from inline profiles, etc. Don’t hesitate even if you know that the person has been already followed on Twitter, Mixero will handle this.
- Wait till somebody not in contacts become active. He will appear in Ungrouped very soon. Add him to a group, so he will stay in contacts forever, till you remove him manually.
- Increase the maximum of following loaded at startup in application settings. Remember that you’ll have to wait till all the tweeps are loaded. Expect slowdown in app responsiveness and updates frequency that time. The setting will be in effect after application restart. It would be wise to return the settings to lower value after you grouped the people fetched.
As always, we eager to hear your feedback.
The limitation on calls to the Twitter API really hamstrings all clients, which is unfortunate. But the reason I wanted to try Mixero is to categorize the moderate number of people I’m following so I can then view my twitter feed by topic/category. I follow only
The limitation on calls to the Twitter API really hamstrings all clients, which is unfortunate. But the reason I wanted to try Mixero is to categorize the moderate number of people I’m following so I can then view my twitter feed by topic/category. I follow only 354 people but that’s still too many to catch the info I want to see. I’ve created 20 categories in Mixero to “reduce the noise,” as you say, but so far I’ve only been able to sort about 100 of them, because the client hasn’t given me any more to work with. I’ve had it open for days now. Surely it can spare a few API calls to flesh out my list.
More importantly, you should let the user decide what they want their API calls to do for them, not make assumptions based on how you envision the software being used. If I have 5000 contacts and I want to stop updates for a half hour to finally import them, the software should let me do that. Make it an option. (There doesn’t seem to be an option in the API settings to allocate them for followers.)
Thanks. This software seems really promising, it just needs a few tweaks. Looking forward to downloading the next update.
where I got invitation code, I already followed Mixero
I like the look of the program…hoping it will have multiple user accounts soon and url previews available…that is something I really like about tweetdeck and power twitter on the web. Thanks!
[...] on refreshing the page. I wasn’t, the reason they do that is explained in the blog post On Contacts vs Following problem. This is one application where watching the how to video and reading the blog is very helpful. [...]
[...] on refreshing the page. I wasn’t, the reason they do that is explained in the blog post On Contacts vs Following problem. This is one application where watching the how to video and reading the blog is very helpful. [...]