Re: favorited value is null in JSON
Very sorry to hear that this issue is causing so many problems. It's not an intentional change, and not one that I believe was introduced inadvertently along with another API-related change. I'll check with my colleagues first thing tomorrow to see where this unexpected behavior could be coming from. On Sun, Dec 7, 2008 at 19:50, Kazuho Okui [EMAIL PROTECTED] wrote: I have received the null value of favorited statuses more frequently today. Thousands of my app users have been struggling for these days. (I guess several other iPhone clients also crash when they receive the null values.) I submitted the new version of my app to AppStore 4 days ago but I guess it will take for another few days to get an approval. If you could address the things on the server side, it would help my users very much. Regards, Kazuho On Thu, Dec 4, 2008 at 10:32 PM, Alex Payne [EMAIL PROTECTED] wrote: Thanks much! On Thu, Dec 4, 2008 at 22:12, Kazuho Okui [EMAIL PROTECTED] wrote: I attached another example which is a result of curl. it contains a request/response headers and a JSON content. I hope this will help to find the issue. Thanks, Kazuho On Thu, Dec 4, 2008 at 1:21 PM, Kazuho Okui [EMAIL PROTECTED] wrote: Hello Alex, I attached JSON objects which my app users gave me. Thus, I don't have any request header, but the request is http://twitter.com/statuses/friends_timeline.json; with auth header. The JSON objects contains favorited:null instead of favorited:true or false randomly. Thanks, Kazuho -- Forwarded message -- From: Alex Payne [EMAIL PROTECTED] Date: Thu, Dec 4, 2008 at 12:11 PM Subject: Re: favorited value is null in JSON To: twitter-development-talk@googlegroups.com If you could please provide example request/response output that would help us track this down. Apologies for the inconsistency. On Wed, Dec 3, 2008 at 17:28, Kazuho Okui [EMAIL PROTECTED] wrote: Today, I suddenly received a JSON value which favorited value is null instead of bool. http://code.google.com/p/twitter-api/issues/detail?id=179 This crushes my Twitter client because it assumed that the value is boolean. The application is written in Objective-C, so the value type is very important for my client. The favorited value was null or true until October, then true or false until today. Could you please define exactly the type of favorite value?? Also, could you use boolean to all favorited status? Thanks, Kazuho -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Search API Rate Limiting
Ah, gotcha! You can, it will just display a browser warning. Which is not what you want :P The Terms say: We do not rate limit the search API under ordinary circumstances, however we have put measures in place to limit the abuse of our API. Try emailing, Alex Payne, or someone at Twitter about a whitelist. On Dec 7, 3:36 pm, Chad Etzel [EMAIL PROTECTED] wrote: No, you can't do an ajax authenticated GET or POST to a 3rd-party site. I am dynamically loading the json in the clients' browser. I would rather know the rate limits so I can abide by them. -Chad On Sun, Dec 7, 2008 at 10:42 AM, fastest963 [EMAIL PROTECTED] wrote: Since your doing this via AJAX and such, this may not be a good idea, but you could try passing a login to Twitter and having that login whitelisted?
Re: Problems with updating profile image
Thanks Alex. I used curl to see what the request should look like and then coded up my request accordingly. It's working for me now. On Dec 6, 11:37 am, Alex Payne [EMAIL PROTECTED] wrote: The test we use for this method is to use curl: curl -F '[EMAIL PROTECTED]/to/test/image.jpg' -u USERNAME:PASSWORDhttp://twitter.com/account/update_profile_image.xml If you use an HTTP proxy, you can see it generating the appropriate request and response. On Sat, Dec 6, 2008 at 00:09, Lien Tran [EMAIL PROTECTED] wrote: Hello, I've been trying to update myprofileimageusing the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying to upload is a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
friends If-Modified-Since and since not working
If-Modified-Since and the 'since' parameter are working great for friends_timeline, but I'm not having any luck with friends. If some one could point out what I'm doing wrong I would greatly appreciate it. Otherwise I will file a defect. ]$ curl -v --header If-Modified-Since: Mon, 08 Dec 2008 03:09:02 GMT -u [EMAIL PROTECTED]:password http://twitter.com/statuses/ friends/xtoddx.xml * About to connect() to twitter.com port 80 (#0) * Trying 128.121.146.100... connected * Connected to twitter.com (128.121.146.100) port 80 (#0) * Server auth using Basic with user '[EMAIL PROTECTED]' GET /statuses/friends/xtoddx.xml HTTP/1.1 Authorization: Basic X User-Agent: curl/7.18.1 (i386-apple-darwin9.3.0) libcurl/7.18.1 zlib/1.2.3 Host: twitter.com Accept: */* If-Modified-Since: Mon, 08 Dec 2008 03:09:02 GMT HTTP/1.1 200 OK Date: Mon, 08 Dec 2008 03:51:04 GMT Server: hi Last-Modified: Mon, 08 Dec 2008 03:51:05 GMT Status: 200 OK ETag: ceee3de5360bc61465e5e962d0927a2b Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 29571 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: lang=en; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: _twitter_sess=BAh7CDoJdXNlcmkENMwLAToHaWQiJTNiZTYyODg0NGJmMjdkNGY5NTJhN2Fl %250ANTQ2M2JiMzNlIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6%250ARmxhc2hIYXNoewAGOgpAdXNlZHsA--9836ed4e7b32f178091290c44d55908ca034d686; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? users type=array user id14209639/id nameLutherand/name screen_nameLutherand/screen_name locationLexington, Kentucky, USA/location descriptionDirector of Technology at Blood-Horse Publications/ description profile_image_urlhttp://s3.amazonaws.com/twitter_production/ profile_images/52605597/me_normal.jpg/profile_image_url url/url protectedfalse/protected followers_count74/followers_count status created_atMon Dec 08 00:25:47 + 2008/created_at id1044183586/id textEating at Gatti Town with the Fam/text sourcelt;a href=quot;http://www.kosertech.com/ quot;gt;ceTwitlt;/agt;/source truncatedfalse/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/in_reply_to_user_id favoritedfalse/favorited /status /user . [plenty more friends that were not added in the last hour]
Re: Search API Rate Limiting
The Terms say: We do not rate limit the search API under ordinary circumstances, however we have put measures in place to limit the abuse of our API. ...yes, which is exactly why I am asking the question in the first place. My code already handles the error case so no browser warnings are popped. I addressed the question to Matt originally since I thought he was the Search API guru, or am I mistaken? -Chad On Mon, Dec 8, 2008 at 10:23 AM, fastest963 [EMAIL PROTECTED] wrote: Ah, gotcha! You can, it will just display a browser warning. Which is not what you want :P The Terms say: We do not rate limit the search API under ordinary circumstances, however we have put measures in place to limit the abuse of our API. Try emailing, Alex Payne, or someone at Twitter about a whitelist. On Dec 7, 3:36 pm, Chad Etzel [EMAIL PROTECTED] wrote: No, you can't do an ajax authenticated GET or POST to a 3rd-party site. I am dynamically loading the json in the clients' browser. I would rather know the rate limits so I can abide by them. -Chad On Sun, Dec 7, 2008 at 10:42 AM, fastest963 [EMAIL PROTECTED] wrote: Since your doing this via AJAX and such, this may not be a good idea, but you could try passing a login to Twitter and having that login whitelisted?
Re: changes to search API?
Hi Alex, As I re-read this and think back to last week I may know the cause. Are you by chance still using summize.com? As part of our move to the Twitter data center we changed the logic of summize.com to redirect to search.twitter.com rather than handle requests to /search. If this is the case please change the host name and everything should work fine. Thanks; — Matt Sanford (@mzsanford) On Dec 8, 2008, at 07:17 AM, Alex wrote: We noticed that around midnight 00:00 GMT on Saturday we started getting 301 redirects for our search queries. Responses such as: htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://search.twitter.com/ search.json?q=junkamp;since_id=1034606772amp;rpp=20here/a./p /body/html Have there been changes to the Twitter Search API?
Re: a simple workaround for lack of OAuth
It won't be available for testing this week, but should be available before the end of the month. I'd definitely encourage you not to launch on it, though, as it will be a beta. On Mon, Dec 8, 2008 at 08:16, Richie [EMAIL PROTECTED] wrote: Hi Alex, do you have any updates on when OAuth is available? Currently I'm doing the finishing touches on a new service and would love to let the users choose OAuth for authentication instead of requiere them to give me their secret pw. I'm experienced in using OAuth so I expect to get it working in a couple of hours. Do you think Twitter will enable OAuth this week or should I start my service with user/pw-authentication first? Richard On Nov 27, 12:38 am, Alex Payne [EMAIL PROTECTED] wrote: As I don't know the entire schedule of our UX team, I can't. I would say less than a month and closer to a week by far, but please don't hold me to that. On Wed, Nov 26, 2008 at 15:41, Amir Michail [EMAIL PROTECTED] wrote: On Nov 24, 5:05 pm, Alex Payne [EMAIL PROTECTED] wrote: We're currently waiting on our User Experience team to put the final touches on a BETA release of ourOAuthsupport. It's going to have bugs, to be sure, but we should have it out there soon. Could you give us a time estimate? In a week? A month? Amir On Mon, Nov 24, 2008 at 12:53, Stut [EMAIL PROTECTED] wrote: On 24 Nov 2008, at 15:13, fastest963 wrote: A better alternative would be to just create an API key for every user. Instead of entering username/password, they would enter their secret API key? This is far less secure thanOAuthand is actually not much better than requiring a username and password. One of the core benefits ofOAuthis the ability to be very specific regarding what each authorised application is allowed to do, on a per application basis. It also allows you to selectively revoke the permissions of any specific application without needing to ask or even tell the application about it. To do this with the API key system you effectively need to re-authorise every app you use when you want to block just one of them. No real difference between this and having to change your password. I would much prefer that the guys (and gals) at Twitter concentrate on gettingOAuthproperly implemented (which is harder than it sounds) than their attention gets diverted by developers too impatient to wait for the right solution to the problem. -Stut -- http://stut.net/ -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Search API Rate Limiting
Matt is the Search API guru, indeed. On Mon, Dec 8, 2008 at 08:16, Chad Etzel [EMAIL PROTECTED] wrote: The Terms say: We do not rate limit the search API under ordinary circumstances, however we have put measures in place to limit the abuse of our API. ...yes, which is exactly why I am asking the question in the first place. My code already handles the error case so no browser warnings are popped. I addressed the question to Matt originally since I thought he was the Search API guru, or am I mistaken? -Chad On Mon, Dec 8, 2008 at 10:23 AM, fastest963 [EMAIL PROTECTED] wrote: Ah, gotcha! You can, it will just display a browser warning. Which is not what you want :P The Terms say: We do not rate limit the search API under ordinary circumstances, however we have put measures in place to limit the abuse of our API. Try emailing, Alex Payne, or someone at Twitter about a whitelist. On Dec 7, 3:36 pm, Chad Etzel [EMAIL PROTECTED] wrote: No, you can't do an ajax authenticated GET or POST to a 3rd-party site. I am dynamically loading the json in the clients' browser. I would rather know the rate limits so I can abide by them. -Chad On Sun, Dec 7, 2008 at 10:42 AM, fastest963 [EMAIL PROTECTED] wrote: Since your doing this via AJAX and such, this may not be a good idea, but you could try passing a login to Twitter and having that login whitelisted? -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Change: Search API Rate Limiting
The error code for search rate limiting will be changing from HTTP 503 to HTTP 401 in the very near future (today or tomorrow). For details, continue reading. Are you sure you want to use 401 for this? 401 would indicate authorization required. If you're asking for credentials, that would make sense, but if you're not, I would think the 503 is still the proper response irrespective of broken proxies. I don't see other codes that have that one's temporal semantics. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- If you have integrity, nothing else matters. -- Alan Simpson ---
Re: changes to search API?
Yes for some reason we were still doing the API query on summize.com, the 301 redirect we were getting was just sending us to the same URL but at search.twitter.com. Everything is sorted out now.. :) Thanks. On Dec 8, 11:42 am, Matt Sanford [EMAIL PROTECTED] wrote: Hi Alex, As I re-read this and think back to last week I may know the cause. Are you by chance still using summize.com? As part of our move to the Twitter data center we changed the logic of summize.com to redirect to search.twitter.com rather than handle requests to /search. If this is the case please change the host name and everything should work fine. Thanks; — Matt Sanford (@mzsanford) On Dec 8, 2008, at 07:17 AM, Alex wrote: We noticed that around midnight 00:00 GMT on Saturday we started getting 301 redirects for our search queries. Responses such as: htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://search.twitter.com/ search.json?q=junkamp;since_id=1034606772amp;rpp=20here/a./p /body/html Have there been changes to the Twitter Search API?
Re: Change: Search API Rate Limiting
Of course right after sending a lengthy public email I see something that could let us keep 503 and fix the proxy errors. I'm working with operations on that, and if it does not pan out I'll confer with Alex on 400 versus 401. Stay tuned. — Matt On Dec 8, 2008, at 09:46 AM, Alex Payne wrote: We use 400 for rate limiting on the REST API. Matt and I are discussing whether or not this might be the correct response. Thoughts? On Mon, Dec 8, 2008 at 09:17, Cameron Kaiser [EMAIL PROTECTED] wrote: The error code for search rate limiting will be changing from HTTP 503 to HTTP 401 in the very near future (today or tomorrow). For details, continue reading. Are you sure you want to use 401 for this? 401 would indicate authorization required. If you're asking for credentials, that would make sense, but if you're not, I would think the 503 is still the proper response irrespective of broken proxies. I don't see other codes that have that one's temporal semantics. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- If you have integrity, nothing else matters. -- Alan Simpson --- -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Change: Search API Rate Limiting
The error code for search rate limiting will be changing from HTTP 503 to HTTP 401 in the very near future (today or tomorrow). For details, continue reading. Are you sure you want to use 401 for this? 401 would indicate authorization required. If you're asking for credentials, that would make sense, but if you're not, I would think the 503 is still the proper response irrespective of broken proxies. I don't see other codes that have that one's temporal semantics. We use 400 for rate limiting on the REST API. Matt and I are discussing whether or not this might be the correct response. Thoughts? I guess that would work there too IMHO. It's ill-defined but that's a bonus in this case :) -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- Logic is the art of going wrong with confidence. -- George Bernard Shaw
Re: Change: Search API Rate Limiting
You could compromise and do a 400.5 O_o On Mon, Dec 8, 2008 at 11:51, Matt Sanford [EMAIL PROTECTED] wrote: Of course right after sending a lengthy public email I see something that could let us keep 503 and fix the proxy errors. I'm working with operations on that, and if it does not pan out I'll confer with Alex on 400 versus 401. Stay tuned. — Matt On Dec 8, 2008, at 09:46 AM, Alex Payne wrote: We use 400 for rate limiting on the REST API. Matt and I are discussing whether or not this might be the correct response. Thoughts? On Mon, Dec 8, 2008 at 09:17, Cameron Kaiser [EMAIL PROTECTED] wrote: The error code for search rate limiting will be changing from HTTP 503 to HTTP 401 in the very near future (today or tomorrow). For details, continue reading. Are you sure you want to use 401 for this? 401 would indicate authorization required. If you're asking for credentials, that would make sense, but if you're not, I would think the 503 is still the proper response irrespective of broken proxies. I don't see other codes that have that one's temporal semantics. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- If you have integrity, nothing else matters. -- Alan Simpson --- -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- | Abraham Williams | Web Developer | http://abrah.am | Brazen Careerist | Pro Hacker | http://www.brazencareerist.com | PoseurTech LLC | Mashup Ambassador | http://poseurte.ch | Web608 | Community Evangelist | http://web608.org | This email is: [] blogable [x] ask first [] private
Re: 400 Error retrieving friends?
On Dec 6, 2:37 am, Alex Payne [EMAIL PROTECTED] wrote: Are you entirely sure that you're sending the HTTP Basic Auth information for your whitelist account with your requests? Yes, I'm using exactly the same procedure for both the friends and followers and I'm only encountering problem with the friends. I'm literally just changing followers to friends in the urls. Should there be any difference in behavior? On Fri, Dec 5, 2008 at 12:11, Bruno G [EMAIL PROTECTED] wrote: Hi, I'm trying to retrieve the friend information for several users and I'm running up against a 400 error after a couple of minutes. This seems to occur roughtly after about 100 requests, so it might indicate a rate limit but my account is whitelisted. I'm making the requests using python's urllib2 and using urls of the form: http://twitter.com/statuses/friends/XXX.xml?page=1 Also, I don't see the same problem when requesting follower information using: http://twitter.com/statuses/followers/XXX.xml?page=1 and exactly the same code (just changing the urls). Is there something I'm missing? Thanks! Bruno -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
questions about twittering-mode
before i start a conversation, i wanted to see if this is the appropriate place to ask about twittering-mode for emacs.. thanks!
Re: Change: Search API Rate Limiting
I think using 400 is much easy to handle the responses than using 401. Because I can use same http client code and same error handling code for both search API and REST API. In my case, I wrote a error handler which alerts a dialog whenever it gets a 401 because search API wouldn't return 401. On Mon, Dec 8, 2008 at 9:56 AM, Abraham Williams [EMAIL PROTECTED] wrote: You could compromise and do a 400.5 O_o On Mon, Dec 8, 2008 at 11:51, Matt Sanford [EMAIL PROTECTED] wrote: Of course right after sending a lengthy public email I see something that could let us keep 503 and fix the proxy errors. I'm working with operations on that, and if it does not pan out I'll confer with Alex on 400 versus 401. Stay tuned. — Matt On Dec 8, 2008, at 09:46 AM, Alex Payne wrote: We use 400 for rate limiting on the REST API. Matt and I are discussing whether or not this might be the correct response. Thoughts? On Mon, Dec 8, 2008 at 09:17, Cameron Kaiser [EMAIL PROTECTED] wrote: The error code for search rate limiting will be changing from HTTP 503 to HTTP 401 in the very near future (today or tomorrow). For details, continue reading. Are you sure you want to use 401 for this? 401 would indicate authorization required. If you're asking for credentials, that would make sense, but if you're not, I would think the 503 is still the proper response irrespective of broken proxies. I don't see other codes that have that one's temporal semantics. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- If you have integrity, nothing else matters. -- Alan Simpson --- -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- | Abraham Williams | Web Developer | http://abrah.am | Brazen Careerist | Pro Hacker | http://www.brazencareerist.com | PoseurTech LLC | Mashup Ambassador | http://poseurte.ch | Web608 | Community Evangelist | http://web608.org | This email is: [] blogable [x] ask first [] private
Re: questions about twittering-mode
Sadly, it's not, unless you've run into an underlying issue with the Twitter API. On Mon, Dec 8, 2008 at 10:57, sergio_101 [EMAIL PROTECTED] wrote: before i start a conversation, i wanted to see if this is the appropriate place to ask about twittering-mode for emacs.. thanks! -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Using CAPTCHAs to get more followers on twitter.
Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir
Re: Using CAPTCHAs to get more followers on twitter.
... and then? I'm thinking of jumping off the Empire State Building tomorrow with Jeb Corliss ... Beside the apparent randomness of your post, was there an underlying question? On Mon, Dec 8, 2008 at 2:44 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 2:52 PM, Andrew Badera [EMAIL PROTECTED] wrote: ... and then? I'm thinking of jumping off the Empire State Building tomorrow with Jeb Corliss ... Beside the apparent randomness of your post, was there an underlying question? Do you think it would work? Is it worth building to try it out? Amir On Mon, Dec 8, 2008 at 2:44 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
How would that get you MORE followers -- you're asking people to read your tweets, then you check to see if they did? On Mon, Dec 8, 2008 at 2:54 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 2:52 PM, Andrew Badera [EMAIL PROTECTED] wrote: ... and then? I'm thinking of jumping off the Empire State Building tomorrow with Jeb Corliss ... Beside the apparent randomness of your post, was there an underlying question? Do you think it would work? Is it worth building to try it out? Amir On Mon, Dec 8, 2008 at 2:44 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
You might look at Amazon's Mechanical Turk if you're interesting in experimenting with human ratings of content. On Mon, Dec 8, 2008 at 11:54, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 2:52 PM, Andrew Badera [EMAIL PROTECTED] wrote: ... and then? I'm thinking of jumping off the Empire State Building tomorrow with Jeb Corliss ... Beside the apparent randomness of your post, was there an underlying question? Do you think it would work? Is it worth building to try it out? Amir On Mon, Dec 8, 2008 at 2:44 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 3:07 PM, Andrew Badera [EMAIL PROTECTED] wrote: But what would be the motivation for someone to script this to begin with? I guess I'm having a hard time understanding the value proposition. In order for your tweet selection to be shown to k people, you need to correctly answer the CAPTCHA for ~k tweet selections. This is all a mechanism to get people to look at each other's tweet selections. Amir On Mon, Dec 8, 2008 at 3:05 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 3:03 PM, Andrew Badera [EMAIL PROTECTED] wrote: But then what are you enforcing with the CAPTCHA? Aren't you just making it more difficult, more hurdles to leap, for people to engage with you? The CAPTCHA is used to get people to look at your tweet selection carefully. Without it, people could just post their tweet selection and use a script to automatically look at other people's tweet selections. Amir On Mon, Dec 8, 2008 at 2:58 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 2:56 PM, Andrew Badera [EMAIL PROTECTED] wrote: How would that get you MORE followers -- you're asking people to read your tweets, then you check to see if they did? If they like your tweet selection, they might consider following you. Amir On Mon, Dec 8, 2008 at 2:54 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 2:52 PM, Andrew Badera [EMAIL PROTECTED] wrote: ... and then? I'm thinking of jumping off the Empire State Building tomorrow with Jeb Corliss ... Beside the apparent randomness of your post, was there an underlying question? Do you think it would work? Is it worth building to try it out? Amir On Mon, Dec 8, 2008 at 2:44 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
Isn't that the point of Twitter to begin with? On Mon, Dec 8, 2008 at 3:09 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 3:07 PM, Andrew Badera [EMAIL PROTECTED] wrote: But what would be the motivation for someone to script this to begin with? I guess I'm having a hard time understanding the value proposition. In order for your tweet selection to be shown to k people, you need to correctly answer the CAPTCHA for ~k tweet selections. This is all a mechanism to get people to look at each other's tweet selections. Amir On Mon, Dec 8, 2008 at 3:05 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 3:03 PM, Andrew Badera [EMAIL PROTECTED] wrote: But then what are you enforcing with the CAPTCHA? Aren't you just making it more difficult, more hurdles to leap, for people to engage with you? The CAPTCHA is used to get people to look at your tweet selection carefully. Without it, people could just post their tweet selection and use a script to automatically look at other people's tweet selections. Amir On Mon, Dec 8, 2008 at 2:58 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 2:56 PM, Andrew Badera [EMAIL PROTECTED] wrote: How would that get you MORE followers -- you're asking people to read your tweets, then you check to see if they did? If they like your tweet selection, they might consider following you. Amir On Mon, Dec 8, 2008 at 2:54 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 2:52 PM, Andrew Badera [EMAIL PROTECTED] wrote: ... and then? I'm thinking of jumping off the Empire State Building tomorrow with Jeb Corliss ... Beside the apparent randomness of your post, was there an underlying question? Do you think it would work? Is it worth building to try it out? Amir On Mon, Dec 8, 2008 at 2:44 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
On Tue, Dec 9, 2008 at 7:05 AM, Amir Michail [EMAIL PROTECTED] wrote: The CAPTCHA is used to get people to look at your tweet selection carefully. Without it, people could just post their tweet selection and use a script to automatically look at other people's tweet selections. And how would you make people look at the tweet instead of the captcha? Honestly, my opinion about it is: If you want do build it, do it. No one here will stop you. -- Julio Biason [EMAIL PROTECTED] Twitter: http://twitter.com/juliobiason
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 4:02 PM, Julio Biason [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 7:05 AM, Amir Michail [EMAIL PROTECTED] wrote: The CAPTCHA is used to get people to look at your tweet selection carefully. Without it, people could just post their tweet selection and use a script to automatically look at other people's tweet selections. And how would you make people look at the tweet instead of the captcha? The idea is to have people submit a CAPTCHA that is directly connected to their tweet selection. For example, it might ask you to select the tweet that is most connected with a certain area of study. Or it might ask you to name the dominant theme in the tweet selection, etc. Amir Honestly, my opinion about it is: If you want do build it, do it. No one here will stop you. -- Julio Biason [EMAIL PROTECTED] Twitter: http://twitter.com/juliobiason -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Problems with updating profile image
Thanks Lien, I am trying to get this done using c#.NET and I think I am getting closer. What is happening with my request is it is getting truncated only a few characters in to the actual image data so I don't have a footer boundary. The post completes successfully, but the image that gets uploaded to the server isn't formatted correctly. Here is the full request body - POST /account/update_profile_image.xml HTTP/1.1 Content-Type: multipart/form-data; boundary=125e2d3d-97d3-44fc-8267-9a8ef2d79644 Authorization: Basic removed Host: twitter.com Content-Length: 201010 Expect: 100-continue --125e2d3d-97d3-44fc-8267-9a8ef2d79644 Content-Disposition: form-data; name=image; filename=seantest.jpg Content-Type: image/jpeg ÿØÿà Any ideas what could be causing the image data to be truncated? Thanks again for your help On Dec 8, 3:24 pm, Lien Tran [EMAIL PROTECTED] wrote: Here's what my request body looks like: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic removed Content-Type: multipart/form-data; boundary=-1228771270538 User-Agent: Java/1.6.0_02 Host: twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 71380 ---1228771270538 Content-Disposition: form-data; name=image; filename=Sunset.jpg Content-Type: image/jpeg binary data here ---1228771270538--HTTP/1.1 200 OK On Dec 8, 8:11 am, Sean [EMAIL PROTECTED] wrote: Would you mind posting a sample of your correctly formatted request here? I am running windows and haven't been able to get curl up and running yet. Thanks Sean On Dec 8, 12:06 am, Lien Tran [EMAIL PROTECTED] wrote: Thanks Alex. I used curl to see what the request should look like and then coded up my request accordingly. It's working for me now. On Dec 6, 11:37 am, Alex Payne [EMAIL PROTECTED] wrote: The test we use for this method is to use curl: curl -F '[EMAIL PROTECTED]/to/test/image.jpg' -u USERNAME:PASSWORDhttp://twitter.com/account/update_profile_image.xml If you use an HTTP proxy, you can see it generating the appropriate request and response. On Sat, Dec 6, 2008 at 00:09, Lien Tran [EMAIL PROTECTED] wrote: Hello, I've been trying to update myprofileimageusing the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying touploadis a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x-Hidequoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
Re: Problems with updating profile image
Thanks Lien, I am trying to get this done using c#.NET and I think I am getting closer. What is happening with my request is it is getting truncated only a few characters in to the actual image data so I don't have a footer boundary. The post completes successfully, but the image that gets uploaded to the server isn't formatted correctly. Here is the full request body - POST /account/update_profile_image.xml HTTP/1.1 Content-Type: multipart/form-data; boundary=125e2d3d-97d3-44fc-8267-9a8ef2d79644 Authorization: Basic removed Host: twitter.com Content-Length: 201010 Expect: 100-continue --125e2d3d-97d3-44fc-8267-9a8ef2d79644 Content-Disposition: form-data; name=image; filename=seantest.jpg Content-Type: image/jpeg ÿØÿà Any ideas what could be causing the image data to be truncated? Thanks again for your help On Dec 8, 3:24 pm, Lien Tran [EMAIL PROTECTED] wrote: Here's what my request body looks like: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic removed Content-Type: multipart/form-data; boundary=-1228771270538 User-Agent: Java/1.6.0_02 Host: twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 71380 ---1228771270538 Content-Disposition: form-data; name=image; filename=Sunset.jpg Content-Type: image/jpeg binary data here ---1228771270538--HTTP/1.1 200 OK On Dec 8, 8:11 am, Sean [EMAIL PROTECTED] wrote: Would you mind posting a sample of your correctly formatted request here? I am running windows and haven't been able to get curl up and running yet. Thanks Sean On Dec 8, 12:06 am, Lien Tran [EMAIL PROTECTED] wrote: Thanks Alex. I used curl to see what the request should look like and then coded up my request accordingly. It's working for me now. On Dec 6, 11:37 am, Alex Payne [EMAIL PROTECTED] wrote: The test we use for this method is to use curl: curl -F '[EMAIL PROTECTED]/to/test/image.jpg' -u USERNAME:PASSWORDhttp://twitter.com/account/update_profile_image.xml If you use an HTTP proxy, you can see it generating the appropriate request and response. On Sat, Dec 6, 2008 at 00:09, Lien Tran [EMAIL PROTECTED] wrote: Hello, I've been trying to update myprofileimageusing the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying touploadis a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x-Hidequoted text - - Show quoted text -- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Twitter Development Talk group. To post to this group, send email to twitter-development-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/twitter-development-talk?hl=en -~--~~~~--~~--~--~---
Re: 400 Error retrieving friends?
The plot thickens... it seems to work fine with curl, but not with python On Dec 8, 1:01 pm, Alex Payne [EMAIL PROTECTED] wrote: No, both the friends and followers methods should return a list of users with current status inline. On Mon, Dec 8, 2008 at 09:50, Bruno G [EMAIL PROTECTED] wrote: On Dec 6, 2:37 am, Alex Payne [EMAIL PROTECTED] wrote: Are you entirely sure that you're sending the HTTP Basic Auth information for your whitelist account with your requests? Yes, I'm using exactly the same procedure for both the friends and followers and I'm only encountering problem with the friends. I'm literally just changing followers to friends in the urls. Should there be any difference in behavior? On Fri, Dec 5, 2008 at 12:11, Bruno G [EMAIL PROTECTED] wrote: Hi, I'm trying to retrieve the friend information for several users and I'm running up against a 400 error after a couple of minutes. This seems to occur roughtly after about 100 requests, so it might indicate a rate limit but my account is whitelisted. I'm making the requests using python's urllib2 and using urls of the form: http://twitter.com/statuses/friends/XXX.xml?page=1 Also, I don't see the same problem when requesting follower information using: http://twitter.com/statuses/followers/XXX.xml?page=1 and exactly the same code (just changing the urls). Is there something I'm missing? Thanks! Bruno -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Using CAPTCHAs to get more followers on twitter.
hmmm, i don't understand how a Turing exam based on comprehension would get more followers. it would likely get less. But maybe higher IQ followers? ;-) Waitman
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 2:56 PM, Waitman Gobble [EMAIL PROTECTED] wrote: hmmm, i don't understand how a Turing exam based on comprehension would get more followers. it would likely get less. But maybe higher IQ followers? ;-) Waitman This would not be intended as an obstacle, but rather, as a way to force people into actually looking at the tweet selection. Amir -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
Hi Amir, I would like to salute your initiative in posting up ideas here, and getting feedback. I personally do not think that this is workable, but feel free to contact me for ideas as well. :) M On Mon, Dec 8, 2008 at 4:09 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 2:56 PM, Waitman Gobble [EMAIL PROTECTED] wrote: hmmm, i don't understand how a Turing exam based on comprehension would get more followers. it would likely get less. But maybe higher IQ followers? ;-) Waitman This would not be intended as an obstacle, but rather, as a way to force people into actually looking at the tweet selection. Amir -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- Discovery - Going Beyond Engagement: http://is.gd/op2 (My Current Pet Project) What I do: http://v3.mingyeow.com/?page_id=5
Re: Using CAPTCHAs to get more followers on twitter.
sheesh, sorry. I posted this before noon (california time). not sure why it took like four hours to appear. SAMF. I guess. I live like 15 minutes from google, figure it would be faster. (ok, teasing.) It's because people who are new, or considered new due to few posts, are automatically put in the moderation queue. There are several of us, but obviously this is a fairly busy group and we might not get to a message immediately as it arrives (or be immediately able to promote a subscriber to non-moderated). This group gets a lot of spam, which I'm sure people are delighted not to be seeing anymore. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- #include std_disclaimer.h
Re: Using CAPTCHAs to get more followers on twitter.
Personally, I think this would be worth building out to test. I don't think you'd get *more* followers but there might be a higher engagement rate with the people who do follow you. After all, they had to go through extra trouble to follow you so they definately see value in your tweets. The question I have is how you would enforce this? Anthony On 12/8/08, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir -- Sent from my mobile device
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 9:13 PM, Anthony Papillion [EMAIL PROTECTED] wrote: Personally, I think this would be worth building out to test. I don't think you'd get *more* followers but there might be a higher engagement rate with the people who do follow you. After all, they had to go through extra trouble to follow you so they definately see value in your tweets. They don't have to go through extra trouble to follow you. But those who would like more followers would use this service, thus giving you more followers if you participate as well. The question I have is how you would enforce this? What do you mean? Amir Anthony On 12/8/08, Amir Michail [EMAIL PROTECTED] wrote: Hi, I'm thinking of building this service using the twitter API: * you submit a selection of your tweets that you are particularly proud of * you also submit a CAPTCHA to check whether someone looking at your selection really looked at it carefully Example: such a CAPTCHA might ask the user to select the tweet in your selection that satisfies a particular criterion. Your tweet selection will be shown to k people provided that you correctly answer the CAPTCHAs in ~ k selections. You could have people use tags to facilitate search/browsing of tweet selections. Moreover, these tags could be used to improve a service such as http://b4utweet.com. Amir -- Sent from my mobile device -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 9:20 PM, Waitman Gobble [EMAIL PROTECTED] wrote: ... Anyways, back to the original topic. I don't understand WHERE these Them are going to submit. (re: original post). I guess that's what I'm missing. Waitman At the service using the twitter API that I'm thinking of building. I didn't realize this idea was so difficult to understand though. Maybe I shouldn't even try... Amir On Dec 8, 5:54 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: It's because people who are new, or considered new due to few posts, are automatically put in the moderation queue. spam, which I'm sure -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
Well, if you're like me you don't really need any cheerleaders to fluff you up and get you going. I mean they're nice and all, but stubborn persistence regardless. And besides, we'd not have much of this stuff if it weren't for some renegades with stubborn idears. You know, the Internet Cowboys. Guys who would crowbar their ways onto the rooftops of bank hi-rises just to set up satellite dishes and offer wireless internet when most people never even heard of broadband. Or rent a back hoe and chaw through public streets without permit to run copper. Back in the 1990's. Those types. Where would we be now? The thing I'm missing in your proposal - I can't see the nookie. I mean, are users getting a higher quality of selection of tweets because you do the Turing exam? Or are they going to get more followers because you have a pool of twitters at the other end waiting for them? (because of the quality of feed). Not cutting, just trying to understand. Waitman On Dec 8, 7:11 pm, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 9:20 PM, Waitman Gobble [EMAIL PROTECTED] wrote: ... Anyways, back to the original topic. I don't understand WHERE these Them are going to submit. (re: original post). I guess that's what I'm missing. Waitman At the service using the twitter API that I'm thinking of building. I didn't realize this idea was so difficult to understand though. Maybe I shouldn't even try... Amir On Dec 8, 5:54 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: It's because people who are new, or considered new due to few posts, are automatically put in the moderation queue. spam, which I'm sure --http://b4utweet.comhttp://chatbotgame.comhttp://numbrosia.comhttp://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 10:31 PM, Waitman Gobble [EMAIL PROTECTED] wrote: Well, if you're like me you don't really need any cheerleaders to fluff you up and get you going. I mean they're nice and all, but stubborn persistence regardless. And besides, we'd not have much of this stuff if it weren't for some renegades with stubborn idears. You know, the Internet Cowboys. Guys who would crowbar their ways onto the rooftops of bank hi-rises just to set up satellite dishes and offer wireless internet when most people never even heard of broadband. Or rent a back hoe and chaw through public streets without permit to run copper. Back in the 1990's. Those types. Where would we be now? The thing I'm missing in your proposal - I can't see the nookie. I mean, are users getting a higher quality of selection of tweets because you do the Turing exam? Or are they going to get more followers because you have a pool of twitters at the other end waiting for them? (because of the quality of feed). Suppose you have two twitter users who are each working on a web 2.0 startup and would like to increase the number of their twitter followers to better their chances of startup success. They could go to this service to increase their followers. So in using this service, they find each other. Even though they don't necessarily want to increase the number of people they follow, they might discover cool tweets that they would like to see anyway. And so they end up following each other, even though it was not their intent to follow more people. Amir Not cutting, just trying to understand. Waitman On Dec 8, 7:11 pm, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 9:20 PM, Waitman Gobble [EMAIL PROTECTED] wrote: ... Anyways, back to the original topic. I don't understand WHERE these Them are going to submit. (re: original post). I guess that's what I'm missing. Waitman At the service using the twitter API that I'm thinking of building. I didn't realize this idea was so difficult to understand though. Maybe I shouldn't even try... Amir On Dec 8, 5:54 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: It's because people who are new, or considered new due to few posts, are automatically put in the moderation queue. spam, which I'm sure --http://b4utweet.comhttp://chatbotgame.comhttp://numbrosia.comhttp://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
On Mon, Dec 8, 2008 at 10:51 PM, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 10:31 PM, Waitman Gobble [EMAIL PROTECTED] wrote: Well, if you're like me you don't really need any cheerleaders to fluff you up and get you going. I mean they're nice and all, but stubborn persistence regardless. And besides, we'd not have much of this stuff if it weren't for some renegades with stubborn idears. You know, the Internet Cowboys. Guys who would crowbar their ways onto the rooftops of bank hi-rises just to set up satellite dishes and offer wireless internet when most people never even heard of broadband. Or rent a back hoe and chaw through public streets without permit to run copper. Back in the 1990's. Those types. Where would we be now? The thing I'm missing in your proposal - I can't see the nookie. I mean, are users getting a higher quality of selection of tweets because you do the Turing exam? Or are they going to get more followers because you have a pool of twitters at the other end waiting for them? (because of the quality of feed). Suppose you have two twitter users who are each working on a web 2.0 startup and would like to increase the number of their twitter followers to better their chances of startup success. They could go to this service to increase their followers. So in using this service, they find each other. Even though they don't necessarily want to increase the number of people they follow, they might discover cool tweets that they would like to see anyway. And so they end up following each other, even though it was not their intent to follow more people. Of course, you could try following a huge number of people on twitter in the hope that some of them would follow you in return. But that might be seen as spamming. Moreover, these people probably won't look at your tweets seriously anyway (as there is no CAPTCHA), so they are unlikely to follow you. Amir Amir Not cutting, just trying to understand. Waitman On Dec 8, 7:11 pm, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 9:20 PM, Waitman Gobble [EMAIL PROTECTED] wrote: ... Anyways, back to the original topic. I don't understand WHERE these Them are going to submit. (re: original post). I guess that's what I'm missing. Waitman At the service using the twitter API that I'm thinking of building. I didn't realize this idea was so difficult to understand though. Maybe I shouldn't even try... Amir On Dec 8, 5:54 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: It's because people who are new, or considered new due to few posts, are automatically put in the moderation queue. spam, which I'm sure --http://b4utweet.comhttp://chatbotgame.comhttp://numbrosia.comhttp://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
very true. I did a 'god mode' experiment for about a week (did you ever play the game Doom years ago?) followed about 45,000 and had roughly 3,000 followers. i didn't tweet much of anything, it was all fiercely automated. and i certainly didn't read all of those posts. It's truly not really that interesting to have so many followers artificially, as i couldn't possibly think of anything useful to tell them all, and it was really just a big 'whirly gig' in the ethers. But a curious experiment anyway. On Dec 8, 8:01 pm, Amir Michail [EMAIL PROTECTED] wrote: Of course, you could try following a huge number of people on twitter in the hope that some of them would follow you in return. But that might be seen as spamming. Moreover, these people probably won't look at your tweets seriously anyway (as there is no CAPTCHA), so they are unlikely to follow you. Amir Amir Not cutting, just trying to understand. Waitman On Dec 8, 7:11 pm, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 9:20 PM, Waitman Gobble [EMAIL PROTECTED] wrote: ... Anyways, back to the original topic. I don't understand WHERE these Them are going to submit. (re: original post). I guess that's what I'm missing. Waitman At the service using the twitter API that I'm thinking of building. I didn't realize this idea was so difficult to understand though. Maybe I shouldn't even try... Amir On Dec 8, 5:54 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: It's because people who are new, or considered new due to few posts, are automatically put in the moderation queue. spam, which I'm sure --http://b4utweet.comhttp://chatbotgame.comhttp://numbrosia.comhttp://t... -- http://b4utweet.com http://chatbotgame.com http://numbrosia.com http://twitter.com/amichail --http://b4utweet.comhttp://chatbotgame.comhttp://numbrosia.comhttp://twitter.com/amichail
Re: Using CAPTCHAs to get more followers on twitter.
ok. So suppose one guy is working at Slide, and is about to gag on the python, or css, and is contemplating going to the fridge and getting yet another Seagrams Berry Blast Cooler, or go downstairs and around the corner check out that hot chick who works at Subway, or maybe just go sit in his car at the parking lot across the street and listen to Metallica Demagnetized, at full volume, or maybe DTP. And on the way down the stairs the thought occurs to him that Max will dump his girlfriend, and maybe he'll even start dating an Amish girl, for who knows, he might just lose all interest whatsoever in shoes and decide to walk in unannounced and pull the plug to the server, and a billion people will lose their amazing flashy image shows on their myspace profiles. And the other guy is hanging out in an even smaller office, working on the Vuvox project. And he starts considering the possibility that John won't sign off and bless the deal, the ebay thing isn't sealed. so they come to b4utweet.com and meet like strangers in the night. or something like that. I think there is some value in slagger-sales. People aren't there to buy your stuff, but they accidentally decide they might try it, because it had not occurred to them before. Sort of like sitting on a flight to Frankfurt and you're tired of watching the GPS coordinates animated on the front screens, and your ipod is depleted, and you don't read novels, and you've already looked up and down all the luftansa chicks more than once - so you start thumbing through the in- flight magazine and see some really cool pogo sticks from the guy who originally started sharper image, so you make a decision to take up pogo bouncing at the park. I think as long as you have a clear idea about what the user will get in the end, your project will be successful. But you know what, it could still be really good anyway, even if you don't know. So go for it. Waitman On Dec 8, 7:51 pm, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 10:31 PM, Waitman Gobble [EMAIL PROTECTED] wrote: Well, if you're like me you don't really need any cheerleaders to fluff you up and get you going. I mean they're nice and all, but stubborn persistence regardless. And besides, we'd not have much of this stuff if it weren't for some renegades with stubborn idears. You know, the Internet Cowboys. Guys who would crowbar their ways onto the rooftops of bank hi-rises just to set up satellite dishes and offer wireless internet when most people never even heard of broadband. Or rent a back hoe and chaw through public streets without permit to run copper. Back in the 1990's. Those types. Where would we be now? The thing I'm missing in your proposal - I can't see the nookie. I mean, are users getting a higher quality of selection of tweets because you do the Turing exam? Or are they going to get more followers because you have a pool of twitters at the other end waiting for them? (because of the quality of feed). Suppose you have two twitter users who are each working on a web 2.0 startup and would like to increase the number of their twitter followers to better their chances of startup success. They could go to this service to increase their followers. So in using this service, they find each other. Even though they don't necessarily want to increase the number of people they follow, they might discover cool tweets that they would like to see anyway. And so they end up following each other, even though it was not their intent to follow more people. Amir Not cutting, just trying to understand. Waitman On Dec 8, 7:11 pm, Amir Michail [EMAIL PROTECTED] wrote: On Mon, Dec 8, 2008 at 9:20 PM, Waitman Gobble [EMAIL PROTECTED] wrote: ... Anyways, back to the original topic. I don't understand WHERE these Them are going to submit. (re: original post). I guess that's what I'm missing. Waitman At the service using the twitter API that I'm thinking of building. I didn't realize this idea was so difficult to understand though. Maybe I shouldn't even try... Amir On Dec 8, 5:54 pm, Cameron Kaiser [EMAIL PROTECTED] wrote: It's because people who are new, or considered new due to few posts, are automatically put in the moderation queue. spam, which I'm sure --http://b4utweet.comhttp://chatbotgame.comhttp://numbrosia.comhttp://t... --http://b4utweet.comhttp://chatbotgame.comhttp://numbrosia.comhttp://twitter.com/amichail
