Hi Alex,
I am using this code for posting status ..
?php
include(class.twitter.php);
if(isset($_POST['name']) and isset($_POST['password'])){
$t= new twitter();
$t-username=$_POST['name'];
$t-password=$_POST['password'];
$res = $t-update('i am
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, we
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
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?
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()
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,
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*
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 no
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 over
The exact response is:
hash
request/statuses/friends.xml/request
errorNot found/error
/hash
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
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
11 matches
Mail list logo
