[twitter-dev] Twitter Search Widget on iPad
Hi All, I recently launched this website: http://makesmyjobeasy.com I have had a few people tell me that the scroll bar visible on the right of the twitter search widget used to move the tweets up and down so you can see the rest doesnt appear on the Safari iPad2 browser (unsure about ipad1). Anyone shed some light onto why or is this just standard?!?! Thanks, Phil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Domain search fails with www prefix
Hi all, I dev for an application where we do timely domain-based searches for all recent tweets involving that domain. Part of the queueing process is automated, and has been working brilliantly, until i discovered an odd quirk just this morning. Let's say a tweet was made linking to www.example.com/one/long/uri (shortened via t.co), and i do a search: http://search.twitter.com/search.json?since_id=&q=www.example.com&rpp=100 That search will fail to find the tweet in question. But this will succeed: http://search.twitter.com/search.json?since_id=&q=example.com&rpp=100 Having noticed exactly this (on a real client's domain), i looked through our DB to notice that no searches on domains prefixed with www. domains had ever succeeded, and a quick sampling showed that tweets had been made on those domains, provided i excised the 'www.' from the search term. I couldn't find this behaviour documented anywhere, and i'm wondering - can it be trusted? If i start stripping www. from my search terms, is it a reasonable expectation that tweets linking to the www. subdomain (and shortened versions of those links) will continue to show in the search? Thanks, Phil -- 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: C# API Wrapper for Site Streams Beta
I've been using a little library for nearly over a year now that I knocked up quite a while ago to connect to the Twitter streaming filter API. I've not looked into the site streams but I would assume that site streams work in a similar way to the filter API. This library maintains a streaming connection and implements what I understand to match the reconnection logic required by Twitter too. Source code is available here: https://github.com/Kwwika/kwwika-tweet-streamer/tree/master/TweetStreamer Feel free to give me a shout if you've any questions. Phil @leggetter On Apr 6, 8:32 am, Broogie wrote: > Awesome, thanks Joe. > > Will be doing some POC work for this application soon, will let you > know how I get on. > > Thanks > > Broogie > > On Apr 5, 11:17 pm, Joe Mayo wrote: > > > > > > > > > Broogie, > > > LINQ to Twitter,http://goo.gl/gKSAG, has support for streaming > > libraries. I haven't heard from too many people that are using it, so > > it would be nice to have someone check it out and tell me what they > > think. There are examples in the solution download. > > > Joe > > > On Apr 4, 2:15 pm, Broogie wrote: > > > > Hey Guys, developing a new Site Streams Beta application and looking > > > for a good C# API Wrapper much like Twitterizer? > > > > 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] Re: Kwwika - World Cup Web Development competition announced using Twitter World Cup data
A Kwwik update on this: We've had a few entries for this competition but not too many so the opportunity to win that iPad is pretty good due to the low number of competitor. The deadline for entry is July 1st but the main thing is to have something in place for that date and you can then build on it. We've also managed to get Opta Sports involved and they are now pushing real-time updates about live games through. So, this is a great chance to play with some cool real-time Opta stats as well as #worldcup real-time tweets. A final incentive is that we have a potential client lined up to use Kwwika and by building an application using Kwwika you put yourself in the shop window to be considered for that contract. As before, if you are interested in entering the competition, or just having a play with Kwwika, please get in touch (p...@kwwika.com). Phil On Jun 14, 9:41 pm, Phil Leggetter wrote: > Hi Dean, > > Not really :o) > > I'm looking to try and drum up some interest in this competition. In > addition to real-time twitter push updates we'll also be pushing out > some world class World Cup sports data to be used in the mashup. > > Phil > > On Jun 12, 7:40 pm, "Dean Collins" wrote: > > > Hi Phil, > > > Check out the twitter integration withwww.LiveWorldCupChat.comif > > that's what you want. > > > Cheers, > > Dean > > > > -Original Message- > > > From: twitter-development-talk@googlegroups.com > > > [mailto:twitter-development- > > > > t...@googlegroups.com] On Behalf Of Phil Leggetter > > > Sent: Saturday, 12 June 2010 11:13 AM > > > To: Twitter Development Talk > > > Subject: [twitter-dev]Kwwika- World Cup Web Development competition > > announced > > > using Twitter World Cup data > > > > Hello all! > > > > I'm working on a project calledKwwikawhich allows anybody to add > > > real-time push functionality to your website. To try and get people > > > developing usingKwwikawe've decided to create a competition that > > > will hopefully encourage web developers to sign up for the opportunity > > > of winning an Apple iPad. > > > > The reason I'm messaging the group is that the majority of data that > > > we are using is from the Twitter streaming API, something a lot of you > > > may be familiar with. > > > > The purpose of the competition is to see who can build the most > > > engaging real-time push World Cup 2010 web application. > > > > More details can be found in the following locations: > > > > * Blog post announcment: > > >http://blog.kwwika.com/kwwika-world-cup-2010-real-> time-push-web-app > > > *KwwikaWiki with competition details: > > >http://wiki.kwwika.com/competitions/world-cup-2010-real-time-push-web-ap > > p- > > > > competition > > > * A real-time push World Cup demo created to give people an idea of > > > what can be built: > > >http://kwwika.com/Standalone/Demos/WorldCup2010/#SouthAfrica > > > > If you have any questions or idea please feel free to get in touch > > > with me via p...@kwwika.com > > > > Thanks, > > > > Phil Leggetter
[twitter-dev] Re: Kwwika - World Cup Web Development competition announced using Twitter World Cup data
Hi Dean, Not really :o) I'm looking to try and drum up some interest in this competition. In addition to real-time twitter push updates we'll also be pushing out some world class World Cup sports data to be used in the mashup. Phil On Jun 12, 7:40 pm, "Dean Collins" wrote: > Hi Phil, > > Check out the twitter integration withwww.LiveWorldCupChat.comif > that's what you want. > > Cheers, > Dean > > > -Original Message- > > From: twitter-development-talk@googlegroups.com > > [mailto:twitter-development- > > > > > t...@googlegroups.com] On Behalf Of Phil Leggetter > > Sent: Saturday, 12 June 2010 11:13 AM > > To: Twitter Development Talk > > Subject: [twitter-dev] Kwwika - World Cup Web Development competition > announced > > using Twitter World Cup data > > > Hello all! > > > I'm working on a project called Kwwika which allows anybody to add > > real-time push functionality to your website. To try and get people > > developing using Kwwika we've decided to create a competition that > > will hopefully encourage web developers to sign up for the opportunity > > of winning an Apple iPad. > > > The reason I'm messaging the group is that the majority of data that > > we are using is from the Twitter streaming API, something a lot of you > > may be familiar with. > > > The purpose of the competition is to see who can build the most > > engaging real-time push World Cup 2010 web application. > > > More details can be found in the following locations: > > > * Blog post announcment: > > http://blog.kwwika.com/kwwika-world-cup-2010-real-> time-push-web-app > > * Kwwika Wiki with competition details: > > http://wiki.kwwika.com/competitions/world-cup-2010-real-time-push-web-ap > p- > > > > > competition > > * A real-time push World Cup demo created to give people an idea of > > what can be built: > >http://kwwika.com/Standalone/Demos/WorldCup2010/#SouthAfrica > > > If you have any questions or idea please feel free to get in touch > > with me via p...@kwwika.com > > > Thanks, > > > Phil Leggetter
[twitter-dev] Kwwika - World Cup Web Development competition announced using Twitter World Cup data
Hello all! I'm working on a project called Kwwika which allows anybody to add real-time push functionality to your website. To try and get people developing using Kwwika we've decided to create a competition that will hopefully encourage web developers to sign up for the opportunity of winning an Apple iPad. The reason I'm messaging the group is that the majority of data that we are using is from the Twitter streaming API, something a lot of you may be familiar with. The purpose of the competition is to see who can build the most engaging real-time push World Cup 2010 web application. More details can be found in the following locations: * Blog post announcment: http://blog.kwwika.com/kwwika-world-cup-2010-real-time-push-web-app * Kwwika Wiki with competition details: http://wiki.kwwika.com/competitions/world-cup-2010-real-time-push-web-app-competition * A real-time push World Cup demo created to give people an idea of what can be built: http://kwwika.com/Standalone/Demos/WorldCup2010/#SouthAfrica If you have any questions or idea please feel free to get in touch with me via p...@kwwika.com Thanks, Phil Leggetter
[twitter-dev] Re: Oauth authentication jquery
All that aside, the other problem would be exposing your secret key.
I am sure you can imagine how terribly bad that can end up...
On Dec 30, 10:57 pm, Hari wrote:
> Is it a case of same origin
> policyhttp://en.wikipedia.org/wiki/Same_origin_policy
>
> On Dec 10, 8:27 am, Daniel Silva wrote:
>
>
>
> > When I trying to do Oauth authentication with jquery it always receives a
> > empty response. I'm doing this:
>
> > $.ajax({
> > beforeSend: function(xhr) {
> > xhr.setRequestHeader("Authentication", authorizationHeader)
> > },
> > url:'https://twitter.com/oauth/request_token',
> > type: 'get',
> > contentType: 'application/x-www-form-urlencoded',
> > async: false,
> > success: function(msg){
> > alert( "Data: " + msg );
> > }
>
> > });
>
> > //output --> "Data: "
>
> > Can someone help me?
> > --
> > best regards,
>
> > Daniel Silva
[twitter-dev] Re: My Issue with the ReTweet API and my solutions
The ReTweet syntax is not that simple though. Some people prefix a tweet with RT @username, others suffix the tweet with (via @username) and I have seen people using a unicode recycling symbol to signify the retweet. Formalising should take issues like that out of the way. However, I do agree that commenting on retweets is an important part of the user-made system and it would be sad to see that go, possibly encouraging people to continue to use the old method. I like some of the ideas and criticisms that others have made, but I don't think any are perfect yet (not that I offer any better solutions I'm afraid, but talk like this can only lead to better ideas and better ways). Phil -- Phil Nash Twitter: http://twitter.com/philnash Find some music: http://yournextfavband.com Web development: http://www.unintentionallyblank.co.uk On Mon, Aug 17, 2009 at 1:25 PM, Vision Jinx wrote: > > I agree with a lot of points Mashable made here >> > http://mashable.com/2009/08/13/project-retweet-analysis/ > > Were ReTweets ever broken? I didn't think so RT @someone - very > sweet and simple (KISS - Keep it simple ...) > > "The existence of Project Retweet — ie. formalized retweeting — > essentially implies that Twitter felt that current retweeting > practices need repairing. But were retweets ever really broken?" > > - Since I felt that RT @someone was easy and simple (and easy to add > to my code) I didn't feel the need to even explore this new API and > add clutter to my code. > > > "the RT and @ symbol will be stripped from the tweet. What you’ll see > instead is the original tweet, from the original author," > > - I don't like that, I want to be able to add my own comments and give > credit (read as "a mention") to the one I follow too by RTing their > user name also so my followers can see who I find interesting to > follow. Plus this seems to be the preferred method users have adopted > (from my exp)... Additionally, I have a real problem with services > that modify my content/text on me. I didn't ask you to so leave it > alone. :( > > > "So let’s say that you follow me but don’t follow Mashable. Now when I > retweet Mashable, you’ll see the tweet from Mashable, not from me. > This could get a little hairy." > > - I agree, If I start seeing a bunch of stuff show up from from ppl I > don't follow, I don't think I will like that and be less inclined to > click any links too. > > > "You’ve already become accustomed to seeing tweets from the people you > follow, so a retweet from a trusted party actually means something." > > - Yep! > > > I also like how it mentions that the Users created ReTweets, and now > with Twi***r trademarking Tweet™ this most likely will mean they will > claim ownership of ReTweet™ also, does this mean we will have to now > use RT™ @someone or RT® @someone :/ > > > Long story short... I just keep thinking, If it ain't broken, don't > fix it ;) That's my $0.02 on it. > > > On Aug 15, 3:00 am, Paul Kinlan wrote: > > Hi Guys, > > When I saw the original message stating that the retweet API I was about > to > > say straight away that I despise the idea, but I thought I would refrain > - > > give it some thought. I still despise the idea and I have to make it > known > > the reasons why I think it is a very very bad idea and in the long term > will > > negatively affect Twitter as a communications platform for the future. > > > >1. You are embedding a user developed based meme into the Twitter > >infrastructure - the popularity of RT itself may wane after some > point. > >Users are very fickle, they change their minds, take a stand and don't > >listen to them - you know your platform and I am pretty sure you know > that > >this is a bit of a hack. Let users use they system how they want, > they will > >evolve how they use it, constraints via an API > > 1. Twitter already has the capability to do smarter things > > that completely negate the need for this API if they just change > > the current > > API a little > >2. Not every app will use RT API (especially legacy ones) and not > every > >user will use it and as such Twitter and this list will get lots of > >questions why certain RT's are accessible by the retweet API. Again, > RT's > >are a user concept, and is very easy for them not use. > >3. Whilst I use TweetDeck, I really dislike the amount of utility > buttons > >it has and the amount of options it has - introducing another API for > >another functi
[twitter-dev] Re: New idea for twitter development
This sort of thing, whilst not built into Twitter has been made possible by a number of 3rd party applications. Philip mentioned CoTweet, which is a good example of a web based method of doing this. Multiple account maintenance is also possible in popular desktop clients, like Tweetdeck, Tweetie and Nambu and in their respective iPhone clients too. Why not give one of those a try? Phil -- Phil Nash Twitter: http://twitter.com/philnash Find some music: http://yournextfavband.com Web development: http://www.unintentionallyblank.co.uk On Mon, Jun 22, 2009 at 12:31 PM, M1Sh0u wrote: > > In settings panel I think that could be added a new tab named Create > Secondary Accounts or Secondary Accounts which have a new sign up form > with or without a new Email information and the same password as the > main account. > > In the sign up form can be added a checkbox named 'Make this account > the Main Account' and when user loges into twitter, the main account > is opened first. Users can manage their new accounts switching them > from a top page select named switch account, and the profile and > settings informations can be changed for the selected account. > > Users should have the possibility to view the messages of all their > accounts or just for the selected account. > > I think that this idea help users very much when they want to create > more than one twitter accounts and they are not forced to log out and > log in every time when they want to switch their accounts. > > Thanks and I hope that this idea is useful. > > > On Jun 22, 7:26 am, Mandakini kumari wrote: > > Hi > > > > Thanks can you give me detail how to do it ? > > > > > > > > On Sun, Jun 21, 2009 at 4:04 PM, M1Sh0u wrote: > > > > > HI, I'm Mihai Matei, WEB Developer from Romania > > > > > I have a new idea that could be implemented on twitter. The idea is > > > that any user can create secondary accounts. What that's means? Each > > > user can manage his accounts from the main account which is the first > > > account created. > > > > > That help the user not to log out and after that log in to another > > > account. He can change his accounts from a top page select. > > > > > What do you think about this idea ? > > > > > Thanks and sorry for my bad english :) > > > > -- > > Regards > > Mandakini >
[twitter-dev] Re: Twitter conference
There is the Twitter Developer Nest in New York and London in the next couple of weeks: http://twitterdevelopernest.com/2009/06/ncy-ldn-twitter-developer-nests/ I went to the first two London ones and they were fun and interesting, they both included a Q&A session with Doug Williams over Skype too. That might be what you're looking for if you're in either area. Phil -- Phil Nash Twitter: http://twitter.com/philnash Find some music: http://yournextfavband.com Web development: http://www.unintentionallyblank.co.uk On Mon, Jun 8, 2009 at 7:26 PM, Emrah wrote: > > Hi everybody, > > Is there any planned Twitter Meetup in the near future? Is there any > official schedule available online? > I heard about #140conf but I was imagining something more developers > oriented. Something to discuss possible improvements, add-ons or similar > stuffs about Twitter and Twitter apps. > > I was actually imagining planning a Web or Phone conference between > Twitter admins, developers and perhaps some interesting users? > In both cases, the conference could be recorded as a podcast to be > redistributed if necessary. > Mixing both telephone and Web conferencing for users who are not able to > join the Web meeting is possible. > > About the Web meeting, it would be possible to support 2 or 3 concurrent > video streams but the number of participants would be unlimited. > Regarding the telephone conferencing, it could be possible to integrate > Skype, VoIP, regular phone lines and a callback function for users who > can't make international phone calls. > > What do you think? > > Emrah >
[twitter-dev] Re: searching for official images for a oauth application
There are a couple of images at the bottom of this page: http://apiwiki.twitter.com/Sign-in-with-Twitter I think they count as official! Phil -- Phil Nash Twitter: http://twitter.com/philnash Find some music: http://yournextfavband.com Web development: http://www.unintentionallyblank.co.uk On Fri, May 22, 2009 at 2:44 PM, Jochen Kaechelin wrote: > > are there any official images provided bei twitter? > > I'am looking for something like "sign in with twitter" ? > > Thanx > > >
[twitter-dev] Re: Callback url during development
That's a great idea, thanks for sharing! I was just wondering what to do now
that oauth_callback won't work.
Thanks!
Phil
--
Phil Nash
Web development: http://www.unintentionallyblank.co.uk
Musical stylings: http://www.hammervsthesnake.co.uk
Twitter: http://twitter.com/philnash
On Thu, Apr 23, 2009 at 11:29 PM, Paul Kinlan wrote:
> Hi,
>
> During development I tend to modify my hosts file to point the callback URL
> domain to my box for instance. This is quite good because all it affects is
> my box.
>
> Paul
>
>
>
> On 23 Apr 2009, at 23:16, Abraham Williams <4bra...@gmail.com> wrote:
>
> The oauth_callback parameter was just disabled do to security issues.
> Currently only the registered callback works. If you need a different
> callback location for development set up a second application.
>
> On Thu, Apr 23, 2009 at 17:12, Jochen Kaechelin <
> giss...@gissmog.de> wrote:
>
>>
>>
>> Am 22.04.2009 um 15:37 schrieb Abraham Williams:
>>
>> > Also when you are building the authorize url to send users to
>> > twitter.com you can add "&oauth_callback= <http://localhost/callback>
>> http://localhost/callback";
>> > and that will override your applications registered callback.
>> >
>>
>>
>> OAuth::Consumer.new("xx", "xx",
>> {
>> :site=>"<http://twitter.com/oauth/authorize?oauth_callback=http://localhost:3000/callback>
>> http://twitter.com/oauth/authorize?oauth_callback=http://localhost:3000/callback
>> " })
>>
>>
>> I can see the site where I have to Deny or Allow access.
>> When I click "Allow" I will be redirected to the Domain which I
>> entered in the
>> OAUTH Clients Registration Form ( <http://www.twitter.com/oauth_cleints>
>> http://www.twitter.com/oauth_cleints)
>>
>> Seems that the oauth_callback parameter does not work!
>> Is it in the wrong place?
>>
>> Any hints!?
>>
>> Thanx
>>
>>
>>
>
>
> --
> Abraham Williams | <http://the.hackerconundrum.com>
> http://the.hackerconundrum.com
> Hacker | <http://abrah.am>http://abrah.am | <http://twitter.com/abraham>
> http://twitter.com/abraham
> Web608 | Community Evangelist | <http://web608.org>http://web608.org
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from Madison, Wisconsin, United States
>
>
Re: Getting more from the source link on a tweet...
I'm not sure I follow. Forgive me, I'm relatively new at this sort of thing. I realize that Twitter has lots of irons in the fire...no doubt of that. Would there be any interest in working on a more involved source parameter? The result may lead to enhancing any monetization goals for Twitter...I'm just sayin'. Thanks. On Oct 23, 10:51 am, "Alex Payne" <[EMAIL PROTECTED]> wrote: > Well, you could always examine the referrers that you get and see if > they're coming from a tweet's permalink URL. > > > > On Thu, Oct 23, 2008 at 6:24 AM, Phil <[EMAIL PROTECTED]> wrote: > > > That's it? Can you suggest some alternatives? For the sake of > > 'development' isn't there more that can be discussed? > > > On Oct 22, 12:39 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > >> Apologies, but we want to keep the source parameter links as simply > >> static URLs to sites and products. > > >> On Wed, Oct 22, 2008 at 9:42 AM, Phil <[EMAIL PROTECTED]> wrote: > > >> > Can get more from the source feature on a tweet for my API. Can that > >> > text be altered to perform a different function? > > >> > Specifically, the source function currently allows a click through to > >> > the website. A function that is the same for any and all tweets > >> > originating from the API. > > >> > Can the text/function be modified so that a click will take the user > >> > to a function on the website specifically related to that individual > >> > tweet, re: a rating function? > > >> -- > >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Getting more from the source link on a tweet...
That's it? Can you suggest some alternatives? For the sake of 'development' isn't there more that can be discussed? On Oct 22, 12:39 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > Apologies, but we want to keep the source parameter links as simply > static URLs to sites and products. > > On Wed, Oct 22, 2008 at 9:42 AM, Phil <[EMAIL PROTECTED]> wrote: > > > Can get more from the source feature on a tweet for my API. Can that > > text be altered to perform a different function? > > > Specifically, the source function currently allows a click through to > > the website. A function that is the same for any and all tweets > > originating from the API. > > > Can the text/function be modified so that a click will take the user > > to a function on the website specifically related to that individual > > tweet, re: a rating function? > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Getting more from the source link on a tweet...
Can get more from the source feature on a tweet for my API. Can that text be altered to perform a different function? Specifically, the source function currently allows a click through to the website. A function that is the same for any and all tweets originating from the API. Can the text/function be modified so that a click will take the user to a function on the website specifically related to that individual tweet, re: a rating function?
Re: user_timeline limits
Great, thanks Alex. Done: http://code.google.com/p/twitter-api/issues/detail?id=128 http://code.google.com/p/twitter-api/issues/detail?id=129 Let me know if I've missed any vital part of the explanation. Cheers, Phil On Oct 20, 6:50 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > Looks like we've got some bugs here, as neither of these > behaviors/limitations are intentional. Please file issues > athttp://code.google.com/p/twitter-api/issues/entryand we'll get them > taken care of. > > > > On Sat, Oct 18, 2008 at 3:46 AM, Phil Gyford <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I'm trying to archive all my twitters to a local database. I'm using > > user_timeline but have hit a couple of problems. > > > First, if I set the 'count' parameter to the maximum of 200 and ask > > for 'page' 2, then it doesn't fetch back tweets 201-400, but instead > > fetches tweets 21-220. So 'count' does not affect the number of tweets > > on a 'page'. So if you set the count to 200 and request several > > incrementally numbered pages, then you're soon only getting 20 new > > tweets each time, plus 180 you've had before. There doesn't seem much > > point in being able to set the count higher than 20 unless you're only > > fetching page 1. Is this normal? > > > Second, I can't fetch tweets further back than page 41 (with 20 tweets > > per page), which is also as far back as I can go on the website. Is > > there any way to fetch tweets older than this? If not, will there be? > > > I'd really like to make a local copy of my tweets but can't see how to > > do so at the moment. > > > Many thanks, > > Phil > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
user_timeline limits
Hi, I'm trying to archive all my twitters to a local database. I'm using user_timeline but have hit a couple of problems. First, if I set the 'count' parameter to the maximum of 200 and ask for 'page' 2, then it doesn't fetch back tweets 201-400, but instead fetches tweets 21-220. So 'count' does not affect the number of tweets on a 'page'. So if you set the count to 200 and request several incrementally numbered pages, then you're soon only getting 20 new tweets each time, plus 180 you've had before. There doesn't seem much point in being able to set the count higher than 20 unless you're only fetching page 1. Is this normal? Second, I can't fetch tweets further back than page 41 (with 20 tweets per page), which is also as far back as I can go on the website. Is there any way to fetch tweets older than this? If not, will there be? I'd really like to make a local copy of my tweets but can't see how to do so at the moment. Many thanks, Phil
