Re: [twitter-dev] People randomly getting unfollowed?
I don't think it is 'random'. It most likely is removal of robot accounts. Some script / human is identifying such spam accounts / fake accounts and suspending them. Many people are getting frustrated by this, to see their followers number reduce. ~*~ On Sat, Aug 14, 2010 at 11:22 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I don't think this has happened to me, but a number of my friends and some well-known Twitter people have reported that Twitter is unfollowing people from their accounts on its own, apparently in some random fashion. I don't have any more detail than that, or I'd file an issue. But I've heard it from so many people that I wanted to bring it up here and see if this triggers any thoughts in the developer community or at Twitter. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
Re: [twitter-dev] People randomly getting unfollowed?
That's not the symptom people are describing to me. It goes something like this: Bob follows Carol. At a later date, Carol says, Bob, when did you unfollow me? Did I piss you off or something? Bob says, But I didn't unfollow you. He then checks and sees that he is in fact no longer following Carol, and has to re-follow her. I have too many friends saying this has happened for it to be a hallucination. The only thing I can recommend to them is to go into the Connections settings panel and revoke all the oAuth approvals and see if it stops happening. I think if we got a list of all the people who've had unfollows like this and cross-checked their oAuth approvals, we might find an app that's not being nice. That's the only mechanism I can think of that would do this. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting S esg...@gmail.com: I don't think it is 'random'. It most likely is removal of robot accounts. Some script / human is identifying such spam accounts / fake accounts and suspending them. Many people are getting frustrated by this, to see their followers number reduce. ~*~ On Sat, Aug 14, 2010 at 11:22 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I don't think this has happened to me, but a number of my friends and some well-known Twitter people have reported that Twitter is unfollowing people from their accounts on its own, apparently in some random fashion. I don't have any more detail than that, or I'd file an issue. But I've heard it from so many people that I wanted to bring it up here and see if this triggers any thoughts in the developer community or at Twitter. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
Re: [twitter-dev] People randomly getting unfollowed?
FWIW, I've heard several people say that the 'who to follow' feature exposed people to them that they thought they were already following. /damon -- http://twitter.com/damon http://blog.damonc.com On Sat, Aug 14, 2010 at 2:12 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: That's not the symptom people are describing to me. It goes something like this: Bob follows Carol. At a later date, Carol says, Bob, when did you unfollow me? Did I piss you off or something? Bob says, But I didn't unfollow you. He then checks and sees that he is in fact no longer following Carol, and has to re-follow her. I have too many friends saying this has happened for it to be a hallucination. The only thing I can recommend to them is to go into the Connections settings panel and revoke all the oAuth approvals and see if it stops happening. I think if we got a list of all the people who've had unfollows like this and cross-checked their oAuth approvals, we might find an app that's not being nice. That's the only mechanism I can think of that would do this. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting S esg...@gmail.com: I don't think it is 'random'. It most likely is removal of robot accounts. Some script / human is identifying such spam accounts / fake accounts and suspending them. Many people are getting frustrated by this, to see their followers number reduce. ~*~ On Sat, Aug 14, 2010 at 11:22 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I don't think this has happened to me, but a number of my friends and some well-known Twitter people have reported that Twitter is unfollowing people from their accounts on its own, apparently in some random fashion. I don't have any more detail than that, or I'd file an issue. But I've heard it from so many people that I wanted to bring it up here and see if this triggers any thoughts in the developer community or at Twitter. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
[twitter-dev] Re: Send Custom Header
thanks all
[twitter-dev] Re: People randomly getting unfollowed?
I have noticed this as well. But I thought I was that uninteresting since I do not tweet regularly enough for some to justify their following me. Thanks for bringing this to light. On Aug 14, 8:57 am, Damon Clinkscales sca...@pobox.com wrote: FWIW, I've heard several people say that the 'who to follow' feature exposed people to them that they thought they were already following. /damon --http://twitter.com/damonhttp://blog.damonc.com On Sat, Aug 14, 2010 at 2:12 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: That's not the symptom people are describing to me. It goes something like this: Bob follows Carol. At a later date, Carol says, Bob, when did you unfollow me? Did I piss you off or something? Bob says, But I didn't unfollow you. He then checks and sees that he is in fact no longer following Carol, and has to re-follow her. I have too many friends saying this has happened for it to be a hallucination. The only thing I can recommend to them is to go into the Connections settings panel and revoke all the oAuth approvals and see if it stops happening. I think if we got a list of all the people who've had unfollows like this and cross-checked their oAuth approvals, we might find an app that's not being nice. That's the only mechanism I can think of that would do this. -- M. Edward (Ed) Borasky http://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting S esg...@gmail.com: I don't think it is 'random'. It most likely is removal of robot accounts. Some script / human is identifying such spam accounts / fake accounts and suspending them. Many people are getting frustrated by this, to see their followers number reduce. ~*~ On Sat, Aug 14, 2010 at 11:22 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I don't think this has happened to me, but a number of my friends and some well-known Twitter people have reported that Twitter is unfollowing people from their accounts on its own, apparently in some random fashion. I don't have any more detail than that, or I'd file an issue. But I've heard it from so many people that I wanted to bring it up here and see if this triggers any thoughts in the developer community or at Twitter. -- M. Edward (Ed) Borasky http://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
[twitter-dev] Re: Questions on user_timeline entities
I think I may answered some of the questions myself. 1. No. 2. Yes. 3. On user_mentions: - @replies are not mentions. So answer is, just @abc. - This one is complex. I still need an answer. - At the time of Tweet creation. Please confirm. Thanks, Sud On Sat, Aug 14, 2010 at 1:10 PM, Sud twitz...@gmail.com wrote: Can someone answer these? 1. *urls:* Are they expanded? 2. *hashtag:* Is #thisahashtag? I think so. 3. *user_mentions: * - Is @replyto a mention? So would @replyto @abc imply two mentions or just @abc? - What about this Tweet: RT @abc blah blah @abc_mention blah blah (nice, cc @my_mention) - Is screen_name the screen_name at the time of Tweet creation or at the time of Tweet access? (this applies in general) Thanks, Sud
[twitter-dev] Help with xAuth and PHP
Hi,
I have been unable to get the access token for xAuth. I've been
granted xAuth but now I need to use it, so that's why I'm requesting
your help.
This is the output I'm getting:
HTTP/1.1 401 Unauthorized Date: Fri, 13 Aug 2010 17:34:58 GMT Server:
hi Status:
401 Unauthorized X-Transaction: 1281720898-35403-17857 Last-Modified:
Fri, 13
Aug 2010 17:34:58 GMT X-Runtime: 0.00533 Content-Type: text/html;
charset=utf-8
Content-Length: 1 Pragma: no-cache X-Revision: DEV Expires: Tue, 31
Mar 1981
05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-
check=0,
post-check=0 Set-Cookie: k=85.49.242.96.1281720898265953; path=/;
expires=Fri,
20-Aug-10 17:34:58 GMT; domain=.twitter.com Set-Cookie:
guest_id=128172089870928288; path=/; expires=Sun, 12 Sep 2010 17:34:58
GMT
Set-Cookie:
_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJfUhGwqAToHaWQiJTRlMzA4NDJlZGMwZDc3%250AMGRhMDY1MjFlODlkNTI2ZjBmIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--3a67a3c1703e00892ec25ae058be95a4476ecb61;
domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close
Can you help me find out what's wrong with this simple example?
Thank!
Regards,
Herman.
Here is my code in PHP 5. It generates an output file (output.html) so
you'll be able to check every step in there.
Just change 4 things: user, password, consumer key and consumer secret
to run it.
?php
/**
* Test based in http://dev.twitter.com/pages/xauth
* Herman Gomez C. - herman_inter...@yahoo.es
* Madrid, 13-Aug-2010.
*/
unlink('output.html');
/**
* Encode a string according to the RFC3986
*/
function urlencode2($s) {
return ($s === false ? $s : str_replace('%7E','~',rawurlencode($s)));
}
/**
* Create sequences like param1=encodevalue1param2=value2 and so on,
where
values are urlrawencoded.
* It's used for post body and signature base.
*/
function encode_params($params) {
$res = '';
foreach($params as $index = $value) $res = $res . $index . '=' .
urlencode2($value) . '';
return substr($res,0,strlen($res)-1);
}
/**
* Create sequences like param1=value1, param2=value2 and so on.
It's used
for oAuth header.
*/
function enquote_params($params) {
$res = '';
foreach($params as $index = $value) $res = $res . $index . '=' .
urlencode2($value) . ', ';
return substr($res,0,strlen($res)-2);
}
/**
* debug var
*/
function debug_var($name,$var) {
$output = b$name/bbrpre . print_r($var,true) . /pre\n\n
\n; echo
$output;
file_put_contents('output.html',$output,FILE_APPEND);
}
/**
* Creating post body
*/
$x_auth_params = array();
$x_auth_params['x_auth_password'] = password; //change this
$x_auth_params['x_auth_username'] = username; //change this
$x_auth_params['x_auth_mode'] = client_auth;
ksort($x_auth_params);
$post_body = encode_params($x_auth_params);
debug_var('post_body',$post_body);
/***
* Creating signature base
*/
$url = https://api.twitter.com/oauth/access_token;;
$url_encoded = urlencode2($url);
$oauth_params = array();
$oauth_params['oauth_consumer_key'] = consumer key; ///change this
$oauth_params['oauth_nonce'] = md5(uniqid(rand(), true));
$oauth_params['oauth_timestamp'] = time();
$oauth_params['oauth_signature_method'] = HMAC-SHA1;
$oauth_params['oauth_version'] = 1.0;
ksort($oauth_params);
$params_encoded = urlencode2(encode_params($oauth_params) . '' .
$post_body);
$signature_base = POST$url_encoded$params_encoded;
debug_var('signature_base',$signature_base);
/**
* Creating signature
*/
$oauth_params['oauth_consumer_secret'] = consumer secret; //change
this
$key = $oauth_params['oauth_consumer_secret'] . '';
$oauth_params['oauth_signature'] =
urlencode2(base64_encode(hash_hmac(sha1,$signature_base,
$key,true)));
/**
* Creating OAuth header
*/
ksort($oauth_params);
$oauth_header = 'OAuth ' . enquote_params($oauth_params);
debug_var('oauth_header',$oauth_header);
$ch = curl_init();
curl_setopt($ch, CURLOPT_HEADER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, array($oauth_header));
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, urlencode2($post_body));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
$exec = curl_exec($ch);
$info = curl_getinfo($ch);
curl_close($ch);
debug_var('info',$info);
debug_var('exec',$exec);
?
[twitter-dev] Questions on user_timeline entities
Can someone answer these? 1. *urls:* Are they expanded? 2. *hashtag:* Is #thisahashtag? I think so. 3. *user_mentions: * - Is @replyto a mention? So would @replyto @abc imply two mentions or just @abc? - What about this Tweet: RT @abc blah blah @abc_mention blah blah (nice, cc @my_mention) - Is screen_name the screen_name at the time of Tweet creation or at the time of Tweet access? (this applies in general) Thanks, Sud
Re: [twitter-dev] Help with xAuth and PHP
Hi,
I've seen several things:
1. I *think* that your URL encode function is slightly wrong - this is
what my PHP OAuth site has :
return str_replace(
'+',
' ',
str_replace('%7E', '~', rawurlencode($input))
);
2. You seem to be lucky that the sort order is right, but your code is
wrong. $params_encoded = urlencode2(encode_params($oauth_params) . ''
. $post_body); is not the correct way - all fields are supposed to be
sorted, not only oauth_params. The Base String itself seems fine.
3. After some testing, I couldn't find anything else wrong. However,
when I looked again, I saw that you were posting the consumer secret in
the OAuth header. You MUST NOT do that. ;-)
4. You aren't sending an Authorization header.
5. You are sending $post_body urlencoded as postfields.
Tom
On 8/14/10 10:54 AM, hgc2002 wrote:
Hi,
I have been unable to get the access token for xAuth. I've been
granted xAuth but now I need to use it, so that's why I'm requesting
your help.
This is the output I'm getting:
HTTP/1.1 401 Unauthorized Date: Fri, 13 Aug 2010 17:34:58 GMT Server:
hi Status:
401 Unauthorized X-Transaction: 1281720898-35403-17857 Last-Modified:
Fri, 13
Aug 2010 17:34:58 GMT X-Runtime: 0.00533 Content-Type: text/html;
charset=utf-8
Content-Length: 1 Pragma: no-cache X-Revision: DEV Expires: Tue, 31
Mar 1981
05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-
check=0,
post-check=0 Set-Cookie: k=85.49.242.96.1281720898265953; path=/;
expires=Fri,
20-Aug-10 17:34:58 GMT; domain=.twitter.com Set-Cookie:
guest_id=128172089870928288; path=/; expires=Sun, 12 Sep 2010 17:34:58
GMT
Set-Cookie:
_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJfUhGwqAToHaWQiJTRlMzA4NDJlZGMwZDc3%250AMGRhMDY1MjFlODlkNTI2ZjBmIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--3a67a3c1703e00892ec25ae058be95a4476ecb61;
domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close
Can you help me find out what's wrong with this simple example?
Thank!
Regards,
Herman.
Here is my code in PHP 5. It generates an output file (output.html) so
you'll be able to check every step in there.
Just change 4 things: user, password, consumer key and consumer secret
to run it.
?php
/**
* Test based in http://dev.twitter.com/pages/xauth
* Herman Gomez C. - herman_inter...@yahoo.es
* Madrid, 13-Aug-2010.
*/
unlink('output.html');
/**
* Encode a string according to the RFC3986
*/
function urlencode2($s) {
return ($s === false ? $s : str_replace('%7E','~',rawurlencode($s)));
}
/**
* Create sequences like param1=encodevalue1param2=value2 and so on,
where
values are urlrawencoded.
* It's used for post body and signature base.
*/
function encode_params($params) {
$res = '';
foreach($params as $index = $value) $res = $res . $index . '=' .
urlencode2($value) . '';
return substr($res,0,strlen($res)-1);
}
/**
* Create sequences like param1=value1, param2=value2 and so on.
It's used
for oAuth header.
*/
function enquote_params($params) {
$res = '';
foreach($params as $index = $value) $res = $res . $index . '=' .
urlencode2($value) . ', ';
return substr($res,0,strlen($res)-2);
}
/**
* debug var
*/
function debug_var($name,$var) {
$output = b$name/bbrpre . print_r($var,true) . /pre\n\n
\n; echo
$output;
file_put_contents('output.html',$output,FILE_APPEND);
}
/**
* Creating post body
*/
$x_auth_params = array();
$x_auth_params['x_auth_password'] = password; //change this
$x_auth_params['x_auth_username'] = username; //change this
$x_auth_params['x_auth_mode'] = client_auth;
ksort($x_auth_params);
$post_body = encode_params($x_auth_params);
debug_var('post_body',$post_body);
/***
* Creating signature base
*/
$url = https://api.twitter.com/oauth/access_token;;
$url_encoded = urlencode2($url);
$oauth_params = array();
$oauth_params['oauth_consumer_key'] = consumer key; ///change this
$oauth_params['oauth_nonce'] = md5(uniqid(rand(), true));
$oauth_params['oauth_timestamp'] = time();
$oauth_params['oauth_signature_method'] = HMAC-SHA1;
$oauth_params['oauth_version'] = 1.0;
ksort($oauth_params);
$params_encoded = urlencode2(encode_params($oauth_params) . '' .
$post_body);
$signature_base = POST$url_encoded$params_encoded;
debug_var('signature_base',$signature_base);
/**
* Creating signature
*/
$oauth_params['oauth_consumer_secret'] = consumer secret; //change
this
$key = $oauth_params['oauth_consumer_secret'] . '';
$oauth_params['oauth_signature'] =
urlencode2(base64_encode(hash_hmac(sha1,$signature_base,
$key,true)));
/**
* Creating OAuth header
*/
ksort($oauth_params);
$oauth_header = 'OAuth ' . enquote_params($oauth_params);
debug_var('oauth_header',$oauth_header);
$ch = curl_init();
curl_setopt($ch, CURLOPT_HEADER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, array($oauth_header));
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch,
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume and freedom of speech
If they can't get to Twitter even once, then the point of the original argument is lost as they need to set up a Twitter account in the first place. Perhaps the OP should obtain permission from Twitter to create accounts for persons affected by censorship and then facilitate their access through his app. On Aug 14, 6:20 pm, Tom van der Woerdt i...@tvdw.eu wrote: Simple answer: because people in china can't even get to twitter.com *once*. Tom On 8/14/10 4:37 PM, Ken wrote: Why is this an issue? A few months ago, someone from Twitter I believe suggested a pattern such as this: User starts to create an account on your site To enable the Twitter integration, you send them to Twitter.com *once* where they allow your app. You store their token and log the user in to your site with a temporary password you generate, that they can change. You might collect their email address this way. From then on, they never have to go to Twitter.com. They can interact with Twitter via your app, using your website, email, sms, etc. Of course, with the massive use of your site that you claim, it won't be long before your site is listed by Websense and the various evil governments mentioned above. On Aug 14, 1:04 am, TheGuru jsort...@gmail.com wrote: Is there no one from Twitter proper who has a position regarding this? On Aug 13, 2:12 pm, TheGuru jsort...@gmail.com wrote: Add that to the list of even more reasons why this is an issue. However, even stating oh well, tell them to use their cell phones, obviously isn't a solution of any degree. Smart Phone penetration in the US, for example, is still less than 20%... On Aug 13, 9:43 am, earth2marsh ma...@earth2marsh.com wrote: At least people at work have the potential to use phones to access Twitter I'm worried about users like those in China behind The Great Firewall. Currently, they can interact with Twitter by using proxies and http basic auth. But OAuth requires access to twitter.com (or some sort of mediation). xAuth could be a solution, but there is already a shortage of clients that support alternate endpoints, and some of those use OAuth instead of xAuth (or neither). When basic auth is shut off, who knows how many Chinese voices will fall silent or in North Korea. Or in Iran. Or in ? I'm interested in hearing what others think about this. Marsh On Aug 12, 10:31 pm, TheGuru jsort...@gmail.com wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access.
Re: [twitter-dev] Twitter 140 character limit break
On 8/14/10 9:27 PM, Chris White wrote: It appears that the new twitter share link can be used to break the 140 character limit. Basically in Firefox you can do this: 1) In the URL bar enter http://twitter.com/share?url=Some over 140 character text 2) Hit enter 3) On the page resulting page click Tweet 4) View in web and notice the limit broken I'm not sure if clients can handle this, but it could turn into a pretty nasty annoyance for users of web if it continues. Might be a good idea to have it looked at. I'm assuming a simple check to verify it's a valid URL would suffice. Just tested it - yes, you are right. How clients handle it? Well, very simple, they simply display a t.co URL. Should be some more checks on the URL though, I agree. Tom
Re: [twitter-dev] Twitter 140 character limit break
On 8/14/10 9:29 PM, Tom van der Woerdt wrote: On 8/14/10 9:27 PM, Chris White wrote: It appears that the new twitter share link can be used to break the 140 character limit. Basically in Firefox you can do this: 1) In the URL bar enter http://twitter.com/share?url=Some over 140 character text 2) Hit enter 3) On the page resulting page click Tweet 4) View in web and notice the limit broken I'm not sure if clients can handle this, but it could turn into a pretty nasty annoyance for users of web if it continues. Might be a good idea to have it looked at. I'm assuming a simple check to verify it's a valid URL would suffice. Just tested it - yes, you are right. How clients handle it? Well, very simple, they simply display a t.co URL. Should be some more checks on the URL though, I agree. Tom One more note, You can't visit a page that has a long link on it. @barthoekstra and I (@tvdw) just tested this - I posted 5 paragraphs of the well-known lorem ipsum (don't worry, deleted after a few seconds) but his timeline started saying Something is technically wrong. I removed my tweet and it was fine again. He then posted an url as well but now he can't remove it anymore. I am assuming that all his ~1500 followers can't use the timeline anymore at the moment. Proof: http://twitter.com/barthoekstra Tom
Re: [twitter-dev] Twitter 140 character limit break
Yay! Robots! Genuine bug and not a scaling issue. Zac On Aug 14, 2010, at 12:43 PM, Tom van der Woerdt wrote: On 8/14/10 9:29 PM, Tom van der Woerdt wrote: On 8/14/10 9:27 PM, Chris White wrote: It appears that the new twitter share link can be used to break the 140 character limit. Basically in Firefox you can do this: 1) In the URL bar enter http://twitter.com/share?url=Some over 140 character text 2) Hit enter 3) On the page resulting page click Tweet 4) View in web and notice the limit broken I'm not sure if clients can handle this, but it could turn into a pretty nasty annoyance for users of web if it continues. Might be a good idea to have it looked at. I'm assuming a simple check to verify it's a valid URL would suffice. Just tested it - yes, you are right. How clients handle it? Well, very simple, they simply display a t.co URL. Should be some more checks on the URL though, I agree. Tom One more note, You can't visit a page that has a long link on it. @barthoekstra and I (@tvdw) just tested this - I posted 5 paragraphs of the well-known lorem ipsum (don't worry, deleted after a few seconds) but his timeline started saying Something is technically wrong. I removed my tweet and it was fine again. He then posted an url as well but now he can't remove it anymore. I am assuming that all his ~1500 followers can't use the timeline anymore at the moment. Proof: http://twitter.com/barthoekstra Tom
Re: [twitter-dev] Twitter 140 character limit break
I filed a bug with our webclient team. Thanks for finding this. -john On Sat, Aug 14, 2010 at 12:43 PM, Tom van der Woerdt i...@tvdw.eu wrote: On 8/14/10 9:29 PM, Tom van der Woerdt wrote: On 8/14/10 9:27 PM, Chris White wrote: It appears that the new twitter share link can be used to break the 140 character limit. Basically in Firefox you can do this: 1) In the URL bar enter http://twitter.com/share?url=Some over 140 character text 2) Hit enter 3) On the page resulting page click Tweet 4) View in web and notice the limit broken I'm not sure if clients can handle this, but it could turn into a pretty nasty annoyance for users of web if it continues. Might be a good idea to have it looked at. I'm assuming a simple check to verify it's a valid URL would suffice. Just tested it - yes, you are right. How clients handle it? Well, very simple, they simply display a t.coURL. Should be some more checks on the URL though, I agree. Tom One more note, You can't visit a page that has a long link on it. @barthoekstra and I (@tvdw) just tested this - I posted 5 paragraphs of the well-known lorem ipsum (don't worry, deleted after a few seconds) but his timeline started saying Something is technically wrong. I removed my tweet and it was fine again. He then posted an url as well but now he can't remove it anymore. I am assuming that all his ~1500 followers can't use the timeline anymore at the moment. Proof: http://twitter.com/barthoekstra Tom
[twitter-dev] Return Public Timeline Tweets based on Geo Location
I've searched for a solution, but couldn't find one. I'm looking for a way that I can feed in a GeoLocation (Lat,Long) and get the latest x tweets posted from around that area. statuses/public_timeline doesn't support GeoLocation. I looked at search, which can limit the returned amount by GeoLocation, however, it requires a query search string, which I don't have. Any help or friendly point in the right direction is appreciated... Thanks. Mark
Re: [twitter-dev] Re: Introducing the Tweet Button
On Fri, Aug 13, 2010 at 4:06 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: We had some caching/rate limiting issues related to tweet counts for a portion of yesterday but these should be relieved now. Please let us know if you continue seeing the zero counts after a reasonable amount of time (they won't update instantaneously). I feel like still having the issue at http://tweetsell.it/users/wineheadlines/products/21170418193 (for example). It's also very disturbing to have the counter incrementing when tweeting about the link, then going back to 0 when you reload the page. Will you try to update this instantaneously later?
Re: [twitter-dev] Return Public Timeline Tweets based on Geo Location
On 8/14/10 11:20 PM, Mark W wrote: I've searched for a solution, but couldn't find one. I'm looking for a way that I can feed in a GeoLocation (Lat,Long) and get the latest x tweets posted from around that area. statuses/public_timeline doesn't support GeoLocation. I looked at search, which can limit the returned amount by GeoLocation, however, it requires a query search string, which I don't have. Any help or friendly point in the right direction is appreciated... Thanks. Mark The streams function of twitter can do this. http://dev.twitter.com/doc/post/statuses/filter Tom
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume and freedom of speech
You're failing to see the point. In the past, with basic auth, there was no need to create any sort of account from the third party app side. No need for a database, local accounts, nothing. A user could login as this wish, without issue, regardless as to whether or not they need to access the Twitter.com domain, ever. Removing this login method changes the entire flow, adds requirements for third party apps to now maintain their own, potentially, local database user accounts, etc, and still requires the user to access, even once, twitter.com. It just doesn't flow to say, hey, when you're home, do this, then come back later. Sure it may work, it's just not eloquent, and has a negative impact on any existing userbase. BTW, for your reference, yes, we have already been web sensed in many cases anyway for many users at their location. Of course, just so my claim rings true with you, please reference the following link, and I'll let you figure out which application applies: http://www.google.com/ig/directory?q=twitter (Note: that's installed userbase for iGoogle only, doesn't count gmail, standalone, wave, etc, that'd take it closer to 1,000,000). On Aug 14, 9:37 am, Ken k...@cimas.ch wrote: Why is this an issue? A few months ago, someone from Twitter I believe suggested a pattern such as this: User starts to create an account on your site To enable the Twitter integration, you send them to Twitter.com *once* where they allow your app. You store their token and log the user in to your site with a temporary password you generate, that they can change. You might collect their email address this way. From then on, they never have to go to Twitter.com. They can interact with Twitter via your app, using your website, email, sms, etc. Of course, with the massive use of your site that you claim, it won't be long before your site is listed by Websense and the various evil governments mentioned above. On Aug 14, 1:04 am, TheGuru jsort...@gmail.com wrote: Is there no one from Twitter proper who has a position regarding this? On Aug 13, 2:12 pm, TheGuru jsort...@gmail.com wrote: Add that to the list of even more reasons why this is an issue. However, even stating oh well, tell them to use their cell phones, obviously isn't a solution of any degree. Smart Phone penetration in the US, for example, is still less than 20%... On Aug 13, 9:43 am, earth2marsh ma...@earth2marsh.com wrote: At least people at work have the potential to use phones to access Twitter… I'm worried about users like those in China behind The Great Firewall. Currently, they can interact with Twitter by using proxies and http basic auth. But OAuth requires access to twitter.com (or some sort of mediation). xAuth could be a solution, but there is already a shortage of clients that support alternate endpoints, and some of those use OAuth instead of xAuth (or neither). When basic auth is shut off, who knows how many Chinese voices will fall silent… or in North Korea. Or in Iran. Or in …? I'm interested in hearing what others think about this. Marsh On Aug 12, 10:31 pm, TheGuru jsort...@gmail.com wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access.
