[twitter-dev] Quota incorrectly displayed in Chrome and Opera - fine in IE and FF
Hi, I'm been developing a client-side app that uses basic HTTP Authentication into twitter.com. The problem is that when logging-in with a whitelisted account, the 20,000 quota is correctly reflected in the remaining hits as displayed on-site whilst using IE and FF, but in Chrome and Opera, the quota is back to 100 when logging in with the same account. You can see here: http://tr.im/iqLY Enter your username and password - immediately at top-right there will be a number - the remaining hits. It seems this quota is dependent on twitter detecting a whitelisted account, which is determined by the browser. Furthermore, http://twitter.com/account/rate_limit_status.json http://twitter.com/account/rate_limit_status.xml in the same browser, eg IE will display different results. Former ~2, latter 100 and across browser, sometimes the results for each are identical, ~100.
[twitter-dev] Re: Settings->Connections
Checked again this morning - after seeing robots on the home page and now link to logout (UI flaw) I cleared browser cookies and tried again. Now I see the connections tab and the one authenticated application for that account. On Apr 7, 5:11 pm, Mobasoft wrote: > I have another account, where I could not see the Connections tab, but > was able to navigate to the url. > I've also just granted OAuth access to that account and I still do not > see a Connections tab, and navigating to the connections url still > says, "No applications have been approved to use your account." > > I'll assume that it is a Twitter caching problem (which seems to have > been a bigger overall problem lately). > > If it shows up anytime soon, I'll add another reply here. > > Michael > > On Apr 7, 4:56 pm, Mobasoft wrote: > > > Robots. > > "Something is technically wrong. > > Thanks for noticing—we're going to fix it up and have things back to > > normal soon." > > > On Apr 7, 4:53 pm, Doug Williams wrote: > > > > Michael, > > > All of the API development team read this forum so it's the best place for > > > issues like this. As Chad replied, the connections tab is working for me > > > as > > > expected. Can you go into more detail about what you are seeing that seems > > > off? > > > > Doug Williams > > > Twitter API Supporthttp://twitter.com/dougw > > > > On Tue, Apr 7, 2009 at 2:43 PM, Chad Etzel wrote: > > > > > Working for me, and displaying all of the authorized apps I've used... > > > > -Chad > > > > > On Tue, Apr 7, 2009 at 5:41 PM, Mobasoft wrote: > > > > > > I understand that a lot of this OAuth development has been and out of > > > > > some flux lately, but is thathttps://twitter.com/account/connections > > > > > link working for anyone? > > > > > > If there is a more prominent place to ask Twitter dev team directly, > > > > > please inform me. > > > > > > Thanks, > > > > > > Michael
[twitter-dev] Re: VB.net auh failure [403]
I confirmed this is still happening by tracing with wireshark last
night; so my expectation for preauthenticate was wrong as it doesn't
stop the initial grab for authentication flavor; setting the header
yourself does the trick for that first call.
On Apr 8, 2:21 am, James Deville wrote:
> Almost. request.PreAuthenticate still sends a double request the first time.
> Behind corporate firewalls (where multiple clients may be getting aggregated
> to one IP address), you can still hit the unauth'ed rate limit.
>
> I'll try tomorrow at work (where I can usually repro the above situation)
> and report back.
>
> JD
>
> On Tue, Apr 7, 2009 at 11:29 AM, Dimebrain wrote:
>
> > Isn't request.PreAuthenticate = true functionally equivalent to adding
> > the credentials manually to avoid the double calls?
>
> > On Apr 5, 1:21 am, James Deville wrote:
> > > Look at what requests you are sending with Netmon or Wireshark. With
> > Witty
> > > (C# wpf app), we discovered that first an unauthenticated request is sent
> > to
> > > find out what auth the server takes, then a authenticated request after
> > > that. This doesn't work on some of the API requests. The solution is to
> > > manually attach the BasicAuth header.
>
> > > JD
>
> > > On Sat, Apr 4, 2009 at 11:38 AM, DIENECES
> > wrote:
>
> > > > Any idea why I'm forbidden?
> > > > Thanks in advance!
> > > > Function writeMessage(ByVal StrPass, ByVal StrUser, ByVal StrMessage,
> > > > ByVal StrTo) As String
> > > > Dim req As System.Net.HttpWebRequest =
> > > > System.Net.HttpWebRequest.Create("http://twitter.com/direct_messages/
> > > > new.xml?user= " +
> > > > StrTo + "&text=" + StrMessage)
> > > > If Not StrUser = "" Or StrPass = "" Then
> > > > req.Credentials = New System.Net.NetworkCredential
> > > > (StrUser, StrPass)
> > > > req.Method = "POST"
> > > > 'req.ContentLength = 0
> > > > 'req.ServicePoint.Expect100Continue = False
> > > > req.ContentType = "application/x-www-form-urlencoded"
> > > > 'req.PreAuthenticate = True
> > > > Dim resp As HttpWebResponse = req.GetResponse()
> > > > Dim sr As New System.IO.StreamReader(resp.GetResponseStream
> > > > ())
> > > > 'sr.Read(req.GetResponse(), )
> > > > Return sr.ReadToEnd()
> > > > End If
>
> > > > End Function
[twitter-dev] OAuth/authorize "Sign out" link
When an application sends the visitor over to Twitter for authroiziation, via https://twitter.com/oauth/authorize , the Sign out link no longer works. It was working fine a few days ago.
[twitter-dev] Re: OAuth/authorize "Sign out" link
http://code.google.com/p/twitter-api/issues/detail?id=422 On Wed, Apr 8, 2009 at 07:29, Mobasoft wrote: > > When an application sends the visitor over to Twitter for > authroiziation, via https://twitter.com/oauth/authorize , the Sign out > link no longer works. It was working fine a few days ago. -- Abraham Williams | Hacker | http://abrah.am @poseurtech | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Tipjoy opens Twitter Payments API, celebrates with an API Contest
Hi Folks, Tipjoy's Twitter Payments have been really successful for P2P and charitable payments. Now we've released an API for Twitter applications to do payments over Twitter: http://tipjoy.com/api Because Twitter is a broadcast platform, these payments are social. That's very valuable. A microgiving cause gets the benefit of all the user's followers seeing the payment. A premium twitter app paid using Tipjoy gets a free advertisement on Twitter. It's not an orchestrated "social media marketing" effort - it's real people actually using your service. Here is a tutorial: http://tipjoy.com/twitterApps We're holding an API contest to celebrate the API release. We'll be giving away lots of schwag and our favorite app will win a MacBook Air. Contest details are here: http://tipjoy.com/APIcontest By the way, the API uses a Twitter username & password for authorization. I'm hacking together something to give all the OAuth applications some love. I'll post here when it's ready. I'd love to hear what you all think! Best, Ivan http://tipjoy.com/twitter http://twitter.com/ikirigin
[twitter-dev] Re: Tipjoy opens Twitter Payments API, celebrates with an API Contest
100% pure awesome. And then some. Thanks- - Andy Badera - and...@badera.us - Google me: http://www.google.com/search?q=andrew+badera Sent from Albany, NY, United States On Wed, Apr 8, 2009 at 9:27 AM, Ivan wrote: > > Hi Folks, > > Tipjoy's Twitter Payments have been really successful for P2P and > charitable payments. Now we've released an API for Twitter > applications to do payments over Twitter: > http://tipjoy.com/api > > Because Twitter is a broadcast platform, these payments are social. > That's very valuable. A microgiving cause gets the benefit of all the > user's followers seeing the payment. A premium twitter app paid using > Tipjoy gets a free advertisement on Twitter. It's not an orchestrated > "social media marketing" effort - it's real people actually using your > service. > > Here is a tutorial: > http://tipjoy.com/twitterApps > > We're holding an API contest to celebrate the API release. We'll be > giving away lots of schwag and our favorite app will win a MacBook > Air. Contest details are here: > http://tipjoy.com/APIcontest > > By the way, the API uses a Twitter username & password for > authorization. I'm hacking together something to give all the OAuth > applications some love. I'll post here when it's ready. > > I'd love to hear what you all think! > > Best, > Ivan > http://tipjoy.com/twitter > http://twitter.com/ikirigin >
[twitter-dev] Re: Tipjoy opens Twitter Payments API, celebrates with an API Contest
Great, now Nigerian royalty can use Twitter to get their millions of secret dollars out of their country, with the aid of Twitter users help! (lol) Or, the first rogue Twitter app. that tweets a Tipjoy payment message from the user who gives up their username/password to the rogue app. It'd be a Tipjoy mugging! At least Tipjoy lets you cancel transactions that aren't paid for yet. But, if you pre-charge your account, and the money is sent from the account, and the recipient has enough to cash out to a PayPal account ... before the transaction is cancelled ... what happens? Sounds so very dangerous. On 4/8/09 9:27 AM, Ivan wrote: Hi Folks, Tipjoy's Twitter Payments have been really successful for P2P and charitable payments. Now we've released an API for Twitter applications to do payments over Twitter: http://tipjoy.com/api -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
[twitter-dev] Re: OAuth/authorize "Sign out" link
Thanks, I'll check there first from now on. Appreciate it. On Apr 8, 7:38 am, Abraham Williams <4bra...@gmail.com> wrote: > http://code.google.com/p/twitter-api/issues/detail?id=422 > > On Wed, Apr 8, 2009 at 07:29, Mobasoft wrote: > > > When an application sends the visitor over to Twitter for > > authroiziation, viahttps://twitter.com/oauth/authorize, the Sign out > > link no longer works. It was working fine a few days ago. > > -- > Abraham Williams | Hacker |http://abrah.am > @poseurtech |http://the.hackerconundrum.com > Web608 | Community Evangelist |http://web608.org > This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Added to Twitter API Wiki - Developers
Hi, I'd like to be added to Twitter API Wiki, Developers - http://apiwiki.twitter.com/Developers Twitter User: Spdyme Web Site: http://www.safedatatech.com I am the author of http://Spdy.me (Link Shortening, Bookmarklet, Web Widget). I have experience working with PHP / MySQL / JS / Ajax / HTML / CSS / .NET / SQL Server, Twitter API w/ oAuth. Located in Jupiter, FL.
[twitter-dev] Re: OAuth question
Hi Derek, Abraham posted some stuff to this group a little while ago with a PHP Twitter OAuth library. That sounds like just what you're looking for. Checkout http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d7aad614a764afc7 Thanks; — Matt Sanford / @mzsanford On Apr 7, 2009, at 09:50 PM, Derek Gathright wrote: So I'm able to authenticate & receive the OAuth tokens, but I've yet to find any documentation on what exactly do with them after they're stored. So, instead of providing HTTP basic auth info, what specifically do I pass along with my request to say... update the user's status? Any PHP code examples that show full client support (found one or two that just do 1 call, such as... user->get_info). Thanks.
[twitter-dev] Re: OAuth in a WordPress Plugin
Comments inline: On Apr 7, 2009, at 10:24 PM, redwall_hp wrote: I'm planning out a WordPress plugin that will make use of the Twitter API (which I have experience with). I'd like to avoid using basic HTTP authentication if I can, in favor of OAuth. I've been doing some reading on OAuth, and I think I get the general idea, though I haven't tried any experiments with it yet. I'm left wondering about a few things though. 1. As I'm developing a WordPress plugin, many different people will be using it on many different servers. How do I handle application registration with Twitter? Do I register an application under the name of the plugin, and then hook that into the plugin? Or would each user of the plugin have to go and register their blog as an application and do some setup with the plugin? If this is a read-only application you could register it once and have all sites effectively act as the same application. This increases the ease of installation but runs the risk of all sites breaking if one user misbehaves enough that we have to suspend the application. For applications with write access I wouldn't recommend distributing the key/secret since each site would likely want their own source name (e.g. "from Matt's Blog"). In that case you would need to leave the token and secret blank and have each installation register themselves. 2. How are API limits handled with OAuth? What are the differences (if any)? Are the API limits logged by IP, by the user authenticating, or to the application? There is a bug right now waiting to be fixed but after that it will work just like Basic Auth does. By user when authenticated, by IP address when not. Thanks; — Matt Sanford / @mzsanford
[twitter-dev] Re: Freelance Twitter API Dev directory?
I'm requesting to be added to the list. Real Name: Michael Bailey Twitter Username(s): @mobasoft, @mobatalk, @mychingo, @redbox, @tagbucket email: mobat...@gmail.com Freelance developer/engineer/analyst/architect based in Independence, Missouri. Prior life experience on the Microsoft side of the road, ASP, SQL, HTML, OWL, C++ more recently crossed the road to open-source, PHP, Linux, Apache, MySQL, jquery, mootools. AJAX from both sides (since back in the days when we called it RemoteScripting). Creator/Developer/Maintainer of MyChingo.com, MobaTalk.com, and occasionally blogging on Mobasoft.com Thanks, Michael
[twitter-dev] Re: Tipjoy opens Twitter Payments API, celebrates with an API Contest
>>the recipient has enough to cash out to a PayPal account ... before the >>transaction is cancelled ... what happens? We audit every cash out, so this step isn't fully automated. It's hard to "take the money and run" Also, we track transactions across the site. As you can imagine with micropayments, any wholesale fraud would require lots of transactions or amounts much larger than the median to make any real money. This makes fraud detection easier. If anyone sees any transactions that are faulty, they can let us know. We already actively block many IPs and domains because of link spam, and expect to do the same for fraudsters too. Best, Ivan http://tipjoy.com On Apr 8, 9:52 am, Dossy Shiobara wrote: > Great, now Nigerian royalty can use Twitter to get their millions of > secret dollars out of their country, with the aid of Twitter users help! > (lol) > > Or, the first rogue Twitter app. that tweets a Tipjoy payment message > from the user who gives up their username/password to the rogue app. > It'd be a Tipjoy mugging! > > At least Tipjoy lets you cancel transactions that aren't paid for yet. > But, if you pre-charge your account, and the money is sent from the > account, and the recipient has enough to cash out to a PayPal account > ... before the transaction is cancelled ... what happens? > > Sounds so very dangerous. > > On 4/8/09 9:27 AM, Ivan wrote: > > > Hi Folks, > > > Tipjoy's Twitter Payments have been really successful for P2P and > > charitable payments. Now we've released an API for Twitter > > applications to do payments over Twitter: > >http://tipjoy.com/api > > -- > Dossy Shiobara | do...@panoptic.com |http://dossy.org/ > Panoptic Computer Network |http://panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70)
[twitter-dev] Extended user information element contains element, too. is it expected?
Hi, According to the REST API Doc, an "Extended user information element" doesn't contain a element. But actually the API returns a user element with one status element. Is it a doc bug? Here is the trace log grabbed just several minutes ago. -- [Thu Apr 09 00:12:41 JST 2009]GET http://twitter.com/account/verify_credentials.xml [Thu Apr 09 00:12:41 JST 2009]Response code: 200 [Thu Apr 09 00:12:41 JST 2009]Response: 6358482 twit4j twit4j location:0.5515412761891139 http://static.twitter.com/images/ default_profile_normal.png false 3 9ae4e8 00 ff e0ff92 87bc44 2 Sun May 27 09:52:09 + 2007 0 -32400 Alaska http://static.twitter.com/images/ themes/theme1/bg.gif false 620 false false Mon Apr 06 16:34:02 + 2009 1463787270 4/7:id1 Twitter4J false false -- Cheers, Yusuke
[twitter-dev] Re: Tipjoy opens Twitter Payments API, celebrates with an API Contest
Hi Ivan, This looks quite interesting. I do have one concern, though. On the main tipjoy.com site, you have a prominent banner saying "click here to sign up in 5 seconds without giving us your password." ...which then leads to the OAuth sign-in. The Tipjoy API requires a twitter user/pass combo for authentication. If I am User A who already has created an account on Tipjoy using OAuth, and now I see another 3rd party application asking for my twitter user/pass to interact with Tipjoy, I am going to be very concerned that this other app is trying to scam me. I guess it just looks like a conflicting message to me. I know you said you are "hacking" something together for OAuth apps, so maybe this concern is unnecessary, but wanted to give you that feedback as a potential user of this system. As a developer, the API looks very interesting. I don't know how many people would actually want to tie their twitter account to actual money transactions, but I guess there's only one way to find out... Congrats on the API launch, -Chad On Wed, Apr 8, 2009 at 10:57 AM, Ivan Kirigin wrote: > >>>the recipient has enough to cash out to a PayPal account ... before the >>>transaction is cancelled ... what happens? > > We audit every cash out, so this step isn't fully automated. It's hard > to "take the money and run" > > Also, we track transactions across the site. As you can imagine with > micropayments, any wholesale fraud would require lots of transactions > or amounts much larger than the median to make any real money. This > makes fraud detection easier. > > If anyone sees any transactions that are faulty, they can let us know. > We already actively block many IPs and domains because of link spam, > and expect to do the same for fraudsters too. > > Best, > Ivan > http://tipjoy.com > > > On Apr 8, 9:52 am, Dossy Shiobara wrote: >> Great, now Nigerian royalty can use Twitter to get their millions of >> secret dollars out of their country, with the aid of Twitter users help! >> (lol) >> >> Or, the first rogue Twitter app. that tweets a Tipjoy payment message >> from the user who gives up their username/password to the rogue app. >> It'd be a Tipjoy mugging! >> >> At least Tipjoy lets you cancel transactions that aren't paid for yet. >> But, if you pre-charge your account, and the money is sent from the >> account, and the recipient has enough to cash out to a PayPal account >> ... before the transaction is cancelled ... what happens? >> >> Sounds so very dangerous. >> >> On 4/8/09 9:27 AM, Ivan wrote: >> >> > Hi Folks, >> >> > Tipjoy's Twitter Payments have been really successful for P2P and >> > charitable payments. Now we've released an API for Twitter >> > applications to do payments over Twitter: >> >http://tipjoy.com/api >> >> -- >> Dossy Shiobara | do...@panoptic.com |http://dossy.org/ >> Panoptic Computer Network |http://panoptic.com/ >> "He realized the fastest way to change is to laugh at your own >> folly -- then you can let go and quickly move on." (p. 70)
[twitter-dev] Re: Extended user information element contains element, too. is it expected?
Not sure if it is expected or not (or if the doc is out of sync), but I would say having the last status included w/ the user object is very handy. -Chad On Wed, Apr 8, 2009 at 11:20 AM, Yusuke wrote: > > Hi, > > According to the REST API Doc, an "Extended user information element" > doesn't contain a element. > But actually the API returns a user element with one status element. > Is it a doc bug? > > Here is the trace log grabbed just several minutes ago. > -- > [Thu Apr 09 00:12:41 JST 2009]GET > http://twitter.com/account/verify_credentials.xml > [Thu Apr 09 00:12:41 JST 2009]Response code: 200 > [Thu Apr 09 00:12:41 JST 2009]Response: encoding="UTF-8"?> > > 6358482 > twit4j > twit4j > location:0.5515412761891139 > > http://static.twitter.com/images/ > default_profile_normal.png > > false > 3 > 9ae4e8 > 00 > ff > e0ff92 > 87bc44 > 2 > Sun May 27 09:52:09 + 2007 > 0 > -32400 > Alaska > http://static.twitter.com/images/ > themes/theme1/bg.gif > false > 620 > false > false > > Mon Apr 06 16:34:02 + 2009 > 1463787270 > 4/7:id1 > Twitter4J > false > > > false > > > > -- > > Cheers, > Yusuke
[twitter-dev] Re: Extended user information element contains element, too. is it expected?
It is documented that Basic user information element contains status element. So *Extended* user information element supposed to contain status element, too. But it's not documented. I'm developing Twitter4J - a Java wrapper for the API and need to ensure that. Thanks in advance, Yusuke On 4月9日, 午前12:23, Chad Etzel wrote: > Not sure if it is expected or not (or if the doc is out of sync), but > I would say having the last status included w/ the user object is very > handy. > -Chad > > On Wed, Apr 8, 2009 at 11:20 AM, Yusuke wrote: > > > Hi, > > > According to the REST API Doc, an "Extended user information element" > > doesn't contain a element. > > But actually the API returns a user element with one status element. > > Is it a doc bug? > > > Here is the trace log grabbed just several minutes ago. > > -- > > [Thu Apr 09 00:12:41 JST > > 2009]GEThttp://twitter.com/account/verify_credentials.xml > > [Thu Apr 09 00:12:41 JST 2009]Response code: 200 > > [Thu Apr 09 00:12:41 JST 2009]Response: > encoding="UTF-8"?> > > > > 6358482 > > twit4j > > twit4j > > location:0.5515412761891139 > > > > http://static.twitter.com/images/ > > default_profile_normal.png > > > > false > > 3 > > 9ae4e8 > > 00 > > ff > > e0ff92 > > 87bc44 > > 2 > > Sun May 27 09:52:09 + 2007 > > 0 > > -32400 > > Alaska > > http://static.twitter.com/images/ > > themes/theme1/bg.gif > > false > > 620 > > false > > false > > > >Mon Apr 06 16:34:02 + 2009 > >1463787270 > >4/7:id1 > >Twitter4J > >false > > > > > >false > > > > > > > > -- > > > Cheers, > > Yusuke
[twitter-dev] Re: Tipjoy opens Twitter Payments API, celebrates with an API Contest
That's an interesting point, Chad. My basic assumption is that "normal" people don't know what the hell OAuth is. They're used to giving out passwords. If clicking a banner makes it work, they're happy. I figured the 3rd party apps would already be using a Twitter password. So they aren't asking for a password to work with Tipjoy, but with their service. For example, an iphone twitter client could, say, turn off ads by making a Tipjoy payment. The Tipjoy account creation, payment, balance extraction, and other API calls would all just use the Twitter password already stored in the client. "It just works*" This is a bit different for applications that sell content, that might want to start selling over Twitter. if http://popcuts.com started using Tipjoy to sell mp3s over twitter, they would need to ask for the Twitter password just to use Tipjoy. Then this concern is valid. Either way, I hope to have the OAuth solution in place this week. No need to keep it a secret: we plan on allowing for a authorization_url param that is an OAuth signed call to http://twitter.com/account/verify_credentials.json We'd verify the call with Twitter, then proceed like we have a twitter password. This call won't work though, because we'd need to update the user's status http://tipjoy.com/api/#creating_twitter_payment We'll enable a work-around by posting the tweet, and calling that endpoint with an id of a tweet already posted. That should all work, right? Thanks! Ivan http://tipjoy.com *ymmv On Apr 8, 11:21 am, Chad Etzel wrote: > Hi Ivan, > > This looks quite interesting. I do have one concern, though. > > On the main tipjoy.com site, you have a prominent banner saying "click > here to sign up in 5 seconds without giving us your password." > ...which then leads to the OAuth sign-in. > > The Tipjoy API requires a twitter user/pass combo for authentication. > If I am User A who already has created an account on Tipjoy using > OAuth, and now I see another 3rd party application asking for my > twitter user/pass to interact with Tipjoy, I am going to be very > concerned that this other app is trying to scam me. > > I guess it just looks like a conflicting message to me. > > I know you said you are "hacking" something together for OAuth apps, > so maybe this concern is unnecessary, but wanted to give you that > feedback as a potential user of this system. > > As a developer, the API looks very interesting. I don't know how many > people would actually want to tie their twitter account to actual > money transactions, but I guess there's only one way to find out... > > Congrats on the API launch, > -Chad > > On Wed, Apr 8, 2009 at 10:57 AM, Ivan Kirigin wrote: > > >>>the recipient has enough to cash out to a PayPal account ... before the > >>>transaction is cancelled ... what happens? > > > We audit every cash out, so this step isn't fully automated. It's hard > > to "take the money and run" > > > Also, we track transactions across the site. As you can imagine with > > micropayments, any wholesale fraud would require lots of transactions > > or amounts much larger than the median to make any real money. This > > makes fraud detection easier. > > > If anyone sees any transactions that are faulty, they can let us know. > > We already actively block many IPs and domains because of link spam, > > and expect to do the same for fraudsters too. > > > Best, > > Ivan > >http://tipjoy.com > > > On Apr 8, 9:52 am, Dossy Shiobara wrote: > >> Great, now Nigerian royalty can use Twitter to get their millions of > >> secret dollars out of their country, with the aid of Twitter users help! > >> (lol) > > >> Or, the first rogue Twitter app. that tweets a Tipjoy payment message > >> from the user who gives up their username/password to the rogue app. > >> It'd be a Tipjoy mugging! > > >> At least Tipjoy lets you cancel transactions that aren't paid for yet. > >> But, if you pre-charge your account, and the money is sent from the > >> account, and the recipient has enough to cash out to a PayPal account > >> ... before the transaction is cancelled ... what happens? > > >> Sounds so very dangerous. > > >> On 4/8/09 9:27 AM, Ivan wrote: > > >> > Hi Folks, > > >> > Tipjoy's Twitter Payments have been really successful for P2P and > >> > charitable payments. Now we've released an API for Twitter > >> > applications to do payments over Twitter: > >> >http://tipjoy.com/api > > >> -- > >> Dossy Shiobara | do...@panoptic.com |http://dossy.org/ > >> Panoptic Computer Network |http://panoptic.com/ > >> "He realized the fastest way to change is to laugh at your own > >> folly -- then you can let go and quickly move on." (p. 70)
[twitter-dev] Re: Tipjoy opens Twitter Payments API, celebrates with an API Contest
On Wed, Apr 8, 2009 at 11:32 AM, Ivan Kirigin wrote: > My basic assumption is that "normal" people don't know what the hell > OAuth is. They're used to giving out passwords. Right, and OAuth is (at least) supposed to help curb that behavior (imho). It does sound like you have been thinking a lot about an OAuth solution, so thanks for that effort. I'm not knocking your API work, I'm just in the paranoid minority :) -Chad > On Apr 8, 11:21 am, Chad Etzel wrote: >> Hi Ivan, >> >> This looks quite interesting. I do have one concern, though. >> >> On the main tipjoy.com site, you have a prominent banner saying "click >> here to sign up in 5 seconds without giving us your password." >> ...which then leads to the OAuth sign-in. >> >> The Tipjoy API requires a twitter user/pass combo for authentication. >> If I am User A who already has created an account on Tipjoy using >> OAuth, and now I see another 3rd party application asking for my >> twitter user/pass to interact with Tipjoy, I am going to be very >> concerned that this other app is trying to scam me. >> >> I guess it just looks like a conflicting message to me. >> >> I know you said you are "hacking" something together for OAuth apps, >> so maybe this concern is unnecessary, but wanted to give you that >> feedback as a potential user of this system. >> >> As a developer, the API looks very interesting. I don't know how many >> people would actually want to tie their twitter account to actual >> money transactions, but I guess there's only one way to find out... >> >> Congrats on the API launch, >> -Chad >> >> On Wed, Apr 8, 2009 at 10:57 AM, Ivan Kirigin wrote: >> >> >>>the recipient has enough to cash out to a PayPal account ... before the >> >>>transaction is cancelled ... what happens? >> >> > We audit every cash out, so this step isn't fully automated. It's hard >> > to "take the money and run" >> >> > Also, we track transactions across the site. As you can imagine with >> > micropayments, any wholesale fraud would require lots of transactions >> > or amounts much larger than the median to make any real money. This >> > makes fraud detection easier. >> >> > If anyone sees any transactions that are faulty, they can let us know. >> > We already actively block many IPs and domains because of link spam, >> > and expect to do the same for fraudsters too. >> >> > Best, >> > Ivan >> >http://tipjoy.com >> >> > On Apr 8, 9:52 am, Dossy Shiobara wrote: >> >> Great, now Nigerian royalty can use Twitter to get their millions of >> >> secret dollars out of their country, with the aid of Twitter users help! >> >> (lol) >> >> >> Or, the first rogue Twitter app. that tweets a Tipjoy payment message >> >> from the user who gives up their username/password to the rogue app. >> >> It'd be a Tipjoy mugging! >> >> >> At least Tipjoy lets you cancel transactions that aren't paid for yet. >> >> But, if you pre-charge your account, and the money is sent from the >> >> account, and the recipient has enough to cash out to a PayPal account >> >> ... before the transaction is cancelled ... what happens? >> >> >> Sounds so very dangerous. >> >> >> On 4/8/09 9:27 AM, Ivan wrote: >> >> >> > Hi Folks, >> >> >> > Tipjoy's Twitter Payments have been really successful for P2P and >> >> > charitable payments. Now we've released an API for Twitter >> >> > applications to do payments over Twitter: >> >> >http://tipjoy.com/api >> >> >> -- >> >> Dossy Shiobara | do...@panoptic.com |http://dossy.org/ >> >> Panoptic Computer Network |http://panoptic.com/ >> >> "He realized the fastest way to change is to laugh at your own >> >> folly -- then you can let go and quickly move on." (p. 70)
[twitter-dev] Search API Refresh Rate
Hello! I'm developing an application which needs to constantly request a search API result. I'm pushing through a since_id to try to help minimise the load on the servers. My question is, what is the optimum time limit to loop the API requests? My application will need to act upon the result of the search pretty much instantly. I currently have the script requesting a search API result every 5 seconds. Will this hammer your servers too much? Do you know the average time third party clients reload tweets? Are there any guidelines for this? As this would have a factor in when my applications actions are seen and so the need to request a search result refresh Thanks, Pete
[twitter-dev] Re: Freelance Twitter API Dev directory?
Alex, If you could please add my details to the list of Twitter API Developers: Name: Peter Hough Twitter: http://twitter.com/peterhough Website: http://www.peterhough.co.uk Email: http://scr.im/peterhough Portfolio: http://twitrand.com Many thanks, Pete On Feb 23, 7:33 pm, Alex Payne wrote: > There isn't one that I'm aware of, but if people would like to post > their contact info in this thread (Twitter username, URL, email, > whatever) I'm happy to collect them on the API Wiki. > > On Sat, Feb 21, 2009 at 18:00, Chad Etzel wrote: > > > Hi All, > > > I have been getting a few requests here and there for twitter API > > development work. I cannot take on any such projects at the moment, > > but I always feel bad for leaving them in the lurch. Is there a list > > or directory anywhere of Twitter API developers that work freelance > > that I can send to them when this happens? I'm happy to forward on > > such requests. > > > -Chad > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: VB.net auh failure [403]
I have a draft written, I'm going to compile and debug tonight. I'll
post my code and/or dll when I'm finished.
On Apr 8, 7:09 am, Dimebrain wrote:
> I confirmed this is still happening by tracing with wireshark last
> night; so my expectation for preauthenticate was wrong as it doesn't
> stop the initial grab for authentication flavor; setting the header
> yourself does the trick for that first call.
>
> On Apr 8, 2:21 am, James Deville wrote:
>
>
>
> > Almost. request.PreAuthenticate still sends a double request the first time.
> > Behind corporate firewalls (where multiple clients may be getting aggregated
> > to one IP address), you can still hit the unauth'ed rate limit.
>
> > I'll try tomorrow at work (where I can usually repro the above situation)
> > and report back.
>
> > JD
>
> > On Tue, Apr 7, 2009 at 11:29 AM, Dimebrain wrote:
>
> > > Isn't request.PreAuthenticate = true functionally equivalent to adding
> > > the credentials manually to avoid the double calls?
>
> > > On Apr 5, 1:21 am, James Deville wrote:
> > > > Look at what requests you are sending with Netmon or Wireshark. With
> > > Witty
> > > > (C# wpf app), we discovered that first an unauthenticated request is
> > > > sent
> > > to
> > > > find out what auth the server takes, then a authenticated request after
> > > > that. This doesn't work on some of the API requests. The solution is to
> > > > manually attach the BasicAuth header.
>
> > > > JD
>
> > > > On Sat, Apr 4, 2009 at 11:38 AM, DIENECES
> > > wrote:
>
> > > > > Any idea why I'm forbidden?
> > > > > Thanks in advance!
> > > > > Function writeMessage(ByVal StrPass, ByVal StrUser, ByVal StrMessage,
> > > > > ByVal StrTo) As String
> > > > > Dim req As System.Net.HttpWebRequest =
> > > > > System.Net.HttpWebRequest.Create("http://twitter.com/direct_messages/
> > > > > new.xml?user= " +
> > > > > StrTo + "&text=" + StrMessage)
> > > > > If Not StrUser = "" Or StrPass = "" Then
> > > > > req.Credentials = New System.Net.NetworkCredential
> > > > > (StrUser, StrPass)
> > > > > req.Method = "POST"
> > > > > 'req.ContentLength = 0
> > > > > 'req.ServicePoint.Expect100Continue = False
> > > > > req.ContentType = "application/x-www-form-urlencoded"
> > > > > 'req.PreAuthenticate = True
> > > > > Dim resp As HttpWebResponse = req.GetResponse()
> > > > > Dim sr As New System.IO.StreamReader(resp.GetResponseStream
> > > > > ())
> > > > > 'sr.Read(req.GetResponse(), )
> > > > > Return sr.ReadToEnd()
> > > > > End If
>
> > > > > End Function- Hide quoted text -
>
> - Show quoted text -
[twitter-dev] Tweet Corpus creation for NLP research
I am interested to do something deeper than the surface-level processing of a user's incoming tweets. For this, I will need to create a corpus of the user's friends_timeline over, say, past one month or any computationally feasible period. Basically, a large enough set of, say, 1-100 Million tweets for someone following 100-1000 people. It would be only a one-time download, as afterwards, incremental downloads should suffice. This would translate into 100MB-10 GB of download for a user. It could be less for people following less or less-active people. Does Twitter API provide support for such corpus creation ? It could be very helpful for Natural Language Processing research if Twitter creates some sample corpus of public_timeline or some selected user's timelines. Looking forward to some help in this regard. Thanks
[twitter-dev] Re: A Twitter Query Language (TQL) ?
Hi Alex
I just want to bring up this topic since we are in the process of
developing a structured query language for Twitter API for our app.
Just want to know is Twitter has intend to go this direction, it's
good for us to know and instead of duplicating efforts in making
Twitter API better! Thanks!
Khang
On Mar 23, 2:40 pm, Alex Payne wrote:
> Thanks for the feedback.
>
>
>
> On Sun, Mar 22, 2009 at 20:46, Zac Bowling wrote:
>
> > If it was built and twitter charged something similar to the rate that
> > Amazon's SimpleDB charges for processing power required to preform the
> >query, I would gladly pay.
>
> > Zac Bowling
>
> > On Sun, Mar 22, 2009 at 7:14 PM, Zac Bowling wrote:
> >> There was the one I mentioned in my first email that was a bridge with
> >> MSSQL (Tweet-SQL) but that is nothing more then a bunch of managed
> >> (written in c#) stored procedure calls for MSSQL 2005 which maybe what
> >> you are thinking of. That's not really anything close to what I'm
> >> looking for.
>
> >> It doesn't even have to be SQL like but just a some kind of structured
> >>querylanguage for twitter. That would be awesome.
>
> >> Zac Bowling
>
> >> On Sun, Mar 22, 2009 at 4:49 PM, Abraham Williams <4bra...@gmail.com>
> >> wrote:
> >>> I'm positive that a third party was providing a tql api for their database
> >>> of tweets and that it was announced on this list but now searching returns
> >>> nothing. Does anybody else remember this? Maybe it was a dream...
>
> >>> On Sun, Mar 22, 2009 at 15:28, Zac Bowling wrote:
>
> I would love it if Twitter would develop an equivalent to Facebook's
> FQL, Yahoo's YQL, Amazon's SimpleDB, or Google's GQL (used for app
> engine data storage).
>
> Basically an abstracted SQL-likequeryengine for doing queries and
> getting back data the data you want using virtual tables of different
> data twitter serves up.
>
> You could do something basic like:
>
> SELECT StatusID, UserID, Text FROM StatusUpdates as S
> WHERE
> S.UserID in (SELECT UserID FROM SocialGraph WHERE FollowerUseringID
> = MYUSERID) and
> S.StatusID > LASTID
> ORDER BY S.StatusID DESC
> LIMIT 200
>
> to get a basic user's following timeline or whatever. From there you
> can build on from that and get a bit more complex.
>
> It could even build on from justquerysyntax to modify and destructive
> calls.
>
> Maybe something like:
> DELETE FROM StatusUpdates WHERE StatusID = 200102;
>
> or:
> INSERT INTO StatusUpdates(text,replyToStatusID,replyToUserID) VALUES
> ('@johnsmith hello',123601020,235133);
>
> or:
> UPDATE StatusUpdates SET favorite = TRUE WHERE StatusID = 123601020;
>
> You could do it where you do an HTTP get/post with aquerylike above
> to twitter's rest api, and the results could come back as JSON or XML
> or whatever.
>
> Some concepts like this could be done in a local side wrapper (like
> I've seen a SQL bridge for MSSQL for twitter on here a while back) but
> it would be awesome if these were processed twitter server side. If
> done right, it can save on overhead on both twitter and from the
> client side.
>
> Like in one case I have where I'm hitting the following timeline, I'm
> missing something out of the user structure that you get back from
> that, so I turn around and do another user call on user for each tweet
> to get that data. Half the data I get back in both cases don't use on
> both calls but it would be awesome to be able to get that data in one
> call.
>
> A lot to consider around optimization and limits and a bit of work to
> build it but I think something like that would be really useful.
>
> Zac
>
> >>> --
> >>> Abraham Williams |http://the.hackerconundrum.com
> >>> Web608 | Community Evangelist |http://web608.org
> >>> This email is: [ ] blogable [x] ask first [ ] private.
> >>> Sent from: Madison WI United States.
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: A Twitter Query Language (TQL) ?
This is not a priority internally so we would love to see you create one
yourself. If anything, it could give us some ideas of what we may want to
adopt in the future.
Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Wed, Apr 8, 2009 at 9:00 AM, Khang Toh wrote:
>
> Hi Alex
>
> I just want to bring up this topic since we are in the process of
> developing a structured query language for Twitter API for our app.
> Just want to know is Twitter has intend to go this direction, it's
> good for us to know and instead of duplicating efforts in making
> Twitter API better! Thanks!
>
> Khang
>
> On Mar 23, 2:40 pm, Alex Payne wrote:
> > Thanks for the feedback.
> >
> >
> >
> > On Sun, Mar 22, 2009 at 20:46, Zac Bowling wrote:
> >
> > > If it was built and twitter charged something similar to the rate that
> > > Amazon's SimpleDB charges for processing power required to preform the
> > >query, I would gladly pay.
> >
> > > Zac Bowling
> >
> > > On Sun, Mar 22, 2009 at 7:14 PM, Zac Bowling
> wrote:
> > >> There was the one I mentioned in my first email that was a bridge with
> > >> MSSQL (Tweet-SQL) but that is nothing more then a bunch of managed
> > >> (written in c#) stored procedure calls for MSSQL 2005 which maybe what
> > >> you are thinking of. That's not really anything close to what I'm
> > >> looking for.
> >
> > >> It doesn't even have to be SQL like but just a some kind of structured
> > >>querylanguage for twitter. That would be awesome.
> >
> > >> Zac Bowling
> >
> > >> On Sun, Mar 22, 2009 at 4:49 PM, Abraham Williams <4bra...@gmail.com>
> wrote:
> > >>> I'm positive that a third party was providing a tql api for their
> database
> > >>> of tweets and that it was announced on this list but now searching
> returns
> > >>> nothing. Does anybody else remember this? Maybe it was a dream...
> >
> > >>> On Sun, Mar 22, 2009 at 15:28, Zac Bowling
> wrote:
> >
> > I would love it if Twitter would develop an equivalent to Facebook's
> > FQL, Yahoo's YQL, Amazon's SimpleDB, or Google's GQL (used for app
> > engine data storage).
> >
> > Basically an abstracted SQL-likequeryengine for doing queries and
> > getting back data the data you want using virtual tables of
> different
> > data twitter serves up.
> >
> > You could do something basic like:
> >
> > SELECT StatusID, UserID, Text FROM StatusUpdates as S
> > WHERE
> > S.UserID in (SELECT UserID FROM SocialGraph WHERE
> FollowerUseringID
> > = MYUSERID) and
> > S.StatusID > LASTID
> > ORDER BY S.StatusID DESC
> > LIMIT 200
> >
> > to get a basic user's following timeline or whatever. From there you
> > can build on from that and get a bit more complex.
> >
> > It could even build on from justquerysyntax to modify and
> destructive
> > calls.
> >
> > Maybe something like:
> > DELETE FROM StatusUpdates WHERE StatusID = 200102;
> >
> > or:
> > INSERT INTO StatusUpdates(text,replyToStatusID,replyToUserID) VALUES
> > ('@johnsmith hello',123601020,235133);
> >
> > or:
> > UPDATE StatusUpdates SET favorite = TRUE WHERE StatusID = 123601020;
> >
> > You could do it where you do an HTTP get/post with aquerylike above
> > to twitter's rest api, and the results could come back as JSON or
> XML
> > or whatever.
> >
> > Some concepts like this could be done in a local side wrapper (like
> > I've seen a SQL bridge for MSSQL for twitter on here a while back)
> but
> > it would be awesome if these were processed twitter server side. If
> > done right, it can save on overhead on both twitter and from the
> > client side.
> >
> > Like in one case I have where I'm hitting the following timeline,
> I'm
> > missing something out of the user structure that you get back from
> > that, so I turn around and do another user call on user for each
> tweet
> > to get that data. Half the data I get back in both cases don't use
> on
> > both calls but it would be awesome to be able to get that data in
> one
> > call.
> >
> > A lot to consider around optimization and limits and a bit of work
> to
> > build it but I think something like that would be really useful.
> >
> > Zac
> >
> > >>> --
> > >>> Abraham Williams |http://the.hackerconundrum.com
> > >>> Web608 | Community Evangelist |http://web608.org
> > >>> This email is: [ ] blogable [x] ask first [ ] private.
> > >>> Sent from: Madison WI United States.
> >
> > --
> > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
>
[twitter-dev] Re: Search API Refresh Rate
Hi Pete, Every 5 seconds is well below the rate limit and seems like a good rate for reasonably quick responses. It sounds like you're doing the same query each time so that should be fine. For people doing requests based on many different queries I recommend that they query less often for searches that have no results than for those that do. By using a back-off you can keep up to date on queries that are hot but not waste cycles requesting queries that very rarely change. Check out the way we do it on search.twitter.com at http://search.twitter.com/javascripts/search/refresher.js Thanks; — Matt Sanford / @mzsanford On Apr 8, 2009, at 02:30 AM, peterhough wrote: Hello! I'm developing an application which needs to constantly request a search API result. I'm pushing through a since_id to try to help minimise the load on the servers. My question is, what is the optimum time limit to loop the API requests? My application will need to act upon the result of the search pretty much instantly. I currently have the script requesting a search API result every 5 seconds. Will this hammer your servers too much? Do you know the average time third party clients reload tweets? Are there any guidelines for this? As this would have a factor in when my applications actions are seen and so the need to request a search result refresh Thanks, Pete
[twitter-dev] Re: Tweet Corpus creation for NLP research
We don't have a method to download the entire friends_timeline for a user. If you search the boards or documentation you will find there is an artificial limit on the number of tweets you can download [1]. Please doing datamining often request access to the datamining feed and cache tweets as they come. 1. http://apiwiki.twitter.com/REST+API+Documentation#PaginationLimiting Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 8, 2009 at 8:26 AM, kanny wrote: > > I am interested to do something deeper than the surface-level > processing of a user's incoming tweets. For this, I will need to > create a corpus of the user's friends_timeline over, say, past one > month or any computationally feasible period. Basically, a large > enough set of, say, 1-100 Million tweets for someone following > 100-1000 people. It would be only a one-time download, as afterwards, > incremental downloads should suffice. > > This would translate into 100MB-10 GB of download for a user. It could > be less for people following less or less-active people. Does Twitter > API provide support for such corpus creation ? It could be very > helpful for Natural Language Processing research if Twitter creates > some sample corpus of public_timeline or some selected user's > timelines. > > Looking forward to some help in this regard. > Thanks >
[twitter-dev] Re: Extended user information element contains element, too. is it expected?
The doc is out of sync. The user object should contain the status element. I'll get that fixed. Doug Williams Twitter API Support http://twitter.com/dougw 2009/4/8 Yusuke > > It is documented that Basic user information element contains status > element. > So *Extended* user information element supposed to contain status > element, too. > But it's not documented. > > I'm developing Twitter4J - a Java wrapper for the API and need to > ensure that. > > Thanks in advance, > Yusuke > > On 4月9日, 午前12:23, Chad Etzel wrote: > > Not sure if it is expected or not (or if the doc is out of sync), but > > I would say having the last status included w/ the user object is very > > handy. > > -Chad > > > > On Wed, Apr 8, 2009 at 11:20 AM, Yusuke wrote: > > > > > Hi, > > > > > According to the REST API Doc, an "Extended user information element" > > > doesn't contain a element. > > > But actually the API returns a user element with one status element. > > > Is it a doc bug? > > > > > Here is the trace log grabbed just several minutes ago. > > > -- > > > [Thu Apr 09 00:12:41 JST 2009]GEThttp:// > twitter.com/account/verify_credentials.xml > > > [Thu Apr 09 00:12:41 JST 2009]Response code: 200 > > > [Thu Apr 09 00:12:41 JST 2009]Response: > > encoding="UTF-8"?> > > > > > > 6358482 > > > twit4j > > > twit4j > > > location:0.5515412761891139 > > > > > > http://static.twitter.com/images/ > > > default_profile_normal.png > > > > > > false > > > 3 > > > 9ae4e8 > > > 00 > > > ff > > > e0ff92 > > > 87bc44 > > > 2 > > > Sun May 27 09:52:09 + 2007 > > > 0 > > > -32400 > > > Alaska > > > http://static.twitter.com/images/ > > > themes/theme1/bg.gif > > > false > > > 620 > > > false > > > false > > > > > >Mon Apr 06 16:34:02 + 2009 > > >1463787270 > > >4/7:id1 > > >Twitter4J > > >false > > > > > > > > >false > > > > > > > > > > > > -- > > > > > Cheers, > > > Yusuke >
[twitter-dev] Re: Sending @replies though Oauth
Can you post the flow of what you are doing? An @reply is simply a status update with another user mentioned using the statuses/update method. Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 7, 2009 at 9:39 PM, matthewlesh wrote: > > Hey, > > I'm currently have an issue when sending @replies when updating > statuses though the twitter API using Oauth. > > The script works fine except when somebody is trying to "@reply" you. > The result is a blank page return [no xml error or anything]. > > Is there some kind of issue i should know about or anyone who has had > a similar issue? >
[twitter-dev] Re: Quota incorrectly displayed in Chrome and Opera - fine in IE and FF
Full HTTP request/response output would help us track this down. On Wed, Apr 8, 2009 at 03:20, Adrian wrote: > > Hi, I'm been developing a client-side app that uses basic HTTP > Authentication into twitter.com. > > The problem is that when logging-in with a whitelisted account, the > 20,000 quota is correctly reflected in the remaining hits as displayed > on-site whilst using IE and FF, but in Chrome and Opera, the quota is > back to 100 when logging in with the same account. > > You can see here: > http://tr.im/iqLY > > Enter your username and password - immediately at top-right there will > be a number - the remaining hits. > It seems this quota is dependent on twitter detecting a whitelisted > account, which is determined by the browser. > > Furthermore, > http://twitter.com/account/rate_limit_status.json > http://twitter.com/account/rate_limit_status.xml > in the same browser, eg IE will display different results. Former > ~2, latter 100 > > and across browser, sometimes the results for each are identical, ~100. > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Settings->Connections
There were a lot of system issues that could have caused the robots. The site should be much happier as the week goes on. Thanks for your patience. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 8, 2009 at 4:28 AM, Mobasoft wrote: > > Checked again this morning - after seeing robots on the home page and > now link to logout (UI flaw) I cleared browser cookies and tried > again. Now I see the connections tab and the one authenticated > application for that account. > > > On Apr 7, 5:11 pm, Mobasoft wrote: > > I have another account, where I could not see the Connections tab, but > > was able to navigate to the url. > > I've also just granted OAuth access to that account and I still do not > > see a Connections tab, and navigating to the connections url still > > says, "No applications have been approved to use your account." > > > > I'll assume that it is a Twitter caching problem (which seems to have > > been a bigger overall problem lately). > > > > If it shows up anytime soon, I'll add another reply here. > > > > Michael > > > > On Apr 7, 4:56 pm, Mobasoft wrote: > > > > > Robots. > > > "Something is technically wrong. > > > Thanks for noticing—we're going to fix it up and have things back to > > > normal soon." > > > > > On Apr 7, 4:53 pm, Doug Williams wrote: > > > > > > Michael, > > > > All of the API development team read this forum so it's the best > place for > > > > issues like this. As Chad replied, the connections tab is working for > me as > > > > expected. Can you go into more detail about what you are seeing that > seems > > > > off? > > > > > > Doug Williams > > > > Twitter API Supporthttp://twitter.com/dougw > > > > > > On Tue, Apr 7, 2009 at 2:43 PM, Chad Etzel > wrote: > > > > > > > Working for me, and displaying all of the authorized apps I've > used... > > > > > -Chad > > > > > > > On Tue, Apr 7, 2009 at 5:41 PM, Mobasoft > wrote: > > > > > > > > I understand that a lot of this OAuth development has been and > out of > > > > > > some flux lately, but is thathttps:// > twitter.com/account/connections > > > > > > link working for anyone? > > > > > > > > If there is a more prominent place to ask Twitter dev team > directly, > > > > > > please inform me. > > > > > > > > Thanks, > > > > > > > > Michael >
[twitter-dev] Re: lots of requests
I've seen some twitter friend recommenders out there. I wonder how they manage to do it fast enough? Or maybe they don't look at that many connections. Any ideas on how this can be done? I think the API is awesome so far and this is a tough problem to solve because it involves a lot of data being transported over the network, but there must be a way. Thank you for your help! --Erdal On Apr 1, 5:53 pm, Alex Payne wrote: > We don't have batch requests at the moment, but similar services make > use of our Social Graph API methods > (http://apiwiki.twitter.com/REST+API+Documentation#SocialGraphMethods) > and cache user objects locally. It'll be painfully slow for your first > few dozen users, but then increasingly less so as you build your own > cache of the Twitter social graph. > > Applications like this are tough to build on our API, and we recognize > that it's a weak spot. > > > > On Wed, Apr 1, 2009 at 11:27,erdal wrote: > > > I am developing a Twitter based app running on Google's App Engine - > >http://twittemmender.appspot.com(it is up but not working properly > > right now) > > > The main idea is to recommend you tweeps that are close to you based > > on your latest tweets (and some machine learning on your tweets). For > > this I need to get a list of all my friends (easy and fast enough to > > do right now), and then for each of those friends get a list of all > > their friends (this is where it starts getting slow because this could > > add up to about 10,000 friends). Then for each of those second degree > > friends I would like to retrieve their latest tweets (20 tweets for > > example). > > > This means I would have to make ~ 10,000 requests. I am currently > > using the python twitter library, which works fine for a few requests > > (ex: just getting my latest tweets, or getting a list of my friends), > > but as soon as I request the friends of friends (second degree > > friends), things start getting slow. > > > My question is, is there a good way of doing this? Maybe some batch > > requests or something similar? > > > Thank you, Twitter API folks! Your help is appreciated! > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Extended user information element contains element, too. is it expected?
Thanks. Please also document the official form of the return value of the Search API. Cheers, Yusuke On 4月9日, 午前1:35, Doug Williams wrote: > The doc is out of sync. The user object should contain the status element. > I'll get that fixed. > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > 2009/4/8 Yusuke > > > > > It is documented that Basic user information element contains status > > element. > > So *Extended* user information element supposed to contain status > > element, too. > > But it's not documented. > > > I'm developing Twitter4J - a Java wrapper for the API and need to > > ensure that. > > > Thanks in advance, > > Yusuke > > > On 4月9日, 午前12:23, Chad Etzel wrote: > > > Not sure if it is expected or not (or if the doc is out of sync), but > > > I would say having the last status included w/ the user object is very > > > handy. > > > -Chad > > > > On Wed, Apr 8, 2009 at 11:20 AM, Yusuke wrote: > > > > > Hi, > > > > > According to the REST API Doc, an "Extended user information element" > > > > doesn't contain a element. > > > > But actually the API returns a user element with one status element. > > > > Is it a doc bug? > > > > > Here is the trace log grabbed just several minutes ago. > > > > -- > > > > [Thu Apr 09 00:12:41 JST 2009]GEThttp:// > > twitter.com/account/verify_credentials.xml > > > > [Thu Apr 09 00:12:41 JST 2009]Response code: 200 > > > > [Thu Apr 09 00:12:41 JST 2009]Response: > > > encoding="UTF-8"?> > > > > > > > > 6358482 > > > > twit4j > > > > twit4j > > > > location:0.5515412761891139 > > > > > > > > http://static.twitter.com/images/ > > > > default_profile_normal.png > > > > > > > > false > > > > 3 > > > > 9ae4e8 > > > > 00 > > > > ff > > > > e0ff92 > > > > 87bc44 > > > > 2 > > > > Sun May 27 09:52:09 + 2007 > > > > 0 > > > > -32400 > > > > Alaska > > > > http://static.twitter.com/images/ > > > > themes/theme1/bg.gif > > > > false > > > > 620 > > > > false > > > > false > > > > > > > >Mon Apr 06 16:34:02 + 2009 > > > >1463787270 > > > >4/7:id1 > > > >Twitter4J > > > >false > > > > > > > > > > > >false > > > > > > > > > > > > > > > > -- > > > > > Cheers, > > > > Yusuke
[twitter-dev] Re: lots of requests
Most probably have extensive local caching and only pull missing or old data. abraham On Wed, Apr 8, 2009 at 11:44, erdal wrote: > > I've seen some twitter friend recommenders out there. I wonder how > they manage to do it fast enough? Or maybe they don't look at that > many connections. > Any ideas on how this can be done? > > I think the API is awesome so far and this is a tough problem to solve > because it involves a lot of data being transported over the network, > but there must be a way. > > Thank you for your help! > --Erdal > > > On Apr 1, 5:53 pm, Alex Payne wrote: > > We don't have batch requests at the moment, but similar services make > > use of our Social Graph API methods > > (http://apiwiki.twitter.com/REST+API+Documentation#SocialGraphMethods) > > and cache user objects locally. It'll be painfully slow for your first > > few dozen users, but then increasingly less so as you build your own > > cache of the Twitter social graph. > > > > Applications like this are tough to build on our API, and we recognize > > that it's a weak spot. > > > > > > > > On Wed, Apr 1, 2009 at 11:27,erdal wrote: > > > > > I am developing a Twitter based app running on Google's App Engine - > > >http://twittemmender.appspot.com(it is up but not working properly > > > right now) > > > > > The main idea is to recommend you tweeps that are close to you based > > > on your latest tweets (and some machine learning on your tweets). For > > > this I need to get a list of all my friends (easy and fast enough to > > > do right now), and then for each of those friends get a list of all > > > their friends (this is where it starts getting slow because this could > > > add up to about 10,000 friends). Then for each of those second degree > > > friends I would like to retrieve their latest tweets (20 tweets for > > > example). > > > > > This means I would have to make ~ 10,000 requests. I am currently > > > using the python twitter library, which works fine for a few requests > > > (ex: just getting my latest tweets, or getting a list of my friends), > > > but as soon as I request the friends of friends (second degree > > > friends), things start getting slow. > > > > > My question is, is there a good way of doing this? Maybe some batch > > > requests or something similar? > > > > > Thank you, Twitter API folks! Your help is appreciated! > > > > -- > > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Abraham Williams | Hacker | http://abrah.am @poseurtech | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Extended user information element contains element, too. is it expected?
I'm working on that now, as well. Doug Williams Twitter API Support http://twitter.com/dougw 2009/4/8 Yusuke > > Thanks. > Please also document the official form of the return value of the > Search API. > > Cheers, > Yusuke > > On 4月9日, 午前1:35, Doug Williams wrote: > > The doc is out of sync. The user object should contain the status > element. > > I'll get that fixed. > > > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw > > > > 2009/4/8 Yusuke > > > > > > > > > It is documented that Basic user information element contains status > > > element. > > > So *Extended* user information element supposed to contain status > > > element, too. > > > But it's not documented. > > > > > I'm developing Twitter4J - a Java wrapper for the API and need to > > > ensure that. > > > > > Thanks in advance, > > > Yusuke > > > > > On 4月9日, 午前12:23, Chad Etzel wrote: > > > > Not sure if it is expected or not (or if the doc is out of sync), but > > > > I would say having the last status included w/ the user object is > very > > > > handy. > > > > -Chad > > > > > > On Wed, Apr 8, 2009 at 11:20 AM, Yusuke wrote: > > > > > > > Hi, > > > > > > > According to the REST API Doc, an "Extended user information > element" > > > > > doesn't contain a element. > > > > > But actually the API returns a user element with one status > element. > > > > > Is it a doc bug? > > > > > > > Here is the trace log grabbed just several minutes ago. > > > > > -- > > > > > [Thu Apr 09 00:12:41 JST 2009]GEThttp:// > > > twitter.com/account/verify_credentials.xml > > > > > [Thu Apr 09 00:12:41 JST 2009]Response code: 200 > > > > > [Thu Apr 09 00:12:41 JST 2009]Response: > > > > encoding="UTF-8"?> > > > > > > > > > > 6358482 > > > > > twit4j > > > > > twit4j > > > > > location:0.5515412761891139 > > > > > > > > > > http://static.twitter.com/images/ > > > > > default_profile_normal.png > > > > > > > > > > false > > > > > 3 > > > > > 9ae4e8 > > > > > 00 > > > > > ff > > > > > e0ff92 > > > > > > 87bc44 > > > > > 2 > > > > > Sun May 27 09:52:09 + 2007 > > > > > 0 > > > > > -32400 > > > > > Alaska > > > > > http://static.twitter.com/images/ > > > > > themes/theme1/bg.gif > > > > > false > > > > > 620 > > > > > false > > > > > false > > > > > > > > > >Mon Apr 06 16:34:02 + 2009 > > > > >1463787270 > > > > >4/7:id1 > > > > >Twitter4J > > > > >false > > > > > > > > > > > > > > >false > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Cheers, > > > > > Yusuke >
[twitter-dev] Re: Search API Refresh Rate
Perfect, thanks Matt On Apr 8, 5:27 pm, Matt Sanford wrote: > Hi Pete, > > Every 5 seconds is well below the rate limit and seems like a > good rate for reasonably quick responses. It sounds like you're doing > the same query each time so that should be fine. > > For people doing requests based on many different queries I > recommend that they query less often for searches that have no results > than for those that do. By using a back-off you can keep up to date on > queries that are hot but not waste cycles requesting queries that very > rarely change. Check out the way we do it on search.twitter.com > athttp://search.twitter.com/javascripts/search/refresher.js > > Thanks; > — Matt Sanford / @mzsanford > > On Apr 8, 2009, at 02:30 AM, peterhough wrote: > > > > > Hello! > > > I'm developing an application which needs to constantly request a > > search API result. I'm pushing through a since_id to try to help > > minimise the load on the servers. My question is, what is the optimum > > time limit to loop the API requests? My application will need to act > > upon the result of the search pretty much instantly. > > > I currently have the script requesting a search API result every 5 > > seconds. Will this hammer your servers too much? > > > Do you know the average time third party clients reload tweets? Are > > there any guidelines for this? As this would have a factor in when my > > applications actions are seen and so the need to request a search > > result refresh > > > Thanks, > > Pete
[twitter-dev] Re: python twitter on google app engine
Thank you, Alex! I found tav's tweetapp also and it's working now. On Mar 31, 1:51 pm, Alex Payne wrote: > You might be interested in this:http://github.com/tav/tweetapp/tree/master > > On Tue, Mar 31, 2009 at 08:50, erdal wrote: > > > Can anybody give some pointers on how to use this api in google app > > engine. > > > I got some errors because of the cache used. Apparently App engine > > doesn't like you trying to access temporary files. Is there a way to > > disable the cache or is that not the best solution? > > > Thank you! > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Background Image Problem
I found someone else having the same problem. Here is a "possible" solution... http://getsatisfaction.com/twitter/topics/1_error_prohibited_this_current_user_from_being_saved2 On Mar 27, 12:23 pm, kristi wrote: > It's giving me this error message when I attempt to add/change my > background image: > > 1 error prohibited this current user from being saved > > There was a problem with the following field: > > * Description is too long (maximum is 160 characters) > > --- > -- > Uncool... > > On Mar 23, 4:16 pm, ctmtcolumbus wrote: > > > I am also having the same problem. Did anyone else get this fixed?
[twitter-dev] Re: Freelance Twitter API Dev directory?
Real Name:Nick Davis Twitter Username(s): @davinic email: n...@indibusiness.com website: http://indibusiness.com Creator and developer of http://twittbot.com. Able to develop custom API projects in .NET and Flex.
[twitter-dev] Re: Freelance Twitter API Dev directory?
My Real Name: Jason Korkin Twitter ID: spdyme Web Site: http://www.safedatatech.com Skills: I am the author of http://Spdy.me (Link Shortening, Bookmarklet, Web Widget). I have extensive experience working with PHP / MySQL / JS / Ajax / HTML / CSS / .NET / SQL Server, Twitter API (Basic Auth and oAuth). Located in Jupiter, FL. On Mar 15, 3:37 pm, Steven Degutis wrote: > Hello, > > Please add me to the list of Developers for Hire. > > I have extensive experience in HTML, CSS, JavaScript, jQuery, and > AJAX, and relatedly, I've even more experience in Cocoa, Cocoa Touch, > iPhone SDK, and general Mac development. > > My website can be found here, along with further information > (including my contact info): > > http://hire.degutis.org/ > > Thanks, > > -Steven > > On Feb 25, 4:28 am, winterstein wrote: > > > > > Hi Alex, > > Please add me to the list. I develop in Java and produced one of the > > open-source Java libraries for the Twitter API. > > > Real name: Daniel Winterstein > > Twitter username: winterstein > > Work URL:http://www.winterwell.com > > Email: dan...@winterwell.com > > > Thank you, > > Daniel > > > On Feb 23, 6:33 pm, Alex Payne wrote: > > > > There isn't one that I'm aware of, but if people would like to post > > > their contact info in this thread (Twitter username, URL, email, > > > whatever) I'm happy to collect them on the API Wiki. > > > > On Sat, Feb 21, 2009 at 18:00, Chad Etzel wrote: > > > > > Hi All, > > > > > I have been getting a few requests here and there for twitter API > > > > development work. I cannot take on any such projects at the moment, > > > > but I always feel bad for leaving them in the lurch. Is there a list > > > > or directory anywhere of Twitter API developers that work freelance > > > > that I can send to them when this happens? I'm happy to forward on > > > > such requests. > > > > > -Chad > > > > -- > > > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x- Hide quoted > > > text - > > - Show quoted text -
[twitter-dev] Re: OAuth in a WordPress Plugin
Okay, thanks for the information! It will be a read/write application. On Apr 8, 10:52 am, Matt Sanford wrote: > Comments inline: > > On Apr 7, 2009, at 10:24 PM, redwall_hp wrote: > > > > > I'm planning out a WordPress plugin that will make use of the Twitter > > API (which I have experience with). I'd like to avoid using basic HTTP > > authentication if I can, in favor of OAuth. I've been doing some > > reading on OAuth, and I think I get the general idea, though I haven't > > tried any experiments with it yet. > > > I'm left wondering about a few things though. > > > 1. As I'm developing a WordPress plugin, many different people will be > > using it on many different servers. How do I handle application > > registration with Twitter? Do I register an application under the name > > of the plugin, and then hook that into the plugin? Or would each user > > of the plugin have to go and register their blog as an application and > > do some setup with the plugin? > > If this is a read-only application you could register it once and > have all sites effectively act as the same application. This increases > the ease of installation but runs the risk of all sites breaking if > one user misbehaves enough that we have to suspend the application. > > For applications with write access I wouldn't recommend > distributing the key/secret since each site would likely want their > own source name (e.g. "from Matt's Blog"). In that case you would need > to leave the token and secret blank and have each installation > register themselves. > > > > > 2. How are API limits handled with OAuth? What are the differences (if > > any)? Are the API limits logged by IP, by the user authenticating, or > > to the application? > > There is a bug right now waiting to be fixed but after that it will > work just like Basic Auth does. By user when authenticated, by IP > address when not. > > Thanks; > — Matt Sanford / @mzsanford
[twitter-dev] Re: lots of requests
Cache lots, and build out lots of servers - that's the only way to do it for now. The rate limit really sucks, especially with a slow API. Hopefully that improves as they get their infrastructure in order (how long have we been saying that?). @Jesse On Wed, Apr 8, 2009 at 10:44 AM, erdal wrote: > > I've seen some twitter friend recommenders out there. I wonder how > they manage to do it fast enough? Or maybe they don't look at that > many connections. > Any ideas on how this can be done? > > I think the API is awesome so far and this is a tough problem to solve > because it involves a lot of data being transported over the network, > but there must be a way. > > Thank you for your help! > --Erdal > > > On Apr 1, 5:53 pm, Alex Payne wrote: > > We don't have batch requests at the moment, but similar services make > > use of our Social Graph API methods > > (http://apiwiki.twitter.com/REST+API+Documentation#SocialGraphMethods) > > and cache user objects locally. It'll be painfully slow for your first > > few dozen users, but then increasingly less so as you build your own > > cache of the Twitter social graph. > > > > Applications like this are tough to build on our API, and we recognize > > that it's a weak spot. > > > > > > > > On Wed, Apr 1, 2009 at 11:27,erdal wrote: > > > > > I am developing a Twitter based app running on Google's App Engine - > > >http://twittemmender.appspot.com(it is up but not working properly > > > right now) > > > > > The main idea is to recommend you tweeps that are close to you based > > > on your latest tweets (and some machine learning on your tweets). For > > > this I need to get a list of all my friends (easy and fast enough to > > > do right now), and then for each of those friends get a list of all > > > their friends (this is where it starts getting slow because this could > > > add up to about 10,000 friends). Then for each of those second degree > > > friends I would like to retrieve their latest tweets (20 tweets for > > > example). > > > > > This means I would have to make ~ 10,000 requests. I am currently > > > using the python twitter library, which works fine for a few requests > > > (ex: just getting my latest tweets, or getting a list of my friends), > > > but as soon as I request the friends of friends (second degree > > > friends), things start getting slow. > > > > > My question is, is there a good way of doing this? Maybe some batch > > > requests or something similar? > > > > > Thank you, Twitter API folks! Your help is appreciated! > > > > -- > > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >
[twitter-dev] Connection Keep-Alive and Max Simultaneous Connections
Does the Twitter API server support keep-alive? I can't seem to get it to work with Apache HttpClient 4. Also is there a limit to the number of simultaneous connections? Thanks! Jamie
[twitter-dev] major issue with getReplies right NOW ?
I just logged what I think is a major bug 436.
Any body else can verify this problem?
It just started happening about 30 minutes ago.
I've had to shut down my word game apps since they do auto replies or
auto DM's in response to user submissions.
All my PHP apps just stopped working properly because the getReplies
with
the since parameter is returning messages that are older than the
since
date. This is a big problem since it causes tons of bogus messages to
be
sent to all my users over and over again. I dont know how long this
has
been happening but at least 30 minutes.
PHP examples ...
getReplies(1239225832,null,1) gets back [created_at] => 1239225827
which
was already processed. see below in trace of returned array.
echo "Getting replies since: ".$replysince.' ';
$a=Array(0);
$page=1;
$nreplies=0;
while (count($a)>0)
{
$a=$t->getReplies($replysince,null,$page);
if ($a[$i]['created_at']>$replysince) $replysince=$a[$i]
['created_at'];
...
Getting replies since: 1239225832
getreplies : Array ( [0] => Array ( [id] => 1479274850 [created_at] =>
1239225827 [text] => @Tweet_Quiz pants [source] => web [user] => Array
(
[id] => 8394312 [name] => Melange [screen_name] => Melangerie
[description]
=> [location] => GA [url] => [protected] => [followers_count] => 220
[profile_image_url] =>
getreplies : Array ( [0] => Array ( [id] => 1479274850 [created_at] =>
1239225827 [text] => @Tweet_Quiz pants [source] => web [user] => Array
(
[id] => 8394312 [name] => Melange [screen_name] => Melangerie
[description]
=> [location] => GA [url] => [protected] => [followers_count] => 220
[profile_image_url] =>
[twitter-dev] Re: major issue with getReplies right NOW ?
> All my PHP apps just stopped working properly because the getReplies with > the since parameter is returning messages that are older than the since > date. Did you read http://groups.google.com/group/twitter-development-talk/browse_thread/thread/76de3c01bdadc209/5b2519b27f5c819a ? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Well done is better than well said. -- Benjamin Franklin ---
[twitter-dev] Problems with creating Twitter accounts for use with an API based application
For confidentially reasons, I can't disclose here the niche that our application operates in but it requires a considerable number of Twitter accounts as it's essentially developing a highly localised service. Each account refering to individual locations in the country. I've already been told in this group that it's not currently possible to use the API to create the 5000 odd accounts we need. So we've been trying to manually register them. But a considerable number of the accounts have been suspended presuamably to prevent spam. We're 100% not a spam operation and once the accounts have been registered we'll offer an incredibly novel and exciting platform that will speed up the uptake of Twitter in our niche market. But we need to be able to register the accounts! Anyone here had similar experiences? Anyone from Twitter able to give us a hand? Outside of a public forum, we're happy to disclose further details. Best wishes Ben
[twitter-dev] Deprecation of source parameter registration
Applications wishing to append the "from [MyApp]" to tweets have traditionally been able to register for a source parameter. This application is then manually approved, and specified in a header parameter (named: source) during the HTTP request. When OAuth is used for API authentication, we can implicitly determine which application is updating on a user's behalf. This allows us to use the application's name as the source parameter and bypass the messy registration and authorization cycle. Beginning late this week or early next week, application developers will no longer be able to request API source parameters. Instead, new source parameters will only be available for OAuth applications, and will be managed by the developer through the registration and management interface ( http://twitter.com/oauth_clients). Three key points: 1) We ARE NOT deprecating Basic Authentication in the near term. We ARE trying to reduce the API team's administrative load. 2) We are trying to encourage OAuth adoption. 3) Just for kicks, I'll restate #1: Basic Authentication will continue to work as it currently does. Registered source parameters will continue to work as they currently do. The FAQ [1] has been updated to reflect this change. 1. http://apiwiki.twitter.com/FAQ#HowdoIget%E2%80%9CfromMyApp%E2%80%9DappendedtoupdatessentfrommyAPIapplication Thanks, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: Problems with creating Twitter accounts for use with an API based application
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e6d8532c3ac46265/a820b56d94bda074?hl=en&#a820b56d94bda074 On Wed, Apr 8, 2009 at 20:03, ben wrote: > > For confidentially reasons, I can't disclose here the niche that our > application operates in but it requires a considerable number of > Twitter accounts as it's essentially developing a highly localised > service. Each account refering to individual locations in the country. > > I've already been told in this group that it's not currently possible > to use the API to create the 5000 odd accounts we need. So we've been > trying to manually register them. But a considerable number of the > accounts have been suspended presuamably to prevent spam. > > We're 100% not a spam operation and once the accounts have been > registered we'll offer an incredibly novel and exciting platform that > will speed up the uptake of Twitter in our niche market. But we need > to be able to register the accounts! > > Anyone here had similar experiences? Anyone from Twitter able to give > us a hand? Outside of a public forum, we're happy to disclose further > details. > > > Best wishes > Ben > -- Abraham Williams | Hacker | http://abrah.am @poseurtech | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: Connection Keep-Alive and Max Simultaneous Connections
On Wed, Apr 8, 2009 at 8:51 PM, orange80 wrote: > > Does the Twitter API server support keep-alive? I can't seem to get > it to work with Apache HttpClient 4. Also is there a limit to the > number of simultaneous connections? > Seeing as how it sends back a "Connection: close" header I'm going to guess no. That's just a guess though. -steve
[twitter-dev] Re: Deprecation of source parameter registration
When you say that you can implicitly determine the application, does that mean that source parameters will become mandatory and anything posting via the API will be automatically assigned one? On Apr 8, 10:14 pm, Doug Williams wrote: > Applications wishing to append the "from [MyApp]" to tweets have > traditionally been able to register for a source parameter. This application > is then manually approved, and specified in a header parameter (named: > source) during the HTTP request. When OAuth is used for API authentication, > we can implicitly determine which application is updating on a user's > behalf. This allows us to use the application's name as the source parameter > and bypass the messy registration and authorization cycle. > > Beginning late this week or early next week, application developers will no > longer be able to request API source parameters. Instead, new source > parameters will only be available for OAuth applications, and will be > managed by the developer through the registration and management interface > (http://twitter.com/oauth_clients). > > Three key points: > 1) We ARE NOT deprecating Basic Authentication in the near term. We ARE > trying to reduce the API team's administrative load. > 2) We are trying to encourage OAuth adoption. > 3) Just for kicks, I'll restate #1: Basic Authentication will continue to > work as it currently does. Registered source parameters will continue to > work as they currently do. > > The FAQ [1] has been updated to reflect this change. > > 1.http://apiwiki.twitter.com/FAQ#HowdoIget%E2%80%9CfromMyApp%E2%80%9Dap... > > Thanks, > Doug Williams > Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] Links into tweets
Why twitter hide links into users tweets? Search results also don't include links, tinyurl links only. Now, our app perform the following steps: 1. request twitter for json or atom 2. extarct all tiny urls (from ALL search results, one twitter request = 15-100 requests to tinyurl.com !!!). 3. extract requred info from decoded tiny url 4. inject search results into UI. How we can get real links from the twitter?
[twitter-dev] Discrepancy in follower count
There seemed to be a discrepancy in the follower count for both of these API calls: 1) http://twitter.com/users/show/.xml 2) http://twitter.com/followers/ids/.xm Is it correct to assume that the (2) will be more accurate? I checked the actual user page online: http://twitter.com/ and it seems to show the same count as the (2). Ronnie
[twitter-dev] Re: Links into tweets
The API does not have a method to retrieve the information for a URLs. tweetmeme offers an API [1] to discover URL information. 1. http://tweetmeme.com/static.php?page=api Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 8, 2009 at 8:10 PM, Mixe wrote: > > Why twitter hide links into users tweets? Search results also don't > include links, tinyurl links only. Now, our app perform the following > steps: > 1. request twitter for json or atom > 2. extarct all tiny urls (from ALL search results, one twitter request > = 15-100 requests to tinyurl.com !!!). > 3. extract requred info from decoded tiny url > 4. inject search results into UI. > > How we can get real links from the twitter? >
[twitter-dev] Re: Deprecation of source parameter registration
Doug, What about applications that do not post through the API, but still want a source parameter? Or is this type of behavior going to be discouraged in the future? As an example, TweetStats does not require you log in to retrieve the data necessary, but I do have "promotional" links on the site that append the source parameter so it appears to come "from TweetStats". It's an extra bit of link juice (although I include a link in the tweet anyway, not all applications may) and it also allows me to get an idea of how many people use that link. Will this type of source specification still be allowed? Or in the future will I just need to sign up for OAuth and use that source parameter even if my application doesn't need auth? Thanks, dpc On Apr 8, 7:14 pm, Doug Williams wrote: > Applications wishing to append the "from [MyApp]" to tweets have > traditionally been able to register for a source parameter. This application > is then manually approved, and specified in a header parameter (named: > source) during the HTTP request. When OAuth is used for API authentication, > we can implicitly determine which application is updating on a user's > behalf. This allows us to use the application's name as the source parameter > and bypass the messy registration and authorization cycle. > > Beginning late this week or early next week, application developers will no > longer be able to request API source parameters. Instead, new source > parameters will only be available for OAuth applications, and will be > managed by the developer through the registration and management interface > (http://twitter.com/oauth_clients). > > Three key points: > 1) We ARE NOT deprecating Basic Authentication in the near term. We ARE > trying to reduce the API team's administrative load. > 2) We are trying to encourage OAuth adoption. > 3) Just for kicks, I'll restate #1: Basic Authentication will continue to > work as it currently does. Registered source parameters will continue to > work as they currently do. > > The FAQ [1] has been updated to reflect this change. > > 1.http://apiwiki.twitter.com/FAQ#HowdoIget%E2%80%9CfromMyApp%E2%80%9Dap... > > Thanks, > Doug Williams > Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] Twitter Profile Search API
I have no idea when (I fully expect them to) Twitter will bring back a complete profile search, but I've been in the process of creating my own for about the past month or so. I've recently added some additional XML and JSON output to enable programmatic access if other developers are interested. It's called TweepSearch (http:// tweepsearch.com) and searches about 1.8m Twitter profiles right now including username, screen name, bio, location and url. I'm also planning on adding geo-based support at some point. A quick (and most definitely dirty) example of using JSON to integrate search results can be seen on my blog at http://dcortesi.com/2009/04/07/twitter-profile-search-api/ If you're interested in using this, please contact me so I can a) be aware and make sure I know who to notify if I make a change and b) what kind of traffic I might be able to expect. For the time being, I'm providing this as a free service until it becomes overwhelming or Twitter releases their own. ;) I look forward to hearing your feedback. Thanks, dpc p.s. An additional thing I set up recently is http://twitteravatar.appspot.com - for when you need programmatic access to a Twitter avatar. I'm familiar with SPIURL, but that seemed like more of a library than something intended to be heavily used.
[twitter-dev] Re: Problems with creating Twitter accounts for use with an API based application
On Apr 8, 2009, at 6:03 PM, ben wrote: For confidentially reasons, I can't disclose here the niche that our application operates in but it requires a considerable number of Twitter accounts as it's essentially developing a highly localised service. Each account refering to individual locations in the country Confidentially reasons or not, you should never have a reason to create 5,000 accounts. Maybe a few ten, but thousands? No. Clearly, there must be a better way to architect your application. Maybe a single application account that takes input related with a location name? I've already been told in this group that it's not currently possible to use the API to create the 5000 odd accounts we need. So we've been trying to manually register them. But a considerable number of the accounts have been suspended presuamably to prevent spam. Yes, because you are creating too many accounts, and showing up on our reports. We're 100% not a spam operation and once the accounts have been registered we'll offer an incredibly novel and exciting platform that will speed up the uptake of Twitter in our niche market. But we need to be able to register the accounts! Please understand it from Twitter's point of view - we want everyone to be able to share our (free and not unlimited) resources, not monopolize them with 5,000 accounts. -j --- John Adams Twitter Operations j...@twitter.com http://twitter.com/netik
[twitter-dev] Re: Deprecation of source parameter registration
We will certainly retain the administrative ability to create source parameters when circumstances warrant an exception. But on the whole, we will prefer that applications use OAuth to create and manage their communication with the site, even in the scenario you mentioned. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 8, 2009 at 10:12 PM, Damon P. Cortesi wrote: > > Doug, > > What about applications that do not post through the API, but still > want a source parameter? Or is this type of behavior going to be > discouraged in the future? > > As an example, TweetStats does not require you log in to retrieve the > data necessary, but I do have "promotional" links on the site that > append the source parameter so it appears to come "from TweetStats". > It's an extra bit of link juice (although I include a link in the > tweet anyway, not all applications may) and it also allows me to get > an idea of how many people use that link. > > Will this type of source specification still be allowed? Or in the > future will I just need to sign up for OAuth and use that source > parameter even if my application doesn't need auth? > > Thanks, > > dpc > > On Apr 8, 7:14 pm, Doug Williams wrote: > > Applications wishing to append the "from [MyApp]" to tweets have > > traditionally been able to register for a source parameter. This > application > > is then manually approved, and specified in a header parameter (named: > > source) during the HTTP request. When OAuth is used for API > authentication, > > we can implicitly determine which application is updating on a user's > > behalf. This allows us to use the application's name as the source > parameter > > and bypass the messy registration and authorization cycle. > > > > Beginning late this week or early next week, application developers will > no > > longer be able to request API source parameters. Instead, new source > > parameters will only be available for OAuth applications, and will be > > managed by the developer through the registration and management > interface (http://twitter.com/oauth_clients). > > > > Three key points: > > 1) We ARE NOT deprecating Basic Authentication in the near term. We ARE > > trying to reduce the API team's administrative load. > > 2) We are trying to encourage OAuth adoption. > > 3) Just for kicks, I'll restate #1: Basic Authentication will continue to > > work as it currently does. Registered source parameters will continue to > > work as they currently do. > > > > The FAQ [1] has been updated to reflect this change. > > > > 1.http://apiwiki.twitter.com/FAQ#HowdoIget%E2%80%9CfromMyApp%E2%80%9Dap. > .. > > > > Thanks, > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw >
[twitter-dev] Re: Connection Keep-Alive and Max Simultaneous Connections
Yeah, I started checking the headers and realized that. It doesn't seem like there's any hard limit on simultaneous connections though so that helps quite a bit. Thanks! Jamie On Apr 8, 9:46 pm, Steve Brunton wrote: > On Wed, Apr 8, 2009 at 8:51 PM, orange80 wrote: > > > Does the Twitter API server support keep-alive? I can't seem to get > > it to work with Apache HttpClient 4. Also is there a limit to the > > number of simultaneous connections? > > Seeing as how it sends back a "Connection: close" header I'm going to > guess no. That's just a guess though. > > -steve
[twitter-dev] Re: Connection Keep-Alive and Max Simultaneous Connections
On Apr 8, 2009, at 10:33 PM, orange80 wrote: Yeah, I started checking the headers and realized that. It doesn't seem like there's any hard limit on simultaneous connections though so that helps quite a bit. Our web servers do not support Keep-Alive. -j --- John Adams Twitter Operations j...@twitter.com http://twitter.com/netik
[twitter-dev] Re: Links into tweets
Twitturly does too. Contact us for access though since it isn't available to the public yet. On Apr 8, 9:03 pm, Doug Williams wrote: > The API does not have a method to retrieve the information for a URLs. > tweetmeme offers an API [1] to discover URL information. > > 1.http://tweetmeme.com/static.php?page=api > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Wed, Apr 8, 2009 at 8:10 PM, Mixe wrote: > > > Why twitter hide links into users tweets? Search results also don't > > include links, tinyurl links only. Now, our app perform the following > > steps: > > 1. request twitter for json or atom > > 2. extarct all tiny urls (from ALL search results, one twitter request > > = 15-100 requests to tinyurl.com !!!). > > 3. extract requred info from decoded tiny url > > 4. inject search results into UI. > > > How we can get real links from the twitter?
[twitter-dev] Re: url as an input
Hi Nick, Yes, we can help with this. We have an API that is nearly complete that will allow you to provide a URL and get all of the tweets that contained a link to the provided URL, regardless of which URL shortener that was used. -Joel On Apr 5, 12:02 pm, Nick Arnett wrote: > On Sun, Apr 5, 2009 at 11:44 AM, Abraham Williams <4bra...@gmail.com> wrote: > > Just pretend the URL is text and search for that text using the default > > Search API call. > > But if you want meaningful results, you'll want to shorten the URL with the > popular shorteners (tinyurl, bitly, etc.) and search on the shortened > versions. > > Or you might be able to accomplish what you're seeking by using Twiturly. > > Nick
[twitter-dev] Re: Discrepancy in follower count
Ronnie, I'm showing that even #2 is different at times - what the user sees on the Web UI at times will be different than both counts. It's all very strange. @Jesse On Wed, Apr 8, 2009 at 9:54 PM, Ronnie wrote: > > There seemed to be a discrepancy in the follower count for both of > these API calls: > > 1) http://twitter.com/users/show/.xml > 2) http://twitter.com/followers/ids/.xm > > Is it correct to assume that the (2) will be more accurate? I checked > the actual user page online: http://twitter.com/ and it > seems to show the same count as the (2). > > > Ronnie
