Re: Posting links to twitter
On Nov 4, 8:18 pm, dowhilesomething [EMAIL PROTECTED]
wrote:
Is this possible? Everything I try to do comes out as text.
As long as it looks like a url it seems to work,
namely with the http://
I wrote a bit of code to tinyurl-ise any links
http://github.com/matthewrudy/rudebay/tree/master/lib/rudebay/twitterer.rb
ruby
def self.make_tinyurl(link)
url = URI.parse('http://tinyurl.com/api-create.php')
req = Net::HTTP::Post.new(url.path)
req.set_form_data('url' = link)
res = Net::HTTP.new(url.host, url.port).start {|http|
http.request(req) }
return res.body
end
Re: Posting links to twitter
On Nov 4, 8:18 pm, dowhilesomething [EMAIL PROTECTED]
wrote:
Is this possible? Everything I try to do comes out as text.
It works fine, as long as it recognises its a url.
(I assume it uses the Rails auto_link, or something of that sort -
http://api.rubyonrails.org/classes/ActionView/Helpers/TextHelper.html#M001338)
namely start the link with an http://;
I wrote a bit of code to tinyurl any links
ruby
def self.make_tinyurl(link)
url = URI.parse('http://tinyurl.com/api-create.php')
req = Net::HTTP::Post.new(url.path)
req.set_form_data('url' = link)
res = Net::HTTP.new(url.host, url.port).start {|http|
http.request(req) }
return res.body
end
http://github.com/matthewrudy/rudebay/tree/master/lib/rudebay/twitterer.rb
enjoy.
(apologies if I sent this twice)
MatthewRudy
Re: Search API feature request: follows:username
On Dec 4, 8:32 pm, Chad Etzel [EMAIL PROTECTED] wrote: Not really an elegant solution/implementation, but I could imagine that the database query needed to the equivalent on the back-end servers would not exactly be trivial either. Yeah. I imagine the search functionality is actually done using lucene, and some sort of facets? Or at least it'd make sense given the nature of the search, and the fact that the query language looks like lucene syntax. Not that I've worked with such big fulltext searching, but our search of 30,000 jobs is incredibly slow once you start adding criteria (especially range queries). With twitters one billion messages I'm sure the game changes quite a lot.
Re: Date Format: ex: about 2 hours ago
All of the clients and the web post friendly things like about 2 hours ago. Can anyone provide a standard routine for converting the pure date element into these english strings? take a look at the way Rails does it as well, http://github.com/rails/rails/tree/master/actionpack/lib/action_view/helpers/date_helper.rb It's quite a common thing, so perhaps you should look at the source for Struts, or some similar java framework, see if you can steal the code directly from there.
[twitter-dev] Search API error {error:since_id too recent, poll less frequently}
I am polling the search API every 60 seconds and intermittently
receiving the following error:
{error:since_id too recent, poll less frequently}
Is this behavior to be expected or is there some problem?
Matthew Schrock
[twitter-dev] Search API error {error:since_id too recent, poll less frequently}
I am polling the Search API and intermittently receive the following
error:
{error:since_id too recent, poll less frequently}
Is this to be expected or this something going wrong on the server
side?
Matthew Schrock
[twitter-dev] Re: Search API error {error:since_id too recent, poll less frequently}
Chad,
Good to know. Thanks for your help.
Matthew
On Jul 21, 2:13 pm, Chad Etzel jazzyc...@gmail.com wrote:
That usually happens when the search servers get out of sync and the
since_id tweet hasn't been indexed on the other server(s) yet, so it
thinks it's a tweet from the future.
-Chad
On Tue, Jul 21, 2009 at 12:38 PM, matthewjesc...@gmail.com wrote:
I am polling the Search API and intermittently receive the following
error:
{error:since_id too recent, poll less frequently}
Is this to be expected or this something going wrong on the server
side?
Matthew Schrock
[twitter-dev] Re: Search API: geocode operator not working?
Chad, It looks like your mi units parameter has been truncated to m. When I add i to the string it works for me. It may be that it is returning results withing 5 meters. Matthew On Jul 22, 3:25 pm, Chad Etzel jazzyc...@gmail.com wrote: Did the geocode operator stop working? I just tried a couple of geocoded searches and got back 0 results. Here is a search for San Francisco, CA within 15 miles. curlhttp://search.twitter.com/search.json?q=geocode%3A37.779160%2C-122.42... Users are complaining to me as well, so I know it's not just my machine/IP Is it working for anyone else? -Chad
[twitter-dev] Re: Search API error {error:since_id too recent, poll less frequently}
Brooks,
Thanks for the link - helps me understand some of the stuff I've been
seeing.
Matthew
On Jul 22, 1:15 pm, Brooks Bennett bsbenn...@gmail.com wrote:
Matt,
Here is another thread pseudo-related to the issue.
http://groups.google.com/group/twitter-development-talk/browse_thread...
Again, thanks to Chad.
Brooks
On Jul 21, 1:35 pm, matthew jesc...@gmail.com wrote:
Chad,
Good to know. Thanks for your help.
Matthew
On Jul 21, 2:13 pm, Chad Etzel jazzyc...@gmail.com wrote:
That usually happens when the search servers get out of sync and the
since_id tweet hasn't been indexed on the other server(s) yet, so it
thinks it's a tweet from the future.
-Chad
On Tue, Jul 21, 2009 at 12:38 PM, matthewjesc...@gmail.com wrote:
I am polling the Search API and intermittently receive the following
error:
{error:since_id too recent, poll less frequently}
Is this to be expected or this something going wrong on the server
side?
Matthew Schrock
[twitter-dev] Re: Random updates coming from API
Have you tried unfollowing @twitterapi? On Jul 22, 8:59 pm, Devonne streeter solelydiv...@gmail.com wrote: I 've been receiving random profile updates coming from API on my profile for the last 4 weeks, i have send request to solve the issue, yet it still happening thank you
[twitter-dev] Whitelist DM limit Question
I'm developing an application and I need to find out how the DM limit will work if I get it Whitelisted. Does the expanded DM limit for whitelisted applications only apply to DM's directly from the account associated with the application that has been whitelisted, or does it apply to an account that uses my application? For example if my application is linked to my account named MyDmAccount and a user with an account called SomeUser uses my application to send DMs. Can SomeUser send an increased amount of DMs through my application, or does the allowed increase in DMs only apply to DMs send directly from MyDmAccount? Trying to design this application to stay within the lines and need to figure this out before moving forward. Thanks, Matt
[twitter-dev] Re: Whitelist DM limit Question
So for example a user using your butler application can only broadcast a single DM to 250 people a day. Is that correct? Thanks, Matt On Sep 1, 1:01 am, Dean Collins d...@cognation.net wrote: if they are logging in as their account they can only send 250 Direct Messages per day. http://help.twitter.com/forums/10713/entries/14959 Last year, Twitter imposed reasonable limits to help prevent system and user abuse. (You can read more about that here http://twitter.zendesk.com/forums/10711/entries/15364 ) If you hit a Twitter limit, we will tell you by showing an error message in your browser when you try to perform an action. If you've hit a limit, it means you've exceeded one of these limits: * 1,000 updates per day * 250 direct messages per day * 150 API requests per hour Cheers, Dean Collinswww.MyTwitterButler.comhttp://www.MyTwitterButler.com From: twitter-development-talk@googlegroups.com on behalf of Matthew Sent: Tue 1/09/2009 12:27 AM To: Twitter Development Talk Subject: [twitter-dev] Whitelist DM limit Question I'm developing an application and I need to find out how the DM limit will work if I get it Whitelisted. Does the expanded DM limit for whitelisted applications only apply to DM's directly from the account associated with the application that has been whitelisted, or does it apply to an account that uses my application? For example if my application is linked to my account named MyDmAccount and a user with an account called SomeUser uses my application to send DMs. Can SomeUser send an increased amount of DMs through my application, or does the allowed increase in DMs only apply to DMs send directly from MyDmAccount? Trying to design this application to stay within the lines and need to figure this out before moving forward. Thanks, Matt winmail.dat 7KViewDownload
[twitter-dev] status/update in_reply_to_user_id not being acknowledged
Hello, Been working on a project that will allow users to reply to tweets. I am having difficulty in getting the 'in_reply_to_message_id' to be acknowledged. I have been using the latest version of Abraham's TwitterOAuth library, also confirmed the problem through apigee. Example request (over POST): http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=26673308442status=looks like its not working for apigee either I can confirm the in_reply_to_status_id message is a message I posted earlier. http://api.twitter.com/1/statuses/show/26673308442.json I get a response back from twitter with field populated except with in_reply_to_status_id : null. Is there currently a glitch in the twitterapi, or am I using this function improperly? Thanks in advance! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: status/update in_reply_to_user_id not being acknowledged
Opps I meant to mark the title as 'in_reply_to_status_id'. On Oct 7, 1:37 pm, Matthew matt.c.w...@gmail.com wrote: Hello, Been working on a project that will allow users to reply to tweets. I am having difficulty in getting the 'in_reply_to_message_id' to be acknowledged. I have been using the latest version of Abraham's TwitterOAuth library, also confirmed the problem through apigee. Example request (over POST):http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=2... like its not working for apigee either I can confirm the in_reply_to_status_id message is a message I posted earlier.http://api.twitter.com/1/statuses/show/26673308442.json I get a response back from twitter with field populated except with in_reply_to_status_id : null. Is there currently a glitch in the twitterapi, or am I using this function improperly? Thanks in advance! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: status/update in_reply_to_user_id not being acknowledged
Thanks Taylor, I appreciate it. I didnt see mention of that in the http://developer.twitter.com/doc/post/statuses/update documentation. -Matt On Oct 7, 1:42 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: With as often as this comes up, it's obvious that we aren't communicating this clearly and the historical aspect of this isn't obvious: An @reply requires that it begins with the @username of the user being replied to. The in_reply_to_status_id field is not enough to associate the tweets as a reply -- the username must also be present. Also: When using a POST method, don't include your fields/parameters on the query string. Instead, put them in the POST body. You may find someday that passing such parameters on the query string just stops working. Taylor On Thu, Oct 7, 2010 at 1:37 PM, Matthew matt.c.w...@gmail.com wrote: Hello, Been working on a project that will allow users to reply to tweets. I am having difficulty in getting the 'in_reply_to_message_id' to be acknowledged. I have been using the latest version of Abraham's TwitterOAuth library, also confirmed the problem through apigee. Example request (over POST): http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=2... like its not working for apigee either I can confirm the in_reply_to_status_id message is a message I posted earlier. http://api.twitter.com/1/statuses/show/26673308442.json I get a response back from twitter with field populated except with in_reply_to_status_id : null. Is there currently a glitch in the twitterapi, or am I using this function improperly? Thanks in advance! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] friendships/destroy Could not authenticate you
Here's the code:
$params = array('user_id'= 16685316);
$oauth = new TwitterOAuth(
TWITTER_OAUTH_CONSUMER_KEY,
TWITTER_OAUTH_SECRET_KEY,
$user-getOauthToken(),
$user-getOauthTokenSecret()
);
Log::debug(params, $params);
$result = $oauth-post('friendships/destroy', $params);
Log::debug(result, $result);
if (isset($result-error)) {
return false;
}
return true;
Problem is all requests to both friendships/destroy and friendships/
create fail with the following:
stdClass Object
(
[request] = /1/friendships/destroy.json
[error] = Could not authenticate you.
)
HOWEVER, using the exact same user object in memory I can successfully
get my personal timeline. ??
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: friendships/destroy Could not authenticate you
Turned out to be a red herring for a totally different problem. Please
disregard.
On Dec 13, 7:39 pm, Matthew matt.c.w...@gmail.com wrote:
Here's the code:
$params = array('user_id'= 16685316);
$oauth = new TwitterOAuth(
TWITTER_OAUTH_CONSUMER_KEY,
TWITTER_OAUTH_SECRET_KEY,
$user-getOauthToken(),
$user-getOauthTokenSecret()
);
Log::debug(params, $params);
$result = $oauth-post('friendships/destroy', $params);
Log::debug(result, $result);
if (isset($result-error)) {
return false;
}
return true;
Problem is all requests to both friendships/destroy and friendships/
create fail with the following:
stdClass Object
(
[request] = /1/friendships/destroy.json
[error] = Could not authenticate you.
)
HOWEVER, using the exact same user object in memory I can successfully
get my personal timeline. ??
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] API Calls to unauthenticated methods
Seems like calls to account/rate_limit_status are throwing errors (presumably all unauthenticated calls are too), is this due to the ddos attack? If so when/will they be back up again?
[twitter-dev] Re: HTTP 409 on status update via API
I'm getting 408s trying to authenticate with OAuth On Aug 6, 10:20 pm, John Kalucki jkalu...@gmail.com wrote: This should be fixed for the Streaming API. -John On Aug 6, 1:59 pm, Jennie Lees trin...@gmail.com wrote: Getting the same thing using the track function of the API. On Thu, Aug 6, 2009 at 9:43 PM, briantroy brian.cosin...@gmail.com wrote: Sorry... these are HTTP 408s... On Aug 6, 1:20 pm, briantroy brian.cosin...@gmail.com wrote: This just started today. It was working fine before and early this morning. I'm send in user updates from a widget via API. My server is whitelisted and I've got a registered service. I get a HTTP 409 on every attempt to submit a status. Not sure why... You can try it here:http://briantroy.com/blog/about I know a 409 should mean timed out... but the response comes back in one second (or just really really fast). Any help appreciated... Brian Roy justSignal -- Jennie Lees Founder, Affect Labs jen...@affectlabs.comhttp://twitter.com/jennielees
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
Yes, you need to ask twitter to fix that. They are using our api, but obviously, they are encoding the ) after the .jpg. Thanks for letting us know, but yes, this is a twitter issue. Good luck with that. Since it is acceptable to have the unencoded ) character in a URL, I don't know how they might interpret that it does not belong. They can make a good guess at best.
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
If in fact URL shortening is possible via the API, then there should at least be an option to suppress it. I have seen the API shorten URLs that I have already shortened which has caused problems but I never got an answer on what the rules were because I have also noticede some longer URLs slip by so there is an algorithm working there somewhere. Silence to the questions is the frustrating part. I guess I'm not big enough yet.
[twitter-dev] Re: non json response
I'm seeing tons of these as well. However, I've found that if you follow the suggestion of the META tag to simply refresh in 0.1 seconds if you get this bogus response, you can hide most of this from users, especially if they are on a fast network. On Thu, Sep 10, 2009 at 2:09 PM, Monica Keller monica.kel...@gmail.comwrote: We see this error 75% of the time. Have you guys made an progress on resolving the issue ? On Sep 6, 8:14 pm, archF6 tylerjpeter...@gmail.com wrote: I am able to consistently reproduce this error. I am making GET requests via PHP from IP: 96.30.16.192. I receive the error without fail after periods of inactivity lasting 2 hours or more. The header response code is 200. Please let me know if I can provide any additional info that might help you diagnose the problem, or if you have suggestions about how best to handle. Thanks. On Sep 6, 3:35 pm, Rudifa rudi.far...@gmail.com wrote: I have seen this same http page with empty body !DOCTYPEhtmlPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/ TR/1999/REC-html401-19991224/strict.dtd !-- !DOCTYPEHTMLPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/TR/html4/strict.dtd; -- HTML HEAD META HTTP-EQUIV=Refresh CONTENT=0.1 META HTTP-EQUIV=Pragma CONTENT=no-cache META HTTP-EQUIV=Expires CONTENT=-1 TITLE/TITLE /HEAD BODYP/BODY /HTML a number of times in the last few days (but intermittently - a good response may come after several attempts), in response tohttp://twitter.com/users/show/rudifa.json The most recent one was on UTC time 2009-09-06 18:55:38.262 My IP is 84.227.186.88 as reported byhttp://www.whatismyip.com/ Could someone at twitter.com please tell us what does this mean? Server (s) overloaded? On Aug 30, 1:20 pm, Steven Wilkin iamthebisc...@gmail.com wrote: I'm consistently getting the same response when accessinghttp:// search.twitter.com/trends.jsonfrom209.40.204.183 Steve On Aug 26, 5:27 pm, Ryan Sarver rsar...@twitter.com wrote: Ben, It's a known issue and we are trying to hunt it down. Can you please provide us with your source IP and an approximate time of when you saw it? Thanks, RyanOn Wed, Aug 26, 2009 at 7:00 AM, ben ben.apperr...@googlemail.com wrote: Occassionally i get back a 200 statushtmlresponse from the json search api which look like this, most times the same search works fine, it just happens occassionally: !DOCTYPEhtmlPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/ TR/1999/REC-html401-19991224/strict.dtd !-- !DOCTYPEHTMLPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/TR/html4/strict.dtd; -- HTML HEAD META HTTP-EQUIV=Refresh CONTENT=0.1 META HTTP-EQUIV=Pragma CONTENT=no-cache META HTTP-EQUIV=Expires CONTENT=-1 TITLE/TITLE /HEAD BODYP/BODY /HTML Does anyone recognise what this kind of response means? Is it normal, or just beta-ish quirks?- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Comments for the group and Twitter staff
Hey Alex, would you consider just giving everybody their money back if they aren't 100% satisfied? On Tue, Sep 15, 2009 at 2:16 PM, Alex Payne a...@twitter.com wrote: The main twitter.com site already uses the API in some places. Our revised mobile site is built entirely on the API, and our Facebook application has been built off our API for some time. Dogfooding! We support it. On Tue, Sep 15, 2009 at 14:08, Jim Renkel james.ren...@gmail.com wrote: I emphatically second and support the idea of twitter.com having to use the API. We had similar quality problems at a place I formerly worked, and they were solved, completely, when such a policy was instituted. Yeah, it puts pressure on the API team and may inconvenience the UI team, or whatever you call them, but in the long run it will be worth it. Side effects that we saw were a simpler, cleaner, more consistent architecture for the whole system, and lower total costs to develop and maintain the system. Bite the bullet and do it now. The longer you wait, the more difficult and expensive it will be. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Scott Haneda Sent: Tuesday, September 15, 2009 15:55 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Comments for the group and Twitter staff Probably too late for this, but perhaps moving forward, it could be done... Twitter.com should move to using their own API. The tools they use to power their own site should be the same tools we use and rely on. In all reality, this seems a simpler approach, rather than pushing out code for their stuff, and then essentially backporting that to an API, just work on making the API, and then integrate that into the twitter.com site. As far as I can tell, this would solve pretty much every problem the API has, as there can not be a case where twitter is down, but the API is up, or the API is down, and twitter is up. Twitter should be eating their own dog food :) -- Scott * If you contact me off list replace talklists@ with scott@ * -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Suggestion for User record
+1 On Sat, Oct 31, 2009 at 11:10 PM, Dave Winer dave.wi...@gmail.com wrote: It would be useful if a user had a lists_count element, in addition to the other counts (followers, statuses, favourites).
[twitter-dev] Show a specific list you can use the new resource
Can someone explain this? GET '/:users/lists/:list_slug.:format' Show a specific list you can use the new resource.
[twitter-dev] member_count lists issue
I SEEM to be getting a zero member count from a list where the only member is the owner of said list. Once I added another member to the list, the member count was 2. Anyone else notice this? Still trying to verify it's not on my end.
Re: [twitter-dev] Re: OAuth DELETE LIST problem
There MAY also be an issue with how a DELETE request is formed. Try putting the parameters in the query string if you aren't. That seemed to make it work for me when it wasn't. On Tue, Dec 15, 2009 at 6:11 PM, Abraham Williams 4bra...@gmail.com wrote: The proper method is with DELETE and no _method=delete. For environments where you can only make GETs and POSTs you can add _method=delete as a work around. That being said I've had issues with random lists being frozen and not deletable. I've heard a number of other people mention the same issue. Abraham On Mon, Dec 14, 2009 at 09:37, volker volker.kr...@googlemail.com wrote: i think your base String should look like this: base: DELETEhttp%3A%2F%2Fstaging..com%2Fapi%2Fmodel%%2Fcontroller %2F2467oauth_consumer_key%thekey%26oauth_nonce %3D1429%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1260804448%26oauth_token%3Dtoken%26oauth_version%3D1.0 so you had to strip out _method=delete and send via POST but the basestring must start with DELETE maybe this helps Volker -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
Re: [twitter-dev] List ID
On Thu, Jan 21, 2010 at 1:00 PM, Lloyd England ll...@lloydengland.comwrote: Hi, quick question which I cannot find an answer for anywhere - how do you find the ID of a twitter list? http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-id Thanks!
Re: [twitter-dev] Re: disparities between bit.ly Google Analytics?
Google Analytics is javascript based which means a browser or some environment that can execute JS needs to open a page for a pageview There are many more HTTP requests for a given URL. Bots, spiders, aggregators etc. Since Bit.ly and other shorteners are doing 301 redirects, they can't really discern between the requests. Well, maybe they could with some well known agents, but it is not really feasible to detect every one out there. At least that probably accounts for much of the discrepancy.
[twitter-dev] OAuth redirect
The redirect back to my site from the OAuth allow page always hangs. Clicking on the link results in sending the user back to the correct page. Trying to figure out how that could be on my end, but I can't see it. It fails 100% of the time, or so it seems.
Re: [twitter-dev] Is Twitter oAuth broken?
I'm getting problems on the return as well. On Mon, Jul 19, 2010 at 2:55 PM, nischalshetty nischalshett...@gmail.comwrote: My apps getting 'user has not given permission' and this is by the hundreds! I presume the oAuth API is having issues!
Re: [twitter-dev] getting 404 error when trying to subscribe to a list
Try screen_name instead of userid. I'm not certain but it rings a bell. Not that it shouldn't work with id, of course. On Tue, Aug 24, 2010 at 8:49 PM, bear bea...@gmail.com wrote: Using oAuth I am making the following call: POST /1/userid/3968155/subscribers.json where userid is the user whose oAuth tokens are in use and 3968155 is the id of the list i'm trying to subscribe to Twitter returns a stock 404 result I've even tried it with the slug id of the list, same result. I also know I have a valid oAuth environment because i'm getting the list information from a previous valid call to /1/userid/lists/ subscriptions.json and I always do /1/account/verify_credentials.json when i'm working on the library code. any clues? thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Tweeting from a CMS
Wheras formerly you must have supplied the Company's Twitter account username and password, you will now need to supply the OAuth credentials of the company account. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials If the case happens to be you were using third party code and you don't know how it works but just supplied the the username and password, then it is very possible that that code will no longer work. You will need to use a library that supports OAuth. There are many. On Fri, Aug 27, 2010 at 7:44 AM, stevew stevewhite...@gmail.com wrote: You mean *from* your company's account? With OAuth, you don't need username/password, because these are replaced by credentials. It's still very much possible. bah, I got shifted onto other projects and completely forgot about this... any ideas where I can find information about doing this? I am stuck Everything I have seen seems to rely on the user getting a token, and re-inputting that into the web app, but I can't seem to get to the satge of twitter offering me a token without being logged in :-( Basically to sum up, I want this :: a user loges into our CMS using their company credentials, they can tweet from/as the company account and all of the twitter stuff is hidden from them. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Help with Oauth update status
I'd like to see this too. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] simple JavaScript code to update status from an html page?
Hi Folks. I'm trying to write a simple HTML document with JavaScript that updates the status for a single Twitter account - mine. It will reside on my own server and I'll load it from my mobile browser. I've searched for hours and come up with no easy answers. @Anywhere's API is undocumented; the OAuth handshaking is complex; Basic Auth is gone; XMLHttpRequest has the cross-domain limitation. I've looked at creating a Google Gadget to do this, but it's complex too. I'm very new to the Twitter API, OAuth, etc, and I'd really love your help. My application is simple, but is important to me. Thanks very much! matt -- Matthew Cornell | m...@matthewcornell.org | 413-626-3621 | 34 Dickinson Street, Amherst MA 01002 | matthewcornell.org -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Twitter-async now let's you view a sequence diagram of calls
++ I only recommend EpiTwitter to folks as a PHP library now, ++ It's solid. On Sat, Sep 4, 2010 at 6:15 PM, Scott Wilcox sc...@dor.ky wrote: Haha, that can only lead to a better experience for the end users. For what its worth, I only recommend EpiTwitter to folks as a PHP library now, and quite the volume of people at that! Shows you're doing something right! :) Scott. On 4 Sep 2010, at 23:10, jmathai wrote: Thanks Scott :). The same sweetness will be added to my fork of Twilio and Facebook's library as well :). I think my goal in life is to add asynchronous-ness to all php libraries :). On Sep 4, 1:31 pm, Scott Wilcox sc...@dor.ky wrote: That's a fantastic addition to an already great library. Great work! On 4 Sep 2010, at 21:22, jmathai wrote: The twitter-async library on github now lets you easily view a sequence diagram of calls. This is specifically useful when you're making multiple calls asynchronously. Here's a sample output (looks better with fixed width font). http://wiki.github.com/jmathai/twitter-async/#sequence (http://api.twitter.com/1/direct_messages.json:: code=200, start=1283577305.2462, end=1283577305.5109, total=0.264562) [] (http://api.twitter.com/1/users/suggestions.json:: code=200, start=1283577305.2726, end=1283577305.3871, total=0.114419) [ = ] (http://api.twitter.com/1/statuses/public_timeline.json:: code=200, start=1283577305.2731, end=1283577305.4195, total=0.146262) [ ] -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] List Statuses Page Limit
What is the per page limit of statuses returned on the: http://dev.twitter.com/doc/get/:user/lists/:id/statuses method? Also, if since_id is passed, how many will be returned in a page by default (if the amount returned is greater than the default)? Thanks, Matt -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] lookupUsers hangs
I'm making unauthenticated calls to getFollowerIDs(), then storing a segment of that return value in an integer array (of 100 user IDs or less) and passing that array to lookupUsers(). My program simply hangs at that point. Enabling twitter4j.debug does show output for the getFollowerIDs() call, but nothing for the lookupUsers() call. Any suggestions for how to debug/troubleshoot this further? Regards, Matthew Turland -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: lookupUsers hangs
Didn't notice this list was for general Twitter development. Clarification: I'm using the twitter4j Java Twitter client library from http://twitter4j.org. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Search and/or streaming rate limits
If my app has 1000 users and each one wants to do a unique search once an hour it seems like that is beyond what is being suggested. Even if I use the streaming api and filters, it looks like I could only have a couple hundred users. ( Am I missing some technique because it doesn't seem like you can do anything useful with my use case if you are limited to a few hundred users. I've never found the rate limits a burden since you can spread the requests out among the users via OAuth, but the IP limits seem way too restrictive. Maybe I'm overlooking a creative workaround. Anyone? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] REST API or best solution
So I am building a caching-proxy on my server to make requests to Twitter's databases when my subsites (100+ of them) want to pull user_timeline. Our rate limit seems to go over its limit too much and thus were going to cache responses from api.twitter, and allow our subsites to pull from there instead of directly from you guys. I was wondering if its possible I can take advantage of the OAuth approach (350requests/hr) in our cache-proxy approach..? Is it possible that I can use our company twitter account as the authorization agent instead of sending the user to a twitter sign in everytime we want to request user_timeline? Or should we be looking into the Streaming API? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/dochttp://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
So yes, I was correct (at least with search) that a web based solution is severely limited compared to a desktop. It will share usage among all it's users while a desktop client can spread the load amongst its users IPs. That stinks in my opinion. (I'm a web developer.) On Wed, Oct 6, 2010 at 7:44 PM, Matt Harris thematthar...@twitter.comwrote: All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
Fair enough. On Wed, Oct 6, 2010 at 8:39 PM, Matt Harris thematthar...@twitter.comwrote: Well remember with Search you don't need to proxy from your server - instead the Search API supports JSONP so you can run it directly from the website. Regarding Toms proxy comment. I think Tom was suggesting it for the userstreams functionality. As userstreams require a long poll connection there are various other obstacles to overcome if it were to be run from within the browser directly. In addition, userstreams are for single user use and not suitable for web applications where multiple users interact. Instead the something like the Site Streams service (currently in beta) could be better suited. On Wed, Oct 6, 2010 at 5:18 PM, Matthew Terenzio mteren...@gmail.com wrote: So yes, I was correct (at least with search) that a web based solution is severely limited compared to a desktop. It will share usage among all it's users while a desktop client can spread the load amongst its users IPs. That stinks in my opinion. (I'm a web developer.) On Wed, Oct 6, 2010 at 7:44 PM, Matt Harris thematthar...@twitter.com wrote: All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi
Re: [twitter-dev] Is authentication required to use Streaming API?
Yes, for the streaming api, http://dev.twitter.com/pages/streaming_api but it sounds like you may want the search api which doesn't require authentication: http://dev.twitter.com/doc/get/search On Thu, Oct 7, 2010 at 12:49 PM, D. Smith emai...@sharedlog.com wrote: Hello! I want to start using streaming API to monitor all tweets with certain keywords in them. Do I need to provide any authentication in order to connect? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Twitter + Gnip Partnership
We have every right in the world to gather this data for analysis without any permission. It's public. Redistributing it will be subject to fair use and copyright law but not gathering it and making broad analysis. That is what search engines do and so far the courts have said they have a right to cache copies on their own servers, not for public display necessarily, but in order to better analyze it. Oddly, the courts landed on the right side for once, saying that the greater good of the utility of search was a societal need and, in this case, more important than minor infringements, if any, on the site's copyrights. On Wed, Nov 17, 2010 at 12:18 PM, Ryan Sarver rsar...@twitter.com wrote: Companies have leveraged Twitter’s open API to analyze and report on conversations and sentiment across the network since its inception. These products have been indispensable in helping brands, marketers and businesses engage with their customers on Twitter. This is an area we want to support more fully, and today we are excited to announce a partnership with Gnip to develop and market data products specifically for these analysis and non-display companies. Gnip will sublicense access to our public Tweets to developers interested in analyzing large amounts of Twitter data. Over the past year we have spoken with many companies and entrepreneurs throughout the ecosystem who need easier access to more data. In particular, companies building analysis and non-display products have asked us for greater volume and coverage. Our partnership with Gnip is built to address this need. Gnip will focus exclusively on creating products to meet the existing and emerging demands of companies creating non-display products. Check out Gnip’s blog to learn more and to see details about their initial Twitter data products: http://blog.gnip.com/gnip-twitter-partnership/. Many of you may wonder what this means for elevated access and whitelisting requests. Our default levels like Spritzer, Follow and Track will not be changing, and will remain free and available directly from Twitter. Companies and developers are encouraged to begin development with these free APIs, available at http://dev.twitter.com/pages/streaming_api. This does affect companies wishing to create products which analyze Tweets and do not display Tweets to end-users. Moving forward, we will begin to encourage these companies needing elevated access for analysis and non-display products to work with Gnip to find the right data products for their commercial needs. We’re excited about this partnership, and the support it offers the data analysis and non-display market. You can learn more about the details and Gnip by visiting http://gnip.com/twitter. Please let me know if you have any questions about how this affects you and your products. To contact Gnip: web: http://gnip.com email: i...@gnip.com twitter: http://twitter.com/gnip Best, Ryan -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter + Gnip Partnership
I don't care what your newsletter says. I'm talking about American law. On Thu, Nov 18, 2010 at 11:28 PM, L. Mohan Arun mar...@gmail.com wrote: We have every right in the world to gather this data for analysis without any permission. It's public. No. You don't get to compile posts from a discussion forum into a product, under the idea that such posts are public domain. They are not. - Unless you own the forum or have a deal with the forum owner, and you stated in the TOS that all posts made in the forum can be repackaged commercially and only you have the right to do that. I am not saying this on my own, this is from one of the newsletters I receive, which covered this exact same topic, I would be happy to share the relevant text of the newsletter if someone is interested ... - - - Mohan Arun www.mohanarun.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter + Gnip Partnership
Just to clarify. I never said they were Public Domain. Twitter or the user own the copyrights. Probably both. I meant it has been made public information, thereby granting some rights to those it was made public to. I wouldn't have a right to redistribute a book written by you, but I have every right to quote it in an article I write about you. More importantly, I can read 1000 books by 1000 different people and then write a paper that says 50% of the books written contained the word 'Obama' and and the average amount of times Obama was used in a book was 14. I wouldn't be breaking any laws. But who cares. In the future, if you want to access the Twitter data for such usage with any sort of speed you will pay to do so. It won't even be worth the headache if you can devise an alternative. On Thu, Nov 18, 2010 at 11:35 PM, Matthew Terenzio mteren...@gmail.comwrote: I don't care what your newsletter says. I'm talking about American law. On Thu, Nov 18, 2010 at 11:28 PM, L. Mohan Arun mar...@gmail.com wrote: We have every right in the world to gather this data for analysis without any permission. It's public. No. You don't get to compile posts from a discussion forum into a product, under the idea that such posts are public domain. They are not. - Unless you own the forum or have a deal with the forum owner, and you stated in the TOS that all posts made in the forum can be repackaged commercially and only you have the right to do that. I am not saying this on my own, this is from one of the newsletters I receive, which covered this exact same topic, I would be happy to share the relevant text of the newsletter if someone is interested ... - - - Mohan Arun www.mohanarun.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Twitter + Gnip Partnership
Right. usage of the API is completely under Twitter control and TOS. I understand that. And yes, all of this is new and subject to litigation. Not worth the headache unless a rug was pulled out under and existing established business and agreement, which is probably only a few companies if any and I'm sure Twitter is working with them. On Fri, Nov 19, 2010 at 12:14 AM, Edward Hotchkiss edw...@edwardhotchkiss.com wrote: Well, they do have their ToS the law has so far placed in favor of usage of apps and apis regardless of ToS as long as it is legal. Yet, due to massive litigation. Best, -- Edward H. Hotchkiss http://www.edwardhotchkiss.com/ http://www.twitter.com/edwardhotchkiss/ -- On Nov 18, 2010, at 2:26 PM, Matthew Terenzio wrote: We have every right in the world to gather this data for analysis without any permission. It's public. Redistributing it will be subject to fair use and copyright law but not gathering it and making broad analysis. That is what search engines do and so far the courts have said they have a right to cache copies on their own servers, not for public display necessarily, but in order to better analyze it. Oddly, the courts landed on the right side for once, saying that the greater good of the utility of search was a societal need and, in this case, more important than minor infringements, if any, on the site's copyrights. On Wed, Nov 17, 2010 at 12:18 PM, Ryan Sarver rsar...@twitter.com wrote: Companies have leveraged Twitter’s open API to analyze and report on conversations and sentiment across the network since its inception. These products have been indispensable in helping brands, marketers and businesses engage with their customers on Twitter. This is an area we want to support more fully, and today we are excited to announce a partnership with Gnip to develop and market data products specifically for these analysis and non-display companies. Gnip will sublicense access to our public Tweets to developers interested in analyzing large amounts of Twitter data. Over the past year we have spoken with many companies and entrepreneurs throughout the ecosystem who need easier access to more data. In particular, companies building analysis and non-display products have asked us for greater volume and coverage. Our partnership with Gnip is built to address this need. Gnip will focus exclusively on creating products to meet the existing and emerging demands of companies creating non-display products. Check out Gnip’s blog to learn more and to see details about their initial Twitter data products: http://blog.gnip.com/gnip-twitter-partnership/. Many of you may wonder what this means for elevated access and whitelisting requests. Our default levels like Spritzer, Follow and Track will not be changing, and will remain free and available directly from Twitter. Companies and developers are encouraged to begin development with these free APIs, available at http://dev.twitter.com/pages/streaming_api. This does affect companies wishing to create products which analyze Tweets and do not display Tweets to end-users. Moving forward, we will begin to encourage these companies needing elevated access for analysis and non-display products to work with Gnip to find the right data products for their commercial needs. We’re excited about this partnership, and the support it offers the data analysis and non-display market. You can learn more about the details and Gnip by visiting http://gnip.com/twitter. Please let me know if you have any questions about how this affects you and your products. To contact Gnip: web: http://gnip.com email: i...@gnip.com twitter: http://twitter.com/gnip Best, Ryan -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter
Re: [twitter-dev] I found a good solution for PHP language detection in tweets
Hi Adam, Did you see this? I haven't tested it. Just was curious to look around after your post. http://stackoverflow.com/questions/1550950/detect-chinese-multibyte-character-in-the-string Matt Terenzio On Thu, Mar 24, 2011 at 10:50 AM, Adam Green 140...@gmail.com wrote: This has been a problem with collecting tweets from the API since I started working with it. My users only want English tweets and they view non-English tweets that I deliver to be a bug in my software. The lang=en argument in the search API only filters a small percentage of this, and I know of no way to do any filtering in the streaming API. I started working with the PHP library call LanguageDetect a few days ago, and it is doing a great job. http://pear.php.net/package/Text_LanguageDetect/ I tested it by filtering 40,000 recent tweets about @barackobama from my 2012twit.com site, and it found almost 20% of the tweets to be non- English. I screened the ones it found as non-English by hand, and found less than a 1% false positive rate. That means I lost 0.2% of the total flow to false positives to eliminate a 20% non-English rate. Pretty good for a solution that is small, about 2,500 lines of code, fast, open source, and free. I use it in my tweet parse phase of tweet collection. First I gather tweets into a MySQL cache with Phirehose, and then I parse the cached tweets into a normalized scheme. During this parsing phase I screen each tweet with LanguageDetect. The additional processing time of language detection is unnoticeable. The only limitation I found is that it doesn't detect Chinese or Japanese, but I think I can find other solutions for this. If anyone knows of a simple PHP detection algorithm for these languages, please let me know. - Adam Green Twitter API Developer http://2012twit.com http://140dev.com @140dev -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Is there a standard PHP linkify routine?
I've never looked at entities but I turn URLs into links using this: $linkedtext = ereg_replace([[:alpha:]]+://[^[:space:]]+[[:alnum:]/],a href=\\\0\\\0/a, $tweet['statustext']); On Tue, Jul 12, 2011 at 10:30 AM, Adam Green 140...@gmail.com wrote: Every PHP app that displays tweets needs to apply the entities as links. Is there a standard function for this available, or are hundreds of thousands of developers each rolling their own? If you have a favorite code snippet, please point it out here. Maybe we can all review them and figure out which is best. I'me specially interested in solving UTF8 character problems, which cause invalid link positioning. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] UserIDs to UserName - in bulk
Is there a way to turn a list of UserIDs into User Name / Profile information in one web service call? or feed? Or for 8000 followers do I need to make 8000 follow up web service calls? Thanks, Matt
Re: [twitter-dev] API response w/ IP
Thanks Scott. I'm making anonymous calls - nothing authenticated. Just pulling some profile/timeline info. -matthew On Sun, May 22, 2011 at 2:41 PM, Scott Wilcox sc...@dor.ky wrote: There is nothing provided by the API that can give you your own IP. Are you making OAuth authenticated calls? On 22 May 2011, at 18:18, matthewvb wrote: Is there a way to get the API to respond back with the IP address hitting it from the call? I'm running into a problem where something is eating away at my API hits / hour. I've put a simple script on a few isolated domains (non- Twitter calling ones) that are also having their API hits eaten up. They have unique IPs assigned to them - so I'm not sure if the problem is on my host's end and how they are showing my server to Twitter, or if it's something on the API end. -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] API response w/ IP
Currently, yes. I thought assigning a unique IP to the domain would solve the problem, but apparently not. I'm working on testing it on a VPS through the same host. On Sun, May 22, 2011 at 3:26 PM, Scott Wilcox sc...@dor.ky wrote: Thats what I was thinking, shared hosting provider? On 22 May 2011, at 20:24, Matthew Vanden Boogart wrote: Thanks Scott. I'm making anonymous calls - nothing authenticated. Just pulling some profile/timeline info. -matthew On Sun, May 22, 2011 at 2:41 PM, Scott Wilcox sc...@dor.ky wrote: There is nothing provided by the API that can give you your own IP. Are you making OAuth authenticated calls? On 22 May 2011, at 18:18, matthewvb wrote: Is there a way to get the API to respond back with the IP address hitting it from the call? I'm running into a problem where something is eating away at my API hits / hour. I've put a simple script on a few isolated domains (non- Twitter calling ones) that are also having their API hits eaten up. They have unique IPs assigned to them - so I'm not sure if the problem is on my host's end and how they are showing my server to Twitter, or if it's something on the API end. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] API response w/ IP
Thanks - I'm going to try out that option in my curl commands. Greatly appreciate the helps Scott. On Sun, May 22, 2011 at 3:34 PM, Scott Wilcox sc...@dor.ky wrote: Depends how they're routing the outbound traffic. You'll need to bind your calls to that IP. If its PHP and you're using CURL, I believe its CURLOPT_INTERFACE. On 22 May 2011, at 20:30, Matthew Vanden Boogart wrote: Currently, yes. I thought assigning a unique IP to the domain would solve the problem, but apparently not. I'm working on testing it on a VPS through the same host. On Sun, May 22, 2011 at 3:26 PM, Scott Wilcox sc...@dor.ky wrote: Thats what I was thinking, shared hosting provider? On 22 May 2011, at 20:24, Matthew Vanden Boogart wrote: Thanks Scott. I'm making anonymous calls - nothing authenticated. Just pulling some profile/timeline info. -matthew On Sun, May 22, 2011 at 2:41 PM, Scott Wilcox sc...@dor.ky wrote: There is nothing provided by the API that can give you your own IP. Are you making OAuth authenticated calls? On 22 May 2011, at 18:18, matthewvb wrote: Is there a way to get the API to respond back with the IP address hitting it from the call? I'm running into a problem where something is eating away at my API hits / hour. I've put a simple script on a few isolated domains (non- Twitter calling ones) that are also having their API hits eaten up. They have unique IPs assigned to them - so I'm not sure if the problem is on my host's end and how they are showing my server to Twitter, or if it's something on the API end. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
