Everyone knows the majority of “join requests” come from spammers who are building their follow list. The few real “join requests”, we get are easy to review and we can their activity. When I review my “joiners” a month later, it is obvious that a most of them have become “dead accounts”.

In my opinion, the most important reason for people leaving Twitter, is that the conversations are shallow or weak. Most “tweets” are statements, one-directional comments, insignificant rants. Insufficient “tweets are actual conversations. So the members do not feel they are part of a community, there is little to draw them back.

Tsk, tsk, tsk.

Michael Martinez’s last blog post..Matt Cutts stresses Google crawling and indexing

Thanks for starting this discussion. Would be nice if Nielsen would reveal their methods, but they have been around a while and usually do a pretty good job gathering their stats. Either way Twitter has a technical challenge of scalability which must be overcome, in doing so, they will also overcome the social perception that there service is unreliable. Lately with the rush of interest, the service has been frustrating for many.

Travis Campbell’s last blog post..Your Business Plan for Failing Social Networking Sites

Samraat Kakkar’s last blog post..The Twitter Burst In India

What my post said is not how they did it, but no matter how they measured the app tweets made no difference because the data was not missing. The data was available just as any other tweet data was available. However, the retrieved the app data from the site it all came from the same DB and all was available on the site. Therefore no data was missing.

How they measured would confirm they knew how to measure data in the first place, but there was not data missing, so not really an effect in this debate.

You post to Twitter on page.
TwitterSite –> TwitterDB —> TwitterAPI —> ClientAPP

Then you answer from your ClientAPP – which then goes
ClientAPP –> TwitterAPI –> TwitterDB –> TwitterSite

Same API, Same DB – same data source- same activity as if you posted on page.
IE What you see in the app, you see on the page.
At least that is the usual path in a push / pull API system.

My client takes in the data and pushes it out to the site where it sits. You can see how many updates I made, what they were, my DM’s, my @schachin. All on my page. The app is a push pull to the site and from the site in an XML feed that is known as the API (well typically XML).

That means there is a record on the website of the activity. They may be using log data from hitwise or they may have other methods to monitor that activity (API?), but the data is all on the site to be seen and consumed on page or through API’s. NO data is lost between your client and the page. The API just pulls and pushes information back and forth between client and site.