Characters are not necessarily a single byte. Which are you counting?
On Thu, Aug 4, 2011 at 5:05 PM, Jason Toy jason...@gmail.com wrote:
I see some tweets going through my system that are over 140
characters, for example tweet id: 86955808553844736 is 284
characters.
Here is the actual
On Fri, Apr 29, 2011 at 10:36 AM, bitrace clive.tw...@googlemail.com wrote:
...
Some investigation indicates that the style sheet may contain an
incorrectly formed link:
link rel=stylesheet type=text/css href=//ajax.googleapis.com/
ajax/libs/yui/3.3.0/build/cssfonts/fonts-min.css
Hmm,
On Mon, Apr 4, 2011 at 1:00 PM, Brian Maso br...@blumenfeld-maso.com wrote:
Just noticed that on a whole lot of tweets I am retrieving through the
Twitter Search API that the tweet id numeric value is not equal to
the id_str value when JSON is turned in to JavaScript objects.
On Thu, Mar 31, 2011 at 1:49 PM, Data Gatherer gatherer...@gmail.com wrote:
...
I would not like the data gathering for one project to affect another
project. If I'm rate limited depending on how much data my single
connection to the data stream receives - this would affect all
projects. If
On Thu, Mar 31, 2011 at 2:48 PM, Augusto Santos augu...@gemeos.org wrote:
No it won't. Streaming has rate limit with around 1% of firehose, if your
search term os too much generic.
If your search term or bouding box get too many tweets, you will start
receive 'limit' status message as doc
There is not, as far as I can tell.
On Wed, Mar 30, 2011 at 10:17 AM, Lauren Sperber
lauren.sper...@gmail.com wrote:
Anyone know if there is a way to search twitter users by the location
provided in their profile?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
On Mon, Mar 28, 2011 at 10:40 AM, Trevor Dean trevord...@gmail.com wrote:
I know Twitter is still working on finding a fix but it's been a couple of
weeks now and it might be a good idea to implement the https to http hack
for now until they resolve the issue. I was hoping there would be a fix
