[twitter-dev] Re: What is the status of URL shortening by Twitter? (no more bit.ly)?
My reply yesterday got swallowed by Google it seems... On Jun 18, 4:58 pm, Matt Sanford m...@twitter.com wrote: Twitter disabled the automatic URL shortening if there is any slowness or other problem accessing the shortener. Thanks for the clarification! simply because a shortening service failed to respond in time. As far as bit.ly goes, they do have an API [1] for getting all of the short versions of a long URL, so you might want to give that a shot. We've I don't think they do - even on the bit.ly development group they said that they don't. Which API call would return the variants? It is odd because on the web site of bit.ly it is possible to see the variants. But they confirmed to me that they don't provide it through the API (yet). That was a couple of weeks ago, but I still can't see an API call that would do it. They seem to return all users who have shortened an URL, but since there is no way to retrieve the user-specific variant of an URL, it does not help much. Björn
[twitter-dev] oauth callback not working
I'm following the rails example for OAuth. I got to the point where the user can click authorize on twitter. However this leads to http://twitter.com/oauth/authorize with a number and Enter the following PIN when prompted... I've configured the app to be a browser app. Anything else I'm missing? Thanks!
[twitter-dev] Re: Failed to validate oauth signature or token with OAuth while updating the status
and now it works...
I guess this was an issue on twitter side...
regards
On Thu, Jun 18, 2009 at 11:25 AM, Borja Martínbor...@dagi3d.net wrote:
Hi,
I removed the in_reply_to_status_id parameter but I'm still getting the same
error...
Thanks anyway
Regards
On Wed, Jun 17, 2009 at 5:17 PM, Matt Sanford m...@twitter.com wrote:
Hi there,
You may want to checkout the issues list for the PHP library. I found
an issue there that seems to be the same:
http://github.com/jmathai/twitter-async/issues/unreads#issue/6
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 17, 2009, at 5:32 AM, Borja Martín wrote:
Hi,
I'm getting the following error while trying to update the user status
who is supposed to be authenticated through OAuth:
'Failed to validate oauth signature or token'
The thing is that this was working a few hours ago and if I try to
call the credentials verfication api method it works fine although I'm
using the same tokens:
$this-_twitter_oauth-setToken($session-oauth_access_token,
$session-oauth_acces_token_secret);
# this works
$info = $this-_twitter_oauth-get_accountVerify_credentials();
$info-response
# this doesn't
$info = $this-_twitter_oauth-post_statusesUpdate(array('status' =
$status, 'in_reply_to_status_id' = $in_reply_to_status_id));
$info-response
(I'm using the EpiTwitter/EpiOAuth php library grabbed from this post:
http://www.jaisenmathai.com/blog/2009/03/31/how-to-quickly-integrate-with-twitters-oauth-api-using-php/)
Did anyone else found this issue?
Thanks in advance
Regards
--
def dagi3d(me)
case me
when :web then http://dagi3d.net;
when :twitter then http://twitter.com/dagi3d;
end
end
--
def dagi3d(me)
case me
when :web then http://dagi3d.net;
when :twitter then http://twitter.com/dagi3d;
end
end
--
def dagi3d(me)
case me
when :web then http://dagi3d.net;
when :twitter then http://twitter.com/dagi3d;
end
end
[twitter-dev] Re: whitelist site -- horror story
I have resolved this problem by changing from GET to POST requests. 14 hours work. I am totally confused why the Get requests that were working for a month no longer work At least my application is working using POST... But I am worried about the reliability of the code I've written Not a good feeling mark
[twitter-dev] Re: OAuth and native clients
Thanks for the pointer... I did some searches, but they were all focused on mobile clients. In my case, I'm not worried about the complexity of implementing OAuth. I can deal with that, and once it's done, it's gone from the picture. It's the user experience that worries me, as exposed on that thread by the TTYtter example. Well, since people are asking, the workflow doesn't significantly differ from other OAuth applications and depends on the fact that access tokens don't expire. When people start TTYtter up for the first time without an access token (or TTYtter tries the access token and it fails), it asks for the usual request token, prints the access URL with the request token it wants the user to authorize, and waits for the user to authorize. Twitter, presumably, will say, ok, tell your program to continue. Back on TTYtter's side, the user hits ENTER, and TTYtter exchanges its request token for an access token *and caches it* once it has verified it can successfully hit the user timeline for data. So far, this is not significantly different than any other OAuth app. Is there any other way to do OAuth and at the same time, behave like a sensible application? Could Twitter implement a basic auth api call to perform the oauth authorization in the first place? Such a call would only be allowed from clients that prove they need it, and could be revoked for rogue clients. I know this lowers the security of OAuth, but it only officializes a hack many apps will try to implement. On Jun 19, 12:39 am, Cameron Kaiser spec...@floodgap.com wrote: Or is the door for basic auth really closing forever? This has been discussed in a number of threads and an exact determination has not yet been made. However, this might give you some context: http://groups.google.com/group/twitter-development-talk/browse_thread... -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- The cost of living has not adversely affected its popularity. --
[twitter-dev] Re: whitelist site -- horror story
Just a shot in the dark, but could it be caused by this?:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/f7cd82f2c43a77d0/464d0df7446d43e7
It sounds like exactly the sort of thing that could cause an app to suddenly
stop working. I see that your new code posted above contained a referer,
but what about the code that was failing? How about putting in a User-Agent
too, for good measure.
Regards,
Alan Evans
On Fri, Jun 19, 2009 at 2:50 PM, markanson mark.an...@gmail.com wrote:
Marco it was all working fine for a month or more
then today it stopped working
My new code that I got from somewhere seems ok but I don't feel really
confident about this
I am using this
function file_post_contents($url,$headers=false) {
$url = parse_url($url);
if (!isset($url['port'])) {
if ($url['scheme'] == 'http') { $url['port']=80; }
elseif ($url['scheme'] == 'https') { $url['port']=443; }
}
$url['query']=isset($url['query'])?$url['query']:'';
$url['protocol']=$url['scheme'].'://';
$eol=\r\n;
$headers = POST .$url['protocol'].$url['host'].$url['path'].
HTTP/1.0.$eol.
Host: .$url['host'].$eol.
Referer: .$url['protocol'].$url['host'].$url['path'].
$eol.
Content-Type: application/x-www-form-urlencoded.
$eol.
Content-Length: .strlen($url['query']).$eol.
$eol.$url['query'];
$fp = fsockopen($url['host'], $url['port'], $errno, $errstr, 30);
if($fp) {
fputs($fp, $headers);
$result = '';
while(!feof($fp)) { $result .= fgets($fp, 128); }
fclose($fp);
if (!$headers) {
//removes headers
$pattern=/^.*\r\n\r\n/s;
$result=preg_replace($pattern,'',$result);
}
return $result;
}
}
[twitter-dev] Re: whitelist site -- horror story
Can you include the specific request you are making?
Thanks,
Doug
On Fri, Jun 19, 2009 at 6:35 AM, Alan Evans alanev...@gmail.com wrote:
Just a shot in the dark, but could it be caused by this?:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/f7cd82f2c43a77d0/464d0df7446d43e7
It sounds like exactly the sort of thing that could cause an app to
suddenly stop working. I see that your new code posted above contained a
referer, but what about the code that was failing? How about putting in a
User-Agent too, for good measure.
Regards,
Alan Evans
On Fri, Jun 19, 2009 at 2:50 PM, markanson mark.an...@gmail.com wrote:
Marco it was all working fine for a month or more
then today it stopped working
My new code that I got from somewhere seems ok but I don't feel really
confident about this
I am using this
function file_post_contents($url,$headers=false) {
$url = parse_url($url);
if (!isset($url['port'])) {
if ($url['scheme'] == 'http') { $url['port']=80; }
elseif ($url['scheme'] == 'https') { $url['port']=443; }
}
$url['query']=isset($url['query'])?$url['query']:'';
$url['protocol']=$url['scheme'].'://';
$eol=\r\n;
$headers = POST .$url['protocol'].$url['host'].$url['path'].
HTTP/1.0.$eol.
Host: .$url['host'].$eol.
Referer: .$url['protocol'].$url['host'].$url['path'].
$eol.
Content-Type: application/x-www-form-urlencoded.
$eol.
Content-Length: .strlen($url['query']).$eol.
$eol.$url['query'];
$fp = fsockopen($url['host'], $url['port'], $errno, $errstr, 30);
if($fp) {
fputs($fp, $headers);
$result = '';
while(!feof($fp)) { $result .= fgets($fp, 128); }
fclose($fp);
if (!$headers) {
//removes headers
$pattern=/^.*\r\n\r\n/s;
$result=preg_replace($pattern,'',$result);
}
return $result;
}
}
[twitter-dev] Re: Users not being indexed by Search
We have plenty of data, now. Thanks for everyone who sent usernames my way. The fix is going to take some time as it requires rewriting algorithms so we appreciate your patience. Thanks, Doug On Thu, Jun 18, 2009 at 6:23 PM, Brooks Bennett bsbenn...@gmail.com wrote: Should we still be sending these? Any new insight on what is happening? The issue seems to have been growing over the past week where almost all of my support requests for my app are about this issue... Brooks On Jun 16, 7:59 pm, Doug Williams d...@twitter.com wrote: Chad, Let's see what light the article sheds and work from there. Send me false-positives in private so that I can share them with our scientist. Thanks, Doug On Tue, Jun 16, 2009 at 5:55 PM, Chad Etzel jazzyc...@gmail.com wrote: Thanks. Even after sending the first email, I got about 5 or 6 other complaints about the same thing. It just seems strange that so many are getting flagged... people I know, even. I know you can't divulge your algorithm, so I won't ask... -Chad On Tue, Jun 16, 2009 at 8:41 PM, Doug Williamsd...@twitter.com wrote: We exclude users from the search index if they are performing behaviors that are outside of our TOS or if they look spammy to our support staff or algorithms. The support folks are writing up an article for http://help.twitter.comto explain this policy. I'll drop the link here when that is available. Thanks, Doug -- Do you follow me?http://twitter.com/dougw On Tue, Jun 16, 2009 at 10:27 AM, Brooks Bennett bsbenn...@gmail.com wrote: I sent this to @twitterapi as well: http://twitter.com/BrooksBennett/status/2191822737 Here are some people pondering the occurrence: http://twitter.com/Sideache/statuses/2188774064 http://twitter.com/LynnMaudlin/statuses/2188727280 This has been an issue off and on for about a month, but in the last few days it has really escalated. Brooks On Jun 16, 11:29 am, Chad Etzel jazzyc...@gmail.com wrote: Hi Matt/Doug, In the last week or so, I've been getting a lot of complaints from TweetGrid users that people are not showing up in their searches. They automatically assume it's TweetGrid's fault and lob a complaint my way. I go verify that the user in question has stopped being indexed by Search and then reply to them that this is the case and that they should open a support ticket with Twitter. This is somewhat time consuming and tedious. I'm not sure how to ask for a solution to this situation. I guess I just wanted to express that people are more actively starting to notice when people do not appear in search results. I have no idea why people are being dropped from indexing (I check each account manually), but is this a very common thing to flip the admin bit to block people from search? -Chad
[twitter-dev] Re: oauth callback not working
Hi there, If you're using the OAuth gem it is automatically sending oauth_callback with a value of oob, which tells twitter to use the PIN style. By passing the oauth_callback in you can override that default. An issue [1] has been files with the gem author. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] - http://github.com/mojodna/oauth/issues#issue/7 On Jun 19, 2009, at 6:07 AM, Ryan Bigg wrote: Hi, when you do get_request_token you need to pass oauth_callback as an option (even though you set this up with your application) Ryan Bigg Mocra http://mocra.com On 19/06/2009, at 18:02, phillee philip.a@gmail.com wrote: I'm following the rails example for OAuth. I got to the point where the user can click authorize on twitter. However this leads to http://twitter.com/oauth/authorize with a number and Enter the following PIN when prompted... I've configured the app to be a browser app. Anything else I'm missing? Thanks!
[twitter-dev] Re: airline accident case study
Topics don't just trend because its something 'important'. Now if it was of significantly larger volume than another topics (like the iphone's launch today), then that is rather interesting, but from what I can tell its mostly the most popular things floating to the top generally, plus some spam-filtering. I haven't figured out the exacting mechanisim for when something hits trending, but its not rocket science either. Maybe I'm missing your point -...@tibbon On Jun 19, 2:35 am, Bjoern bjoer...@googlemail.com wrote: On Jun 19, 7:00 am, AJ cano...@gmail.com wrote: This case study shows the difference between various trending applications. A good real time semantic analysis is the key that makes the difference, I think. Maybe I misunderstood, but isn't the more likely explanation that the topic simply wasn't trending? Björn
