In my friends_timeline.json for tweet 1005190499 I'm getting a
profile_image_url value of
http://s3.amazonaws.com/twitter_production/profile_images/64498715/rollins_narrowweb__300x460_0_normal.jpg
-- which is a 404.
The correct, working profile image URL that shows up on twitter.com is
http://
The exact response is:
/statuses/friends.xml
Not found
This occurs even if I try to access http://twitter.com/statuses/friends.xml
in the browser, and is still occuring as I post this.
On Nov 14, 9:52 am, fastest963 <[EMAIL PROTECTED]> wrote:
> Is that all that is sent? A 404 header and "Not F
Hi,
It seems like the follow limit changed. It used to be 2,000 however
today I can't seem to follow more than 1,580.
Also, the Search API has a statement about no limits to search - are
search requests disregarded when determining the 100 GET requests per
hour?
Thank you,
Waitman
I've been using advanced search to create feeds from the public
timeline on specific keywords and so forth. One thing I'd like to do
is not pull tweets that are @[username] replies, but not sure how. Is
it possible to append an additional parameter to a feed URL to prevent
pulling @[username] repl
Jesse Stay wrote:
>
> I'm okay with anything - OAuth or not, so long as we're not forced to
> store plain-text credentials.
I just don't want a user's password. A proxy (API key token, OAuth
secret, whatever) is better, even if it doesn't afford any extra actual
security.
Users are educated ov
On Fri, Nov 14, 2008 at 15:15, Alex Payne <[EMAIL PROTECTED]> wrote:
>
> I've just added the first entry to the REST API Changelog at
> http://apiwiki.twitter.com/REST+API+Changelog. You'll find that we
> shipped a number of fixes today:
>
Awesome.
> * Security: statuses of protected users are
Thanks for sharing with us what you shipped, when you shipped it.
This is a welcome change. Keep it up!
Jesse
On Nov 14, 2008, at 2:15 PM, Alex Payne wrote:
I've just added the first entry to the REST API Changelog at
http://apiwiki.twitter.com/REST+API+Changelog. You'll find that we
s
I'm okay with anything - OAuth or not, so long as we're not forced to
store plain-text credentials.
Jesse
On Nov 14, 2008, at 1:28 PM, Alex Payne wrote:
I'd like to confirm that Cameron's interpretation of email is the
intended one. He wrote:
"I read Alex's E-mail to say, '*sooner* wit
I can't say I was keeping any of these bugs as pets, but Matt (and all you
guys) - great work. Your continuing effort is inspiring. :)
On Fri, Nov 14, 2008 at 4:15 PM, Alex Payne <[EMAIL PROTECTED]> wrote:
>
> I've just added the first entry to the REST API Changelog at
> http://apiwiki.twitter.
I've just added the first entry to the REST API Changelog at
http://apiwiki.twitter.com/REST+API+Changelog. You'll find that we
shipped a number of fixes today:
* Fixed: error messages returned by the API will be returned in the
format of the original request. For example, if you request
/statu
As noted in issue 151 we just launched a fix for this. It may take a
half an hour or so to be rolled out to all servers.
— Matt Sanford
On Nov 12, 1:04 pm, Niall Kennedy <[EMAIL PROTECTED]> wrote:
> Filed as issue 151.
>
> http://code.google.com/p/twitter-api/issues/detail?id=151
>
> -Niall Kenn
I'd like to confirm that Cameron's interpretation of email is the
intended one. He wrote:
"I read Alex's E-mail to say, '*sooner* with minimal effort' [but
will occur regardless of the effort required], emphasis mine. So far I
haven't seen anything to dispute that interpretation."
Indeed, whe
On Fri, Nov 14, 2008 at 1:20 PM, Jesse Stay <[EMAIL PROTECTED]> wrote:
> there's absolutely nothing we can do about it because we have no option
> but to store passwords in plain text.
>
Store the passwords encrypted then decrypt them when you need to
use them. There's a chicken-and-egg problem w
Frankly, I'm in your boat. I've seen this over and over in the last
year or two - the bug report says it's low priority, which is a
concern for me. All it takes is for some developer (I actually saw
this the other day in a proof of concept by another developer) to
build an app that coll
You might take a look at the source for Spaz, an open source Twitter
AIR client: http://code.google.com/p/spaz/
On Fri, Nov 14, 2008 at 12:21 AM, abhishek <[EMAIL PROTECTED]> wrote:
>
> how can we used twitter api with air
>
--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
On Fri, Nov 14, 2008 at 11:20 AM, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
>
> Ed Finkler wrote:
>> I do understand the frustration, really. But I think I can safely say
>> that the dudes who post here from Twitter bust their ass for you and
>> me, and this kind of thing really doesn't help.
>
>
Ed Finkler wrote:
> I do understand the frustration, really. But I think I can safely say
> that the dudes who post here from Twitter bust their ass for you and
> me, and this kind of thing really doesn't help.
So, what would help? Sycophantic cheerleading? I don't think so.
Lets talk about re
I love free stuff! But hard to get disappointed when it doesn't work
out the way we hope, yes?
I do understand the frustration, really. But I think I can safely say
that the dudes who post here from Twitter bust their ass for you and
me, and this kind of thing really doesn't help.
--
Ed Finkler
Ed Finkler wrote:
> Why are you still watching, then?
Because it's free?
--
Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go a
Is that all that is sent? A 404 header and "Not Found" in the content?
When did you access the APIs? I know that twitter was having some
trouble yesterday with their site, is it still not working?
For some reason it seems it didn't post my fix,
here it is again:
In the process() function, change:
if($this->username !== false && $this->password !== false)
curl_setopt($ch, CURLOPT_USERPWD, $this->username.':'.$this-
>password);
To:
if($this->username !== false && $this->password !== false)
it seems it didn't post my fix
here it is again:
In the process() function, change:
if($this->username !== false && $this->password !== false)
curl_setopt($ch, CURLOPT_USERPWD, $this->username.':'.$this-
>password);
To:
if($this->username !== false && $this->password !== false)
curl_setopt($ch
Why are you still watching, then?
On Fri, Nov 14, 2008 at 8:50 AM, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
>
> Cameron Kaiser wrote:
>> 2) I read Alex's E-mail to say, '*sooner* with minimal effort' [but will
>> occur regardless of the effort required], emphasis mine. So far I haven't
>> seen
This library is not coded very accurately. I will post a fixed version
within the next few days. My dev computer is currently under-repair,
but when its finished (tonight?) I will work and fix this library. In
the mean-time, just make the change noted in my previous post and the
update() function
Whenever I try to access these REST API URLs, I get a "Not found" xml
error. Are they deprecated, or is this a temporary problem?
On Fri, Nov 14, 2008 at 6:52 AM, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
>
> OAuth won't happen until Twitter has to shut down the service when
> someone steals 50% of the user's passwords through some poorly written
> API-using app that gets pwnt.
>
And... people have to change their password.
We are working on a members website.
Users will join create a profile and add things like youtube feeds,
images etc,
We would like users to be able to add there twitter account details
and feed all their tweets into their profile and randomly pull out
tweets from different members onto the
Cameron Kaiser wrote:
> 2) I read Alex's E-mail to say, '*sooner* with minimal effort' [but will
> occur regardless of the effort required], emphasis mine. So far I haven't
> seen anything to dispute that interpretation.
Right. Just like "IM to Twitter will eventually come back" became
"sorry, w
> > Thanks for being open about it Alex - it helps us plan better, and it's
> > comforting to know it is a priority.
>
> Dude, the only priority it has is LOW. Did you an I read different
> emails? Alex wrote:
>
> "If we can deliver it sooner with minimal effort, though, we will."
>
> Basical
how can we used twitter api with air
Hi Alex,
I am using this code for posting status ..
username=$_POST['name'];
$t->password=$_POST['password'];
$res = $t->update('i am testing twitter.class.php');
if($res===false){
echo "ERROR";
echo "";
print_r($t->responseInfo);
Hi Alex,
I am using this one http://twitter.slawcup.com/twitter.class.phps
Thanks
Rahul
On Fri, Nov 14, 2008 at 12:15 PM, Alex Payne <[EMAIL PROTECTED]> wrote:
>
> Which Twitter PHP class are you using?
>
> On Thu, Nov 13, 2008 at 10:24 PM, Rahul <[EMAIL PROTECTED]> wrote:
> >
> > Hi All,
> >
>
If your using:
http://code.google.com/p/php-twitter/
which is what it looks like... then you need to specify
$twit->username = "";
$twit->password = "";
$twit->User-Agent = "";
then call the $twit->update
If that's not the correctly library, you still should have to set
those somehow, either stat
Jesse Stay wrote:
>
> Thanks for being open about it Alex - it helps us plan better, and it's
> comforting to know it is a priority.
Dude, the only priority it has is LOW. Did you an I read different
emails? Alex wrote:
"If we can deliver it sooner with minimal effort, though, we will."
Basi
Alex Payne wrote:
> Hope that helps. Long story short, we've been punting on OAuth to try
> to minimize duplication of labor as we transition to some new
> technologies, but we're willing to be pragmatic if the libraries have
> improved.
Ugh. If the available OAuth implementations (libraries) s
35 matches
Mail list logo
