[twitter-dev] Re: OAuth rate limit of 150
This has now been fixed in the latest version(0.9.10) On Sep 4, 6:16 am, Daniel Ribeiro dan...@gmail.com wrote: I had this issue as well. Posted this ticket on the project's page:http://github.com/jnunemaker/twitter/issues#issue/59 On Sep 3, 1:05 pm, Matt Harris thematthar...@twitter.com wrote: Hey Roger, Thanks for posting the solution which worked for you and glad it was sorted out. For completeness the answer to your question about getting a different rate limit on a different IP is expected if authentication isn't happening. This is because each IP has it's own 150 requests. Best, Matt On Fri, Sep 3, 2010 at 7:09 AM, Roger Ertesvåg webfo...@webfokus.no wrote: So just in case case someone else experience the same problem, I solved it by switching from version 0.9.8 to 0.9.7 of the Ruby Twitter Gem. Still not sure what the problem was, but I'm pretty sure I was properly authenticated since I could do things like updating lists. Regards Roger On Aug 31, 10:09 pm, Roger Ertesvåg webfo...@webfokus.no wrote: Hi Matt, thanks for your thorough response. So I assume this rate limit would be IP based then? I did some tests and got different rate limits on the server and on my development machine, which seems to support your theory that I'm not authenticated properly. After some more testing it seems that the problem is in the library, after switching to a previous version I get a rate limit of 350. I will do some more testing tomorrow to confirm this. Again, thanks for your help. Regards Roger On Aug 31, 8:34 pm, Matt Harris thematthar...@twitter.com wrote: Hey Roger, Thanks for sharing your code. A few things about the rate limits you are seeing: The 150 rate limit is for non-authenticated requests to the Twitter API. These requests happen when no user identifying details are sent. The 350 rate limit is for OAuth authenticated requests to the Twitter API. These requests happen when you send a user token and secret. As you are not authenticating with Basic Auth in any of your requests you would only see the unauthenticated rate limit (150) or your OAuth rate limit (350). The reason you could be seeing 150 is that the token and secret you have are no longer valid - although in that situation I would expect us to return an error saying Could not authenticate with OAuth. I'll be looking into other reasons why that might be happening later today. Hope that explains what you are seeing, Matt On Tue, Aug 31, 2010 at 12:39 AM, Roger Ertesvåg webfo...@webfokus.no wrote: Hi, I'm using the ruby twitter gem: http://github.com/jnunemaker/twitter So to set it up I do: oauth = Twitter::OAuth.new(CONFIG['twitter_key'], CONFIG['twitter_secret']) oauth.authorize_from_access(CONFIG['twitter_atoken'], CONFIG['twitter_asecret']) base = Twitter::Base.new(oauth) Then when I do: base.rate_limit_status I get: #Hashie::Mash hourly_limit=150 remaining_hits=150 reset_time=Tue Aug 31 08:26:37 + 2010 reset_time_in_seconds=1283243197 If I use the exact same code for other accounts I have I get: #Hashie::Mash hourly_limit=350 remaining_hits=350 reset_time=Tue Aug 31 08:22:40 + 2010 reset_time_in_seconds=1283242960 Also, if I was not authorized by OAuth shouldn't the limit be even lower? Regards Roger On Aug 31, 1:03 am, Matt Harris thematthar...@twitter.com wrote: Hi Roger, It sounds like the OAuth part of your request isn't being seen by our servers. A rate limit of 150 will be reported whenever you make a request without authorisation. Can you share the code you are using to make the requests so we can see what might be going wrong? Thanks, Matt On Mon, Aug 30, 2010 at 11:30 AM, Roger Ertesvåg webfo...@webfokus.no wrote: The OAuth rate limit for one of my accounts is stuck at 150. From what I'm reading, and seeing from other accounts I have, it is my understanding that it should be 350. What can I do to fix this? Regards Roger Ertesvag -- 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
[twitter-dev] Per user retweet count
Hi, Is there any way to get the Retweet count per user? i.e., number of tweets of a particular user that are Retweeted? Search api with 'RT @username' gives the retweets but again its a only a few days of data. 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
[twitter-dev] tweetbutton color
can we change the color of the tweetbutton icon? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Search with geocode does not respect search radius?
Hello, Since a few days it seems that search restricted by geolocation and search radius is not working correctly anymore. If I submit this request: http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C1kmrpp=100 I expect all resuls to originate from a geocode within 1km radius around the central coordinate. As of a few days ago I get many results from much farther away, up to several tens of kilometers. Is this a known issue? Any time to a fix? Or has there been an API change? Note: I revisited the API documentation ad could not find any recent changes. Best, Joe. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Search with geocode does not respect search radius?
We have a bug right now effecting exactly these kinds of searches. I'm not sure how quickly it will be fixed, but I'm hoping it will be early next week. I don't think there are any functional workarounds besides merging multiple searches. Sorry about the mess! Taylor On Fri, Sep 24, 2010 at 6:57 AM, Johannes la Poutre jsixp...@gmail.comwrote: Hello, Since a few days it seems that search restricted by geolocation and search radius is not working correctly anymore. If I submit this request: http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C1kmrpp=100 I expect all resuls to originate from a geocode within 1km radius around the central coordinate. As of a few days ago I get many results from much farther away, up to several tens of kilometers. Is this a known issue? Any time to a fix? Or has there been an API change? Note: I revisited the API documentation ad could not find any recent changes. Best, Joe. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Per user retweet count
IIRC Matt / Taylor have said that Twitter search typically only keeps 7 days worth of data for searching, so you can't go any further back than that at the moment. Cheers -N On Sep 24, 8:14 am, Karthik K karthikkato...@gmail.com wrote: Hi, Is there any way to get the Retweet count per user? i.e., number of tweets of a particular user that are Retweeted? Search api with 'RT @username' gives the retweets but again its a only a few days of data. 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
Re: [twitter-dev] Re: Per user retweet count
Karthik, I definitely think it's an interesting value to work with/report to a user -- the number of retweets a given user has issued. Right now, there's no way to get that info without manually counting them from the user_timeline for a user. user_timeline typically goes back around 3200 tweets (+/- some amount), so for users with less than 3200 tweets you could calculate the total number of retweets pretty easily. Otherwise, you could just provide the # of RTs in the period of time from point 0 to -1 of the entire user_timeline. Taylor On Fri, Sep 24, 2010 at 7:34 AM, Nik Fletcher nik.fletc...@gmail.comwrote: IIRC Matt / Taylor have said that Twitter search typically only keeps 7 days worth of data for searching, so you can't go any further back than that at the moment. Cheers -N On Sep 24, 8:14 am, Karthik K karthikkato...@gmail.com wrote: Hi, Is there any way to get the Retweet count per user? i.e., number of tweets of a particular user that are Retweeted? Search api with 'RT @username' gives the retweets but again its a only a few days of data. 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 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] include_rts for /1/statuses/home_timeline
The latest announcement mentions include_rts for /1/statuses/ user_timeline and /1/statuses/friends_timeline but not for /1/statuses/ home_timeline. Am I alone in desiring include_rts for /1/statuses/ home_timeline as well? I find the current method of blocking retweets per user to be somewhat cumbersome, but I can understand Twitter's rationale behind this (some people retweet interesting things while others don't). What makes this platform great is that it can be consumed in so many different ways by so many different types of consumers. While a timeline-level block of retweets might be confusing when paired with user-level block of retweets, I see value in providing it to clients dedicated to simple reading of timelines by users who only want to read from those he or she follows. Thank you for your time, --Derek -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Missing entities in REST
This entities not appearing problem still exists, unfortunately. It's maddeningly sporadic. No update yet on when there will be a fix for this issue. Hope for it to be soon! Taylor 2010/9/23 András Bártházi and...@barthazi.hu Hi, My problem is a bit different, for the very same requests with PHP I'm getting entities, while with Node.js I can't get entities, even with include_entities=true. As I see, the only difference between the two requests (the application is the same, the user is the same, the server is the same, even the oauth user login is the same) is that the PHP OAuth client is sending the OAuth params (oauth_consumer_key and so) with the url as GET params, but the Node.js client is using HTTP headers. Any idea? Bye, Andras We're still investigating this issue -- it is not happening consistently across the board and has been difficult to track down. If you're *never* getting entities when requesting timelines, and you're including include_entities=true then please leave your member id here for additional investigation. Hope to have this fixed soon. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How do I create a developer account?
Ok thanks! Sorry I'm probably the only developer on earth that doesn't use twitter :) ~kim On Sep 23, 8:00 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi CSKim, You can use your regular old Twitter account, or otherwise create a new Twitter account. Apps belong to Twitter accounts. Sorry that this isn't clear! Taylor On Thu, Sep 23, 2010 at 4:40 PM, CSKim kim.maccorm...@gmail.com wrote: I want to register an application, but when I click on the link, it takes me to a sign in page. I can't find anywhere to create an account. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Using @Anywhere under SSL
I agree its a real limit to an otherwise highly convenient product. Seems easy enough to get akamai to use the right ssl cert. Is there some other technical snafu here or is this just an administrative item you haven't gotten to yet? I'd vote to bump it up in priority if its the latter. Cheers, Bob On Sep 22, 7:03 am, Justin justin.realw...@gmail.com wrote: It is a shame Cassie, I'm having to use OAuth - more flexability but would be nice to have the simplicity of Anywhere On Sep 21, 8:37 pm, Cassie Lynn cassie.schwendi...@gmail.com wrote: yet? Do we have any way of knowing when this might happen? And thanks for asking this here Justin! I asked on @anywhere and no one has replied (it has been almost a week). Thanks! - Cassie On Sep 20, 5:00 am, Tom van der Woerdt i...@tvdw.eu wrote: FYI, there's a Mailing List specifically for @Anywhere. The list you mailed to is the API developer list. http://groups.google.com/group/twitter-dev-anywhere To answer your question: no, there's no SSL version (yet). Tom On Mon, 20 Sep 2010 02:53:05 -0700 (PDT), Justin justin.realw...@gmail.com wrote: I would love to use the Connect with Twitter @Anywhere function but I would need to use it in a secure enviroment - that is under SSL. I first tried this when @Anywhere was first launched adn gave up thinking that perhaps it's a little too early? Having recently returned to it, I was disapointed to discover that the situation doesn't seem to have changed. Does anyone know if this is possible? Simply adding an s to http://platform.twitter.com/anywhere.jsdoesn'twork, I wonder if there's another unpublished URL, or if Twitter have any plans to impliment this. I'd prefer to use @Anywhere over oAuth, but may not have a choice :-( Thanks Justin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Search with geocode does not respect search radius?
Ouch, that is pretty nasty... I'll see what can be done as merging multiple searches will degrade response times rather badly. Thanks for the reply! On Sep 24, 4:33 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We have a bug right now effecting exactly these kinds of searches. I'm not sure how quickly it will be fixed, but I'm hoping it will be early next week. I don't think there are any functional workarounds besides merging multiple searches. Sorry about the mess! Taylor On Fri, Sep 24, 2010 at 6:57 AM, Johannes la Poutre jsixp...@gmail.comwrote: Hello, Since a few days it seems that search restricted by geolocation and search radius is not working correctly anymore. If I submit this request: http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C... I expect all resuls to originate from a geocode within 1km radius around the central coordinate. As of a few days ago I get many results from much farther away, up to several tens of kilometers. Is this a known issue? Any time to a fix? Or has there been an API change? Note: I revisited the API documentation ad could not find any recent changes. Best, Joe. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Perl Net::Twitter and oAuth
* sftriman dal...@gmail.com [100923 07:19]: I see - well, I'm using cPanel and tried, got this: Installing Perl Module HTTP::Message Method: Perl Expect Testing connection speed...(using fast method)...Done Ping:0 (ticks) Testing connection speed to cpan.erlbaum.net using pureperl...(14957.14 bytes/s)...Done Ping:0 (ticks) Testing connection speed to mirrors.24-7-solutions.net using pureperl...(103966.67 bytes/s)...Done Ping:0 (ticks) Testing connection speed to cpan.belfry.net using pureperl...(157050.00 bytes/s)...Done Three usable mirrors located Mirror Check passed for cpan.belfry.net (/index.html) commit: wrote '/usr/lib/perl5/5.8.8/CPAN/Config.pm' CPAN: Storable loaded ok (v2.21) Going to read /home/.cpan/Metadata Database was generated on Wed, 22 Sep 2010 00:34:03 GMT cPCPAN: Module (HTTP::Message) holdback (5.837 held back to 5.810) HTTP::Message is up to date (5.810). perlmod--Install done So not sure what to do. Take a look at local::lib: http://search.cpan.org/~getty/local-lib-1.006007/lib/local/lib.pm You should be able to install your own, local modules in your home directory. -Marc -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Streaming API skips users
John- Thanks for confirming the way this should work. We'll work on the client side code to see what it's doing with the stream data and how it compares to the raw stream from curl. -Ginny On Sep 24, 12:01 pm, John Kalucki j...@twitter.com wrote: Accounts should work all of the time, almost always with very low latency, unless they are protected accounts or otherwise filtered from search and streaming. Once an account is filtered, it should remain filtered for a very long time and not bounce back and forth. If you perform the same request with curl, and study the output, do you see the data that you expect? -John Kaluckihttp://twitter.com/jkalucki Twitter, Inc. On Thu, Sep 23, 2010 at 8:59 PM, Ginny Hendry ginnyhen...@gmail.com wrote: We are new to the Twitter API. In early stages of testing an app, we reading from the streaming API to get tweets for a list of users. It seems to work for some users and not others, and if it fails for one or two users today it will work for them tomorrow. We are doing a post to this url with four user IDs in the post data in the format shown: http://username:passw...@stream.twitter.com/1/statuses/filter.json follow=111,222,333,444 We start the stream and then enter tweets manually from several of the Twitter accounts. Some of the accounts work some of the time, that is, for some of the accounts the tweets appear in our stream. If we test the same thing later a different selection of accounts work. We haven't seen any pattern. None of the accounts are set to be private. So our question is: Is this supposed to work? Are all new tweets entered for the four users supposed to appear in the stream within a short time? How can we debug this? Any suggestions welcome. Thanks. -Ginny -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] URL encoding of status= parameter in #newtwitter
The following link works fine for users with access to #vintagetwitter but breaks on the first URL encoded (%26) or # (%23) for users with #newtwitter: http://twitter.com/home?status=Trying+out+URL+encoding+%26+stuff+on+%23newtwitter+vs+%23vintagetwitter Is this intentional? Thanks, -jonathan -- Jonathan Strauss, Co-Founder http://awe.sm Blog: http://jonathanhstrauss.com Twitter: http://twitter.com/jhstrauss -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Search and/or streaming rate limits
If my app has 1000 users and each one wants to do a unique search once an hour it seems like that is beyond what is being suggested. Even if I use the streaming api and filters, it looks like I could only have a couple hundred users. ( Am I missing some technique because it doesn't seem like you can do anything useful with my use case if you are limited to a few hundred users. I've never found the rate limits a burden since you can spread the requests out among the users via OAuth, but the IP limits seem way too restrictive. Maybe I'm overlooking a creative workaround. Anyone? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] User Access Tokens and direct messages
Hello all: New to the forum but looking for some help. I'm an engineer but not a hacker, and have been having a discussion with my developer. We're using Oauth and my developer says we can not save a users ID so that we can send them direct messages whenever we want, even after they authorize our application. So is there a simple way to send users that authorize my application DMs whenever we want? Perhaps if we save their access token? As I understand it we can keep this token until a user de-authorizes it. I'm not sure though what privileged and access token grants. Any help is truly appreciated. Hope this isn't a dumb question Curtis -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Access Tokens and direct messages
You're quite free to store the users tokens and their user ID. Keep in mind you can only DM those who are following you. Scott. On 24 Sep 2010, at 21:58, Dialflow wrote: Hello all: New to the forum but looking for some help. I'm an engineer but not a hacker, and have been having a discussion with my developer. We're using Oauth and my developer says we can not save a users ID so that we can send them direct messages whenever we want, even after they authorize our application. So is there a simple way to send users that authorize my application DMs whenever we want? Perhaps if we save their access token? As I understand it we can keep this token until a user de-authorizes it. I'm not sure though what privileged and access token grants. Any help is truly appreciated. Hope this isn't a dumb question -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Searching for tweets containing a specific domain
I'll start digging into the Search API and seeing how that performs. I can tell you from experience that the streaming API does not currently carry the expanded URL metadata in its payload. All you get is a match on raw tweet content. On Sep 24, 6:34 am, Brian Medendorp brian.medend...@gmail.com wrote: I just did a search for a domain, and it did indeed return results from shortened URLs, so it seems to still work (or they fixed the problem). The only reasonable way I have found to consume the feed of a specific domain is to use the search API. You'll need to periodically perform a search, and keep track of the most recent ID that you found in the previous search so you'll know when to stop. You may also need to adjust the time between searches based on how many results you get. You could probably also use the streaming API with a filter for the domain, though I am not sure if that will work with the shortened URLs, and it would of course require keeping a connection open. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Using @Anywhere under SSL
Hi Bob, Sadly adding SSL to the CDN is not that straight forward. We continue to investigate ways to make this happen reliably and will post updates as progress is made. Best, @themattharris On Fri, Sep 24, 2010 at 8:19 AM, Bob Lyons nextd...@gmail.com wrote: I agree its a real limit to an otherwise highly convenient product. Seems easy enough to get akamai to use the right ssl cert. Is there some other technical snafu here or is this just an administrative item you haven't gotten to yet? I'd vote to bump it up in priority if its the latter. Cheers, Bob On Sep 22, 7:03 am, Justin justin.realw...@gmail.com wrote: It is a shame Cassie, I'm having to use OAuth - more flexability but would be nice to have the simplicity of Anywhere On Sep 21, 8:37 pm, Cassie Lynn cassie.schwendi...@gmail.com wrote: yet? Do we have any way of knowing when this might happen? And thanks for asking this here Justin! I asked on @anywhere and no one has replied (it has been almost a week). Thanks! - Cassie On Sep 20, 5:00 am, Tom van der Woerdt i...@tvdw.eu wrote: FYI, there's a Mailing List specifically for @Anywhere. The list you mailed to is the API developer list. http://groups.google.com/group/twitter-dev-anywhere To answer your question: no, there's no SSL version (yet). Tom On Mon, 20 Sep 2010 02:53:05 -0700 (PDT), Justin justin.realw...@gmail.com wrote: I would love to use the Connect with Twitter @Anywhere function but I would need to use it in a secure enviroment - that is under SSL. I first tried this when @Anywhere was first launched adn gave up thinking that perhaps it's a little too early? Having recently returned to it, I was disapointed to discover that the situation doesn't seem to have changed. Does anyone know if this is possible? Simply adding an s to http://platform.twitter.com/anywhere.jsdoesn'twork, I wonder if there's another unpublished URL, or if Twitter have any plans to impliment this. I'd prefer to use @Anywhere over oAuth, but may not have a choice :-( Thanks Justin -- 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 -- 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
Re: [twitter-dev] include_rts for /1/statuses/home_timeline
Hey Derek, The home_timeline includes retweets so the include_rts parameter is not required. The reason we added the parameter to the user_timeline and friends_timeline is because those methods, by default, do not include retweets. This was for backwards compatibility with early users of the API. For comparison, the home_timeline is the same as the friends_timeline with include_rts=1 set. Hope that clarifies the reason why include_rts isn't includes with the home_timeline method. Best, @themattharris On Fri, Sep 24, 2010 at 7:39 AM, @giromide girom...@gmail.com wrote: The latest announcement mentions include_rts for /1/statuses/ user_timeline and /1/statuses/friends_timeline but not for /1/statuses/ home_timeline. Am I alone in desiring include_rts for /1/statuses/ home_timeline as well? I find the current method of blocking retweets per user to be somewhat cumbersome, but I can understand Twitter's rationale behind this (some people retweet interesting things while others don't). What makes this platform great is that it can be consumed in so many different ways by so many different types of consumers. While a timeline-level block of retweets might be confusing when paired with user-level block of retweets, I see value in providing it to clients dedicated to simple reading of timelines by users who only want to read from those he or she follows. Thank you for your time, --Derek -- 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 -- 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
Re: [twitter-dev] tweetbutton color
Hi @puciwuci, Other than the language the Tweet Button cannot be altered. If you require custom colours you might be interested in building your own Tweet Button. We have an example of this on our developer resources site: http://dev.twitter.com/pages/tweet_button#build-your-own-example Best, @themattharris On Fri, Sep 24, 2010 at 1:01 AM, @puciwuci niendriar...@gmail.com wrote: can we change the color of the tweetbutton icon? -- 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 -- 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
[twitter-dev] Re: URL encoding of status= parameter in #newtwitter
Hey Matt, I know the tweet button very well, and I agree that it's better for most use-cases (we're actually driving our customers towards using / share instead of /home?status= for their custom share to Twitter interfaces). However, all legacy 'Share on Twitter' or 'Tweet This' implementations (that don't go through OAuth) use /home?status= and if the things that worked before stop working as #newtwitter rolls out to the full userbase, it's going to break a lot of stuff for people who haven't yet had a chance to switch to the tweet button or a custom integration with /share. Thanks, -jonathan On Sep 24, 5:47 pm, Matt Harris thematthar...@twitter.com wrote: Hi Jonathan, I'll look into this but have you consider using the Tweet Button instead. Using the Tweet Button gives a better experience and means users don't need to leave your website to tweet your message. You can get the Tweet Button on our Goodies page: http://twitter.com/goodies/tweetbutton or create your own using the developer resources: http://dev.twitter.com/pages/tweet_button Best, @themattharris On Fri, Sep 24, 2010 at 12:36 PM, Jonathan Strauss jonat...@awe.sm wrote: The following link works fine for users with access to #vintagetwitter but breaks on the first URL encoded (%26) or # (%23) for users with #newtwitter: http://twitter.com/home?status=Trying+out+URL+encoding+%26+stuff+on+%... Is this intentional? Thanks, -jonathan -- Jonathan Strauss, Co-Founder http://awe.sm Blog:http://jonathanhstrauss.com Twitter:http://twitter.com/jhstrauss -- 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 -- 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
Re: [twitter-dev] Re: URL encoding of status= parameter in #newtwitter
Hey Jonathan, Absolutely! Just wanted to put the Tweet Button out there as an option. So we can track this can you file an issue on: http://code.google.com/p/twitter-api/issues/list I'll keep that updated with progress. Thanks, @themattharris On Sep 24, 2010, at 18:54, Jonathan Strauss jonat...@awe.sm wrote: Hey Matt, I know the tweet button very well, and I agree that it's better for most use-cases (we're actually driving our customers towards using / share instead of /home?status= for their custom share to Twitter interfaces). However, all legacy 'Share on Twitter' or 'Tweet This' implementations (that don't go through OAuth) use /home?status= and if the things that worked before stop working as #newtwitter rolls out to the full userbase, it's going to break a lot of stuff for people who haven't yet had a chance to switch to the tweet button or a custom integration with /share. Thanks, -jonathan On Sep 24, 5:47 pm, Matt Harris thematthar...@twitter.com wrote: Hi Jonathan, I'll look into this but have you consider using the Tweet Button instead. Using the Tweet Button gives a better experience and means users don't need to leave your website to tweet your message. You can get the Tweet Button on our Goodies page: http://twitter.com/goodies/tweetbutton or create your own using the developer resources: http://dev.twitter.com/pages/tweet_button Best, @themattharris On Fri, Sep 24, 2010 at 12:36 PM, Jonathan Strauss jonat...@awe.sm wrote: The following link works fine for users with access to #vintagetwitter but breaks on the first URL encoded (%26) or # (%23) for users with #newtwitter: http://twitter.com/home?status=Trying+out+URL+encoding+%26+stuff+on+%... Is this intentional? Thanks, -jonathan -- Jonathan Strauss, Co-Founder http://awe.sm Blog:http://jonathanhstrauss.com Twitter:http://twitter.com/jhstrauss -- 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 -- 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 -- 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
