John:
Thanks very much for the reply.
On Nov 14, 8:30 pm, John Kalucki wrote:
> This sounds like you were ignoring HTTP error codes and eventually got
> blacklisted.
> Consider:http://apiwiki.twitter.com/Streaming-API-Documentation#Connecting
Hmm... I was launching single curl requests, makin
I had the same issue. And i was blacklisted.
On 11/15/09, Jim DeLaHunt wrote:
>
> John:
>
> Thanks very much for the reply.
>
> On Nov 14, 8:30 pm, John Kalucki wrote:
>> This sounds like you were ignoring HTTP error codes and eventually got
>> blacklisted.
>> Consider:http://apiwiki.twitter.co
Hi Amir,
I have no problems posting Hebrew Tweets - go to twitter.com/
twtmarketerpro
You'll see my Hebrew test Tweet there (among others)
בברכה
= Oren
On Nov 14, 9:06 pm, אמיר סימן טוב wrote:
> Hi all,
>
> Hope that this is the right place.
>
> Posting to Twitter is
> easy:http://www.twitt
i concur - until we are sending back an error code if your status
update was rejected (for being a duplicate or for going over 140
characters), option #1 seems like the most prudent want to go about
this.
Twitter has stated that providing a clear indication of when this has
occurred (I d
There are two levels of blacklisting. One is a temporary band that
resets every few minutes. This one gives you 401 errors. Then there's
an IP black hole that is removed by an operator. Currently the IP
black hole sends a TCP RST, but we might might also null route you.
You can verify an IP block
I believe I answered this question on Nov 12 (message 2) in this
thread.
http://groups.google.com/group/twitter-development-talk/tree/browse_frm/thread/c6046a1df338f0ae/1c4bf379d27abb32?rnum=1&q=413&_done=%2Fgroup%2Ftwitter-development-talk%2Fbrowse_frm%2Fthread%2Fc6046a1df338f0ae%2Fb886df7e063a8
The uptime of twitter search {API} has degraded to the point of making
our client app useless.
Hoping @twitter finds the issue soon.
hi mikawhite.
in the absence of actionable information, i'm not sure what you would
like us to look into. in order for us to help you out, please provide
information such as which calls you are making, when you are seeing
failures, and any other information you can provide us to correlate
Hi Raffi,
Three issues:
1) Search API returns 15 pages in 59+ seconds. Two weeks ago this was
less than 10 seconds. I sent @ej a tweet last week.
2) 503 Service Unavailable - increasing frequency {I'm now recording a
log to examine which searches this occurs with} {seems "to:xxx" is
most frequ
Raffi,
Pls add this to a script - fails every time today.
http://search.twitter.com/search?q=to:mrskutcher
1) Search API returns 15 pages in 59+ seconds. Two weeks ago this was
less than 10 seconds. I sent @ej a tweet last week.
just for reference - in the future, please file a bug on the google
code tracker rather than sending @replies directly to twitter folk.
we're better able to keep track o
Raffi, please note as soon as I tried the query below via the browser,
it slowly begins to work in the API.
On Nov 15, 10:25 am, mikawhite wrote:
> http://search.twitter.com/search?q=to:mrskutcher
personally, that's not how i would do it.
http://search.twitter.com/search.json?to=mrskutcher
works just fine for me.
Raffi,
Pls add this to a script - fails every time today.
http://search.twitter.com/search?q=to:mrskutcher
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com
Raffi,
Re: streaming API - I chatted with John about this. My take away is
the Streaming API isn't ready for a desktop client with an installed
base over several hundred users. Did I mis-understand?
I'd hope my installed base will eventually be tens of thousands.
On Nov 15, 10:26 am, Raffi Kri
Details:
Calling "http://search.twitter.com/search.json?to=mrskutcher"; through
my client app did not work until I called same link via a browser.
Once called via the browser, it works in my client app.
Why?
On Nov 15, 10:29 am, Raffi Krikorian wrote:
> personally, that's not how i would do i
Thanks John,
I am not sure I understand when you say "There is no single role in
the Streaming API that will allow that many follows and track
parameters.", your documentation says :
"The default access level allows up to 200 track keywords and 400
follow userids. Increased access levels allow 8
I'd like to float an open discussion / dialog here.
"How many developers are getting to the point where they are choosing
NOT to develop on the Twitter platform"
And
"If Twitter offered you a PAID commercial account which came with
dedicated access and dedicated support would this inte
I just wanted to add some additional color to this as it didn't come
through well in our email announcement. The actual change is happening
Monday morning. Our email unfortunately said "today" as we were
planning to send it the day of, but we ended up sending it earlier to
give more notice and for
Dean, please start a new thread. Regarding my original thread topic,
support from twitter is awesome.
The default access levels are track 200 and follow 400.
Shadow increases follow to 80k, but leaves track at the default of
200.
TrackRestricted increases track keywords to 10k but leaves follow at
the default of 400.
All of the other mentioned roles do the same, they increase access on
one dimen
Hi there,
I'm doing some dev work and I'm getting occasional ssl errors when making
calls against api.twitter.com/1. The most recent was posting to
favorites/create.
Is it possible some of the servers have bad certificates? Or is it likely
I'm doing something very wrong?
Tim.
On Nov 15, 2009, at 1:16 PM, Tim Haines wrote:
Hi there,
I'm doing some dev work and I'm getting occasional ssl errors when
making calls against api.twitter.com/1. The most recent was posting
to favorites/create.
Is it possible some of the servers have bad certificates? Or is it
likel
This could possibly be related,
I recently switched from using https://twitter.com to https://api.twitter.com
and found that the majority of my cURL calls (via php) to the api
started failing, although no other parts of my function changed.
Out of curiosity I changed it to http://api.twitter.com
When you use HTTP over HTTPS you will never have trouble with (TLS)
certs because they
are never used for port 80 traffic.
On Sun, Nov 15, 2009 at 19:56, dean.j.robinson
wrote:
>
> This could possibly be related,
>
> I recently switched from using https://twitter.com to https://api.twitter.com
>
You wrote "So causes a problem for a cURL message. The message
is truncated at the ampersand."
This could be due to the fact that on UNIX-like systems (including
Mac), the command line interprets the ampersand as "everything before
this point should be run in the background." Anything after the
OK, just checked this morning and "in reply to" links are back on the
website! Thanks for fixing the bug, twitter team! =)
On Nov 13, 2:00 pm, bassmanjase wrote:
> Hi,
>
> I use twitter (@bassmanjase), and access it via the website and teh
> Echofon plugin for Firefox. I've just noticed today th
Thanks a lot John for this clear explaination.
Is it possible to have the following settings:
- superfeedr_foll as Shadow
- superfeedr_trac as TrackRestricted
That would truly be awesome. I will change our implementation so that
we use 2 different accounts for the 2 purposes.
Again, thx.
Julien
Using Twitter is definitely the right way to social network - with the
new/up and coming sites capitalizing on twitter such as the "retweet,"
a new niche has emerged...the "pretweet" found exclusively at
http://www.goTWEETme.com. This is a site that allows anyone to
request other twitter users to
I apologize about the miscommunication. On twitter-api-announce
(http://bit.ly/3UQ0LU) I posted the date of Monday (11/16), but
unfortunately posted the wrong date on this group.
Sorry again for the confusion.
On Nov 15, 10:40 am, Ryan Sarver wrote:
> I just wanted to add some additional color
Please request the additional access by whatever means you requested
your initial access.
-John
On Nov 15, 3:35 pm, Julien wrote:
> Thanks a lot John for this clear explaination.
> Is it possible to have the following settings:
> - superfeedr_foll as Shadow
> - superfeedr_trac as TrackRestricte
hmm.
http://lmgtfy.com/?q=jquery+basic+authentication+
(not being a great javascript/jquery coder, i may recommend doing a
$.ajax call instead of the $.getJSON -- in the beforeSend callback do
a request.setRequestHeader with the basic auth headers as documented
at http://en.wikipedia.or
Thanks Ryan - that makes me feel much better. :-) I love that Twitter has
been improving these practices.
Jesse
On Sun, Nov 15, 2009 at 11:40 AM, Ryan Sarver wrote:
>
> I just wanted to add some additional color to this as it didn't come
> through well in our email announcement. The actual cha
Hi All,
Update profile background using twitter api is working fine
with username and password but on oauth its causing the problem and
returning the message
"Something is technically wrong.
Thanks for noticing—we're going to fix it up and have things back to
normal soon."
I have tri
I should state that without passing any extra parameters (eg.
since_id) I can get this to sign just fine, so I think I must be doing
something wrong, but I'm not sure what I'm doing wrong.
Here's a sample of a request that signs fine and I get the statuses:
GET /statuses/friends_timeline.xml?
oau
Ok I sent an email, but Ryan takes forever to respond to my emails :/
Isn't there anything you could do?
thanks,
On Nov 15, 6:34 pm, John Kalucki wrote:
> Please request the additional access by whatever means you requested
> your initial access.
>
> -John
>
> On Nov 15, 3:35 pm, Julien wrote:
35 matches
Mail list logo
