[twitter-dev] Re: Why won't the twitter feed show in my flex app?
The Twitter API call is working correctly. ( http://twitter.com/statuses/user_timeline/zenbullets.xml?count=5 ). I would recommend asking in a Flex developer forum where they specialize in Flex development. Abraham On Wed, Sep 9, 2009 at 09:10, Markus thonhau...@gmail.com wrote: Hi! I'm trying to display a twitterfeed in my Flex app, but it simply wont show. Could someone please point out what the problem is? The code: http://norskwebforum.no/pastebin/11139 -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs!
I've always just stored as 64bit integers, I'd assumed that 32bit wouldn't be enough. Now, if it goes above 64bit then I'm screwed, because neither my language or database have built in support for that! :P From: JDG Sent: Thursday, September 10, 2009 4:21 AM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs! if you were on signed32 you'd have had a problem a long time ago. not quite sure why people haven't just taken to treating/storing as strings -- sure there's a bit more overhead mem/storage-wise, but you don't have to change your code every few months. On Wed, Sep 9, 2009 at 16:45, Joseph Cheek jos...@cheek.com wrote: Twitter is in league with Al Qaida! You heard it first here, folks! Ok, seriously, this message I wrote wasn't worth the electrons it took to transmit it... let's see if I can increase the s2n ratio: 4294967296, that an unsigned 32-bit int? ok, fair enough. i know some of my apps use signed 64bit ints, but i'm not sure about the db... will need to check... might be signed32... Joseph Cheek jos...@cheek.com, www.cheek.com twitter: http://twitter.com/cheekdotcom Nicholas Moline wrote: And nobody thought about the significance of accelerating anything called a *pocolypse to be on the anniversary of a date that thousands died in a terrorist attack Tactful Twitter... Real Tactful On Wed, Sep 9, 2009 at 1:00 PM, Alex Payne a...@twitter.com mailto:a...@twitter.com wrote: Sorry, an error in phrasing. It was previously mentioned that this change was pending. We had not previously announced a date for the change. Normally, we prefer to provide more advance notice where possible, but I'm letting you all know immediately after our operations team informed me that it was necessary to make this change on Friday. On Wed, Sep 9, 2009 at 12:13, Hwee-Boon Yarhweeb...@gmail.com mailto:hweeb...@gmail.com wrote: May I know when and where was it mentioned that it will be artificially increased this coming Friday? -- Hwee-Boon On Sep 10, 2:49 am, Alex Payne a...@twitter.com mailto:a...@twitter.com wrote: As mentioned previously, the Twitter operations team willartificially increase the maximum status ID to 4294967296 this coming Friday, September 11th. This action is part of routine database upgrades and maintenance. If your Twitter API application stores status IDs, please be sure that your datastore is configured to handle integers of that size. Thanks. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Internets. Serious business.
[twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs!
What is the documented range for status IDs? (How high can they go?) Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.com -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Alex Payne Sent: Wednesday, September 09, 2009 1:01 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs! Sorry, an error in phrasing. It was previously mentioned that this change was pending. We had not previously announced a date for the change. Normally, we prefer to provide more advance notice where possible, but I'm letting you all know immediately after our operations team informed me that it was necessary to make this change on Friday. On Wed, Sep 9, 2009 at 12:13, Hwee-Boon Yarhweeb...@gmail.com wrote: May I know when and where was it mentioned that it will be artificially increased this coming Friday? -- Hwee-Boon On Sep 10, 2:49 am, Alex Payne a...@twitter.com wrote: As mentioned previously, the Twitter operations team willartificially increase the maximum status ID to 4294967296 this coming Friday, September 11th. This action is part of routine database upgrades and maintenance. If your Twitter API application stores status IDs, please be sure that your datastore is configured to handle integers of that size. Thanks. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Twitter for a Library
Here is the Verified Account info: http://twitter.com/help/verified http://twitter.com/help/verifiedAbraham On Tue, Sep 8, 2009 at 07:20, hughes...@sbcglobal.net wrote: Howard, Can you do that on the regular set up account page or do you have to go through something else? Sent from my BlackBerry Smartphone provided by Alltel -- *From*: Howard Siegel *Date*: Mon, 7 Sep 2009 23:30:20 -0700 *To*: twitter-development-talk@googlegroups.com *Subject*: [twitter-dev] Re: Twitter for a Library You should get a verified account since they'll presumably want to be a trusted provider of information. - h On Mon, Sep 7, 2009 at 20:01, spyrrow hughes...@sbcglobal.net wrote: I need to set up a Twitter account for one of my clients, which is a public library. Anything I need to set up differently then what is provided on your set up account page? What would you suggest? Spyrrow -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: Search by KW then RT
PHP libraries / examples are here: http://apiwiki.twitter.com/Libraries#PHP On Sep 10, 6:55 am, Joel Strellner j...@twitturly.com wrote: Something like this is going to require a server-side language, like PHP, Perl, Ruby, etc. JavaScript wont cut it. I'm not sure how you'd do this without it being spammy though. IMO it should be manual, or at least semi-manual using a queue of some sort that you need to approve prior to it going out. -Joel On Wed, Sep 9, 2009 at 5:17 PM, 00__00 mrjchris...@gmail.com wrote: Can you help? I want to search Streaming OR Search (not fussed which) for Keyword (say Wimbledon) then ReTweet those individual results. 1. Search 2. ReTweet each search item including (via @xyz) Now I have seen this done in a spammy fashion, which is poor, so to reassure the group: I don;t wish to do this. I want to create a uber feed for my football team, hometown, and sports leagues in one...all automatically . The preferrred language is Javascript, but PHP could also work? Anyone know any libraries of such, or have any samples. Please bear in mind I am a lightweight programmer, and a bit embarrased to even ask on here!! Cheers
[twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs!
Seeing as 32bit signed was 2,147,483,647 and 32bit unsigned is 4,294,967,295 And 64bit signed is 9,223,372,036,854,775,807, I'd say we're safe for a good little while yet! On Sep 10, 7:23 am, Ted Neward ted.new...@gmail.com wrote: What is the documented range for status IDs? (How high can they go?) Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writinghttp://www.tedneward.com -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Alex Payne Sent: Wednesday, September 09, 2009 1:01 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs! Sorry, an error in phrasing. It was previously mentioned that this change was pending. We had not previously announced a date for the change. Normally, we prefer to provide more advance notice where possible, but I'm letting you all know immediately after our operations team informed me that it was necessary to make this change on Friday. On Wed, Sep 9, 2009 at 12:13, Hwee-Boon Yarhweeb...@gmail.com wrote: May I know when and where was it mentioned that it will be artificially increased this coming Friday? -- Hwee-Boon On Sep 10, 2:49 am, Alex Payne a...@twitter.com wrote: As mentioned previously, the Twitter operations team willartificially increase the maximum status ID to 4294967296 this coming Friday, September 11th. This action is part of routine database upgrades and maintenance. If your Twitter API application stores status IDs, please be sure that your datastore is configured to handle integers of that size. Thanks. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs!
and if they are, just store the twos complement of the ID in the DB and do the math when you retrieve if it's negative. :) On Thu, Sep 10, 2009 at 00:12, Rob Ashton robash...@codeofrob.com wrote: I've always just stored as 64bit integers, I'd assumed that 32bit wouldn't be enough. Now, if it goes above 64bit then I'm screwed, because neither my language or database have built in support for that! :P *From:* JDG ghil...@gmail.com *Sent:* Thursday, September 10, 2009 4:21 AM *To:* twitter-development-talk@googlegroups.com *Subject:* [twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs! if you were on signed32 you'd have had a problem a long time ago. not quite sure why people haven't just taken to treating/storing as strings -- sure there's a bit more overhead mem/storage-wise, but you don't have to change your code every few months. On Wed, Sep 9, 2009 at 16:45, Joseph Cheek jos...@cheek.com wrote: Twitter is in league with Al Qaida! You heard it first here, folks! Ok, seriously, this message I wrote wasn't worth the electrons it took to transmit it... let's see if I can increase the s2n ratio: 4294967296, that an unsigned 32-bit int? ok, fair enough. i know some of my apps use signed 64bit ints, but i'm not sure about the db... will need to check... might be signed32... Joseph Cheek jos...@cheek.com, www.cheek.com twitter: http://twitter.com/cheekdotcom Nicholas Moline wrote: And nobody thought about the significance of accelerating anything called a *pocolypse to be on the anniversary of a date that thousands died in a terrorist attack Tactful Twitter... Real Tactful On Wed, Sep 9, 2009 at 1:00 PM, Alex Payne a...@twitter.com mailto:a...@twitter.com wrote: Sorry, an error in phrasing. It was previously mentioned that this change was pending. We had not previously announced a date for the change. Normally, we prefer to provide more advance notice where possible, but I'm letting you all know immediately after our operations team informed me that it was necessary to make this change on Friday. On Wed, Sep 9, 2009 at 12:13, Hwee-Boon Yarhweeb...@gmail.com mailto:hweeb...@gmail.com wrote: May I know when and where was it mentioned that it will be artificially increased this coming Friday? -- Hwee-Boon On Sep 10, 2:49 am, Alex Payne a...@twitter.com mailto:a...@twitter.com wrote: As mentioned previously, the Twitter operations team willartificially increase the maximum status ID to 4294967296 this coming Friday, September 11th. This action is part of routine database upgrades and maintenance. If your Twitter API application stores status IDs, please be sure that your datastore is configured to handle integers of that size. Thanks. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Internets. Serious business. -- Internets. Serious business.
[twitter-dev] Re: Why won't the twitter feed show in my flex app?
You need to add: result=onRes(event) to the mx:HTTPService, because if you add a breakpoint to your onRes function it never gets called as its not told what to do on getting any result back. On Sep 9, 3:10 pm, Markus thonhau...@gmail.com wrote: Hi! I'm trying to display a twitterfeed in my Flex app, but it simply wont show. Could someone please point out what the problem is? The code:http://norskwebforum.no/pastebin/11139
[twitter-dev] Search API Not From a Source
Hello Twitter Developers, Is there a way to use the search API to get Tweets not from a particular source (i.e via web, TweetDeck etc)? I am trying to get a search full of tweet that isn't from my application but is referencing a hash tag. Is this possible? Thanks, Greg
[twitter-dev] link posted on my site
I want to complain to Twitter, because Dana Web Pro post links to my Twitter pages rying to get my pages sut down, you see from the link below one is good one advertising his site and the other one going to give me a warning.- I paid Dana Web Pro to do some work for me, so he had my password to my twitter, I went and removed all the links that click on, that had the warning on them I been try contact some one two days now. I save the links for proof, he accidently put to links on one twits the show where the link came from. Free Web Site Promotion 1000's of Search Engines GOOGLE Worldwide http://bit.ly/Vuycg http://bit.ly/FP33J 8:07 AM Sep 9th from TweetDeck Warning - this site has been flagged and may contain unsolicited content.
[twitter-dev] Re: Random 408 errors having been appearing the last 48 hours
I'm still seeing this recurring problem. Are only oauth users experiencing this? If so, maybe its time for us to give up on OAuth? On Sep 9, 12:16 pm, John Kalucki jkalu...@gmail.com wrote: Point your mobile device through a web proxy that you control. Monitor the traffic there with tcpdump. On Sep 9, 7:07 am, Naveen A knig...@gmail.com wrote: It might be useful if detailed (step by step) instructions of how to generate the debug information twitter needs to track down this HTTP data being returned on the API, I am not sure how much data you are getting but I would really like to provide as much as I possibly can and provide others with the tools to make providing this information as easily as possible. We unfortunately can't easily provide the necessary information as our application runs on a mobile device where we can not easily get the detailed information you require. I understand how to provide the ip address, and the verbose curl request.. Unclear what you are looking for when you are requesting a tcp dump.. I would be happy to attempt to generate this information if it will help expedite solving this problem.. On Sep 7, 10:06 pm, John Kalucki jkalu...@gmail.com wrote: If you are having connection problems like this, please send your IP address, account(s), a curl(1) -vvv trace, and a tcpdump of the failure to a...@twitter.com. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter inc. On Sep 7, 5:02 pm, fablau fabri...@virtualsheetmusic.com wrote: I am having the same issue, most of the times I cannot connect to Twitter, I get 408 error and the API is mostly unusable form my side. I am able to connect just a couple of times every 36-48 hours! Are we the only people having this issue? How that can be possible? Is there any way to contact Twitter folks about this issue? Are they aware of this? Any more thoughts and testimonials about this issue would be appreciated. Thank you for sharing. Best,
[twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs!
Call me crazy, but I store any data from a 3rd party in strings. Typically, I used a text blob to store some serialized object (like json or a python pickle) which maximizes flexibility. For the tweet id, I think I used 64 chars. In about 10 years, after I've cleared all the other higher priority and more impactful optimizations, I might think about dealing with this again. Ivan http://kirigin.com On Sep 10, 5:48 am, JDG ghil...@gmail.com wrote: and if they are, just store the twos complement of the ID in the DB and do the math when you retrieve if it's negative. :) On Thu, Sep 10, 2009 at 00:12, Rob Ashton robash...@codeofrob.com wrote: I've always just stored as 64bit integers, I'd assumed that 32bit wouldn't be enough. Now, if it goes above 64bit then I'm screwed, because neither my language or database have built in support for that! :P *From:* JDG ghil...@gmail.com *Sent:* Thursday, September 10, 2009 4:21 AM *To:* twitter-development-talk@googlegroups.com *Subject:* [twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs! if you were on signed32 you'd have had a problem a long time ago. not quite sure why people haven't just taken to treating/storing as strings -- sure there's a bit more overhead mem/storage-wise, but you don't have to change your code every few months. On Wed, Sep 9, 2009 at 16:45, Joseph Cheek jos...@cheek.com wrote: Twitter is in league with Al Qaida! You heard it first here, folks! Ok, seriously, this message I wrote wasn't worth the electrons it took to transmit it... let's see if I can increase the s2n ratio: 4294967296, that an unsigned 32-bit int? ok, fair enough. i know some of my apps use signed 64bit ints, but i'm not sure about the db... will need to check... might be signed32... Joseph Cheek jos...@cheek.com,www.cheek.com twitter:http://twitter.com/cheekdotcom Nicholas Moline wrote: And nobody thought about the significance of accelerating anything called a *pocolypse to be on the anniversary of a date that thousands died in a terrorist attack Tactful Twitter... Real Tactful On Wed, Sep 9, 2009 at 1:00 PM, Alex Payne a...@twitter.com mailto:a...@twitter.com wrote: Sorry, an error in phrasing. It was previously mentioned that this change was pending. We had not previously announced a date for the change. Normally, we prefer to provide more advance notice where possible, but I'm letting you all know immediately after our operations team informed me that it was necessary to make this change on Friday. On Wed, Sep 9, 2009 at 12:13, Hwee-Boon Yarhweeb...@gmail.com mailto:hweeb...@gmail.com wrote: May I know when and where was it mentioned that it will be artificially increased this coming Friday? -- Hwee-Boon On Sep 10, 2:49 am, Alex Payne a...@twitter.com mailto:a...@twitter.com wrote: As mentioned previously, the Twitter operations team willartificially increase the maximum status ID to 4294967296 this coming Friday, September 11th. This action is part of routine database upgrades and maintenance. If your Twitter API application stores status IDs, please be sure that your datastore is configured to handle integers of that size. Thanks. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Internets. Serious business. -- Internets. Serious business.
[twitter-dev] GeoMeme, search api /or rest api
hello raffi and everyone, a demo and a question; GeoMeme is geo-app using the Location field to provide measurement and comparison of real-time local twitter trends, e.g. see http://www.geome.me/51ARK to compare New Yorkers tweeting about Snow Leopard vs. Windows 7. when geolocation is available for individual tweets, that will allow more tweets to be located accurately on the map. for now, it may be useful for others to see as an example geo-app. i'd love to hear what this group thinks about GeoMeme, either here or @geomeme and my question to Raffi; will the geo tags be contained in results from the public Search API /or just the REST API? cheers, bob
[twitter-dev] Re: GeoMeme, search api /or rest api
hey bob. will the geo tags be contained in results from the public Search API /or just the REST API? the plan is to have geo in the public search API as well! -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Re: What is 140 characters?
On Wed, Sep 9, 2009 at 1:07 AM, Matt Sanford m...@twitter.com wrote: I more than agree with the above statement that a character is a character and Twitter shouldn't care. Data should be data. The main issue with that is that some clients compose characters and some don't. My common example of this is é. Depending on your client Twitter could get: é - 1 byte - URL Encoded UTF-8: %C3%A9 - http://www.fileformat.info/info/unicode/char/00e9/index.htm -- or -- é - 2 bytes - URL Encoded UTF-8: %65%CC%81 - http://www.fileformat.info/info/unicode/char/0065/index.htm + plus: http://www.fileformat.info/info/unicode/char/0301/index.htm So, my fix will make it so that no matter the client if the user sees é it counts as a single character. I'll announce something in the change log once my fix is deployed. Sorry for being picky about this, I'm just trying to make sure that I'm understanding the terms correctly as you are using them. I tend to think of Twitter as 140 characters (rather than bytes). I realize that character may not have a precise definition, but to me, each of these is one character: e é Am I understanding you correctly that Twitter is moving to standardize where you can send a message with 140 characters regardless of whether that's 140 e or 140 é or 140 or 140 or 140 ? I think that's what is being said, I just want to make sure I'm understanding properly. Thanks! TjL
[twitter-dev] Re: Paging (or cursoring) will always return unreliable (or jittery) results
Hey developers, any hints/tips on how I can get the Twitter API team to focus on this issue? It's hard to build a business on the Twitter API when a crucial feature like this just stops working and we get radio silence for days. Any tips on how I can help the team focus on this?? On Sep 9, 10:10 am, alexc chy101...@gmail.com wrote: this issue still pops up :http://twitter.com/friends/ids/downingstreet.xml?page=3
[twitter-dev] Errornous link - Bracket problem with bit.ly
I'm not developer, but couldn't find better place to report. I looked around to see if this issue as been submited but not seen. The folowing discussion is from 2 weeks ago (forgot to report). The issue is that if you don't put space at the end of link, the bracket is sent to bit.ly engine for encoding. Here's a mail discussion adressed to bit.ly support: Using twitter, i sent a text that was: Cool Tuesday. idk what to do, so i do nothing :). (jodie foster fan http://thecia.com.au/reviews/f/images/flight-plan-0.jpg) and as turned (automatic feature) into: Cool Tuesday. idk what to do, so i do nothing :). (jodie foster fan http://bit.ly/y3mtF ...string that make the link errornous. Do you think I need to adress my suggestion to twitter instead ? --reply Yes, you need to ask twitter to fix that. They are using our api, but obviously, they are encoding the ) after the .jpg. Thanks for letting us know, but yes, this is a twitter issue. Rex rex dixon | m: 314.324.4124 | r...@bit.ly Gtalk: rexduffdixon | Skype: rexdixon1 | AIM: RexDixon2006 | Twitter: @RexDixon | Twitter: @bitly | Suggestions: http://bit.ly/pvNq | Ask And Answer: http://bit.ly/13qnK
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
Yes, you need to ask twitter to fix that. They are using our api, but obviously, they are encoding the ) after the .jpg. Thanks for letting us know, but yes, this is a twitter issue. Good luck with that. Since it is acceptable to have the unencoded ) character in a URL, I don't know how they might interpret that it does not belong. They can make a good guess at best.
[twitter-dev] Re: non json response
People are working on this as a high-priority issue. I'd imagine that the API team will have an update soon. On Sep 10, 2:09 pm, Monica Keller monica.kel...@gmail.com wrote: We see this error 75% of the time. Have you guys made an progress on resolving the issue ? On Sep 6, 8:14 pm, archF6 tylerjpeter...@gmail.com wrote: I am able to consistently reproduce this error. I am making GET requests via PHP from IP: 96.30.16.192. I receive the error without fail after periods of inactivity lasting 2 hours or more. The header response code is 200. Please let me know if I can provide any additional info that might help you diagnose the problem, or if you have suggestions about how best to handle. Thanks. On Sep 6, 3:35 pm, Rudifa rudi.far...@gmail.com wrote: I have seen this same http page with empty body !DOCTYPEhtmlPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/ TR/1999/REC-html401-19991224/strict.dtd !-- !DOCTYPEHTMLPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/TR/html4/strict.dtd; -- HTML HEAD META HTTP-EQUIV=Refresh CONTENT=0.1 META HTTP-EQUIV=Pragma CONTENT=no-cache META HTTP-EQUIV=Expires CONTENT=-1 TITLE/TITLE /HEAD BODYP/BODY /HTML a number of times in the last few days (but intermittently - a good response may come after several attempts), in response tohttp://twitter.com/users/show/rudifa.json The most recent one was on UTC time 2009-09-06 18:55:38.262 My IP is 84.227.186.88 as reported byhttp://www.whatismyip.com/ Could someone at twitter.com please tell us what does this mean? Server (s) overloaded? On Aug 30, 1:20 pm, Steven Wilkin iamthebisc...@gmail.com wrote: I'm consistently getting the same response when accessinghttp://search.twitter.com/trends.jsonfrom209.40.204.183 Steve On Aug 26, 5:27 pm, Ryan Sarver rsar...@twitter.com wrote: Ben, It's a known issue and we are trying to hunt it down. Can you please provide us with your source IP and an approximate time of when you saw it? Thanks, RyanOn Wed, Aug 26, 2009 at 7:00 AM, benben.apperr...@googlemail.com wrote: Occassionally i get back a 200 statushtmlresponse from the json search api which look like this, most times the same search works fine, it just happens occassionally: !DOCTYPEhtmlPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/ TR/1999/REC-html401-19991224/strict.dtd !-- !DOCTYPEHTMLPUBLIC -//W3C//DTDHTML4.01//EN http://www.w3.org/TR/html4/strict.dtd; -- HTML HEAD META HTTP-EQUIV=Refresh CONTENT=0.1 META HTTP-EQUIV=Pragma CONTENT=no-cache META HTTP-EQUIV=Expires CONTENT=-1 TITLE/TITLE /HEAD BODYP/BODY /HTML Does anyone recognise what this kind of response means? Is it normal, or just beta-ish quirks?- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
Yet another reason Twitter should NOT be bit.ly encoding URLs that do not cause tweets to go 140 chars. (or at all for that matter, leave that up to the users) On Thu, Sep 10, 2009 at 13:42, Matthew Terenzio mteren...@gmail.com wrote: Yes, you need to ask twitter to fix that. They are using our api, but obviously, they are encoding the ) after the .jpg. Thanks for letting us know, but yes, this is a twitter issue. Good luck with that. Since it is acceptable to have the unencoded ) character in a URL, I don't know how they might interpret that it does not belong. They can make a good guess at best. -- Internets. Serious business.
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
I completely agree with the sentiment as stated, but have a question. Does the URL shortening happen only for tweets entered at twitter.com? Or does it also happen for tweets created via the API? The former is a twitter UI issue, and if they want to shorten tweets, well, that's their business. But shortening URLs in tweets created via the API is *MY* business as a user of the API, and, IMHO, none of theirs. If I and / or my user want a URL shortened, we'll do it. And if I or my user *DON'T* want it shortened, then the API should not do it. If in fact URL shortening is possible via the API, then there should at least be an option to suppress it. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of JDG Sent: Thursday, September 10, 2009 16:19 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Errornous link - Bracket problem with bit.ly Yet another reason Twitter should NOT be bit.ly encoding URLs that do not cause tweets to go 140 chars. (or at all for that matter, leave that up to the users) On Thu, Sep 10, 2009 at 13:42, Matthew Terenzio mteren...@gmail.com wrote: Yes, you need to ask twitter to fix that. They are using our api, but obviously, they are encoding the ) after the .jpg. Thanks for letting us know, but yes, this is a twitter issue. Good luck with that. Since it is acceptable to have the unencoded ) character in a URL, I don't know how they might interpret that it does not belong. They can make a good guess at best. -- Internets. Serious business.
[twitter-dev] Friends Ids API
Hi guys, I don't seem to have found any trace of this report before, so I thought I should post it. According to the http://apiwiki.twitter.com/Twitter-REST-API-Method:-friends ids documentation, you can actually get the results using any of the following 4 URIs: http://twitter.com/friends/ids/numeric_id.json http://twitter.com/friends/ids/screen_name.json http://twitter.com/friends/ids/ids.json?user_id=numeric_id http://twitter.com/friends/ids/ids.json?screen_name=screen_name Now, I know this may sound weird or I've just missed this par, but the results I'm getting back from the first 2 requests are different to the ones for the last 2 URIs. The size of the second result set is significantly smaller than the first one. As an additional clarification: I am testing these against an account that doesn't follow more than 5000 users. 2. I have found the first line from the doc a bit confusing: [q] Returns an array of numeric IDs for every user the specified user is following.[/q] I'd suggest rephrasing it to something like: [q]Returns the array of numeric IDs of all users following the specified user.[/q] Looking forward to hearing your comment on the first issue. Thanks in advance, ./alex
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
On Thu, Sep 10, 2009 at 2:45 PM, Jim Renkel james.ren...@gmail.com wrote: Does the URL shortening happen only for tweets entered at twitter.com? Or does it also happen for tweets created via the API? The former is a twitter UI issue, and if they want to shorten tweets, well, that’s their business. The API also shortens the urls into bit.ly links. I have seen no option to suppress this behavior. - Hedley On Thu, Sep 10, 2009 at 2:45 PM, Jim Renkel james.ren...@gmail.com wrote: I completely agree with the sentiment as stated, but have a question. Does the URL shortening happen only for tweets entered at twitter.com? Or does it also happen for tweets created via the API? The former is a twitter UI issue, and if they want to shorten tweets, well, that’s their business. But shortening URLs in tweets created via the API is **MY** business as a user of the API, and, IMHO, none of theirs. If I and / or my user want a URL shortened, we’ll do it. And if I or my user **DON’T** want it shortened, then the API should not do it. If in fact URL shortening is possible via the API, then there should at least be an option to suppress it.
[twitter-dev] Error 400 while fetching twitter feeds
Hi, Our app has been using twitter RSS for a while for fetching status updates of users. (e.g. http://twitter.com/statuses/user_timeline/serenity.atom). Its worked fine. But in the last couple of days we are getting more and more error 400 when we do the HTTP get on the ATOM URL. The IP of the machine that is making the requests is 208.96.18.86. We don't poll for a given user's feed more than once an hour. Are ATOM requests throttled whereas API requests are not by twitter? Is this issue arising because we are using the ATOM based API and not the formal Twitter API? Any help would be much appreciated. Regards, rahul
[twitter-dev] stream api track method return null for getInReplyToScreenName()
I recently switched from search api to stream api. Consquently, I needed to use the getInReplyToScreenName() to get the reply name. However, this is returning null. Therefore, I am parsing the tweet text directly to extract the @lithium token.
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
If in fact URL shortening is possible via the API, then there should at least be an option to suppress it. I have seen the API shorten URLs that I have already shortened which has caused problems but I never got an answer on what the rules were because I have also noticede some longer URLs slip by so there is an algorithm working there somewhere. Silence to the questions is the frustrating part. I guess I'm not big enough yet.
[twitter-dev] Draft: Twitter Rules for API Use
To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules at http://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement at http://bit.ly/2ZXsyW for some background. We encourage you to use the contact us link at http://twitter.com/apirules with any feedback you may have. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Error 400 while fetching twitter feeds
The only link that was did like was the person did them purposely he is web master, he know what he was doing. On Thu, Sep 10, 2009 at 4:31 PM, Mytweetopics monsoon@gmail.com wrote: Hi, Our app has been using twitter RSS for a while for fetching status updates of users. (e.g. http://twitter.com/statuses/user_timeline/serenity.atom). Its worked fine. But in the last couple of days we are getting more and more error 400 when we do the HTTP get on the ATOM URL. The IP of the machine that is making the requests is 208.96.18.86. We don't poll for a given user's feed more than once an hour. Are ATOM requests throttled whereas API requests are not by twitter? Is this issue arising because we are using the ATOM based API and not the formal Twitter API? Any help would be much appreciated. Regards, rahul
[twitter-dev] Re: Draft: Twitter Rules for API Use
I expected to see more along the lines of rules of which the violation would cause a blacklisting of the app. No problems with what is in the draft at present. Dewald
[twitter-dev] Re: Draft: Twitter Rules for API Use
No offence but can you please post these 'draft' rules along with the current API rules. Sorry if I sound 'overtly suspicious' but as you can imagine I'm a little wary of anything that twitter inc says at the moment and would like to have all of the rules in a single location as it causes confusion for developers and twitter alike (oh and twitters lawyers as well .). Regards, Dean Collins d...@mytwitterbutler.com -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Marcel Molina Sent: Thursday, September 10, 2009 7:58 PM To: twitter-api-annou...@googlegroups.com; twitter-development-talk@googlegroups.com Subject: [twitter-dev] Draft: Twitter Rules for API Use To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules at http://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement at http://bit.ly/2ZXsyW for some background. We encourage you to use the contact us link at http://twitter.com/apirules with any feedback you may have. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Draft: Twitter Rules for API Use
Dean, That's basically what I meant. We know those are not the only rules, so the other rules should also in the draft, shouldn't they? Dewald On Sep 10, 9:50 pm, Dean Collins d...@cognation.net wrote: No offence but can you please post these 'draft' rules along with the current API rules. Sorry if I sound 'overtly suspicious' but as you can imagine I'm a little wary of anything that twitter inc says at the moment and would like to have all of the rules in a single location as it causes confusion for developers and twitter alike (oh and twitters lawyers as well .). Regards, Dean Collins d...@mytwitterbutler.com -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Marcel Molina Sent: Thursday, September 10, 2009 7:58 PM To: twitter-api-annou...@googlegroups.com; twitter-development-talk@googlegroups.com Subject: [twitter-dev] Draft: Twitter Rules for API Use To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules athttp://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement athttp://bit.ly/2ZXsyWfor some background. We encourage you to use the contact us link athttp://twitter.com/apiruleswith any feedback you may have. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Draft: Twitter Rules for API Use
This is great news! Regarding sending Tweets on a user's behalf, does that refer to DMs as well, and when seeking permission, must it be on a tweet-by-tweet basis, or can a user give you permission beforehand to have complete control over Tweeting on their behalf? I'd like to see that part clarified more. Thanks, Jesse On Thu, Sep 10, 2009 at 5:58 PM, Marcel Molina mar...@twitter.com wrote: To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules at http://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement at http://bit.ly/2ZXsyW for some background. We encourage you to use the contact us link at http://twitter.com/apirules with any feedback you may have. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Draft: Twitter Rules for API Use
Yep exactly - having ALL of the rules clearly spelled out will save confusion. It's probably an automatic suspension because the twittersphere went crazy today talking about the Titans V's Steelers game tonight but my @LiveNFLchat twitter account has been suspended this afternoon even though I followed all of the Twitter API rules for 24 hour follow limits. Like I said it's probably an automated suspension but it's hard not to feel that someone singled this account out because of my use of MyTwitterButler for the first time in 2 weeks. I'm holding off raising hell with the press and going public for 24 hours and hopefully someone at twitter re-activates the account but this yet another example of why twitter needs to implement commercial high volume accounts asap. Regards, Dean Collins Live Chat Concepts Inc d...@livechatconcepts.com +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dewald Pretorius Sent: Thursday, September 10, 2009 8:55 PM To: Twitter Development Talk Subject: [twitter-dev] Re: Draft: Twitter Rules for API Use Dean, That's basically what I meant. We know those are not the only rules, so the other rules should also in the draft, shouldn't they? Dewald On Sep 10, 9:50 pm, Dean Collins d...@cognation.net wrote: No offence but can you please post these 'draft' rules along with the current API rules. Sorry if I sound 'overtly suspicious' but as you can imagine I'm a little wary of anything that twitter inc says at the moment and would like to have all of the rules in a single location as it causes confusion for developers and twitter alike (oh and twitters lawyers as well .). Regards, Dean Collins d...@mytwitterbutler.com -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Marcel Molina Sent: Thursday, September 10, 2009 7:58 PM To: twitter-api-annou...@googlegroups.com; twitter-development-talk@googlegroups.com Subject: [twitter-dev] Draft: Twitter Rules for API Use To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules athttp://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement athttp://bit.ly/2ZXsyWfor some background. We encourage you to use the contact us link athttp://twitter.com/apiruleswith any feedback you may have. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio image001.jpg
[twitter-dev] Re: Draft: Twitter Rules for API Use
Jesse, I know where you are heading with this. ;-) If a user explicitly activates a feature in an app that sends DMs on their behalf, they at that point explicitly grants the app permission to do so. Dewald On Sep 10, 10:10 pm, Jesse Stay jesses...@gmail.com wrote: This is great news! Regarding sending Tweets on a user's behalf, does that refer to DMs as well, and when seeking permission, must it be on a tweet-by-tweet basis, or can a user give you permission beforehand to have complete control over Tweeting on their behalf? I'd like to see that part clarified more. Thanks, Jesse On Thu, Sep 10, 2009 at 5:58 PM, Marcel Molina mar...@twitter.com wrote: To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules at http://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement athttp://bit.ly/2ZXsyWfor some background. We encourage you to use the contact us link athttp://twitter.com/apiruleswith any feedback you may have. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Draft: Twitter Rules for API Use
Dewald, I'm not heading anywhere with it. I just want Twitter to clarify the terms, that's all. Feel free to leave your input if you have an opinion on what those details should be. Jesse On Thu, Sep 10, 2009 at 7:35 PM, Dewald Pretorius dpr...@gmail.com wrote: Jesse, I know where you are heading with this. ;-) If a user explicitly activates a feature in an app that sends DMs on their behalf, they at that point explicitly grants the app permission to do so. Dewald On Sep 10, 10:10 pm, Jesse Stay jesses...@gmail.com wrote: This is great news! Regarding sending Tweets on a user's behalf, does that refer to DMs as well, and when seeking permission, must it be on a tweet-by-tweet basis, or can a user give you permission beforehand to have complete control over Tweeting on their behalf? I'd like to see that part clarified more. Thanks, Jesse On Thu, Sep 10, 2009 at 5:58 PM, Marcel Molina mar...@twitter.com wrote: To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules at http://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement athttp://bit.ly/2ZXsyWfor some background. We encourage you to use the contact us link athttp://twitter.com/apiruleswith any feedback you may have. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Draft: Twitter Rules for API Use
Jesse, I apologize. Then I made incorrect assumptions. I thought you saw it as the potential Excalibur in the fight against auto-DMs. In my case, not only does the user activate the feature, he also provides the exact text that must be sent. Not only is that express consent, it is express instruction. Dewald On Sep 10, 10:37 pm, Jesse Stay jesses...@gmail.com wrote: Dewald, I'm not heading anywhere with it. I just want Twitter to clarify the terms, that's all. Feel free to leave your input if you have an opinion on what those details should be. Jesse On Thu, Sep 10, 2009 at 7:35 PM, Dewald Pretorius dpr...@gmail.com wrote: Jesse, I know where you are heading with this. ;-) If a user explicitly activates a feature in an app that sends DMs on their behalf, they at that point explicitly grants the app permission to do so. Dewald On Sep 10, 10:10 pm, Jesse Stay jesses...@gmail.com wrote: This is great news! Regarding sending Tweets on a user's behalf, does that refer to DMs as well, and when seeking permission, must it be on a tweet-by-tweet basis, or can a user give you permission beforehand to have complete control over Tweeting on their behalf? I'd like to see that part clarified more. Thanks, Jesse On Thu, Sep 10, 2009 at 5:58 PM, Marcel Molina mar...@twitter.com wrote: To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules at http://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement athttp://bit.ly/2ZXsyWforsome background. We encourage you to use the contact us link athttp://twitter.com/apiruleswith any feedback you may have. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Error 400 while fetching twitter feeds
I think I understand this better now and have applied for a white listed IP. Thanks, rahul On Sep 10, 4:31 pm, Mytweetopics monsoon@gmail.com wrote: Hi, Our app has been using twitter RSS for a while for fetching status updates of users. (e.g.http://twitter.com/statuses/user_timeline/serenity.atom). Its worked fine. But in the last couple of days we are getting more and more error 400 when we do the HTTP get on the ATOM URL. The IP of the machine that is making the requests is 208.96.18.86. We don't poll for a given user's feed more than once an hour. Are ATOM requests throttled whereas API requests are not by twitter? Is this issue arising because we are using the ATOM based API and not the formal Twitter API? Any help would be much appreciated. Regards, rahul
[twitter-dev] Comments on cursor/non-cursor-based followers/friends API.
Hi there, A few notes on the new cursor-based API. Despite promises a month ago, it's not documented (except in an e-mail to this list) Rather than have the old, admittedly broken API return errors, you've elected to keep it up, corrupting databases everywhere. What was the thinking behind this? The new 'cursor', at least sometimes, is a 60 bit integer, which cannot be represented as an IEEE754 double, ie. the Javascript number type. Most/every JS implementation I know of will silently truncate this number. How does your API deal with that? It's questionable whether this should be used in its raw form for the JSON API. Can't you just quote it? Or more simply.. Presuming the 'cursor' is merely an encoded follower/friend ID used as a low key in an '' index scan, why not just expose this directly as a parameter, rather than completely change the output format for an existing URL? What's going on with all the mystical encoding? And if it was for the 'prev_cursor' property, then what is the use of this? You cannot have prior knowledge without forward scanning from '-1' to discover these 'numbers' (or can you?), at which point you know all previous cursors anyway... Is it ever likely at some future date these endpoints will be capable of returning more than 39kb data per roundtrip (ie raw size of a 64bit int)? Some of us are charged for CPU time by the millisecond. David
[twitter-dev] Re: stream api track method return null for getInReplyToScreenName()
There is a in_reply_to_screen_name field prepopulated for you on a Streaming API methods. The Streaming API cannot return null, as you cannot represent null over HTTP. I suspect you are having other problems. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 10, 4:43 pm, lithium lithium...@gmail.com wrote: I recently switched from search api to stream api. Consquently, I needed to use the getInReplyToScreenName() to get the reply name. However, this is returning null. Therefore, I am parsing the tweet text directly to extract the @lithium token.
[twitter-dev] Unannounced API change -- new unauthorized errors for blocking users
We believe an unannounced Twitter API change happened today or yesterday, and we just want to fill the group in on our findings. This change caused some consternation from some of our user base (your app doesn't work!), and we want to help preclude that for others. As you know, if user A blocks user B, there's no easy way for user B to know that A has blocked him. On Twitter.com, user B can still view user A's friends, followers, tweet stream, and profile. Before yesterday, as far as we experienced, this used to also be the case for Twitter API calls. That's now changed. If you do authenticated calls for a blocking user, you will receive Unauthorized errors. These calls include statuses/user_timeline, friends/ids, followers/ids, and presumably others. While this change certainly makes sense for the otherwise limited block feature, I have two requests from the Twitter team: 1. Can you please match this behavior on Twitter.com? As it is, users of our app are frustrated because they can, e.g., view the user_timeline of a blocking competitor on Twitter.com, but not through our app. This leads to complaints from users saying our app is broken. 2. Can you please tell us when API changes occur? As it is, the changelog (http://apiwiki.twitter.com/REST-API-Changelog ) hasn't been updated for almost 2 months. Seemingly small changes like this can have significant consequences for apps with larger user bases.
[twitter-dev] Re: Draft: Twitter Rules for API Use
This document needs further detail, specifics, and allowances. 1. Identify the user that authored or provided the Tweet What do you mean by this? Presumably the author of the tweet is the person for whom the tweet appears on Twitter.com and who therefore actually made the tweet or authorized it, right? Isn't that sufficient? Or do you mean, say, that all those vampire bite tweets must identify that they come from vampiresRus.com (or wherever) IN THE TWEET ITSELF? Does a source parameter count as identification, or must the tweet itself contain separate identification along with the content of the tweet? 2. Maintain the integrity of Tweets and not edit or revise them. Wait, we can edit tweets?! I think you need to be more precise with your language and definitions here. In my mind, a tweet is something that appears on Twitter.com, and isn't something which may soon appear on Twitter.com. If Barack Obama says a sentence, it isn't a tweet until it is on Twitter.com. Furthermore, you should get rid of the part where it says edit or revise. It is sufficient to say integrity, particularly as new transformational tools come on line. For example, if a user queues up tweets and indicates that he wishes for them to be translated into Klingon prior to their tweeting, that does constitute edits and revisions to those tweets. But presumably this is acceptable as the user has approved such transformation. Similarly, I think you need to account for the fact that many applications allow the user to approve action-based Tweets where there is no actual text to approve. For example, the Firefox add-ons that let me tweet a particular URL, or one that lets me tweet stock trades I am making, etc. In these cases, I have approved the method to create the tweet (that I press a button and the URL and Title of the page I am on will be tweeted), but I haven't explicitly approved the text of that URL/title (nor would I want to go through that hassle). I would reword the section, then, as something like: Maintain the integrity of the user-approved text to be tweeted, or the process by which the text to be tweeted is created; and do not edit or revise said text, except where the user has specifically approved such transformations. 3. Get each user's consent before sending Tweets or other messages on their behalf. A user authenticating with your application does not constitute consent to send a message. Okay, so what DOES constitute consent? A checkbox that defaults to 'on' with the Tweet? Or a checkbox that defaults to 'off' and which the user can turn on? What about if the user agrees to a long small- type contract wherein it stipulates that the app can tweet on their behalf (yet which the user most likely hasn't fully read)? I think instead of defining what DOESNT constitute consent, you should give examples of what does constitute consent. On Sep 10, 4:58 pm, Marcel Molina mar...@twitter.com wrote: To accompany our updated Terms of Service (http://bit.ly/2ZXsyW) we've posted a draft of the Twitter API rules athttp://twitter.com/apirules. As the subject states, these rules are a work in progress and feedback is welcome. Please read the TOS announcement athttp://bit.ly/2ZXsyWfor some background. We encourage you to use the contact us link athttp://twitter.com/apiruleswith any feedback you may have. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
