Two twitters on same blog on blogger
Hi, maybe a stupid question. But I have a blog on blogger and now I started a twitter and I made my twitter-posts appear in the blog. Now, my gf have a twitter account as well and I want her twitter-posts to appear on the same blog. I am using this code that I got from twitter: div id=twitter_div h2 style=display:none; class=sidebar-titleTwitter Updates/h2 ul id=twitter_update_list/ul a id=twitter-link style=display:block;text-align:right; href=http://twitter.com/**;follow me on Twitter/a /div script src=http://twitter.com/javascripts/blogger.js; type=text/ javascript/script script src=http://twitter.com/statuses/user_timeline/ *.json?callback=twitterCallback2amp;count=5 type=text/ javascript/script where * indicates my twitter-name and for my gf´s twitter-gadget i use the same code but with different twitter-names. The code was generated in twitter so it should be alright, but when I load my blog it doesnt work. The first gadget gets the twitter-posts from the second twitter and the second gadget doesnt get any twitter- posts at all. Also, the first gadget seems to first load the right twitter-posts, but then they dissappear and the wrong ones appear. It seems that the blogger-site cannot handle two twitters or whar is the problem???
Re: Since not returning 304?
Hi James, Sorry for the late reply, I was swamped yesterday. You included a barrage of questions in that opening paragraph so I'll try and answer what I can. 1. To save on resources we don't keep track of which since has been requested before, and it seems incorrect to return 304 if that since has never been called before but there happens to be no data. So, we return 200. I can talk to Alex about if we want the blank results to return 304 but it doesn't seem right to me. 2. A GET request will count against the rate limit even if we do 304. Since we have to do the same queries and checks in order to determine it's a 304 that seems only fair. 3. The since_id works the same was as since in that blank results are not a 304. 4. You are correct, we do not rate limit *successful* calls to the verify_credentials method. If you call verify_credentials (or any authenticated method for that matter) with incorrect credentials enough times we will lock the account to prevent a dictionary attack. Thanks; — Matt Sanford / @mzsanford On Jan 28, 2009, at 11:52 PM, jredville wrote: Any ideas? On Jan 28, 12:30 am, jredville james.devi...@gmail.com wrote: Is this expected. I was setting the since param to a recent time, curl showed no tweets, but when I add --head, it shows 200 instead of 304. I'll also ask what I wanted to find out. If I request with since, and I get a 304, does it cost an API hit? Or is it a free call? Also, does since_id work that way as well? Finally, is account/ validate_credentials meant to be a free call, or is that a bug? None of these things are documented on the wiki, but I would be happy to update them with the results of this thread. C:\Users\jdeville\projects\wittytwitter [40] » curl -u jredville: http://twitter.com/statuses/ friends_timeline.json?since=Wed%2C+28+Jan+2009+08%3A23 %3A30+GMT []C:\Users\jdeville\projects\wittytwitter [41] » curl -u jredville: http://twitter.com/statuses/ friends_timeline.json?since=Wed%2C+28+Jan+2009+08%3A23 %3A30+GMT --head HTTP/1.1 200 OK Date: Wed, 28 Jan 2009 08:23:22 GMT Server: hi Last-Modified: Wed, 28 Jan 2009 08:23:22 GMT Status: 200 OK ETag: d751713988987e9331980363e24189ce Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/json; charset=utf-8 Content-Length: 2 Expires: Tue, 31 Mar 1981 05:00:00 GMT X-Revision: f00b1c05573da382f8afb2d6e9ddff447d5b55f9 Set-Cookie: lang=en; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: _twitter_sess =BAh7CToJdXNlcmkDJcQcOhNwYXNzd29yZF90b2tlbiItY2M3MGU4YzkxNzky %250AZDkyOGE3YWZmY2E1ZDIyMjg0NTIzM WQ5ZTlhMDoHaWQiJTA1YjgxNmZlMmM4 %250AYzY4ZTAyMGVjNmQ4NjZlMTNkOTgzIgpmbGFzaElDOidBY3Rpb25Db250cm9s %250AbGVyOjpGbGFzaDo6Rmx hc2hIYXNoewAGOgpAdXNlZHsA--a08bb0639b3e3c4744adbc652562d6fc6a2f2ad7; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close
Search trends.json returning old data?
Hi there, I am seeing some strange behavior that the trends.json info is intermittently being returned with old data (e.g. from last night). I don't think it's a local machine caching issue, since I saw the same old data returned on two separate machines at the same time. Is anyone else experiencing this? I have tried appending a random value on the end of the request (i.e. trends.json?rand=983yq928ry923y9qu ) to force avoiding caching issues... Thanks, -Chad
Why all Web 2.0 sites should be twitter apps.
Hi, Why should a Web 2.0 site that has nothing to do with microblogging be a twitter app? Putting aside twitter's viral marketing potential, I will focus instead on two key issues in Web 2.0 apps: (1) reducing spam/ inappropriate content; and (2) encouraging user contributions. (1) Reducing spam/inappropriate content Since twitter users have a reputation to preserve, they are unlikely to spam your site and/or submit inappropriate content. Moreover, filtering of inappropriate profile images is already done by twitter so you don't have to do it. Moreover, you could only allow contributions from users with at least some minimum number of followers to ensure that they have a reputation to preserve. (2) Encouraging user contributions Whenever users contribute content to your site, you can put their photo, name, twitter home page, bio, url alongside that content as a reward. So basically, the incentive to contribute quality content to your site is self-promotion. Amir
Re: Search trends.json returning old data?
Hi Chad, Thanks for the headers. We're working on a production issue with slow searches right now and in the process I deployed the latest code to the hosts and restarted. Let me know if you see any more problems. — Matt On Jan 29, 2009, at 11:47 AM, Chad Etzel wrote: Just happened again... it returned the trends from about last night (i think somewhere around 9-10PM PST). Here are the header dumps: * About to connect() to search.twitter.com port 80 (#0) * Trying 128.121.146.107... * connected * Connected to search.twitter.com (128.121.146.107) port 80 (#0) GET /trends.json?rand=9df8ebc86a49b8bb6e5f4e37b5576a7e HTTP/1.1 Host: search.twitter.com Accept: */* Content-Length: 7 Content-Type: application/x-www-form-urlencoded HTTP/1.1 200 OK Date: Thu, 29 Jan 2009 19:42:51 GMT Server: hi Status: 200 OK ETag: 51ff4c3a20fd92262dadaa468be7d198 Cache-Control: private, max-age=0, must-revalidate, max-age=300 Content-Type: application/json; charset=utf-8 X-Served-By: searchweb005.twitter.com Content-Length: 859 Expires: Thu, 29 Jan 2009 19:47:51 GMT Vary: Accept-Encoding Set-Cookie: _search_twitter_sess =BAh7BiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo %0ASGFzaHsABjoKQHVzZWR7AA%3D %3D--105f4e06b6532a8b5e836f918bea0ef4c38e03fe; path=/ Connection: close * Closing connection #0 -1 - 1 - #Lost -1 - 2 - Obama -1 - 3 - Melbourne -1 - 4 - Top Chef -1 - 5 - Slumdog Millionaire -1 - 6 - Goodnight -1 - 7 - Lie To Me -1 - 8 - iTunes -1 - 9 - Charles Widmore -1 - 10 - Mars -Chad On Thu, Jan 29, 2009 at 1:03 PM, Matt Sanford m...@twitter.com wrote: Hi Chad, I haven't seen anything like that. If you are still seeing it can you try using 'curl -v' or capturing the headers in your application? It will help me find out what server might be causing problems. Thanks; — Matt On Jan 29, 2009, at 10:00 AM, Chad Etzel wrote: Hi there, I am seeing some strange behavior that the trends.json info is intermittently being returned with old data (e.g. from last night). I don't think it's a local machine caching issue, since I saw the same old data returned on two separate machines at the same time. Is anyone else experiencing this? I have tried appending a random value on the end of the request (i.e. trends.json?rand=983yq928ry923y9qu ) to force avoiding caching issues... Thanks, -Chad
Re: Only @reply Tweets have conversation threads?
A quick follow-up. We noticed today that in the rest API, under the following section (URL pasted below) it shows the anatomy of a Tweet, including the in_reply_to_status_ID. Doesn't this mean that we can call from Twitter for the in_reply_to_status_ID for any Tweet? And thus create accurate conversations in our mashup for any given Tweet? http://apiwiki.twitter.com/REST+API+Documentation#Statuselement On Jan 27, 8:37 pm, Matt Sanford m...@twitter.com wrote: Hi there, That has always been the case on search.twitter.com. We're working on how to support conversations better both on the site and via the API using things like in_reply_to_id. We'll keep you posted as new stuff becomes available. Thanks; — Matt Sanford On Jan 27, 2009, at 05:30 PM, drupalot wrote: I'm not sure if it's always been this way or if it's a new development, but I noticed for the first time today that the only Tweets with a show conversation thread attached to them in search.twitter results are @reply Tweets. Just to emphasize, I mean that only Tweets that being with @[username] have conversation- threads attached to them. Regardless of how someone replies to a a particular Tweet, it will not display a show conversation thread unless the original Tweet begins with an @reply. This seems strange. Has this always been the case? Is there a reason for this? Is there any way to find conversations that don't begin with an @reply tweet? I can explain why this is important for our mashup, but wanted to start with this question.
Re: Putting a ceiling on requests from users and IPs on the whitelist
Shipping tomorrow, Monday if it slips. On Thu, Jan 29, 2009 at 10:51, Karthik fermis...@gmail.com wrote: Alex, Any updates on these new API's? We are eagerly awaiting for its release. Thanks, Karthik On Jan 23, 3:46 am, Alex Payne a...@twitter.com wrote: I'm already working on this. It'll be new methods, I think. Should be ready to deploy by early next week. On Thu, Jan 22, 2009 at 10:15, Scott C. Lemon scottcle...@gmail.com wrote: Alex, Thank you for the quick reply ... and I agree ... it seems that returning the list of followers or friends as an array of IDs would be most effective. This is somewhat how Facebook does it with their API. That would allow us to gain access to the information in a much more compact way. Obviously this would also make the amount of data being returned much less, as it wouldn't have to include the status of those people or anything else ... we can get that in subsequent requests, or by monitoring and caching the feed. So maybe there could be two new APIs? http://twitter.com/statuses/friendIDs.format http://twitter.com/statuses/followerIDs.format What do you propose as next steps for this? Do I/we have to enter a bug/issue to make the request? Or are you already working on a solution for this? We would be very interested in seeing this new API so that we can fine tune our operation and minimize the number of requests we'll be making ... Scott On Jan 21, 11:49 pm, Alex Payne a...@twitter.com wrote: Can you please address the issue of how you would recommend that an application be able to fetch the total list of a users followers? I'm hearing all sorts of accusations and bluster, but want to understand from your perspective how you would propose an application do this? Right now, you can page through the lists of friends and followers. We'll see about ways to get the friends list in one shot. I think our best bet for a method that returns the entire set of friends or followers would be simply returning an array of user IDs. Even here on the list there are people suggesting that you enhance the API to simply drop the current status ... and only return the list of followers ... which would seem to be a much simpler, and less intensive, query. We'll certainly consider that. As a side note, we are currently working on three twitter applications ... two that are hosted services, and one that is a desktop application. I want to ensure that we continue to build these fully understanding how to work cooperatively with you! All you need to do is send us an email, and we'll find solutions. It may take some time if the solution you need isn't on our development roadmap, but we're here to make it happen. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Only @reply Tweets have conversation threads?
On Fri, Jan 30, 2009 at 8:29 AM, drupalot oax...@gmail.com wrote: A quick follow-up. We noticed today that in the rest API, under the following section (URL pasted below) it shows the anatomy of a Tweet, including the in_reply_to_status_ID. Doesn't this mean that we can call from Twitter for the in_reply_to_status_ID for any Tweet? And thus create accurate conversations in our mashup for any given Tweet? That's what I do in Mitter. You may hit a protected tweet, though. -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
requesting whitelisting
Hi, I just wanna ask for the request whitelisting, I have search a lot for this matter but I can't understand what is the request whitelisting all about. How is it work? what are the advantages and disadvantage of that? I need more details for the request whitelisting, When does the 100 request per hour counted, is it per IP address when I'm using my application? I'm sorry but i can't understand fully the purpose of whitelisting ... I'm an app developer. I hope that you can helo me in my problem. Thanks in advance!
Re: requesting whitelisting
If you want to pull data from twitter more then 100 times per hour you need to be whitelisted. http://apiwiki.twitter.com/REST+API+Documentation#RateLimiting On Thu, Jan 29, 2009 at 16:18, chrizsziee crizreg...@gmail.com wrote: Hi, I just wanna ask for the request whitelisting, I have search a lot for this matter but I can't understand what is the request whitelisting all about. How is it work? what are the advantages and disadvantage of that? I need more details for the request whitelisting, When does the 100 request per hour counted, is it per IP address when I'm using my application? I'm sorry but i can't understand fully the purpose of whitelisting ... I'm an app developer. I hope that you can helo me in my problem. Thanks in advance! -- | Abraham Williams | http://the.hackerconundrum.com | Web608 | Community Evangelist | http://web608.org | ggd | betaGeek | http://girlsgeeksanddating.com | Micro-email: http://userscripts.org/scripts/show/38822 | This email is: [] blogable [x] ask first [] private
Re: requesting whitelisting
Thanks Abraham for your quick reply, one thing more, when does the 100 times per hour decreased, when you pull the data from twitter, Is it per IP address or username account? I'm using my application? On Fri, Jan 30, 2009 at 7:42 AM, Abraham Williams 4bra...@gmail.com wrote: If you want to pull data from twitter more then 100 times per hour you need to be whitelisted. http://apiwiki.twitter.com/REST+API+Documentation#RateLimiting On Thu, Jan 29, 2009 at 16:18, chrizsziee crizreg...@gmail.com wrote: Hi, I just wanna ask for the request whitelisting, I have search a lot for this matter but I can't understand what is the request whitelisting all about. How is it work? what are the advantages and disadvantage of that? I need more details for the request whitelisting, When does the 100 request per hour counted, is it per IP address when I'm using my application? I'm sorry but i can't understand fully the purpose of whitelisting ... I'm an app developer. I hope that you can helo me in my problem. Thanks in advance! -- | Abraham Williams | http://the.hackerconundrum.com | Web608 | Community Evangelist | http://web608.org | ggd | betaGeek | http://girlsgeeksanddating.com | Micro-email: http://userscripts.org/scripts/show/38822 | This email is: [] blogable [x] ask first [] private
Re: xmpp + entire pubsub
Really annoyed that Twitter are halting Gnip from allowing new users access their xmpp feed until Twitter api updated but no dates on Twitter api release means we are stuck. Prefer the xmpp solution and would like to use it asap. Also cannot access api.wiki so cannot read the upaste on native xmpp firehose support Thanks in advance Sam W: www.twitblogs.com/ssethi M: +44 7985 705075 Sent from my iPhone On 29 Jan 2009, at 13:58, Stuart stut...@gmail.com wrote: 2009/1/29 ledil leonardo.dile...@googlemail.com: how to get the entire pubsub without gnip or how can I make use of XMPP (firehouse) ? You can't at the moment. There is a new firehose solution on the way but it's pure HTTP not XMPP. Gnip is your best option. Might I ask what you have against using them? -Stuart -- http://stut.net/
SPANISH OR SPECIAL CHARACTERS
Hi!! I'm using ASP.NET to post status updates into twitter but all the accents and special characters are shown as ?. Any solution? My Code is: Dim user As String = Convert.ToBase64String (System.Text.Encoding.UTF8.GetBytes(username : pass)) Dim bytes As Byte() = System.Text.Encoding.ASCII.GetBytes (status= status source=metaki) Dim request As HttpWebRequest = CType(WebRequest.Create (http://twitter.com/statuses/update.xml;), HttpWebRequest) request.Method = POST request.ServicePoint.Expect100Continue = False request.Headers.Add(Authorization, Basic user) request.ContentType = application/x-www-form-urlencoded request.ContentLength = bytes.Length Dim reqStream As Stream = request.GetRequestStream() reqStream.Write(bytes, 0, bytes.Length) reqStream.Close()
Lots of 502 errors
Hi, we've been receiving lots of Twitter/timeout errors on search with 502 error codes. The account we use is klout. I would say 1 in 4 calls to search result in 502s... Any ideas on how to reduce the errors? Maybe go 50 instead of 100 results? example call: http://search.twitter.com/search.atom?q=from=usernamephrase=bit.lyrpp=100page=1
Re: learning about protecting my updates
It sounds like you were logged in to the Twitter API with a basic auth session in the browser on your primary machine. When you asked for your timeline, it applied your credentials. You are, of course, allowed to see your own content. On Thu, Jan 29, 2009 at 21:17, Naveen naveen.s.sax...@gmail.com wrote: I am new to Twitter so beg to apologize upfront for my naive questions... I am quite confused by the behavior I saw I logged into Twitter and then within my settings I checked the Protect my updates checkbox. I then posted an update. I logged out of twitter and then tried the following REST call: http://twitter.com/statuses/user_timeline.rss?id=my twitter screen name #1. I was able to see the updates that I posted after protecting my updates from a completely separate browser that would not have had any cookies or other identifying information about my twitter account. #2. I tried the same thing from a browser on a completely different machine and this time I got prompted for basic auth credentials. Can someone explain the behavior I saw? Also, if #2 was possible without any auth credentials, then what does it mean to protect my updates if any one who knows my screen name can get to them? Naveen -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
