> The above page doesnt document what the effect is on the user if the
> User Rate limit of 100 reqs/ph is exceeded.
In the past, it usually involved dismemberment, but this was revised in an
early version of the API and now the user simply has to wait for the next
hour interval when the rate lim
http://apiwiki.twitter.com/Rate-limiting
The above page doesnt document what the effect is on the user if the
User Rate limit of 100 reqs/ph is exceeded.
>From what I remember its an hour, but am having trouble finding this
documented anywhere.
Cheers
M
Any particular reason the blocks/exist function returns the
information for the user requested if the block exist and a hash error
response if not? I would think following the same kind of format as
the friendship exist function would make more sense; something like:
true/false
An error response
Doug:
At least we are not expecting this bug to be fixed. So we will have to
go with a peripheral API call. I would have really love to get this in
the same stanza however because, as Dave said very *loudly*, that
makes life much easier for us mobile developers.
Now we will have to wrap this in
Hi All,
Blocking now gets more fun:
- Feature (REST): Added methods to retrieve blocking information
See also: Google Code Issue 9:
http://code.google.com/p/twitter-api/issues/detail?id=9
See also: blocks/exists =>
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-blocks-exists
See also:
This thread might help shed some light:
http://groups.google.com/group/oauth/browse_thread/thread/bdf8b99e84a8aaef/0f95410fdeb64284
On Mon, May 11, 2009 at 19:37, Joe McCann wrote:
>
> No takers on this?
>
> On May 9, 2:04 pm, Joe McCann wrote:
> > Hello Folks,
> >
> > I have built a simple boo
No takers on this?
On May 9, 2:04 pm, Joe McCann wrote:
> Hello Folks,
>
> I have built a simple bookmarklet
> (http://www.subprint.com/blog/projects/imgly_bookmarklet/
> ) that utilizes Img.ly's web service for posting pictures and tweets
> via Img.ly's REST API. If you use Img.ly directly, v
Thanks Chad...you're absolutely right. Thanks!
On May 9, 5:38 pm, Chad Etzel wrote:
> Probably because Twitter considers $ by themselves to be unsearchable
> punctuation. They added it as a token modifier a while ago (like #
> for hashtags), so you could search things like $BAC, but $$ itself
You can get .atom feeds from the Search API already... Not sure if
that is close enough to XML for your needs, though...
-Chad
On Mon, May 11, 2009 at 8:22 PM, Jeff Bishop wrote:
> I see that the Twitter API shows JSON objects as the returning data feed for
> search API calls. Can we get XML/RS
http://apiwiki.twitter.com/V2-Roadmap#MergingRESTandSearchAPIs
On Mon, May 11, 2009 at 19:22, Jeff Bishop wrote:
> I see that the Twitter API shows JSON objects as the returning data feed
> for search API calls. Can we get XML/RSS feeds instead of JSON for easier
> usage in some environments?
Verify_credentials returns . That is unique.
On Mon, May 11, 2009 at 18:55, Jochen Kaechelin wrote:
>
> def callback
> @request_token =
> OAuth::RequestToken.new(UsersController.consumer,
> session[:request_token], session[:request_token_secret])
> @response = UsersController.consu
Something to keep in mind is that when switching from a computer to a mobile
device you are losing power/features for mobility. You have to expect the
same loss in functionality.
On Mon, May 11, 2009 at 18:38, Dave Mc wrote:
>
> To be blunt this is very unsatisfactory. Once again you guys are no
I see that the Twitter API shows JSON objects as the returning data feed for
search API calls. Can we get XML/RSS feeds instead of JSON for easier usage in
some environments?
Jeff
def callback
@request_token =
OAuth::RequestToken.new(UsersController.consumer,
session[:request_token], session[:request_token_secret])
@response = UsersController.consumer.request(:get, '/account/
verify_credentials.json', @access_token, { :scheme => :query_string })
case
David,
As with any solution there are compromises (the normal big three are time,
resources, quality of service) and while this change may make your
particular use of the API more difficult, it is not only important but also
necessary given our architecture and growth. The API provides Twitter data
To be blunt this is very unsatisfactory. Once again you guys are not
being at all cognisant of the requirements of mobile Twitter client
apps. These face much bigger problems than just the rate limit. They
are constrained by physical limitations such as battery life, latency
and bandwidth. And the
I'll admit I'm a little disappointed that the info won't be part of
the user objects anymore (will have to rethink some of my planned
features... ie. won't be able to dynamically show/hide the dm button
next to tweets if it means I need an additional api call for each
user) instead relying on anot
Hi.
We feel compelled to briefly explain what we at escarp do. escarp is a
review of brief poetry and prose distributed through Twitter. On our
site (http://escarp.org) we use the API to show the most recent
pieces, as well as handle comments and news.
To distribute an author's bio, many Twitter
The default is: "show me: @replies to the people that I'm following". The
vast majority of our users keep this default. If this setting is indeed
removed this is the behavior we will use.
Note: I will update the thread when/if this setting is axed (even though
it's not really an API decision) to c
OK, thanks for the heads up.
On May 11, 11:30 pm, Doug Williams wrote:
> We have had a debate internally (today) where we have all but decided to
> remove this setting in the near future. I would not create any application
> that relied on this. Almost all of our users leave it at the default (o
Wait, did the default not used to be "Show all @ replies" (it is the
first option in the dropdown box)? Did that change? Personally, I
like seeing all of them as it leads me to follow new and interesting
people...
If this goes away, is everyone going to be set to "only show @replies
to people I
We have had a debate internally (today) where we have all but decided to
remove this setting in the near future. I would not create any application
that relied on this. Almost all of our users leave it at the default (only
show @replies to people I follow) so the cost of maintaining the setting
doe
Please see the recent message on following and notification deprecation:
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/42ba883b9f8e3c6e
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Mon, May 11, 2009 at 1:27 PM, TjL wrote:
>
Issues 419 [1] and 474 [2] are very popular, in the painful kind of way. The
defects report that methods returning user objects (see users/show for an
example [3]) are returning incorrect or invalid values for the
element.
The fix for this inconsistency is in fact non trivial [4]. The problem lie
1) http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
suggests that you can use any of: xml json rss atom but rss and atom
are not working at all:
Try this on the commandline:
for EXT in xml json rss atom
do;
echo "
$EXT:"
curl "http://twitter.com/users/show.$EXT?screen_name=
Thanks, I'm familiar with the setting.
Somehow the setting does not have any effect with the account I'm
testing with: not when logged in to twitter.com, and not when using
statuses/friends_timeline. Chad's posting made me do some tests with
two other accounts: there the setting works as it shoul
My apologies! I was looking at a different user in a different
terminal and I've been staring at this screen too long. status_count
is reporting accurately.
Sorry for the false alarm.
On May 11, 1:25 pm, iematthew wrote:
> The REST API is reporting the status_count as zero for the following
> u
There is a setting to change this behavior:
http://help.twitter.com/forums/23786/entries/14595
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Mon, May 11, 2009 at 10:44 AM, Chad Etzel wrote:
>
> I'm confused now. I just pulled my friends_timeline and it
Well, I started over and about two hours later I had a script written.
I've been testing / tweaking it today and it does seem to work.
Basic premise is fairly simple, it checks
"http://twitter.com/statuses/mentions.rss?since_id=$LAST_ID";
where $LAST_ID is stored in a text file as the last ID t
I'm confused now. I just pulled my friends_timeline and it is
definitely showing @replies from my friends to people I don't follow.
i.e. I'm getting the "firehose" as it pertains to my
friends_timeline are you saying you're not seeing the same thing?
-Chad
On Mon, May 11, 2009 at 1:36 PM, v
On May 10, 12:00 am, Abraham Williams <4bra...@gmail.com> wrote:
> I would think that statuses/friends_timeline [1] would not be effected by
> @-reply settings [2]. If it is your only option is to use the search method
> you mentioned. The down side of this is protected accounts are not included.
The REST API is reporting the status_count as zero for the following
user, even though there are quite a few updates under the user's
account:
https://twitter.com/users/show/MoorparkRealtor.xml
I'm also receiving no statuses when I request the user's timeline.
I've only encountered this one use
Any joy with this yet?
I've looked at it a few times but have yet to see the light...
Will monitor this thread for any updates.
Many thanks
Justin
On May 1, 4:41 pm, Richard L wrote:
> Hi Robert,
>
> I'm also looking into this once I get my .NET version problems sorted
> out - will let you kn
If you aren't trying to do this in realtime you can get around this by
doing a broad search and storing the results in a MySQL database. You
could then play with the data and apply some more advanced filters to
it.
On May 1, 12:03 pm, hill79 wrote:
> Insanely quick replies - thanks :)
>
> On Ma
That sure is odd. I know this is off-topic, but have you tried to see if your
customers would be willing to pay for the service you offer?
Actually, it sounds like that is what you are going to have to do…
--
Patrick Burrows
http://Categorical.ly (the Best Twitter Client Possible)
@Cate
hi,
I am trying to develop an application using twitter API's(using
twitter4j jar file). Can you suggest me a method to acess users
replies without knowing the users password(I have the users username
in the data base).
Surya Sravanthi
On Mon, May 11, 2009 at 7:14 PM, Paul Kinlan wrote:
> Hi,
This should be fixed. The database the public timeline service was pointing
to went down. This problem has been fixed and a permanent/dynamic solution
was put in place to ensure this doesn't happen again.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Sun, Ma
This should be fixed. The database the public timeline service was pointing
to went down. This problem has been fixed and a permanent/dynamic solution
was put in place to ensure this doesn't happen again.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Sun, M
Hi,
We don't know why we were blocked, we had a commercial contract in place -
but the provider aren't very forthcomming. The model that was used was an
"Adsense" for mobiles, which meant that we were supposed to be paid for
every message we processed, however the network never attached any adver
If this is just for yourself, then you could send them through your carrier
provided SMS to email gateway (as far as I know, every carrier provides
one.) It is an email address that you can use to send yourself text
messages. For instance, for AT&T, it is @txt.att.net. An
email sent there will sho
Why were you blocked?
And there seems to be a lot of competition in this space (SMS Gateway
providers) can’t you just go to someone else?
--
Patrick Burrows
http://Categorical.ly (the Best Twitter Client Possible)
@Categorically
From: twitter-development-talk@googlegroups.com
[mailto
Hi,
Just to let you know, I developed www.twe2.com exactly for this purpose.
However, we have just been blocked by our SMS provider.
It is a shame really because we sent 2 million SMS's to the Twitter
community,
Paul
2009/5/11 Arik Fraimovich
>
> Someone already developed an application that
Someone already developed an application that forwards mentions to DM
(see here: http://apiwiki.twitter.com/Application-Ideas).
When I tried it, it didn't work that good, but I think he did some
changes since then.
On May 11, 8:15 am, TjL wrote:
> I've been banging my head against this for seve
Nice work guys, talk about the firehose has been floating around for
ages, great to see it finally appear and with numerous variants
available (thats a bonus). I personally don't have any use for it
(yet) but I'm sure it'll please quite a few.
On May 10, 2:04 pm, John Kalucki wrote:
> Note: Th
Oh god. Please share where is this twitter-announce list?
--
Hwee-Boon
On May 10, 12:51 pm, Jesse Stay wrote:
> Not to be picky, but can we get these announcements on the twitter-announce
> list in the future? Who is this John and is he a real Twitter employee?
>
>
>
> On Sat, May 9, 2009 at 10
45 matches
Mail list logo
