[twitter-dev] Re: Error messages during authorize and redirect processes (OAuth)
On Jul 7, 9:07 pm, Andy wrote: > Bad: At Google Chrome browser (Version 5.0.375.99) it shows error, > when I go to authorize-page (with question "Connect your account?") at > retweet: > > Here is the complete error message: > > - > This page contains the following errors: > error on line 393 at column 41: Entity 'rarr' not defined > Below is a rendering of the page up to the first error. > - > > At lines 391 - 393 stands: > > > Zugreifen und aktualisieren? → > I just hit the same problem with Chrome, on the English version of the OAuth authorise page http://m.twitter.com/oauth/authorize. I'm sure that if Chrome disagrees with → then many mobile browsers are also likely to have trouble with it too. Is this likely to be fixed soon? -- Richard -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Twitter Streaming API rate limiting frequency-track
Hi, Since there is no per keyword rate limiting in streaming api, adding one keyword which gets lot of tweets can limit the data of low frequency keywords. What is the frequency at which data is limited at different access levels?Is it constant or keeps changing? If this is known we can find the frequency of a keyword before tracking using another stream or search api and add it only if the sum is not exceeding the maximum. Please confirm whether this is a good strategy for such situation? Thanks, Karthik -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Relating Twitter connecting error
Hello.. I have some problem of Twitter log-in. I use a mobile network which is provided by LG Telecom in Korean. There is a mobile Twitter log-in page which is provided by LG Telecom as well. When I attempt to log-in to Twitter, then the Twitter server sends me a TCP RST packet. As I know, LG Telecom uses a proxy server to provide a web access. Do you guys have any idea? FYI : I've attached some TCP transactions as below. [SYN] Browser -> Twitter Transmission Control Protocol, Src Port: 55432 (55432), Dst Port: http (80), Seq: 0, Len: 0 Source port: 55432 (55432) Destination port: http (80) Sequence number: 0(relative sequence number) Header length: 44 bytes Flags: 0x02 (SYN) Window size: 65535 Checksum: 0x4ab2 [validation disabled] Options: (24 bytes) [SYN,ACK] Twitter -> Browser Transmission Control Protocol, Src Port: http (80), Dst Port: 55432 (55432), Seq: 0, Ack: 1, Len: 0 Source port: http (80) Destination port: 55432 (55432) Sequence number: 0(relative sequence number) Acknowledgement number: 1(relative ack number) Header length: 24 bytes Flags: 0x12 (SYN, ACK) Window size: 18200 Checksum: 0x7ebb [validation disabled] Options: (4 bytes) Maximum segment size: 1460 bytes [TCP Segment of a reassembled PDU] Browser -> Twitter Transmission Control Protocol, Src Port: 55432 (55432), Dst Port: http (80), Seq: 1, Ack: 1, Len: 1360 Source port: 55432 (55432) Destination port: http (80) Sequence number: 1(relative sequence number) Acknowledgement number: 1(relative ack number) Header length: 20 bytes Flags: 0x18 (PSH, ACK) Window size: 65535 Checksum: 0x9e31 [validation disabled] TCP segment data (1360 bytes) [TCP Segment of a reassembled PDU] Browser -> Twitter Transmission Control Protocol, Src Port: 55432 (55432), Dst Port: http (80), Seq: 1361, Ack: 1, Len: 257 Source port: 55432 (55432) Destination port: http (80) Sequence number: 1361(relative sequence number) Acknowledgement number: 1(relative ack number) Header length: 20 bytes Flags: 0x18 (PSH, ACK) Window size: 65535 Checksum: 0x897d [validation disabled] TCP segment data (257 bytes) [RST] Twitter -> Browser Transmission Control Protocol, Src Port: http (80), Dst Port: 55432 (55432), Seq: 1, Len: 0 Source port: http (80) Destination port: 55432 (55432) Sequence number: 1(relative sequence number) Acknowledgement number: Broken TCP. The acknowledge field is nonzero while the ACK flag is not set Header length: 20 bytes Flags: 0x04 (RST) Window size: 65535 Checksum: 0xd84c [validation disabled] -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: NULLS in JSON responses and OAuth web page errors on mobile now resolved
Excellent... thanks for the communication Matt :) On Aug 26, 10:44 am, Matt Harris wrote: > Hey everyone, > > The issues which were affecting our JSON responses and mobile OAuth > web pages should be resolved now. Fixes were deployed a little earlier > today and we haven't heard of any more problems. > > If you do still experience errors when trying to Allow applications > access through the OAuth webpages on mobile, or see NULLs in the JSON > responses please let us know along with your Twitter screen_name, what > platform you were using and the API request you made. > > Thanks for your patience whilst we worked those issue out, > Best, > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Status IDs are changing on 21st September
2**64 - 1 users? Can you say "Internet of things?" ;-) Sent from my Verizon Wireless Phone - Reply message - From: "John Kalucki" Date: Wed, Aug 25, 2010 7:08 pm Subject: [twitter-dev] Re: Status IDs are changing on 21st September To: It'll still be a long int. I don't know what format is. User_id generation will, someday, be similar. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Aug 25, 2010 at 6:59 PM, D. Smith wrote: > Ok, so what column type show we make the status_id now in MySQL? > > By the way, you are not planning to also change format or user_id, are > you? > > On Aug 23, 11:17 pm, John Kalucki wrote: > > We're not using Cassandra to store tweets just yet. See: > http://engineering.twitter.com/2010/07/cassandra-at-twitter-today.html > > > > I don't think we've announced our approach for tweet storage as yet. > > > > -John Kaluckihttp://twitter.com/jkalucki > > Twitter, Inc. > > > > > > > > On Mon, Aug 23, 2010 at 8:03 PM, D. Smith wrote: > > > > > Another one hits the MySQL brick wall. > > > I'm surprised someone with as much data as you have have managed to > > > stay with MySQL for as long as you have. > > > I must have been a real pain to constantly fight the loosing MySQL > > > optimization battle. > > > > > It would be very interesting to know what made you choose Cassandra > > > over other NoSQL solutions. > > > I hope you will post a nice blog post about this, why you chose > > > Cassandra? What alternative have you considered? > > > > > On Aug 23, 6:45 pm, Matt Harris wrote: > > > > Hey Developers! > > > > > > A while ago we let you know about the new Tweet ID generation service > > > > we developed called Snowflake and published the source code so you > > > > could get familiar with how it works. Today, we're announcing that at > > > > 10am PDT on Tuesday September 21st, 2010 Snowflake will be in use on > > > > our production systems and that status IDs will no longer be > > > > sequential. > > > > > > Snowflake still uses 64-bit unsigned integers but instead of being > > > > sequential they will instead be based on time and composed of: a > > > > timestamp, a worker number and a sequence number. For the majority of > > > > you this change will go unnoticed and your applications will continue > > > > to function without the need for any changes. In addition the API is > > > > ready for Snowflake and parameters such as max_id and since_id will > > > > work as expected. Snowflake does mean Tweet IDs will no longer be > > > > useful for data analysis, and things like counting Tweets by > > > > subtracting status IDs will not be possible. > > > > > > We listened when you told us about sorting Tweets by ID and knew that > > > > we needed to keep the ID roughly sortable. With Snowflake if two > > > > Tweets are posted within 1 second of each other they will be within a > > > > second of each other in the ID space too. This means although Tweets > > > > will no longer be sorted, they will be k-sorted to approximately 1 > > > > second. > > > > > > The key points: > > > > * Status IDs will be unique > > > > * Status IDs will continue to increase - Tweets created later in the > > > > day will have a higher ID that those created in the morning > > > > * Order will be maintained for Tweets allowing you to sort by Status > > > > ID. The accuracy of the sort will be to approximately 1 second, > > > > meaning Tweets created within a second of each other have no order. > > > > * All existing API methods will continue to work the same as before > > > > * Previous status IDs will be unchanged > > > > * There will be a noticeable jump in the numerical value of status > IDs > > > > when we change. > > > > > > You can read more about Snowflake on the Twitter Engineering blog: > > >http://bit.ly/announcing-snowflake > > > > > > Best > > > > > > Matt Harris > > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Status IDs are changing on 21st September
It'll still be a long int. I don't know what format is. User_id generation will, someday, be similar. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Aug 25, 2010 at 6:59 PM, D. Smith wrote: > Ok, so what column type show we make the status_id now in MySQL? > > By the way, you are not planning to also change format or user_id, are > you? > > On Aug 23, 11:17 pm, John Kalucki wrote: > > We're not using Cassandra to store tweets just yet. See: > http://engineering.twitter.com/2010/07/cassandra-at-twitter-today.html > > > > I don't think we've announced our approach for tweet storage as yet. > > > > -John Kaluckihttp://twitter.com/jkalucki > > Twitter, Inc. > > > > > > > > On Mon, Aug 23, 2010 at 8:03 PM, D. Smith wrote: > > > > > Another one hits the MySQL brick wall. > > > I'm surprised someone with as much data as you have have managed to > > > stay with MySQL for as long as you have. > > > I must have been a real pain to constantly fight the loosing MySQL > > > optimization battle. > > > > > It would be very interesting to know what made you choose Cassandra > > > over other NoSQL solutions. > > > I hope you will post a nice blog post about this, why you chose > > > Cassandra? What alternative have you considered? > > > > > On Aug 23, 6:45 pm, Matt Harris wrote: > > > > Hey Developers! > > > > > > A while ago we let you know about the new Tweet ID generation service > > > > we developed called Snowflake and published the source code so you > > > > could get familiar with how it works. Today, we're announcing that at > > > > 10am PDT on Tuesday September 21st, 2010 Snowflake will be in use on > > > > our production systems and that status IDs will no longer be > > > > sequential. > > > > > > Snowflake still uses 64-bit unsigned integers but instead of being > > > > sequential they will instead be based on time and composed of: a > > > > timestamp, a worker number and a sequence number. For the majority of > > > > you this change will go unnoticed and your applications will continue > > > > to function without the need for any changes. In addition the API is > > > > ready for Snowflake and parameters such as max_id and since_id will > > > > work as expected. Snowflake does mean Tweet IDs will no longer be > > > > useful for data analysis, and things like counting Tweets by > > > > subtracting status IDs will not be possible. > > > > > > We listened when you told us about sorting Tweets by ID and knew that > > > > we needed to keep the ID roughly sortable. With Snowflake if two > > > > Tweets are posted within 1 second of each other they will be within a > > > > second of each other in the ID space too. This means although Tweets > > > > will no longer be sorted, they will be k-sorted to approximately 1 > > > > second. > > > > > > The key points: > > > > * Status IDs will be unique > > > > * Status IDs will continue to increase - Tweets created later in the > > > > day will have a higher ID that those created in the morning > > > > * Order will be maintained for Tweets allowing you to sort by Status > > > > ID. The accuracy of the sort will be to approximately 1 second, > > > > meaning Tweets created within a second of each other have no order. > > > > * All existing API methods will continue to work the same as before > > > > * Previous status IDs will be unchanged > > > > * There will be a noticeable jump in the numerical value of status > IDs > > > > when we change. > > > > > > You can read more about Snowflake on the Twitter Engineering blog: > > >http://bit.ly/announcing-snowflake > > > > > > Best > > > > > > Matt Harris > > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Status IDs are changing on 21st September
Ok, so what column type show we make the status_id now in MySQL? By the way, you are not planning to also change format or user_id, are you? On Aug 23, 11:17 pm, John Kalucki wrote: > We're not using Cassandra to store tweets just yet. > See:http://engineering.twitter.com/2010/07/cassandra-at-twitter-today.html > > I don't think we've announced our approach for tweet storage as yet. > > -John Kaluckihttp://twitter.com/jkalucki > Twitter, Inc. > > > > On Mon, Aug 23, 2010 at 8:03 PM, D. Smith wrote: > > > Another one hits the MySQL brick wall. > > I'm surprised someone with as much data as you have have managed to > > stay with MySQL for as long as you have. > > I must have been a real pain to constantly fight the loosing MySQL > > optimization battle. > > > It would be very interesting to know what made you choose Cassandra > > over other NoSQL solutions. > > I hope you will post a nice blog post about this, why you chose > > Cassandra? What alternative have you considered? > > > On Aug 23, 6:45 pm, Matt Harris wrote: > > > Hey Developers! > > > > A while ago we let you know about the new Tweet ID generation service > > > we developed called Snowflake and published the source code so you > > > could get familiar with how it works. Today, we're announcing that at > > > 10am PDT on Tuesday September 21st, 2010 Snowflake will be in use on > > > our production systems and that status IDs will no longer be > > > sequential. > > > > Snowflake still uses 64-bit unsigned integers but instead of being > > > sequential they will instead be based on time and composed of: a > > > timestamp, a worker number and a sequence number. For the majority of > > > you this change will go unnoticed and your applications will continue > > > to function without the need for any changes. In addition the API is > > > ready for Snowflake and parameters such as max_id and since_id will > > > work as expected. Snowflake does mean Tweet IDs will no longer be > > > useful for data analysis, and things like counting Tweets by > > > subtracting status IDs will not be possible. > > > > We listened when you told us about sorting Tweets by ID and knew that > > > we needed to keep the ID roughly sortable. With Snowflake if two > > > Tweets are posted within 1 second of each other they will be within a > > > second of each other in the ID space too. This means although Tweets > > > will no longer be sorted, they will be k-sorted to approximately 1 > > > second. > > > > The key points: > > > * Status IDs will be unique > > > * Status IDs will continue to increase - Tweets created later in the > > > day will have a higher ID that those created in the morning > > > * Order will be maintained for Tweets allowing you to sort by Status > > > ID. The accuracy of the sort will be to approximately 1 second, > > > meaning Tweets created within a second of each other have no order. > > > * All existing API methods will continue to work the same as before > > > * Previous status IDs will be unchanged > > > * There will be a noticeable jump in the numerical value of status IDs > > > when we change. > > > > You can read more about Snowflake on the Twitter Engineering blog: > >http://bit.ly/announcing-snowflake > > > > Best > > > > Matt Harris > > > Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: New SSL certificate issue with WTK 2.5.2
Hi Amit, This is an issue with the Sun WTK 2.5.2 not accepting wildcard SSL certificates and not with the Twitter API. In the future we would like to move to a single domain certificate but there is no date as to when that will be. Whilst it isn't something we like you to do, the OAuth process isn't forbidden over SSL, just strongly discouraged. This means HTTP could be used - but again, this is discouraged. Instead, as wildcard SSL certificates are perfectly valid, I recommend asking on the developer forums for the Sun WTK to see if support will be added to the toolkit itself. Best, Matt On Mon, Aug 23, 2010 at 12:35 AM, Netroboost wrote: > Hi, > > Has this issue been resolved yet? > > I am using Sun WTK 2.5.2 and facing the same issue. The error message > reads: > > "Subject alternative name did not match site name" > > Please help if anyone knows how to deal with this. > > Thanks, > > Amit. > > > > On Jul 23, 10:18 pm, Matt Harris wrote: >> Hi, >> >> I've seen similar reports for other service providers about this issue as >> well. My concern is wildcard certificates are perfectly valid and are >> described in RFC2818 [1]. I'm not sure why Sun WTK doesn't support them or >> of any workarounds but I would suggest asking on their support channels. >> >> If there are any changes on our systems we will be communicate them through >> this developer mailing list. >> >> Best, >> Matt >> >> 1.http://www.ietf.org/rfc/rfc2818.txt >> >> >> >> On Fri, Jul 23, 2010 at 4:56 AM, bjcoredev wrote: >> > How will we be warned when api.twitter.com fixed SSL certificate >> > will be effective ? >> >> > On 22 juil, 21:17, John Adams wrote: >> > > Unfortunately, the current situation is that api.twitter.com is on a >> > > wildcard certificate. >> >> > > We have plans to move it a fixed SSL certificate in the near future, but >> > no >> > > definite date yet. >> >> > > -j >> >> > > On Thu, Jul 22, 2010 at 11:50 AM, bjcoredev wrote: >> >> > > > My app doesn't use the mobile site. >> >> > > > My twitter client is written in J2ME (Java Micro Edition) and is not >> > > > using the mobile site but the Twitter API. >> >> > > > I m coding my client with WTK 2.5.2 Sun Wireless Toolkit (like many >> > > > other Java mobile developers) and since the 21/07/2001 1AM GMT >> > > > my app running under WTK can't access the url >> > > >https://api.twitter.com/oauth/access_token >> > > > because the WTK CAN'T HANDLE WILDCARD SSL certificates. >> > > > returning the error:"Subject alternative name did not match site >> > > > name". >> >> > > > I'have read that real (real devices opposite to the emulator) mobile >> > > > JAVA platforms (Sony ericsson,WM 5.0,..) don't accept wildcard SSL >> > > > certificates so twitter clients using twitter API written in J2ME >> > > > running under these platform can't access the url >> > > >https://api.twitter.com/oauth/access_token >> > > > anymore so can't process xAuth authentication wich will be mandatory >> > > > on 15 august >> > > > So . >> >> > > > On 22 juil, 20:20, John Adams wrote: >> > > > > The mobile site has used a wildcard certificate for the last two >> > years; >> > > > Did >> > > > > you recently begin experiencing this issue or was your code working >> > in >> > > > the >> > > > > past? >> >> > > > > -j >> >> > > > > On Thu, Jul 22, 2010 at 6:43 AM, bjcoredev wrote: >> > > > > > It seems that SUN WTK 2.5.2 doesn't accept wildcard certificates >> > > > > > I hope that mobile platforms accept wildcard SSL certificates. If >> > this >> > > > > > not the case, it will make twitter xAuth/oAuth unusable >> >> > > > > > Regards >> >> > > > > > On 22 juil, 14:57, bjcoredev wrote: >> > > > > > > Hi >> >> > > > > > > My mobile app logged to twitter using xAuth and was working like >> > a >> > > > > > > charm until the last SSL certicate changed >> > > > > > > (seehttp:// >> > > > > > groups.google.com/group/twitter-development-talk/browse_thread...) >> >> > > > > > > My app logs correctly with the new certicate on real device (N97) >> > > > but >> > > > > > > failed with the 2.5.2 Sun Wireless Toolkit wich i use to develop >> > my >> > > > > > > app. >> >> > > > > > > when i request token with the url (with all the parameters >> > needed): >> > > > > >https://api.twitter.com/oauth/access_token >> >> > > > > > > I get the following error message relative to the SSL >> > certificate: >> >> > > > > > > Subject alternative name did not match site name >> >> > > > > > > It seems that the SSSL certificate doesn't match the host name >> > > > > > > (api.twitter.com) >> >> > > > > > > I can't now no longer code end test my app on the computer >> > > > > > > Help !!! >> >> > > > > > > I repeat: All was working fine before the SSL certificate change >> > on >> > > > > > > the 21/07/2001 1AM GMT. >> >> > > > > > > Regards- Masquer le texte des messages précédents - >> >> > > > > - Afficher le texte des messages précédents -- Masquer le texte des >> > messages précédents - >> >> > >
Re: [twitter-dev] WIDGET ISSUES
Hey lingamaneni, Are you still seeing this problem? I ask because i'm not able to reproduce the issue using IE8 on my test machine. Best, Matt On Tue, Aug 24, 2010 at 10:44 PM, lingamaneni wrote: > Hi Guys, > > I have tried to add a twitter profile widget from twitter goodies link > on my website.I could'nt get the widget code because of the following > warnings shown on my status bar in IE8. > > Webpage error details > > User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/ > 4.0; InfoPath.2; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR > 3.5.30729) > Timestamp: Wed, 25 Aug 2010 05:31:50 UTC > > > Message: Object doesn't support this property or method > Line: 1 > Char: 1 > Code: 0 > URI: http://a0.twimg.com/a/1282682459/javascripts/api.js?1282685502 > > > Message: Object doesn't support this property or method > Line: 252 > Char: 1 > Code: 0 > URI: http://twitter.com/goodies/widgets > > hope u guys there resolve these errors at the earliest. > > Thanks > lingamaneni. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Twitter Button Counts
Hi Jonathan, The counting of URLs like yours will count correctly for Tweets from now on. Thanks for letting us know about the problems you were having so we could track the bug down and fix it. Best, Matt On Aug 24, 6:30 pm, Jonathan Strauss wrote: > Ah, canonicalization. Thanks Matt. > > As you probably know, those URL parameters (other than awesm=) are > standard Google Analytics tracking parameters. So, it's something that > should probably be handled better by the counter code. But at least we > now know the root cause. > > Thanks, > -jonathan > > On Aug 24, 5:23 pm, Matt Harris wrote: > > > > > Hi Jonathan, > > > The count we use is completely separate to search so no inference > > should be drawn from there. As well as that the search index is only 5 > > or so days now so anything Tweeted before then won't be found. > > When counting URLs we count the final destination of a shortURL so it > > doesn't matter which is used. > > > Knowing this I took a look at the code you shared and it looks good, > > but here's the problem I noticed. The URL being Tweeted is not the URL > > you placed in data-counturl. You can see this when you hover over the > > short URL in the backtype results. > > > Instead of: > > http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni... > > > You are Tweeting: > > http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni... > > > When I replaced your data-counturl with the Tweeted URL I was shown a > > count of 6. In this case 6 makes sense as this is the number of t.co > > links created from that longer query string URL. The 3 other URLs are > > not counted recognised because they have different utm_content and > > awesm values. > > > I've passed this information onto the Tweet Button team who are > > working on ways to identify that the URLs like this below are > > collapsed into the correct URL: > > >http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni.. > > > I hope this explains why your situation occurs, > > Best, > > Matt > > > On Tue, Aug 24, 2010 at 10:46 AM, Jonathan Strauss > > > wrote: > > > Matt, I've been using data-counturl from the start and still seeing 0 > > > counts. > > > > Here is the source for the button on > > >http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shorteni... > > > which is showing 0 tweets: > > > > http://twitter.com/share"; class="twitter-share-button" data- > > > url="http://awe.sm/59O75"; data-counturl="http:// > > > blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for- > > > wordpress/" data-text="Tweet Button with Shortening for WordPress" > > > data-count="vertical" data-via="snowballfactory" data- > > > related="jhstrauss:Author of the post">Tweethttp://platform.twitter.com/widgets.js";> > > > > As you can see, BackType is indexing the tweets correctly: > > >http://www.backtype.com/page/blog.snowballfactory.com%2F2010%2F08%2F1... > > > > Yet Twitter search doesn't appear to be: > > >http://search.twitter.com/search?q=http%3A%2F%2Fblog.snowballfactory > > > > From what I can see, the issue appears to be related to what short > > > URLs Twitter is choosing to index for the count. > > > > Thanks, > > > -jonathan > > > > On Aug 24, 12:10 am, Matt Harris wrote: > > >> Hey everyone, > > > >> This is a repeat of a message on another thread. > > > >> I've updated the Tweet Button docs today with information which I hope > > >> will answer a number of your questions. In particular the example > > >> about using a short URL with the parameter data-counturl should help > > >> those of you whose counts are staying at 0. > > >> http://dev.twitter.com/pages/tweet_button#using-shorturl > > > >> For reference the documentation URLs are: > > >> http://dev.twitter.com/pages/tweet_button > > >> and > > >> http://dev.twitter.com/pages/tweet_button_faq > > > >> Hope that helps, > > >> Matt > > > >> On Mon, Aug 23, 2010 at 2:10 AM, artesea wrote: > > >> > Just tried something else, I click on a tweet containing one of my > > >> > short urls > > >> > this actually redirects to > > >> >http://www.libdemvoice.org/?p=20818&utm_source=tweet&utm_medium=twitt... > > >> > by setting > > >> > data-counturl="http://www.libdemvoice.org/?p=20818"; > > >> > it finally counts all the posts. > > > >> > If you are still seeing zeros, double check to see where you exactly > > >> > redirect to. > > > >> > Regards > > >> > Ryan > > > >> > On Aug 22, 12:27 pm, artesea wrote: > > >> >> Anyone from Twitter looking at this list??? > > > >> >> I now have a post with 32 tweets when looking > > >> >> athttp://twitter.com/#search?q=http%3A%2F%2Fldv.org.uk%2F20818 > > >> >> Yet the post itself is still showing 0. > > > >> >> Until this is fixed there is no point having the numbers displayed. > > > >> >> Completely useless. > > > >> >> Ryan > > > >> >> On Aug 19, 9:22 am, artesea wrote: > > > >> >> > I don't give a damn about bit.ly or t.co. > > >> >> > I just want people to a) tweet wi
[twitter-dev] NULLS in JSON responses and OAuth web page errors on mobile now resolved
Hey everyone, The issues which were affecting our JSON responses and mobile OAuth web pages should be resolved now. Fixes were deployed a little earlier today and we haven't heard of any more problems. If you do still experience errors when trying to Allow applications access through the OAuth webpages on mobile, or see NULLs in the JSON responses please let us know along with your Twitter screen_name, what platform you were using and the API request you made. Thanks for your patience whilst we worked those issue out, Best, Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Whitelist and Authentication
Hi Juan, IP based whitelisting stays the same except that any authorised requests must use OAuth. This means any requests you make at the moment with a username or password will have to be converted to OAuth. If you only use public methods (no username and password) then you don't need to make any changes. It is still worth understanding what needs to be done to make OAuth work though - just in case you want to make authenticated requests. More information on converting can be found on our developer resources site: http://dev.twitter.com/pages/basic_to_oauth Hope that answers your question, Best, Matt On Wed, Aug 25, 2010 at 10:59 AM, JuanP wrote: > Hi, > We have our application (actually our IP) whitelisted in order to > access the 20K per hour rate. Our app. mainly access public timeline > for different users and nothing else that requires authentication. > When you shutdown basic authentication, will we have to use OAuth in > order to get the 20K rate? Or we just get it having our IP > whitelisted? > Thanks for your help, > > Juan > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: POST Daily limits and Direct Messages
Hey Dave, Glad to have helped. You know where we are if you have any questions when developing your app. Best, Matt On Wed, Aug 25, 2010 at 11:30 AM, DaveH wrote: > Thanks, Matt. > > Since I am still in development I do not need higher limits. So there > is no concern at the moment. Once I am in production it will be an > issue. From what you say here, my recourse is to use the whitelisting > process so seek higher limits when they are needed. > > Thanks for the clarification! > > Dave > > On Aug 24, 6:13 pm, Matt Harris wrote: >> Hi Dave, >> >> Thanks for the reply, and i'm sorry the documentation didn't answer >> your question. >> >> OAuth does have a rate limit of 350 REST API requests per hour which >> applies mainly to GET requests. This API rate limit is separate to the >> limits you found on the support pages. In fact, the limits on the >> support pages are ones which apply if you use the API or not. >> >> The options you have are this: >> >> If your application requires a higher rate limit you can apply for >> whitelisting using the Whitelisting Request Form. Be aware that >> whitelisting is only available to developers and to applications in >> production though; all other requests are rejected. The link and >> details of what to expect for this can be found in the Whitelisting >> section of the Rate Limiting documentation: >> http://dev.twitter.com/pages/rate-limiting#whitelisting >> >> The alternative is to open a support ticket explaining your situation. >> The user support team will then be able to advise you on what options >> are available. You can open a ticket usinghttp://bit.ly/twicket >> >> Hope that helps, >> Matt >> >> >> >> >> >> On Tue, Aug 24, 2010 at 9:09 AM, DaveH wrote: >> > Matt: >> >> > Not sure what you want me to pick up in the documentation. I must be >> > missing something. >> >> > When I read the page on daily POST limits [http://support.twitter.com/ >> > forums/10711/entries/15364] I see: >> > >> > Current Twitter Limits >> > The current technical limits for accounts are: >> >> > Direct Messages: 250 per day. >> > API Requests: 150 per hour. >> > Updates: 1,000 per day. The daily update limit is further broken down >> > into smaller limits for semi-hourly intervals. Retweets are counted as >> > updates. >> > Changes to Account Email: 4 per hour. >> > Following (daily): Please note that this is a technical account limit >> > only, and there are additional rules prohibiting aggressive following >> > behavior. You can find detailed page describing following limits and >> > prohibited behavior on the Follow Limits and Best Practices Page. The >> > technical follow limit is 1,000 per day. >> > Following (account-based): Once an account is following 2,000 other >> > users, additional follow attempts are limited by account-specific >> > ratios. The Follow Limits and Best Practices Page has more >> > information. >> > >> >> > When I read the page you pointed me to, I see that OAuth calls are 350 >> > per hour. >> >> > So I am still left with the same question, when we hit the daily POST >> > limit, is there a process to ask for an increase? The documentation >> > says it is controlled at a user level, which implies an increase is >> > possible. Yet the documentation does not explicitly say how an >> > increase is requested. >> >> > I am sure the answer is obvious, I just have been unable to find it. >> >> > Looking forward to your reply... >> >> > Dave >> >> -- >> >> Matt Harris >> Developer Advocate, Twitterhttp://twitter.com/themattharris > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] HTML errors on /signup, /account/new, /account/create
Hey, Thanks for highlighting this to us. I've let the web team know about so they can address it. Best, Matt On Wed, Aug 25, 2010 at 12:27 PM, RF wrote: > The account setup pages have several HTML errors exposed by the W3C > Markup Validation Service. The worst is on line 169. A reference to > the non-existent ID "user_password" causes the next field, email, to > forget the email address submitted. This error bumps the attempt > counter, thus giving the user only 3 actual attempts to setup an > account. > > The following link invokes the validator and lists the errors for / > account/new: > > http://validator.w3.org/check?uri=https%3A%2F%2Ftwitter.com%2Faccount%2Fnew&charset=%28detect+automatically%29&doctype=Inline&group=0 > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Recent API changes and new fields
This is exactly what userstreams allows you to do. ---Mark http://twitter.com/mccv On Wed, Aug 25, 2010 at 12:08 PM, arian wrote: > Hi Matt > > Zac Bowling > Is there a time line for the streaming API getting these > changes? > > Information like retweet_count, followers_count and friends_count are > very volatile and change all the time. > would be nice receive this kind of notification when any of these > fields are changed. > but I guess you woudn't build something like this. > > Arian > > On 24 ago, 21:38, Matt Harris wrote: >> Hey Zac, >> >> The Streaming API already has these fields included. >> >> Matt >> >> >> >> On Tue, Aug 24, 2010 at 9:38 AM, Zac Bowling wrote: >> > Is there a time line for the streaming API getting these changes? >> >> > Zac Bowling >> >> > On Mon, Aug 23, 2010 at 11:40 PM, Matt Harris >> > wrote: >> >> Hey everyone, >> >> >> Thanks for the questions. I'll try and answer them all in this message. >> >> >> 1) are the counts turned on? >> >> This weekend the counts were turned off and have remained off. This is >> >> because of some bugs we found in the way the value was calculated. >> >> I'll let you know when we have this resolved. >> >> >> 2) Will thesefieldsshow up in the Search and Streaming API? >> >> Thefieldsare already in the Streaming API but be aware the >> >> 'retweeted' field is not meaningful here. This is because the streamed >> >> status knows nothing of the connected user. >> >> The search API does not include this information. >> >> >> 3) How do I know if the feature is turned off? >> >> Tweets will contain a retweeted_count if available. If the service is >> >> not enabled newer Tweets will likely be missing their retweeted_count. >> >> The safest thing to do is code to handle missing values. If they are >> >> present use them, if they are not, treat them the same as when the >> >> field didn't exist. This way your code works when the retweeted_count >> >> is both enabled and disabled. >> >> >> 4) When was the feature turned on? >> >> The service was rolled out the week beginning Aug 16th >> >> >> Hope that answers your questions, >> >> Matt >> >> >> On Sat, Aug 21, 2010 at 4:33 PM, Joe wrote: >> >>> will we see this in both search and stream API? >> >> >>> On Aug 20, 6:45 pm, Matt Harris wrote: >> Hey everyone, >> >> This week we rolled out a couple ofnewdatafieldsfor the status and user >> objects. For a while it has been difficult for you to get the number of >> lists a user is listed in, or the number of times a Tweet has been >> retweeted. You were also finding it hard to know if the user had >> retweeted >> the status themselves or not. The feature requests you filed and the >> messages on the developer mailing list showed this is a pain point for >> many >> of you as it uses up many of your hourly API requests. >> >> Thesefieldsare live now and many of you have already seen them in our >> API >> responses. We intended to tell you about these changes before they were >> live, and in the future for things like this we will, but this time >> around >> our system for doing that didn't work. The good news is we know what >> went >> wrong and have made the necessary improvements needed to ensure you are >> notified before the changes happen. >> >> The recent changes which have been made affect the user and status >> objects. >> In both cases we have addedfields: >> >> To the user object: >> --- >> >> listed_count >> represents the number of public lists a user is listed in. This field >> is an >> integer. As this is anewfield it is possible some users will not have a >> listed_count value yet. >> >> follow_request_sent >> representing whether the user you are authenticating as has requested to >> follow the user you are viewing. This will be false unless the >> friendship >> request is pending. The field is a boolean and will be true or false. >> >> To the status object: >> - >> retweet_count >> represents the number of times a status has been retweeted using the >> Twitter >> retweet action. This field is an integer. There will not be a value for >> this >> field when the feature is turned off, or the Tweet was created before we >> added retweet_count support. >> >> retweeted >> represents whether the user you are authenticating as has retweeted this >> status or not. The field is a boolean and can be true or false. >> >> Changes to existing methods >> -- >> users/show >> When requesting data for suspended users the user/show used to return an >> HTTP 404 status code - it now returns HTTP 403. >> >> This change is in response to number of users who were asking if there >> was a >> >>
[twitter-dev] Re: 401 errors with xAuth
Hi Tom, Indeed, you were right, there was a line which I forgot to uncomment, which did the encoding, now I got a 200 response Thanks, Felix On Aug 25, 11:50 pm, Tom van der Woerdt wrote: > Hi Felix, > > You are not urlencoding your base string properly, specifically the nvp part. > > Tom > > Sent from my iPod > > On 25 aug. 2010, at 21:57, Felix wrote: > > > > > Hello there > > > Got an interesting situation where, although my app is xAuth enabled > > and (in theory) everything is in place the response is still 401, > > which means that I'm probably missing something > > > I am using POST over SSL tohttps://api.twitter.com/oauth/access_token > > my signature base is > > > POST&https://api.twitter.com/oauth/ > > access_token&oauth_consumer_key=CONSUMER_KEY&oauth_nonce=5a10827b9b20fbc49c > > 6c2e26e5145ef6&oauth_signature_method=HMAC- > > SHA1&oauth_timestamp=1282765745&oauth_version=1.0&x_auth_mode=client_auth&x > > _auth_password=PASSWORD&x_auth_username=fixone > > > The entire POST looks like this > > > POST /oauth/access_token HTTP/1.1 > > Host: api.twitter.com > > Connection: close > > Accept-encoding: gzip, deflate > > User-Agent: Zend_Http_Client > > Authorization: OAuth > > realm="",oauth_consumer_key="CONSUMER_KEY",oauth_nonce="5a10827b9b20fbc49c6 > > c2e26e5145ef6",oauth_signature_method="HMAC- > > SHA1",oauth_timestamp="1282765745",oauth_signature="Co3f8kQMa7vbYzLGx5NF0js > > 7BOQ > > %3D", oauth_version="1.0" > > Content-Type: application/x-www-form-urlencoded > > Content-Length: 71 > > > x_auth_mode=client_auth&x_auth_password=PASSWORD&x_auth_username=fixone > > > And the response is , of course, "401 Unauthorized" > > > I would need some help figuring out what's wrong. > > > KR > > Felix > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list > > Change your membership to this > > group:http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Entities support in Streaming API
We've got a few checks left to do before fully enabling this so we are going to wait until tomorrow. We'll post an update to @twitterapi and the mailing list with details shortly. Matt On Wed, Aug 25, 2010 at 2:12 PM, worksapp wrote: > Is Entities support in Streaming API going live today? If yes, any > specific time for go live that Twitter team would want to share. > > > Thank you > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: מענה: Re: [twitter-dev] Re: User_Timeline - include_rts not working
Hey Hen, Sorry to hear that. So I can investigate further could you please share the code you are using to obtain the timeline. Our tests show this is working as expected so I need to see how you are requesting them. Best, Matt On Wed, Aug 25, 2010 at 1:53 PM, Hen Asraf wrote: > True, I still can't see retweets > > > -הודעה מקורית- > מאת: Matt Harris > נשלח: 25/08/2010 8:30:48 pm > נושא: Re: [twitter-dev] Re: User_Timeline - include_rts not working > > Hey Hen, > > Are you still finding retweets are not showing up for you? > > Matt > > > > On Sat, Aug 21, 2010 at 7:19 AM, henasraf wrote: >> Matt, >> Any user I show in my app would not show retweets, even if they surely >> exist. You can see for yourself at http://wosaic.net/twitguin (still >> early stages, don't mind it being a bit lame), see any user such as >> myself at http://wosaic.net/twitguin/user/henasraf ; you may go >> through pages and see that no retweets ever show; they should be color >> coded in orange. You can compare to http://twitter.com/henasraf to see >> retweets that should show. >> >> Thanks, >> Hen >> >> On Aug 19, 11:34 pm, Matt Harris wrote: >>> Hey, >>> >>> Retweets should be included if they exist in the users timeline when you >>> request them. For example if you request 20 Tweets of the timeline and one >>> of those last 20 was a retweet - it will be included. If one of the last 20 >>> Tweets wasn't a retweet it won't be included, even if include_rts is true. >>> >>> Does this explain what is happening in your app? >>> If not could you give an example of a username which shows this problem. >>> >>> Best, >>> Matt >>> >>> On Thu, Aug 19, 2010 at 1:24 PM, henasraf wrote: >>> > Hey all, I'm using user_timeline to fetch the timeline of a user in my >>> > app. Problem is, it doesn't include native Retweets, even though I've >>> > set include_rts to true. The docs clearly say it should work, but it >>> > doesn't. What could be the problem? Thanks in advance :) >>> >>> -- >>> >>> Matt Harris >>> Developer Advocate, Twitterhttp://twitter.com/themattharris >> > > > > -- > > > Matt Harris > Developer Advocate, Twitter > http://twitter.com/themattharris > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Entities support in Streaming API
Is Entities support in Streaming API going live today? If yes, any specific time for go live that Twitter team would want to share. Thank you -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Twitter button not showing up in IE7
Hey Artem, I've looked at your page and can see in your code that the Tweet Button is rendering successfully, just not being shown. Looking at your code it looks like the problem is with your position: absolute; rule. In IE positioned objects like this can be missing their 'hasLayout' setting. To fix this it can be helpful to add something like zoom: 1 or height: 1% to the div. Hope that helps, Matt On Mon, Aug 23, 2010 at 11:21 PM, Artem Russakovskii wrote: > Hi there, > > I installed the new twitter button today at http://www.androidpolice.com > and it is not showing up in IE7 (in both IE8 compatibility mode and > IETester). I don't see any JS errors, but absolutely nothing is > showing up, on either the main page or the post pages. > > I tried to move the js into the header but that didn't help. > > Any ideas? > > Thank you. > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
מענה: Re: [twitter-dev] Re: User_Timeline - incl ude_rts not working
True, I still can't see retweets -הודעה מקורית- מאת: Matt Harris נשלח: 25/08/2010 8:30:48 pm נושא: Re: [twitter-dev] Re: User_Timeline - include_rts not working Hey Hen, Are you still finding retweets are not showing up for you? Matt On Sat, Aug 21, 2010 at 7:19 AM, henasraf wrote: > Matt, > Any user I show in my app would not show retweets, even if they surely > exist. You can see for yourself at http://wosaic.net/twitguin (still > early stages, don't mind it being a bit lame), see any user such as > myself at http://wosaic.net/twitguin/user/henasraf ; you may go > through pages and see that no retweets ever show; they should be color > coded in orange. You can compare to http://twitter.com/henasraf to see > retweets that should show. > > Thanks, > Hen > > On Aug 19, 11:34 pm, Matt Harris wrote: >> Hey, >> >> Retweets should be included if they exist in the users timeline when you >> request them. For example if you request 20 Tweets of the timeline and one >> of those last 20 was a retweet - it will be included. If one of the last 20 >> Tweets wasn't a retweet it won't be included, even if include_rts is true. >> >> Does this explain what is happening in your app? >> If not could you give an example of a username which shows this problem. >> >> Best, >> Matt >> >> On Thu, Aug 19, 2010 at 1:24 PM, henasraf wrote: >> > Hey all, I'm using user_timeline to fetch the timeline of a user in my >> > app. Problem is, it doesn't include native Retweets, even though I've >> > set include_rts to true. The docs clearly say it should work, but it >> > doesn't. What could be the problem? Thanks in advance :) >> >> -- >> >> Matt Harris >> Developer Advocate, Twitterhttp://twitter.com/themattharris > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] 401 errors with xAuth
Hi Felix, You are not urlencoding your base string properly, specifically the nvp part. Tom Sent from my iPod On 25 aug. 2010, at 21:57, Felix wrote: > Hello there > > Got an interesting situation where, although my app is xAuth enabled > and (in theory) everything is in place the response is still 401, > which means that I'm probably missing something > > I am using POST over SSL to https://api.twitter.com/oauth/access_token > my signature base is > > POST&https://api.twitter.com/oauth/ > access_token&oauth_consumer_key=CONSUMER_KEY&oauth_nonce=5a10827b9b20fbc49c6c2e26e5145ef6&oauth_signature_method=HMAC- > SHA1&oauth_timestamp=1282765745&oauth_version=1.0&x_auth_mode=client_auth&x_auth_password=PASSWORD&x_auth_username=fixone > > The entire POST looks like this > > POST /oauth/access_token HTTP/1.1 > Host: api.twitter.com > Connection: close > Accept-encoding: gzip, deflate > User-Agent: Zend_Http_Client > Authorization: OAuth > realm="",oauth_consumer_key="CONSUMER_KEY",oauth_nonce="5a10827b9b20fbc49c6c2e26e5145ef6",oauth_signature_method="HMAC- > SHA1",oauth_timestamp="1282765745",oauth_signature="Co3f8kQMa7vbYzLGx5NF0js7BOQ > %3D", oauth_version="1.0" > Content-Type: application/x-www-form-urlencoded > Content-Length: 71 > > x_auth_mode=client_auth&x_auth_password=PASSWORD&x_auth_username=fixone > > > And the response is , of course, "401 Unauthorized" > > I would need some help figuring out what's wrong. > > KR > Felix > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] 401 errors with xAuth
Hello there Got an interesting situation where, although my app is xAuth enabled and (in theory) everything is in place the response is still 401, which means that I'm probably missing something I am using POST over SSL to https://api.twitter.com/oauth/access_token my signature base is POST&https://api.twitter.com/oauth/ access_token&oauth_consumer_key=CONSUMER_KEY&oauth_nonce=5a10827b9b20fbc49c6c2e26e5145ef6&oauth_signature_method=HMAC- SHA1&oauth_timestamp=1282765745&oauth_version=1.0&x_auth_mode=client_auth&x_auth_password=PASSWORD&x_auth_username=fixone The entire POST looks like this POST /oauth/access_token HTTP/1.1 Host: api.twitter.com Connection: close Accept-encoding: gzip, deflate User-Agent: Zend_Http_Client Authorization: OAuth realm="",oauth_consumer_key="CONSUMER_KEY",oauth_nonce="5a10827b9b20fbc49c6c2e26e5145ef6",oauth_signature_method="HMAC- SHA1",oauth_timestamp="1282765745",oauth_signature="Co3f8kQMa7vbYzLGx5NF0js7BOQ %3D", oauth_version="1.0" Content-Type: application/x-www-form-urlencoded Content-Length: 71 x_auth_mode=client_auth&x_auth_password=PASSWORD&x_auth_username=fixone And the response is , of course, "401 Unauthorized" I would need some help figuring out what's wrong. KR Felix -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Recent API changes and new fields
Hi Matt Zac Bowling > Is there a time line for the streaming API getting these changes? Information like retweet_count, followers_count and friends_count are very volatile and change all the time. would be nice receive this kind of notification when any of these fields are changed. but I guess you woudn't build something like this. Arian On 24 ago, 21:38, Matt Harris wrote: > Hey Zac, > > The Streaming API already has these fields included. > > Matt > > > > On Tue, Aug 24, 2010 at 9:38 AM, Zac Bowling wrote: > > Is there a time line for the streaming API getting these changes? > > > Zac Bowling > > > On Mon, Aug 23, 2010 at 11:40 PM, Matt Harris > > wrote: > >> Hey everyone, > > >> Thanks for the questions. I'll try and answer them all in this message. > > >> 1) are the counts turned on? > >> This weekend the counts were turned off and have remained off. This is > >> because of some bugs we found in the way the value was calculated. > >> I'll let you know when we have this resolved. > > >> 2) Will thesefieldsshow up in the Search and Streaming API? > >> Thefieldsare already in the Streaming API but be aware the > >> 'retweeted' field is not meaningful here. This is because the streamed > >> status knows nothing of the connected user. > >> The search API does not include this information. > > >> 3) How do I know if the feature is turned off? > >> Tweets will contain a retweeted_count if available. If the service is > >> not enabled newer Tweets will likely be missing their retweeted_count. > >> The safest thing to do is code to handle missing values. If they are > >> present use them, if they are not, treat them the same as when the > >> field didn't exist. This way your code works when the retweeted_count > >> is both enabled and disabled. > > >> 4) When was the feature turned on? > >> The service was rolled out the week beginning Aug 16th > > >> Hope that answers your questions, > >> Matt > > >> On Sat, Aug 21, 2010 at 4:33 PM, Joe wrote: > >>> will we see this in both search and stream API? > > >>> On Aug 20, 6:45 pm, Matt Harris wrote: > Hey everyone, > > This week we rolled out a couple ofnewdatafieldsfor the status and user > objects. For a while it has been difficult for you to get the number of > lists a user is listed in, or the number of times a Tweet has been > retweeted. You were also finding it hard to know if the user had > retweeted > the status themselves or not. The feature requests you filed and the > messages on the developer mailing list showed this is a pain point for > many > of you as it uses up many of your hourly API requests. > > Thesefieldsare live now and many of you have already seen them in our API > responses. We intended to tell you about these changes before they were > live, and in the future for things like this we will, but this time > around > our system for doing that didn't work. The good news is we know what went > wrong and have made the necessary improvements needed to ensure you are > notified before the changes happen. > > The recent changes which have been made affect the user and status > objects. > In both cases we have addedfields: > > To the user object: > --- > > listed_count > represents the number of public lists a user is listed in. This field is > an > integer. As this is anewfield it is possible some users will not have a > listed_count value yet. > > follow_request_sent > representing whether the user you are authenticating as has requested to > follow the user you are viewing. This will be false unless the friendship > request is pending. The field is a boolean and will be true or false. > > To the status object: > - > retweet_count > represents the number of times a status has been retweeted using the > Twitter > retweet action. This field is an integer. There will not be a value for > this > field when the feature is turned off, or the Tweet was created before we > added retweet_count support. > > retweeted > represents whether the user you are authenticating as has retweeted this > status or not. The field is a boolean and can be true or false. > > Changes to existing methods > -- > users/show > When requesting data for suspended users the user/show used to return an > HTTP 404 status code - it now returns HTTP 403. > > This change is in response to number of users who were asking if there > was a > way to know if a user they were getting data for had been deleted or was > instead suspended. The change means the API agrees with the twitter.com > in > that we confirm a user exists, but that you may not see their information > because they are suspended. > > If you c
[twitter-dev] HTML errors on /signup, /account/new, /account/create
The account setup pages have several HTML errors exposed by the W3C Markup Validation Service. The worst is on line 169. A reference to the non-existent ID "user_password" causes the next field, email, to forget the email address submitted. This error bumps the attempt counter, thus giving the user only 3 actual attempts to setup an account. The following link invokes the validator and lists the errors for / account/new: http://validator.w3.org/check?uri=https%3A%2F%2Ftwitter.com%2Faccount%2Fnew&charset=%28detect+automatically%29&doctype=Inline&group=0 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] followed_by_my_follows or follows_in_common via API?
Hi TjL, The API doesn't yet support these features yet but we hope to add support soon. When it is provided we'll send an email to this developer list so you all know how to access it. Best, Matt On Wed, Aug 25, 2010 at 11:58 AM, TJ Luoma wrote: > I noticed the /follows_in_common and /followed_by_my_follows on > twitter.com, but I can't see anywhere to access this information via > the API (and didn't see any mention of it on the list). > > Is there not (yet?) a way to access that information? > > TjL > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] followed_by_my_follows or follows_in_common via API?
I noticed the /follows_in_common and /followed_by_my_follows on twitter.com, but I can't see anywhere to access this information via the API (and didn't see any mention of it on the list). Is there not (yet?) a way to access that information? TjL -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Request to better style the "Tweet" button
Hey, Thanks for the suggestion. We currently use the same behavior a default button or input uses on a webpage but I think this is an interesting idea. Can you file this as an enhancement on our issue and enhancements tracker so we have it logged. http://code.google.com/p/twitter-api/issues/list Thanks, Matt On Sat, Aug 21, 2010 at 2:04 PM, D. Smith wrote: > Just a small request: please add the style="cursor: pointer;" to the > official Tweet button. It will look better when you mouseover the > button. Tweetmeme button does that. > > Also please add the same to the "Follow" button and other buttons > produced by @Anywhere UI > > Thanks! > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: OAuth throws HTTPBadResponse error when used to get friends_timeline "since_id"
Glad to hear you worked this one out and thanks for sharing the
solution that worked for you.
Best,
Matt
On Sat, Aug 21, 2010 at 1:43 PM, kanny wrote:
> Well, it turned out to be one of those micro mistakes. I was reading
> the lasttweetid from a file by
>
> lastid = open('lasttweetid').read
>
> which was appending an "\n" at the end thus messing with the request
> generation in accessToken.
> So, just need to make it
>
> lastid = open('lasttweetid').read.strip
>
> and everything is fine.
> Now that my pet projects are OAuth-enabled, I can heave a sigh of
> relief!
>
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] last_read_status_id and last_read_dm_id
Hey Fabian, Thanks for the idea. This enhancement request exists on our issue and enhancements tracker. If you think this is a good idea you can star the request. The enhancement request is here: http://code.google.com/p/twitter-api/issues/detail?id=563 Best, Matt On Sat, Aug 21, 2010 at 3:13 AM, Fabian Schlenz wrote: > Hi there. > > Anyone who uses Twitter from multiple devices will have noticed one thing: It > can be really hard to figure out which Tweets he already read and which are > new. Many clients incorporate some sort of sync-feature between multiple > clients, but those info isn't available to clients from another publisher. So > why not save this info in the twitter account-data? Here are some thoughts > about this: > > Tweets have an incrementing ID and (IMO) should mostly be read in the correct > order. So there is not need to individually track which user read which > tweets. You could just save the ID of the newest tweet the user read (same > goes for DMs because they have their own IDs). Tweets with an ID greater than > the memorized ID would be considered new. > > On Twitter's side there would be two new field necessary. Let's for example > call them last_read_status_id and last_read_dm_id. Also we would need two > more API endpoints: account/get_last_read_ids, which just returns > last_read_status_id and last_read_dm_id and account/set_last_read_ids, which > would take at least one of both values and save them to the Twitter account > the user is authenticated for. > > > What do you think? I'd love to see this feature in the twitter API and would > implement it in my clients ASAP. > > Best regards, > Fabian Schlenz > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Twitter OAuth Authentication Fails
Hi Matt, Has this fix gone out yet? I'm still seeing the error. Thanks, Mark -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: User_Timeline - include_rts not working
Hey Hen, Are you still finding retweets are not showing up for you? Matt On Sat, Aug 21, 2010 at 7:19 AM, henasraf wrote: > Matt, > Any user I show in my app would not show retweets, even if they surely > exist. You can see for yourself at http://wosaic.net/twitguin (still > early stages, don't mind it being a bit lame), see any user such as > myself at http://wosaic.net/twitguin/user/henasraf ; you may go > through pages and see that no retweets ever show; they should be color > coded in orange. You can compare to http://twitter.com/henasraf to see > retweets that should show. > > Thanks, > Hen > > On Aug 19, 11:34 pm, Matt Harris wrote: >> Hey, >> >> Retweets should be included if they exist in the users timeline when you >> request them. For example if you request 20 Tweets of the timeline and one >> of those last 20 was a retweet - it will be included. If one of the last 20 >> Tweets wasn't a retweet it won't be included, even if include_rts is true. >> >> Does this explain what is happening in your app? >> If not could you give an example of a username which shows this problem. >> >> Best, >> Matt >> >> On Thu, Aug 19, 2010 at 1:24 PM, henasraf wrote: >> > Hey all, I'm using user_timeline to fetch the timeline of a user in my >> > app. Problem is, it doesn't include native Retweets, even though I've >> > set include_rts to true. The docs clearly say it should work, but it >> > doesn't. What could be the problem? Thanks in advance :) >> >> -- >> >> Matt Harris >> Developer Advocate, Twitterhttp://twitter.com/themattharris > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: POST Daily limits and Direct Messages
Thanks, Matt. Since I am still in development I do not need higher limits. So there is no concern at the moment. Once I am in production it will be an issue. From what you say here, my recourse is to use the whitelisting process so seek higher limits when they are needed. Thanks for the clarification! Dave On Aug 24, 6:13 pm, Matt Harris wrote: > Hi Dave, > > Thanks for the reply, and i'm sorry the documentation didn't answer > your question. > > OAuth does have a rate limit of 350 REST API requests per hour which > applies mainly to GET requests. This API rate limit is separate to the > limits you found on the support pages. In fact, the limits on the > support pages are ones which apply if you use the API or not. > > The options you have are this: > > If your application requires a higher rate limit you can apply for > whitelisting using the Whitelisting Request Form. Be aware that > whitelisting is only available to developers and to applications in > production though; all other requests are rejected. The link and > details of what to expect for this can be found in the Whitelisting > section of the Rate Limiting documentation: > http://dev.twitter.com/pages/rate-limiting#whitelisting > > The alternative is to open a support ticket explaining your situation. > The user support team will then be able to advise you on what options > are available. You can open a ticket usinghttp://bit.ly/twicket > > Hope that helps, > Matt > > > > > > On Tue, Aug 24, 2010 at 9:09 AM, DaveH wrote: > > Matt: > > > Not sure what you want me to pick up in the documentation. I must be > > missing something. > > > When I read the page on daily POST limits [http://support.twitter.com/ > > forums/10711/entries/15364] I see: > > > > Current Twitter Limits > > The current technical limits for accounts are: > > > Direct Messages: 250 per day. > > API Requests: 150 per hour. > > Updates: 1,000 per day. The daily update limit is further broken down > > into smaller limits for semi-hourly intervals. Retweets are counted as > > updates. > > Changes to Account Email: 4 per hour. > > Following (daily): Please note that this is a technical account limit > > only, and there are additional rules prohibiting aggressive following > > behavior. You can find detailed page describing following limits and > > prohibited behavior on the Follow Limits and Best Practices Page. The > > technical follow limit is 1,000 per day. > > Following (account-based): Once an account is following 2,000 other > > users, additional follow attempts are limited by account-specific > > ratios. The Follow Limits and Best Practices Page has more > > information. > > > > > When I read the page you pointed me to, I see that OAuth calls are 350 > > per hour. > > > So I am still left with the same question, when we hit the daily POST > > limit, is there a process to ask for an increase? The documentation > > says it is controlled at a user level, which implies an increase is > > possible. Yet the documentation does not explicitly say how an > > increase is requested. > > > I am sure the answer is obvious, I just have been unable to find it. > > > Looking forward to your reply... > > > Dave > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Whitelist and Authentication
Hi, We have our application (actually our IP) whitelisted in order to access the 20K per hour rate. Our app. mainly access public timeline for different users and nothing else that requires authentication. When you shutdown basic authentication, will we have to use OAuth in order to get the 20K rate? Or we just get it having our IP whitelisted? Thanks for your help, Juan -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Tweed API calls getting lots of failures
We have a fix about to go out which we think will fix this issue, we'll update this list when it has been deployed. Matt On Tue, Aug 24, 2010 at 11:26 AM, DWF wrote: > We're using OAuth/xAuth successfully for a while now, but last night > some users started reporting constant failures. I didn't start seeing > it until this morning. We're getting 401s, so we ask for the user's > password again and attempt to re-auth (& get a new token) but it never > succeeds. > > Any thoughts on what we should look at? Does our app look OK on your > end? > > Any other OAuth folks have their apps on fire? > > thx, > > --dwf > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Replies/mentions not available?
If you are missing mentions on both the website and the API you should open a support ticket with Twitter support. The team there can check your account and let you know what can be done. You can contact support through this form (make sure you are signed in as the account whose mentions are missing): http://bit.ly/twicket Matt On Wed, Aug 25, 2010 at 5:48 AM, srikanth reddy wrote: > I have very few mentions(total less than 10) but none of them are visible > in my mentions tab even in web page let alone using api. I have verified > this with 3 other accounts and none of them show the mentions . Its always > blank. But those mentions are not very recent (the last one being in FEB of > this year) > > On Tue, Aug 24, 2010 at 10:54 PM, SM wrote: >> >> Hi Taylor, >> I am missing all mentions since July 31. This has been the case for at >> least a week, probably more. >> >> On Aug 24, 8:17 am, Taylor Singletary >> wrote: >> > There is a known issue related to JSON timelines containing null >> > elements, >> > which has crippled some clients. We'll have a fix for this deployed >> > today as >> > soon as we can. >> > >> > As for your mentions not showing on your web page -- can you share any >> > status ids that you think should be there that aren't? >> > >> > Thanks, >> > Taylor >> > >> > On Tue, Aug 24, 2010 at 7:52 AM, srikanth reddy >> > wrote: >> > >> > >> > >> > > I am not getting the mentions even in web page. Is there some problem? >> > > Also one of my users has complained about the inconsistency in >> > > fetching >> > > the results for hometimeline (related to json output. Not sure(yet) if >> > > this >> > > is my app's problem or from twitter but just want to check if there >> > > are any >> > > known problems from twitter related to json output) > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: null posts in home_timeline
Thanks for the information about this. We're aware nulls were showing
up again overnight and are looking into it now. I'll post an update
when I have more information.
Thanks for your patience everyone,
Matt
On Tue, Aug 24, 2010 at 9:51 PM, Caizer wrote:
> I read that it should be fixed from @twitterapi.
>
> But I am still receiving the null in exactly same location.
> Will it take some time to be applied to entire tweet response?
>
>
> Caizer.
>
>
> On Aug 24, 11:34 pm, Matt Harris wrote:
>> Hey everyone,
>>
>> Thanks for your patience and for sharing the erroneous responses.
>> We're working on this and will have a fix rolled out soon.
>>
>> Best,
>> Matt
>>
>>
>>
>>
>>
>> On Tue, Aug 24, 2010 at 7:25 AM, Nik Fletcher wrote:
>> >http://twitter.com/twitterapi/status/22002256380
>>
>> > -N
>>
>> > --
>> > Nik Fletcher
>> > @nikf
>>
>> > On Aug 24, 9:49 am, emmettoc wrote:
>> >> Hello,
>>
>> >> Many users of some client apps are still in trouble because of null
>> >> results in home_timeline.
>> >> You can check usernames in trouble by searching famous twitter app
>> >> names.
>>
>> >> Did you change the api specific? Or do you have any plan to fix this?
>>
>> >> Thanks,
>> >> emmettoc
>>
>> >> On 8月24日, 午後3:41, Matt Harris wrote:
>>
>> >> > Hi David,
>>
>> >> > Could you provide a couple of status IDs or a username so we can take
>> >> > a look at this.
>>
>> >> > Thanks,
>> >> > Matt
>>
>> >> > On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
>>
>> >> > wrote:
>> >> > > Hey, seeing json like this:
>>
>> >> > >
>> >> > > "text": "I really need to work out a way to make myself read
>> >> > > more books...I've found three in the last 10 minutes."
>> >> > > },
>> >> > > null,
>> >> > > {
>> >> > > "coordinates": null,
>> >> > > .
>>
>> >> > > null objects being included in the list of tweets?
>>
>> >> > > Only seems to have started today.
>>
>> >> > > David
>>
>> >> > --
>>
>> >> > Matt Harris
>> >> > Developer Advocate, Twitterhttp://twitter.com/themattharris
>>
>> --
>>
>> Matt Harris
>> Developer Advocate, Twitterhttp://twitter.com/themattharris
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Tweet button fails to parse URL
Hello, When I try and populate a Tweet button link with a data-url attribute of the form: http://www.wordnik.com/thesaurus/hen#w1=bird&w2=fowl I get the message: "'url' parameter does not contain a valid URL." I first thought I needed to escape the ampersand, but after trying every conceivable way of doing that, I instead replaced the # with a ?, and it works fine. So it seems ampersands are only a problem when there is no ?. This strikes me as a bug -- the url above is valid (it's using the onhashchange event to save state). Is this a known issue, or is there a workaround for it, or am I missing something here? Best, John -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Twitter OAuth Authentication Fails
Looks like the problem is there still. Any word on the fix? Skylar On Aug 24, 9:59 pm, Matt Harris wrote: > Hi Kevin, > > Thanks for raising this query. We have a fix on it's way out tonight > or tomorrow morning for this. > > Also, whilst this isn't related to the issue you are experiencing I > recommended updating your URL to point to our API. > > All requests for the API should be directed > tohttp://api.twitter.com/1/. > OAuth requests should go > tohttps://api.twitter.com/oauth/,e.g.https://api.twitter.com/oauth/authenticate > > Best, > Matt > > > > On Tue, Aug 24, 2010 at 4:55 PM, Kevin Wallace > wrote: > > I have three iPhone apps that use OAuth to communicate with Twitter. > > They have been working well for several months but recently when > > trying to set-up authentication and exchange the various OAuth tokens > > using Safari on the iPhone, Safari brings up a page from Twitter that > > says: > > > Something is technically wrong. > > Thanks for noticing -- we're going to fix it up and have things back > > to normal soon. > > > Normally authentication works and the page Twitter returns redirects > > back to our application on the iPhone. Again, this has all worked for > > several months until very recently. We just noticed the problem > > ourselves today. Here's an example authenticate URL that used to work > > but now fails: > > >http://twitter.com/oauth/authenticate?oauth_token=r8ZW21dPbUteSOgfFJ0... > > > Does anyone out there know what's going wrong? This has all worked > > for hundreds of thousands of our customers for several months now and > > nothing in our app has changed in two months. Can anyone shed light > > on this for me? Thanks! > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list > > Change your membership to this > > group:http://groups.google.com/group/twitter-development-talk?hl=en > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Application Crash
Still having crash issues even after a reinstall. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] WIDGET ISSUES
Hi Guys, I have tried to add a twitter profile widget from twitter goodies link on my website.I could'nt get the widget code because of the following warnings shown on my status bar in IE8. Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/ 4.0; InfoPath.2; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Timestamp: Wed, 25 Aug 2010 05:31:50 UTC Message: Object doesn't support this property or method Line: 1 Char: 1 Code: 0 URI: http://a0.twimg.com/a/1282682459/javascripts/api.js?1282685502 Message: Object doesn't support this property or method Line: 252 Char: 1 Code: 0 URI: http://twitter.com/goodies/widgets hope u guys there resolve these errors at the earliest. Thanks lingamaneni. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Twitter OAuth Authentication Fails
We are also getting this error. You can recreate the "Something is technically wrong." on both iPads and iPhones using these demos: http://twitter.abrah.am http://sinitter.moocode.com Here is a screenshot of the error: http://db.tt/FmYjCC2 Interestingly, they work fine on desktop Safari. Can you please update this post when the fix is up? Thanks, Skylar On Aug 24, 9:59 pm, Matt Harris wrote: > Hi Kevin, > > Thanks for raising this query. We have a fix on it's way out tonight > or tomorrow morning for this. > > Also, whilst this isn't related to the issue you are experiencing I > recommended updating your URL to point to our API. > > All requests for the API should be directed > tohttp://api.twitter.com/1/. > OAuth requests should go > tohttps://api.twitter.com/oauth/,e.g.https://api.twitter.com/oauth/authenticate > > Best, > Matt > > > > On Tue, Aug 24, 2010 at 4:55 PM, Kevin Wallace > wrote: > > I have three iPhone apps that use OAuth to communicate with Twitter. > > They have been working well for several months but recently when > > trying to set-up authentication and exchange the various OAuth tokens > > using Safari on the iPhone, Safari brings up a page from Twitter that > > says: > > > Something is technically wrong. > > Thanks for noticing -- we're going to fix it up and have things back > > to normal soon. > > > Normally authentication works and the page Twitter returns redirects > > back to our application on the iPhone. Again, this has all worked for > > several months until very recently. We just noticed the problem > > ourselves today. Here's an example authenticate URL that used to work > > but now fails: > > >http://twitter.com/oauth/authenticate?oauth_token=r8ZW21dPbUteSOgfFJ0... > > > Does anyone out there know what's going wrong? This has all worked > > for hundreds of thousands of our customers for several months now and > > nothing in our app has changed in two months. Can anyone shed light > > on this for me? Thanks! > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list > > Change your membership to this > > group:http://groups.google.com/group/twitter-development-talk?hl=en > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: null posts in home_timeline
I read that it should be fixed from @twitterapi.
But I am still receiving the null in exactly same location.
Will it take some time to be applied to entire tweet response?
Caizer.
On Aug 24, 11:34 pm, Matt Harris wrote:
> Hey everyone,
>
> Thanks for your patience and for sharing the erroneous responses.
> We're working on this and will have a fix rolled out soon.
>
> Best,
> Matt
>
>
>
>
>
> On Tue, Aug 24, 2010 at 7:25 AM, Nik Fletcher wrote:
> >http://twitter.com/twitterapi/status/22002256380
>
> > -N
>
> > --
> > Nik Fletcher
> > @nikf
>
> > On Aug 24, 9:49 am, emmettoc wrote:
> >> Hello,
>
> >> Many users of some client apps are still in trouble because of null
> >> results in home_timeline.
> >> You can check usernames in trouble by searching famous twitter app
> >> names.
>
> >> Did you change the api specific? Or do you have any plan to fix this?
>
> >> Thanks,
> >> emmettoc
>
> >> On 8月24日, 午後3:41, Matt Harris wrote:
>
> >> > Hi David,
>
> >> > Could you provide a couple of status IDs or a username so we can take
> >> > a look at this.
>
> >> > Thanks,
> >> > Matt
>
> >> > On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
>
> >> > wrote:
> >> > > Hey, seeing json like this:
>
> >> > >
> >> > > "text": "I really need to work out a way to make myself read
> >> > > more books...I've found three in the last 10 minutes."
> >> > > },
> >> > > null,
> >> > > {
> >> > > "coordinates": null,
> >> > > .
>
> >> > > null objects being included in the list of tweets?
>
> >> > > Only seems to have started today.
>
> >> > > David
>
> >> > --
>
> >> > Matt Harris
> >> > Developer Advocate, Twitterhttp://twitter.com/themattharris
>
> --
>
> Matt Harris
> Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: Replies/mentions not available?
I have very few mentions(total less than 10) but none of them are visible in my mentions tab even in web page let alone using api. I have verified this with 3 other accounts and none of them show the mentions . Its always blank. But those mentions are not very recent (the last one being in FEB of this year) On Tue, Aug 24, 2010 at 10:54 PM, SM wrote: > Hi Taylor, > I am missing all mentions since July 31. This has been the case for at > least a week, probably more. > > On Aug 24, 8:17 am, Taylor Singletary > wrote: > > There is a known issue related to JSON timelines containing null > elements, > > which has crippled some clients. We'll have a fix for this deployed today > as > > soon as we can. > > > > As for your mentions not showing on your web page -- can you share any > > status ids that you think should be there that aren't? > > > > Thanks, > > Taylor > > > > On Tue, Aug 24, 2010 at 7:52 AM, srikanth reddy > > wrote: > > > > > > > > > I am not getting the mentions even in web page. Is there some problem? > > > Also one of my users has complained about the inconsistency in > fetching > > > the results for hometimeline (related to json output. Not sure(yet) if > this > > > is my app's problem or from twitter but just want to check if there are > any > > > known problems from twitter related to json output) > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: null posts in home_timeline
Hey Matt,
Just a quick update. We're seeing a number of further reports of this
overnight. I'm trying to track it down with our users, but my own home
timeline is no longer showing the issue.
Cheers
-N
--
Nik Fletcher
@nikf
On Aug 24, 3:34 pm, Matt Harris wrote:
> Hey everyone,
>
> Thanks for your patience and for sharing the erroneous responses.
> We're working on this and will have a fix rolled out soon.
>
> Best,
> Matt
>
>
>
>
>
> On Tue, Aug 24, 2010 at 7:25 AM, Nik Fletcher wrote:
> >http://twitter.com/twitterapi/status/22002256380
>
> > -N
>
> > --
> > Nik Fletcher
> > @nikf
>
> > On Aug 24, 9:49 am, emmettoc wrote:
> >> Hello,
>
> >> Many users of some client apps are still in trouble because of null
> >> results in home_timeline.
> >> You can check usernames in trouble by searching famous twitter app
> >> names.
>
> >> Did you change the api specific? Or do you have any plan to fix this?
>
> >> Thanks,
> >> emmettoc
>
> >> On 8月24日, 午後3:41, Matt Harris wrote:
>
> >> > Hi David,
>
> >> > Could you provide a couple of status IDs or a username so we can take
> >> > a look at this.
>
> >> > Thanks,
> >> > Matt
>
> >> > On Mon, Aug 23, 2010 at 10:15 PM, David Novakovic
>
> >> > wrote:
> >> > > Hey, seeing json like this:
>
> >> > >
> >> > > "text": "I really need to work out a way to make myself read
> >> > > more books...I've found three in the last 10 minutes."
> >> > > },
> >> > > null,
> >> > > {
> >> > > "coordinates": null,
> >> > > .
>
> >> > > null objects being included in the list of tweets?
>
> >> > > Only seems to have started today.
>
> >> > > David
>
> >> > --
>
> >> > Matt Harris
> >> > Developer Advocate, Twitterhttp://twitter.com/themattharris
>
> --
>
> Matt Harris
> Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: ReTweet / Count Consistency
Hi Matt,
First - thanks for getting back to me so quickly and clearly. Makes a
developer feel very welcome to know there's support at hand.
--- Search API (A&B ) ---
Understood and thanks for the examples.
There does to be a discrepancy though between /search?q={} and /search.
(json|xml|atom)?q={} - is this intentional?
The rendered output for Twitter API is currently showing three tweets
(screenshot: http://goo.gl/Oz02) that are not available in the same
query under json... the nodes just don't seem to appear so I wonder
if this is a feature of the website that's not been rolled out to the
data output yet?
Actually - I notice that the recent_retweets node is present in the
docs example: http://dev.twitter.com/doc/get/search#example-requests -
am I doing something wrong for it not to appear in a test case or is
this in-development as per the main API's "retweet_count" node?
Also; is there a lower limit of retweets before the retweet
information appears?
--- Twitter API (X&Y) ---
Thanks, that's great. I'll wait to hear when it's re-released.
All the best,
Jim
On Aug 24, 11:59 pm, Matt Harris wrote:
> Hey Jimbo,
>
> I can understand your confusion. Each of the APIs handles things
> differently and their different approaches can make things like this
> hard to work out. I've answered your questions inline.
>
> A) Search API: Keyword Search
> --
> All retweets appear, against matching search term ( some text from the
> tweet ) including opening phrase: "retweeter RT @retweeted
> {tweet.}"
>
> This is expected behavior although the Retweet you refer to is the
> "old style" and is not counted as a retweet in our system. Native
> retweets show as a single Tweet with a block underneath saying
> something like "100+ recent retweets". Native retweets do not show as
> separate entries in the search API.
>
> So searching for a keyword will show the original Tweet with a block
> underneath indicating how many native retweets that Tweet had. It will
> also find old style RTs as to Twitter those are the same as a Tweet.
> Example "JSON NULL"
>
> B) Search API: Username
> --
> Only the original tweet plus those RT's that have been done the "old
> fashioned" way appear.
>
> If you are searching for just the username and not "from:username",
> the results behave the same as A.
> So searching for a username will show the original Tweet with a block
> underneath indicating how many native retweets that Tweet had. It will
> also find old style RTs as to Twitter those are the same as a Tweet.
> Example "twitterapi"
>
> X) Twitter Website - twitter.com/#retweeted_of_mine
> --
> Tweets appear plus lots of information about the retweets; count, user IDs
> etc.
>
> In some ways it is useful to think of Search as Index which points you
> to the actual Tweet. If you think of it that way it makes sense the
> website knows more about a Tweet than Search does. twitter.com is also
> built to show you complete information about Tweets. Search is
> designed to find real-time relevant Tweets about a keyword.
>
> Y) Twitter API -http://api.twitter.com/1/statuses/retweets_of_me.json
> --
> Original retweeted tweets appear but there's no retweet data. There's
> an empty "retweet_count" node and a FALSE "retweeted" node ( which is
> demonstrably wrong ).
>
> Many developers have been asking for access to the retweet information
> displayed on the website so we added the retweet_count and retweeted
> nodes last week. Unfortunately we found an issue with those fields
> soon after launch which we need to work out. Until then those fields
> will not include useful information. We'll be updating this mailing
> list with developments.
>
> I hope that answers you questions and clarifies reason for the differences.
>
> Matt Harris
> Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk?hl=en
