[twitter-dev] Re: Inconsistencies b/t XML and JSON
I'll definitely post if I come across more. It's usually just more of a Charlie Brown *augh* than a show-stopper by any means. And then like you said, it eventually sorts itself out. I did consider switching to XML as that always seems to be the cache copy that's up-to-date, but then realized I would have to update a variety of other things to deal with the proper data types. Thanks for the detail! dpc On Mar 11, 11:05 am, Alex Payne wrote: > Snapshots in time of the XML output and JSON output are helpful. But I > certainly believe that there could be such discrepancies. They tend to > arise when our database replication lag increases. Some client > requests UncachedUserA in XML, and those inaccurate counts get "frozen > in time" until a cache invalidation event occurs. Then the replication > lag sorts itself out, and someone requests UncachedUserB and sees the > correct values. > > It's a very frustrating property of our system's architecture at the > moment, but one we're working on solutions for. > > > > On Wed, Mar 11, 2009 at 10:09, Damon C wrote: > > > I've seen this from time-to-time before, but could never really pin it > > down to specific users or timeframes. > > > In any case, I frequently see inconsistencies between the data in XML > > and JSON representations. The example I came across last night was > > with the ActiveRainMaker account. The caches have since caught up (un) > > fortunately, and I don't have another example. > > > In this case, though, the XML had a friends_count of ~1800 while the > > JSON had a friends_count of ~800. I'm not really sure what else I can > > provide and I probably didn't post before b/c it just sounds like > > complaining. ;) > > > Thanks! > > > dpc > > > -- > > Damon P. Cortesi > > Security Guy, Twitter Apps > > www. tweetstats | tweepsearch | tweetsum .com > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Source parameter
Sounds good. Thanks for the quick feedback Doug. Gee On Mar 12, 11:15 am, Doug Williams wrote: > Gee, > You will receive an email with our decision. The timeline varies by our > workload because we do manually look at and consider each request. You > should expect to hear from use within a few days of your request. Thank you > for your patience. > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > > > On Wed, Mar 11, 2009 at 10:01 PM, gee wrote: > > > What's the expected timeline for this process? Submitted a request > > yesterday, and so far testing has shown that it's not been accepted > > yet. our app name is 'smart.fm'. > > > Also, how will we hear about the outcome of the application.. direct > > message from twitter? e-mail? just test until it works? > > > Thanks > > Gee > > > On Feb 25, 11:29 pm, Burhan TANWEER wrote: > > > You can add source parameter in tweet by requesting to add source value > > and > > > where it should be linked. Once it is accepted by twitter then they will > > add > > > source value and its link in their database. > > > > You should be able to upload your tweet with source= and it will > > > appear on all tweets updated through your app. > > > > On Wed, Feb 25, 2009 at 4:24 AM, daniel.winterst...@gmail.com < > > > > daniel.winterst...@gmail.com> wrote: > > > > > I'd like to set the source parameter in tweets. It seems only some > > > > values will work, with others defaulting to web. How can I add my own > > > > app-name to the list of valid parameters? > > > > -- > > > Sincerely, > > > > Burhan Tanweerwww.explorewww.com > > > expl...@explorewww.com
[twitter-dev] Re: Source parameter
Gee, You will receive an email with our decision. The timeline varies by our workload because we do manually look at and consider each request. You should expect to hear from use within a few days of your request. Thank you for your patience. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 10:01 PM, gee wrote: > > > What's the expected timeline for this process? Submitted a request > yesterday, and so far testing has shown that it's not been accepted > yet. our app name is 'smart.fm'. > > Also, how will we hear about the outcome of the application.. direct > message from twitter? e-mail? just test until it works? > > Thanks > Gee > > > On Feb 25, 11:29 pm, Burhan TANWEER wrote: > > You can add source parameter in tweet by requesting to add source value > and > > where it should be linked. Once it is accepted by twitter then they will > add > > source value and its link in their database. > > > > You should be able to upload your tweet with source= and it will > > appear on all tweets updated through your app. > > > > On Wed, Feb 25, 2009 at 4:24 AM, daniel.winterst...@gmail.com < > > > > daniel.winterst...@gmail.com> wrote: > > > > > I'd like to set the source parameter in tweets. It seems only some > > > values will work, with others defaulting to web. How can I add my own > > > app-name to the list of valid parameters? > > > > -- > > Sincerely, > > > > Burhan Tanweerwww.explorewww.com > > expl...@explorewww.com >
[twitter-dev] Re: Source parameter
What's the expected timeline for this process? Submitted a request yesterday, and so far testing has shown that it's not been accepted yet. our app name is 'smart.fm'. Also, how will we hear about the outcome of the application.. direct message from twitter? e-mail? just test until it works? Thanks Gee On Feb 25, 11:29 pm, Burhan TANWEER wrote: > You can add source parameter in tweet by requesting to add source value and > where it should be linked. Once it is accepted by twitter then they will add > source value and its link in their database. > > You should be able to upload your tweet with source= and it will > appear on all tweets updated through your app. > > On Wed, Feb 25, 2009 at 4:24 AM, daniel.winterst...@gmail.com < > > daniel.winterst...@gmail.com> wrote: > > > I'd like to set the source parameter in tweets. It seems only some > > values will work, with others defaulting to web. How can I add my own > > app-name to the list of valid parameters? > > -- > Sincerely, > > Burhan Tanweerwww.explorewww.com > expl...@explorewww.com
[twitter-dev] Developers
Please add me to the Developers list on the wiki (http:// apiwiki.twitter.com/Developers): Josh Carrico Twitter: @SIGEPJEDI Personal Site: JoshCarrico.com Experience: +12yrs Location: Tampa FL Code of choice: ColdFusion, JSON, MS SQL, mySQL, Fusebox Framework SITES: http://tweepletwak.com - As featured on mashable: http://mashable.com/2008/10/29/tweeple-twak/ Other Twitter API related sites: http://Tampabloggers.com http://TopTweeple.com http://sqlPutDowns.com http://peevd.com
[twitter-dev] Re: Missing tweets in filter:links search
Hi, Can you create a new entry for that issue [1] so Matt can properly track that enhancement request? [1] - http://code.google.com/p/twitter-api/issues/entry Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 9:19 PM, TCI wrote: > > Hello, > filter:links in search returns tweets containing http://whatever but > not those containing www.whatever - even though the www.whatever are > correctly detected as links in twitter.com UI and linked > automatically... > > TCI >
[twitter-dev] Missing tweets in filter:links search
Hello, filter:links in search returns tweets containing http://whatever but not those containing www.whatever - even though the www.whatever are correctly detected as links in twitter.com UI and linked automatically... TCI
[twitter-dev] Re: Sorting search by Most Followers
They do. I actually already did it before I read this. But it was along the lines of just storing the users I find and their follower count and just ordering by that. I was using this for the Search API. Another curious thing is that there is a parameter called "filter(s)". The only argument I know I can pass to this is "links", are there more? It's unlisted: http://apiwiki.twitter.com/Search-API-Documentation On Mar 10, 9:47 am, Doug Williams wrote: > Kenefick, > There is nothing in the official API that will do that for you. You > would have to write such a filter yourself. So you can either: > > 1) have a list of users you want to follow and you can look for their > tweets. If this is your goal, it's best to simply create a user, > follow the list of users, and monitor the user's friend timeline. > > 2) Otherwise, the timeline methods return a list of status elements > [1] which do include the author's followers_count. So you could filter > based on a followers_count threshold easily. > > Do either of these options help? > > [1] -http://apiwiki.twitter.com/REST+API+Documentation#Statuselement > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Mon, Mar 9, 2009 at 9:04 PM, Kenefick wrote: > > > Is there a filter to sort the public timeline by most / least > > followers? > > > Or do you just have to add the big dogs and filter it out from there ?
[twitter-dev] Re: Issue with Search API 'show_user' URL parameter
I'll do that.
Thanks Matt.
On Mar 11, 6:18 pm, Matt Sanford wrote:
> Hi there,
>
> The show_user=true was only ever intended to work with atom feeds
> due to some feed readers not displaying the author. If you need this
> to work via JSON please file a ticket
> athttp://code.google.com/p/twitter-api/issues/entry
>
> Thanks;
> — Matt Sanford
>
> On Mar 11, 2009, at 02:17 PM, Frank wrote:
>
>
>
> > I'm integrating Twitter's search api with a PHP based application. I'm
> > using the Search API in JSON format, and I found out that when i
> > specify 'show_user=true' in the url, information does not get
> > returned in the response.
>
> > The request i'm making looks like this:
> >http://search.twitter.com/search.json?q=soccer&show_user=true&rpp=100
>
> > And the response for each entry looks like:
> > {
> > "text":"About to warm up for soccer match.",
> > "to_user_id":null,
> > "from_user":"scooter42481",
> > "id":1312698600,
> > "from_user_id":2456152,
> > "iso_language_code":"en",
> > "source":"Tweetie<\/a>",
> > "profile_image_url":"http:\/\/s3.amazonaws.com\/twitter_production\/
> > profile_images\/68476866\/JSC_normal.jpg",
> > "created_at":"Wed, 11 Mar 2009 21:11:26 +"
> > }
>
> > Am I doing anything wrong?
>
> > Thanks in advance.
[twitter-dev] Re: direct messages fractured, have been for months
If it's any consolation, we were just talking about the completely unacceptable inconsistencies of this sort in our daily meeting of the people responsible for Twitter's infrastructure. I've sent along your email to that group as a perfect illustration of those inconsistencies, and why fixing them needs to be a priority. I hope we'll have solutions in hand soon. On Wed, Mar 11, 2009 at 14:35, blairblends wrote: > > I realize this may not be the most exacting place to bring up this > topic, but the other avenues for Twitter support have all proven, at > least for me, to be black holes. > > Since at least September, whether referenced from the web interface or > the API calls, the number of direct messages in my account is not > consistent from one call to the next. For example, right now there > are actually 10 messages in my inbox. However, when I load the web > interface, it says 7. I immediately reload, and it says 9. I reload > again and it says 7. A fourth reload and I finally get 10, the > correct number. And this just continues over and over. > > And, for example, when the web interface or API reports 7 messages, > that's all I can actually see. The three recent messages ahead of it > are not listed to me. However, if I reload a few seconds later, and > I'm shown the count 10, I can see them all. > > It's very frustrating, since it can sometimes take me an hour to be > able to see a DM someone sends me. > > (ASIDE: It's maddening on an entirely different level because SMS > hasn't worked for me for almost 6 weeks. I used to at least get DM > notifications, but even those have stopped. I have all the settings > correct on the Twitter site, but now I just get NO direct messages. > That's an entirely issue entirely, but I point it out only to > emphasize that my attempts to get support on that matter have also > been totally black holed. The only thing I ever hear back from the > Twitter support site is a form response which, itself, is a COPY of > that page. It's utterly Sisyphean.) > > So, I raise the issue of the DM fracture here, where it has great > chance of getting some attention. I'm not in the least angry, just > pointing out a 5-month old issue I have tried to raise over and over, > when on your status page, it appears as if direct messages are problem > free...when myself and many others are noticing this same problem. > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Issue with Search API 'show_user' URL parameter
Hi there,
The show_user=true was only ever intended to work with atom feeds
due to some feed readers not displaying the author. If you need this
to work via JSON please file a ticket at http://code.google.com/p/twitter-api/issues/entry
Thanks;
— Matt Sanford
On Mar 11, 2009, at 02:17 PM, Frank wrote:
I'm integrating Twitter's search api with a PHP based application. I'm
using the Search API in JSON format, and I found out that when i
specify 'show_user=true' in the url, information does not get
returned in the response.
The request i'm making looks like this:
http://search.twitter.com/search.json?q=soccer&show_user=true&rpp=100
And the response for each entry looks like:
{
"text":"About to warm up for soccer match.",
"to_user_id":null,
"from_user":"scooter42481",
"id":1312698600,
"from_user_id":2456152,
"iso_language_code":"en",
"source":"Tweetie<\/a>",
"profile_image_url":"http:\/\/s3.amazonaws.com\/twitter_production\/
profile_images\/68476866\/JSC_normal.jpg",
"created_at":"Wed, 11 Mar 2009 21:11:26 +"
}
Am I doing anything wrong?
Thanks in advance.
[twitter-dev] Re: direct messages fractured, have been for months
have you tried using a twitter client, like a twitteriffic? On Wed, Mar 11, 2009 at 2:35 PM, blairblends wrote: > > I realize this may not be the most exacting place to bring up this > topic, but the other avenues for Twitter support have all proven, at > least for me, to be black holes. > > Since at least September, whether referenced from the web interface or > the API calls, the number of direct messages in my account is not > consistent from one call to the next. For example, right now there > are actually 10 messages in my inbox. However, when I load the web > interface, it says 7. I immediately reload, and it says 9. I reload > again and it says 7. A fourth reload and I finally get 10, the > correct number. And this just continues over and over. > > And, for example, when the web interface or API reports 7 messages, > that's all I can actually see. The three recent messages ahead of it > are not listed to me. However, if I reload a few seconds later, and > I'm shown the count 10, I can see them all. > > It's very frustrating, since it can sometimes take me an hour to be > able to see a DM someone sends me. > > (ASIDE: It's maddening on an entirely different level because SMS > hasn't worked for me for almost 6 weeks. I used to at least get DM > notifications, but even those have stopped. I have all the settings > correct on the Twitter site, but now I just get NO direct messages. > That's an entirely issue entirely, but I point it out only to > emphasize that my attempts to get support on that matter have also > been totally black holed. The only thing I ever hear back from the > Twitter support site is a form response which, itself, is a COPY of > that page. It's utterly Sisyphean.) > > So, I raise the issue of the DM fracture here, where it has great > chance of getting some attention. I'm not in the least angry, just > pointing out a 5-month old issue I have tried to raise over and over, > when on your status page, it appears as if direct messages are problem > free...when myself and many others are noticing this same problem. > -- Peter M. Denton www.twibs.com i...@twibs.com Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c
[twitter-dev] direct messages fractured, have been for months
I realize this may not be the most exacting place to bring up this topic, but the other avenues for Twitter support have all proven, at least for me, to be black holes. Since at least September, whether referenced from the web interface or the API calls, the number of direct messages in my account is not consistent from one call to the next. For example, right now there are actually 10 messages in my inbox. However, when I load the web interface, it says 7. I immediately reload, and it says 9. I reload again and it says 7. A fourth reload and I finally get 10, the correct number. And this just continues over and over. And, for example, when the web interface or API reports 7 messages, that's all I can actually see. The three recent messages ahead of it are not listed to me. However, if I reload a few seconds later, and I'm shown the count 10, I can see them all. It's very frustrating, since it can sometimes take me an hour to be able to see a DM someone sends me. (ASIDE: It's maddening on an entirely different level because SMS hasn't worked for me for almost 6 weeks. I used to at least get DM notifications, but even those have stopped. I have all the settings correct on the Twitter site, but now I just get NO direct messages. That's an entirely issue entirely, but I point it out only to emphasize that my attempts to get support on that matter have also been totally black holed. The only thing I ever hear back from the Twitter support site is a form response which, itself, is a COPY of that page. It's utterly Sisyphean.) So, I raise the issue of the DM fracture here, where it has great chance of getting some attention. I'm not in the least angry, just pointing out a 5-month old issue I have tried to raise over and over, when on your status page, it appears as if direct messages are problem free...when myself and many others are noticing this same problem.
[twitter-dev] Issue with Search API 'show_user' URL parameter
I'm integrating Twitter's search api with a PHP based application. I'm
using the Search API in JSON format, and I found out that when i
specify 'show_user=true' in the url, information does not get
returned in the response.
The request i'm making looks like this:
http://search.twitter.com/search.json?q=soccer&show_user=true&rpp=100
And the response for each entry looks like:
{
"text":"About to warm up for soccer match.",
"to_user_id":null,
"from_user":"scooter42481",
"id":1312698600,
"from_user_id":2456152,
"iso_language_code":"en",
"source":"Tweetie<\/a>",
"profile_image_url":"http:\/\/s3.amazonaws.com\/twitter_production\/
profile_images\/68476866\/JSC_normal.jpg",
"created_at":"Wed, 11 Mar 2009 21:11:26 +"
}
Am I doing anything wrong?
Thanks in advance.
[twitter-dev] Re: Retrieve tweets with ID greater than a passed-in ID?
Hi Greg, I sent an email about this about a week ago because I thought that since_id should return all the tweets after the given ID. Apparently, (thanks to Matt Sanford) you also need the count parameter in the call. As far as I can tell, your call is to the API is otherwise OK. Hope that helps, Nick On 11 Μαρ 2009, at 1:39 ΠΜ, Greg Maletic wrote: Thanks, Josh. That gives me some valuable insight into what's needed behind the scenes. I think, however, I'm going to try out MGTwitterEngine, as it's a full-featured framework that'll save me from having to figure this whole thing out. Thanks for everyone's help! Much appreciated. --Greg Nick Toumpelis email: n...@toumpelis.me.uk twitter: macsphere
[twitter-dev] Patch for permanent portrait URLs with SPIURL
I've been using Shannon Whitley's SPIURL code for the last couple of weeks, and it's a very simple way to create permanent links to user's portraits. In the last few days though I started to notice it returning a lot of 404 errors for images. Digging into it, I was hitting the 100 request-per-hour limit. Looking through the documentation this makes sense, what has me confused is how it was working before! Was the limit not actually being enforced for anonymous access to http://twitter.com/users/show/screen_name.xml until recently? I know there's some other developers using this, so here's my patch to authenticate those API calls: http://petewarden.typepad.com/searchbrowser/2009/03/adding-authentication-to-the-spiurl-permanent-twitter-portrait-project.html Pete Warden
[twitter-dev] Re: TinyUrl and Twitter. Should I use it?
Why would you want a local library? bit.ly offers a full REST API. On Wed, Mar 11, 2009 at 7:14 AM, shapper wrote: > > Does anyone knows if there is a reliable C# library to generate bit.ly > urls? > > Thanks, > Miguel > > On Mar 11, 4:16 am, Steve Brunton wrote: >> [top quoting is the debil] >> >> Another +1 for bit.ly. I was trying to do a "tweet this" for .com, but >> I couldn't work any ju-ju to get it to work the way I wanted. When >> OAuth is public (or out of private beta) I'll work on it again and use >> bit.ly to shorten the URL's back to the news story. >> >> -steve >
[twitter-dev] Re: Using max_id to navigate to pages after 15
Hi Matt, The bug has been logged over at: http://code.google.com/p/twitter-api/issues/detail?id=342&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Milestone Thanks for replying and looking into it. On Mar 11, 9:29 am, Matt Sanford wrote: > Hi, > > That query of 'ors=sad=all' looks a little goofy, I would suggest > 'q=sad+OR+all' if you're looking for both. I just tried a few > different things and it seems like this is an issue with combining > max_id and since_id. The max_id parameter was added to make sure the > page parameter works correctly. I've oddly never tested using it to > circumvent the pagination limit. I'll take a look at it but please > open a Google Code issue (http://code.google.com/p/twitter-api/issues/entry > ) so I don't forget. > > A quick aside about the pagination limit: It's not there to make > it hard on people or somehow hide our data, it's there to make > searches faster. When you go back in time we have to read data from > disk and replace recent data in memory with that older data. The > pagination limit is there to prevent too much of our memory space > being taken up by old data that a very small percentage of requests > need. > > Thanks; > — Matt > > On Mar 11, 2009, at 09:11 AM, Ronnie wrote: > > > > > Hey Matt, > > > Nish is right, I don't see a warning message that the max_id that > > max_id is adjusted unless since_id is not specified > > > Here's a sample json request: > >http://search.twitter.com/search.json?ors=sad=all&rpp=100&since_id=13... > > > The id of the first result is higher than the requested max_id but > > there was no warning message > > > Thanks, > > Ronnie > > > On Mar 11, 8:57 am, nish wrote: > >> HI, > > >> I am facing the same problem as Ronin. The output does not contain > >> any warning message. Just that the max_id passed in is ignored and a > >> new max_id much higher than the one passed in is assigned. > > >> Thanks, > >> Nish. > > >> PS: If since_id is not specified, then I do see a warning message > >> that it was adjusted, but thats a different case. > > >> On Mar 11, 7:48 am, Matt Sanford wrote: > > >>> Hi Ronnie, > > >>> Did the output contain any sort of warning message? When the > >>> max_id is too old we have to adjust it and the output will contain a > >>> warning saying as much. > > >>> Thanks; > >>> — Matt Sanford > > >>> On Mar 11, 2009, at 02:34 AM, ronin wrote: > > Hi Doug, > > I tried the approach that Karthik mentioned but it didn't quite > work. > > So after the first 15 pages worth of tweets were retrieved, I set > the > max_id to the id of the last tweet and page =1 > > For example, > > id of last tweet = 1000 > max_id = 1000 > page = 1 > > then the next query (for the next 15 pages)http://search...? > max_id=1000&since_id=100&page=1... > > The results returned basically ignored the max_id and the ids > were all > greater than the stipulated 1000. > > Any idea why the max_id was ignored ? Is there a way to retrieve > tweets beyond 15 pages? > > Thanks for the help in advance, > Ronnie > > On Mar 10, 4:45 pm, Doug Williams wrote: > > Nish, > > The way I read your question, it sounds like you are trying to use > > the > > max_id parameter incorrectly. max_id allows you to specify the > > maximum > > status id to return. It is the way to limit the results to > > statuses > > before a > > given status id. It is complementary to the since_id parameter, > > capping the > > results of a query at the top of the result list where since_id > > closes the > > bottom. > > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw > > > On Tue, Mar 10, 2009 at 7:20 PM, nish > > wrote: > > >> Hi, > > >> Were you able to get more than 1500 tweets using the max_id > >> method? > > >> I somehow cannot get it. I am using the search JSON API and > >> whenever > >> I set the max_id looks like the server resets it to something > >> else. > > >> Thanks. > > >> On Feb 24, 11:59 am, Karthik wrote: > >>> Please confirm, if the following is allowed? > > >>> 1. Set rpp=100 and retrieve 15 pages search results by > >>> incrementing > >>> the param 'page' > >>> 2. Get the id of the last status on page 15 and set that as the > >>> max_id > >>> for the next query > >>> 3. If we have more results, go to step 1 > > > On Mar 11, 8:57 am, nish wrote: > >> HI, > > >> I am facing the same problem as Ronin. The output does not contain > >> any warning message. Just that the max_id passed in is ignored and a > >> new max_id much higher than the one passed in is assigned. > > >> Thanks, > >> Nish. > > >> PS: If since_id is not specified, then I do see a warning message > >> that it was adjusted, but thats a different case. > > >
[twitter-dev] Re: Inconsistencies b/t XML and JSON
Snapshots in time of the XML output and JSON output are helpful. But I certainly believe that there could be such discrepancies. They tend to arise when our database replication lag increases. Some client requests UncachedUserA in XML, and those inaccurate counts get "frozen in time" until a cache invalidation event occurs. Then the replication lag sorts itself out, and someone requests UncachedUserB and sees the correct values. It's a very frustrating property of our system's architecture at the moment, but one we're working on solutions for. On Wed, Mar 11, 2009 at 10:09, Damon C wrote: > > I've seen this from time-to-time before, but could never really pin it > down to specific users or timeframes. > > In any case, I frequently see inconsistencies between the data in XML > and JSON representations. The example I came across last night was > with the ActiveRainMaker account. The caches have since caught up (un) > fortunately, and I don't have another example. > > In this case, though, the XML had a friends_count of ~1800 while the > JSON had a friends_count of ~800. I'm not really sure what else I can > provide and I probably didn't post before b/c it just sounds like > complaining. ;) > > Thanks! > > dpc > > -- > Damon P. Cortesi > Security Guy, Twitter Apps > www. tweetstats | tweepsearch | tweetsum .com > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Twitter image
Miguel, Sounds good! Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 1:46 PM, shapper wrote: > > Maybe you did not understand ... > > The users will never think they are no twitter. > > This is just an image (400px wide by 120 x height) with a design that > will incorporate a bird, blue color, a similar font and other elements > not related to twitter but to this web site I am creating. It will > also incorporate an arrow saying "My Web Site on Twitter >>>". > So people click this banner to go and check our twitter. > > It is just a banner incorporated on this web site. > I am using only similar elements on the banner so the user identifies > it as something related to twitter. > But the web site itself has nothing to do in design or anything else > with Twitter. > > Thanks, > Miguel > > On Mar 11, 3:01 pm, Doug Williams wrote: > > Miguel, > > We ask that you ensure your efforts do not give users the impression they > > are on Twitter.com, so please provide clear clues or differences in your > > design that inform users that they are not on the main site. Otherwise we > > have no issue with you basing your design on ours. You can refer to the > > Terms of Service [1] during the design process or reply back if you have > > specific questions. > > > > [1] -http://twitter.com/terms > > > > Best, > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw > > > > On Tue, Mar 10, 2009 at 9:34 PM, shapper wrote: > > > > > Hello, > > > > > I would like to add a twitter image on my web site saying something > > > like: > > > > > ThisWebSite.com in Twitter. > > > > > I am using a font similar's to Twitter's logo font. > > > > > I would like to create a design that is familiar to the users ... > > > using a similar font, blue color and a bird. > > > > > Is this a problem? > > > > > Thanks, > > > Miguel >
[twitter-dev] Re: Twitter image
Maybe you did not understand ... The users will never think they are no twitter. This is just an image (400px wide by 120 x height) with a design that will incorporate a bird, blue color, a similar font and other elements not related to twitter but to this web site I am creating. It will also incorporate an arrow saying "My Web Site on Twitter >>>". So people click this banner to go and check our twitter. It is just a banner incorporated on this web site. I am using only similar elements on the banner so the user identifies it as something related to twitter. But the web site itself has nothing to do in design or anything else with Twitter. Thanks, Miguel On Mar 11, 3:01 pm, Doug Williams wrote: > Miguel, > We ask that you ensure your efforts do not give users the impression they > are on Twitter.com, so please provide clear clues or differences in your > design that inform users that they are not on the main site. Otherwise we > have no issue with you basing your design on ours. You can refer to the > Terms of Service [1] during the design process or reply back if you have > specific questions. > > [1] -http://twitter.com/terms > > Best, > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Tue, Mar 10, 2009 at 9:34 PM, shapper wrote: > > > Hello, > > > I would like to add a twitter image on my web site saying something > > like: > > > ThisWebSite.com in Twitter. > > > I am using a font similar's to Twitter's logo font. > > > I would like to create a design that is familiar to the users ... > > using a similar font, blue color and a bird. > > > Is this a problem? > > > Thanks, > > Miguel
[twitter-dev] Inconsistencies b/t XML and JSON
I've seen this from time-to-time before, but could never really pin it down to specific users or timeframes. In any case, I frequently see inconsistencies between the data in XML and JSON representations. The example I came across last night was with the ActiveRainMaker account. The caches have since caught up (un) fortunately, and I don't have another example. In this case, though, the XML had a friends_count of ~1800 while the JSON had a friends_count of ~800. I'm not really sure what else I can provide and I probably didn't post before b/c it just sounds like complaining. ;) Thanks! dpc -- Damon P. Cortesi Security Guy, Twitter Apps www. tweetstats | tweepsearch | tweetsum .com
[twitter-dev] Re: getting replies to user if user is not following the replying user
I think it does if you use: @user -to:user On Mar 11, 2009, at 09:42 AM, Jeff Bishop wrote: Right, but using the Search API doesn't provide a way of filtering out those already processed by the Twitter Replies API. See what I mean? Jeff - Original Message - From: Doug Williams To: twitter-development-talk@googlegroups.com Sent: Wednesday, March 11, 2009 9:36 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user Jeff, A Search for @replies will return any tweet that contains a reference to the user. The current implementation of replies from the REST API will only return tweets that start with a reference to that user. Thus the result from the search API is the superset of all @replies and public mentions of a user. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:31 PM, Jeff Bishop wrote: I am also wanting to insure that I filter those items that I already processed from the Twitter API. I would rather not have duplicates. It is unclear if the Search API will return to me the Twitter ID values of a tweet to ignore already filtered tweets from the Twitter API. Sorry if this is confusing. - Original Message - From: Doug Williams To: twitter-development-talk@googlegroups.com Sent: Wednesday, March 11, 2009 9:23 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user Jeff, The search API [1] is drop dead simple. Say you have a search for any @reply or mention to @twitterapi [2]. Changing the search URL to include a format (json or atom) will give you a feed that can be parsed programmatically. For example: http://search.twitter.com/search.atom?q=%40twitterapi [1] - http://apiwiki.twitter.com/Search+API+Documentation [2] - http://search.twitter.com/search?q=%40twitterapi Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: I would prefer to get them in a feed like the Twitter API provides (like in a Status node). Will these appear in the replies Twitter API call? - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 8:59 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: getting replies to user if user is not following the replying user
Right, but using the Search API doesn't provide a way of filtering out those already processed by the Twitter Replies API. See what I mean? Jeff - Original Message - From: Doug Williams To: twitter-development-talk@googlegroups.com Sent: Wednesday, March 11, 2009 9:36 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user Jeff, A Search for @replies will return any tweet that contains a reference to the user. The current implementation of replies from the REST API will only return tweets that start with a reference to that user. Thus the result from the search API is the superset of all @replies and public mentions of a user. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:31 PM, Jeff Bishop wrote: I am also wanting to insure that I filter those items that I already processed from the Twitter API. I would rather not have duplicates. It is unclear if the Search API will return to me the Twitter ID values of a tweet to ignore already filtered tweets from the Twitter API. Sorry if this is confusing. - Original Message - From: Doug Williams To: twitter-development-talk@googlegroups.com Sent: Wednesday, March 11, 2009 9:23 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user Jeff, The search API [1] is drop dead simple. Say you have a search for any @reply or mention to @twitterapi [2]. Changing the search URL to include a format (json or atom) will give you a feed that can be parsed programmatically. For example: http://search.twitter.com/search.atom?q=%40twitterapi [1] - http://apiwiki.twitter.com/Search+API+Documentation [2] - http://search.twitter.com/search?q=%40twitterapi Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: I would prefer to get them in a feed like the Twitter API provides (like in a Status node). Will these appear in the replies Twitter API call? - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 8:59 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: getting replies to user if user is not following the replying user
Yes, thank you. - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 9:39 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user Let me give an example: Let's say I am UserA, and I send out this tweet: "@UserB @UserC @UserD can't wait to see you this weekend for dinner with @UserE!!" Then only UserB will see that tweet in their Reply feed (because the tweet physically starts with "@UserB"). UserC, UserD and UserE are SOL and won't see this tweet in their Reply feed. They would have to use the Search API to search for themselves to see this tweet and know they were mentioned... make a bit more sense? -Chad On Wed, Mar 11, 2009 at 12:34 PM, Jeff Bishop wrote: Do you mean if I have something like: @jeff1, @jeff2, @jeff3 then jeff1 will appear but not jeff2 or jeff3? - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 9:32 AM - Show quoted text - Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: I would prefer to get them in a feed like the Twitter API provides (like in a Status node). Will these appear in the replies Twitter API call? They will appear in the Replies Twitter API feed. However, they will only be ones that begin with @user. If @user appears anywhere else (what I call (and several others) a "mention") it will not be in the Replies feed... -Chad - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 8:59 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user - Show quoted text - I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: getting replies to user if user is not following the replying user
Let me give an example: Let's say I am UserA, and I send out this tweet: "@UserB @UserC @UserD can't wait to see you this weekend for dinner with @UserE!!" Then only UserB will see that tweet in their Reply feed (because the tweet physically starts with "@UserB"). UserC, UserD and UserE are SOL and won't see this tweet in their Reply feed. They would have to use the Search API to search for themselves to see this tweet and know they were mentioned... make a bit more sense? -Chad On Wed, Mar 11, 2009 at 12:34 PM, Jeff Bishop wrote: > > Do you mean if I have something like: > > @jeff1, @jeff2, @jeff3 > > then jeff1 will appear but not jeff2 or jeff3? > > - Original Message - From: "Chad Etzel" > To: > Sent: Wednesday, March 11, 2009 9:32 AM > - Show quoted text - > Subject: [twitter-dev] Re: getting replies to user if user is not following > the replying user > > > > On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: >> >> I would prefer to get them in a feed like the Twitter API provides (like >> in >> a Status node). Will these appear in the replies Twitter API call? > > They will appear in the Replies Twitter API feed. However, they will > only be ones that begin with @user. If @user appears anywhere else > (what I call (and several others) a "mention") it will not be in the > Replies feed... > -Chad > > >> >> - Original Message - From: "Chad Etzel" >> To: >> Sent: Wednesday, March 11, 2009 8:59 AM >> Subject: [twitter-dev] Re: getting replies to user if user is not >> following >> the replying user >> - Show quoted text - >> >> >> >> I thought that those type of replies would show up under the replies >> tab anyway (i.e. there doesn't need to be a relationship between two >> users (in either direction) for a reply to show up in the replies >> tab). I could be wrong, or maybe something changed... >> >> However, if you head to http://search.twitter.com/ and search for >> @user you will see all mentions of that user from all public accounts. >> You can grab the resultant search as an RSS/Atom feed if you like. >> >> -Chad >> >> On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop >> wrote: >>> >>> Hello, >>> >>> Is it possible to track replies sent to a user even though that user is >>> not >>> following that person? If so, how? >>> >>> Jeff >>> >> >> > >
[twitter-dev] Re: getting replies to user if user is not following the replying user
Jeff, A Search for @replies will return any tweet that contains a reference to the user. The current implementation of replies from the REST API will only return tweets that start with a reference to that user. Thus the result from the search API is the superset of all @replies and public mentions of a user. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:31 PM, Jeff Bishop wrote: > I am also wanting to insure that I filter those items that I already > processed from the Twitter API. I would rather not have duplicates. It is > unclear if the Search API will return to me the Twitter ID values of a tweet > to ignore already filtered tweets from the Twitter API. Sorry if this is > confusing. > > - Original Message - > *From:* Doug Williams > *To:* twitter-development-talk@googlegroups.com > *Sent:* Wednesday, March 11, 2009 9:23 AM > *Subject:* [twitter-dev] Re: getting replies to user if user is not > following the replying user > > Jeff, > The search API [1] is drop dead simple. Say you have a search for any > @reply or mention to @twitterapi [2]. Changing the search URL to include a > format (json or atom) will give you a feed that can be parsed > programmatically. For example: > > http://search.twitter.com/search.atom?q=%40twitterapi > > [1] - http://apiwiki.twitter.com/Search+API+Documentation > [2] - http://search.twitter.com/search?q=%40twitterapi > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: > >> >> I would prefer to get them in a feed like the Twitter API provides (like >> in a Status node). Will these appear in the replies Twitter API call? >> >> - Original Message - From: "Chad Etzel" >> To: >> Sent: Wednesday, March 11, 2009 8:59 AM >> Subject: [twitter-dev] Re: getting replies to user if user is not >> following the replying user >> >> >> >> >> I thought that those type of replies would show up under the replies >> tab anyway (i.e. there doesn't need to be a relationship between two >> users (in either direction) for a reply to show up in the replies >> tab). I could be wrong, or maybe something changed... >> >> However, if you head to http://search.twitter.com/ and search for >> @user you will see all mentions of that user from all public accounts. >> You can grab the resultant search as an RSS/Atom feed if you like. >> >> -Chad >> >> On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop >> wrote: >> >>> Hello, >>> >>> Is it possible to track replies sent to a user even though that user is >>> not >>> following that person? If so, how? >>> >>> Jeff >>> >>> >> >
[twitter-dev] Re: getting replies to user if user is not following the replying user
Do you mean if I have something like: @jeff1, @jeff2, @jeff3 then jeff1 will appear but not jeff2 or jeff3? - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 9:32 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: I would prefer to get them in a feed like the Twitter API provides (like in a Status node). Will these appear in the replies Twitter API call? They will appear in the Replies Twitter API feed. However, they will only be ones that begin with @user. If @user appears anywhere else (what I call (and several others) a "mention") it will not be in the Replies feed... -Chad - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 8:59 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user - Show quoted text - I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: getting replies to user if user is not following the replying user
On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: > > I would prefer to get them in a feed like the Twitter API provides (like in > a Status node). Will these appear in the replies Twitter API call? They will appear in the Replies Twitter API feed. However, they will only be ones that begin with @user. If @user appears anywhere else (what I call (and several others) a "mention") it will not be in the Replies feed... -Chad > > - Original Message - From: "Chad Etzel" > To: > Sent: Wednesday, March 11, 2009 8:59 AM > Subject: [twitter-dev] Re: getting replies to user if user is not following > the replying user > - Show quoted text - > > > > I thought that those type of replies would show up under the replies > tab anyway (i.e. there doesn't need to be a relationship between two > users (in either direction) for a reply to show up in the replies > tab). I could be wrong, or maybe something changed... > > However, if you head to http://search.twitter.com/ and search for > @user you will see all mentions of that user from all public accounts. > You can grab the resultant search as an RSS/Atom feed if you like. > > -Chad > > On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: >> >> Hello, >> >> Is it possible to track replies sent to a user even though that user is >> not >> following that person? If so, how? >> >> Jeff >> > >
[twitter-dev] Re: getting replies to user if user is not following the replying user
I am also wanting to insure that I filter those items that I already processed from the Twitter API. I would rather not have duplicates. It is unclear if the Search API will return to me the Twitter ID values of a tweet to ignore already filtered tweets from the Twitter API. Sorry if this is confusing. - Original Message - From: Doug Williams To: twitter-development-talk@googlegroups.com Sent: Wednesday, March 11, 2009 9:23 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user Jeff, The search API [1] is drop dead simple. Say you have a search for any @reply or mention to @twitterapi [2]. Changing the search URL to include a format (json or atom) will give you a feed that can be parsed programmatically. For example: http://search.twitter.com/search.atom?q=%40twitterapi [1] - http://apiwiki.twitter.com/Search+API+Documentation [2] - http://search.twitter.com/search?q=%40twitterapi Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: I would prefer to get them in a feed like the Twitter API provides (like in a Status node). Will these appear in the replies Twitter API call? - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 8:59 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: getting replies to user if user is not following the replying user
Doug, OK, good enough, but, will the Replies method of the Twitter API not give me those details? Jeff - Original Message - From: Doug Williams To: twitter-development-talk@googlegroups.com Sent: Wednesday, March 11, 2009 9:23 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user Jeff, The search API [1] is drop dead simple. Say you have a search for any @reply or mention to @twitterapi [2]. Changing the search URL to include a format (json or atom) will give you a feed that can be parsed programmatically. For example: http://search.twitter.com/search.atom?q=%40twitterapi [1] - http://apiwiki.twitter.com/Search+API+Documentation [2] - http://search.twitter.com/search?q=%40twitterapi Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: I would prefer to get them in a feed like the Twitter API provides (like in a Status node). Will these appear in the replies Twitter API call? - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 8:59 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: Using max_id to navigate to pages after 15
Hi, That query of 'ors=sad=all' looks a little goofy, I would suggest 'q=sad+OR+all' if you're looking for both. I just tried a few different things and it seems like this is an issue with combining max_id and since_id. The max_id parameter was added to make sure the page parameter works correctly. I've oddly never tested using it to circumvent the pagination limit. I'll take a look at it but please open a Google Code issue (http://code.google.com/p/twitter-api/issues/entry ) so I don't forget. A quick aside about the pagination limit: It's not there to make it hard on people or somehow hide our data, it's there to make searches faster. When you go back in time we have to read data from disk and replace recent data in memory with that older data. The pagination limit is there to prevent too much of our memory space being taken up by old data that a very small percentage of requests need. Thanks; — Matt On Mar 11, 2009, at 09:11 AM, Ronnie wrote: Hey Matt, Nish is right, I don't see a warning message that the max_id that max_id is adjusted unless since_id is not specified Here's a sample json request: http://search.twitter.com/search.json?ors=sad=all&rpp=100&since_id=1309564503&max_id=1311104069&page=1 The id of the first result is higher than the requested max_id but there was no warning message Thanks, Ronnie On Mar 11, 8:57 am, nish wrote: HI, I am facing the same problem as Ronin. The output does not contain any warning message. Just that the max_id passed in is ignored and a new max_id much higher than the one passed in is assigned. Thanks, Nish. PS: If since_id is not specified, then I do see a warning message that it was adjusted, but thats a different case. On Mar 11, 7:48 am, Matt Sanford wrote: Hi Ronnie, Did the output contain any sort of warning message? When the max_id is too old we have to adjust it and the output will contain a warning saying as much. Thanks; — Matt Sanford On Mar 11, 2009, at 02:34 AM, ronin wrote: Hi Doug, I tried the approach that Karthik mentioned but it didn't quite work. So after the first 15 pages worth of tweets were retrieved, I set the max_id to the id of the last tweet and page =1 For example, id of last tweet = 1000 max_id = 1000 page = 1 then the next query (for the next 15 pages)http://search...? max_id=1000&since_id=100&page=1... The results returned basically ignored the max_id and the ids were all greater than the stipulated 1000. Any idea why the max_id was ignored ? Is there a way to retrieve tweets beyond 15 pages? Thanks for the help in advance, Ronnie On Mar 10, 4:45 pm, Doug Williams wrote: Nish, The way I read your question, it sounds like you are trying to use the max_id parameter incorrectly. max_id allows you to specify the maximum status id to return. It is the way to limit the results to statuses before a given status id. It is complementary to the since_id parameter, capping the results of a query at the top of the result list where since_id closes the bottom. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Tue, Mar 10, 2009 at 7:20 PM, nish wrote: Hi, Were you able to get more than 1500 tweets using the max_id method? I somehow cannot get it. I am using the search JSON API and whenever I set the max_id looks like the server resets it to something else. Thanks. On Feb 24, 11:59 am, Karthik wrote: Please confirm, if the following is allowed? 1. Set rpp=100 and retrieve 15 pages search results by incrementing the param 'page' 2. Get the id of the last status on page 15 and set that as the max_id for the next query 3. If we have more results, go to step 1 On Mar 11, 8:57 am, nish wrote: HI, I am facing the same problem as Ronin. The output does not contain any warning message. Just that the max_id passed in is ignored and a new max_id much higher than the one passed in is assigned. Thanks, Nish. PS: If since_id is not specified, then I do see a warning message that it was adjusted, but thats a different case. On Mar 11, 7:48 am, Matt Sanford wrote: Hi Ronnie, Did the output contain any sort of warning message? When the max_id is too old we have to adjust it and the output will contain a warning saying as much. Thanks; — Matt Sanford On Mar 11, 2009, at 02:34 AM, ronin wrote: Hi Doug, I tried the approach that Karthik mentioned but it didn't quite work. So after the first 15 pages worth of tweets were retrieved, I set the max_id to the id of the last tweet and page =1 For example, id of last tweet = 1000 max_id = 1000 page = 1 then the next query (for the next 15 pages)http://search...? max_id=1000&since_id=100&page=1... The results returned basically ignored the max_id and the ids were all greater than the stipulated 1000. Any idea why the max_id was ignored ? Is there a way to retrieve tweets beyond 15 pages? Thanks for the he
[twitter-dev] Re: getting replies to user if user is not following the replying user
Jeff, The search API [1] is drop dead simple. Say you have a search for any @reply or mention to @twitterapi [2]. Changing the search URL to include a format (json or atom) will give you a feed that can be parsed programmatically. For example: http://search.twitter.com/search.atom?q=%40twitterapi [1] - http://apiwiki.twitter.com/Search+API+Documentation [2] - http://search.twitter.com/search?q=%40twitterapi Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Mar 11, 2009 at 12:16 PM, Jeff Bishop wrote: > > I would prefer to get them in a feed like the Twitter API provides (like in > a Status node). Will these appear in the replies Twitter API call? > > - Original Message - From: "Chad Etzel" > To: > Sent: Wednesday, March 11, 2009 8:59 AM > Subject: [twitter-dev] Re: getting replies to user if user is not following > the replying user > > > > > I thought that those type of replies would show up under the replies > tab anyway (i.e. there doesn't need to be a relationship between two > users (in either direction) for a reply to show up in the replies > tab). I could be wrong, or maybe something changed... > > However, if you head to http://search.twitter.com/ and search for > @user you will see all mentions of that user from all public accounts. > You can grab the resultant search as an RSS/Atom feed if you like. > > -Chad > > On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop > wrote: > >> Hello, >> >> Is it possible to track replies sent to a user even though that user is >> not >> following that person? If so, how? >> >> Jeff >> >> >
[twitter-dev] Re: getting replies to user if user is not following the replying user
I would prefer to get them in a feed like the Twitter API provides (like in a Status node). Will these appear in the replies Twitter API call? - Original Message - From: "Chad Etzel" To: Sent: Wednesday, March 11, 2009 8:59 AM Subject: [twitter-dev] Re: getting replies to user if user is not following the replying user I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: Using max_id to navigate to pages after 15
Hey Matt, Nish is right, I don't see a warning message that the max_id that max_id is adjusted unless since_id is not specified Here's a sample json request: http://search.twitter.com/search.json?ors=sad=all&rpp=100&since_id=1309564503&max_id=1311104069&page=1 The id of the first result is higher than the requested max_id but there was no warning message Thanks, Ronnie On Mar 11, 8:57 am, nish wrote: > HI, > > I am facing the same problem as Ronin. The output does not contain > any warning message. Just that the max_id passed in is ignored and a > new max_id much higher than the one passed in is assigned. > > Thanks, > Nish. > > PS: If since_id is not specified, then I do see a warning message > that it was adjusted, but thats a different case. > > On Mar 11, 7:48 am, Matt Sanford wrote: > > > Hi Ronnie, > > > Did the output contain any sort of warning message? When the > > max_id is too old we have to adjust it and the output will contain a > > warning saying as much. > > > Thanks; > >— Matt Sanford > > > On Mar 11, 2009, at 02:34 AM, ronin wrote: > > > > Hi Doug, > > > > I tried the approach that Karthik mentioned but it didn't quite work. > > > > So after the first 15 pages worth of tweets were retrieved, I set the > > > max_id to the id of the last tweet and page =1 > > > > For example, > > > > id of last tweet = 1000 > > > max_id = 1000 > > > page = 1 > > > > then the next query (for the next 15 pages)http://search...? > > > max_id=1000&since_id=100&page=1... > > > > The results returned basically ignored the max_id and the ids were all > > > greater than the stipulated 1000. > > > > Any idea why the max_id was ignored ? Is there a way to retrieve > > > tweets beyond 15 pages? > > > > Thanks for the help in advance, > > > Ronnie > > > > On Mar 10, 4:45 pm, Doug Williams wrote: > > >> Nish, > > >> The way I read your question, it sounds like you are trying to use > > >> the > > >> max_id parameter incorrectly. max_id allows you to specify the > > >> maximum > > >> status id to return. It is the way to limit the results to statuses > > >> before a > > >> given status id. It is complementary to the since_id parameter, > > >> capping the > > >> results of a query at the top of the result list where since_id > > >> closes the > > >> bottom. > > > >> Doug Williams > > >> Twitter API Supporthttp://twitter.com/dougw > > > >> On Tue, Mar 10, 2009 at 7:20 PM, nish wrote: > > > >>> Hi, > > > >>> Were you able to get more than 1500 tweets using the max_id method? > > > >>> I somehow cannot get it. I am using the search JSON API and > > >>> whenever > > >>> I set the max_id looks like the server resets it to something else. > > > >>> Thanks. > > > >>> On Feb 24, 11:59 am, Karthik wrote: > > Please confirm, if the following is allowed? > > > 1. Set rpp=100 and retrieve 15 pages search results by incrementing > > the param 'page' > > 2. Get the id of the last status on page 15 and set that as the > > max_id > > for the next query > > 3. If we have more results, go to step 1 On Mar 11, 8:57 am, nish wrote: > HI, > > I am facing the same problem as Ronin. The output does not contain > any warning message. Just that the max_id passed in is ignored and a > new max_id much higher than the one passed in is assigned. > > Thanks, > Nish. > > PS: If since_id is not specified, then I do see a warning message > that it was adjusted, but thats a different case. > > On Mar 11, 7:48 am, Matt Sanford wrote: > > > Hi Ronnie, > > > Did the output contain any sort of warning message? When the > > max_id is too old we have to adjust it and the output will contain a > > warning saying as much. > > > Thanks; > > — Matt Sanford > > > On Mar 11, 2009, at 02:34 AM, ronin wrote: > > > > Hi Doug, > > > > I tried the approach that Karthik mentioned but it didn't quite work. > > > > So after the first 15 pages worth of tweets were retrieved, I set the > > > max_id to the id of the last tweet and page =1 > > > > For example, > > > > id of last tweet = 1000 > > > max_id = 1000 > > > page = 1 > > > > then the next query (for the next 15 pages)http://search...? > > > max_id=1000&since_id=100&page=1... > > > > The results returned basically ignored the max_id and the ids were all > > > greater than the stipulated 1000. > > > > Any idea why the max_id was ignored ? Is there a way to retrieve > > > tweets beyond 15 pages? > > > > Thanks for the help in advance, > > > Ronnie > > > > On Mar 10, 4:45 pm, Doug Williams wrote: > > >> Nish, > > >> The way I read your question, it sounds like you are trying to use > > >> the > > >> max_id parameter incorrectly. max_id allows you to specify the > > >> maximum > > >> status id to return. It is the way to limit the results to statuses > > >> before a > > >> given status id. It is complementary to the since_id parameter, > > >> capping the > > >> results of a query at the top of the result list where since_id > > >> closes the > > >> bott
[twitter-dev] Re: Freelance Twitter API Dev directory?
Another one for the list! Username: @lgladdy URL: http://www.gladdymedia.com Technologies: AJAX/Web Specialist, PHP/MySQL. Thanks :)
[twitter-dev] Re: getting replies to user if user is not following the replying user
I thought that those type of replies would show up under the replies tab anyway (i.e. there doesn't need to be a relationship between two users (in either direction) for a reply to show up in the replies tab). I could be wrong, or maybe something changed... However, if you head to http://search.twitter.com/ and search for @user you will see all mentions of that user from all public accounts. You can grab the resultant search as an RSS/Atom feed if you like. -Chad On Wed, Mar 11, 2009 at 11:56 AM, Jeff Bishop wrote: > Hello, > > Is it possible to track replies sent to a user even though that user is not > following that person? If so, how? > > Jeff >
[twitter-dev] Re: Using max_id to navigate to pages after 15
HI, I am facing the same problem as Ronin. The output does not contain any warning message. Just that the max_id passed in is ignored and a new max_id much higher than the one passed in is assigned. Thanks, Nish. PS: If since_id is not specified, then I do see a warning message that it was adjusted, but thats a different case. On Mar 11, 7:48 am, Matt Sanford wrote: > Hi Ronnie, > > Did the output contain any sort of warning message? When the > max_id is too old we have to adjust it and the output will contain a > warning saying as much. > > Thanks; >— Matt Sanford > > On Mar 11, 2009, at 02:34 AM, ronin wrote: > > > > > Hi Doug, > > > I tried the approach that Karthik mentioned but it didn't quite work. > > > So after the first 15 pages worth of tweets were retrieved, I set the > > max_id to the id of the last tweet and page =1 > > > For example, > > > id of last tweet = 1000 > > max_id = 1000 > > page = 1 > > > then the next query (for the next 15 pages)http://search...? > > max_id=1000&since_id=100&page=1... > > > The results returned basically ignored the max_id and the ids were all > > greater than the stipulated 1000. > > > Any idea why the max_id was ignored ? Is there a way to retrieve > > tweets beyond 15 pages? > > > Thanks for the help in advance, > > Ronnie > > > On Mar 10, 4:45 pm, Doug Williams wrote: > >> Nish, > >> The way I read your question, it sounds like you are trying to use > >> the > >> max_id parameter incorrectly. max_id allows you to specify the > >> maximum > >> status id to return. It is the way to limit the results to statuses > >> before a > >> given status id. It is complementary to the since_id parameter, > >> capping the > >> results of a query at the top of the result list where since_id > >> closes the > >> bottom. > > >> Doug Williams > >> Twitter API Supporthttp://twitter.com/dougw > > >> On Tue, Mar 10, 2009 at 7:20 PM, nish wrote: > > >>> Hi, > > >>> Were you able to get more than 1500 tweets using the max_id method? > > >>> I somehow cannot get it. I am using the search JSON API and > >>> whenever > >>> I set the max_id looks like the server resets it to something else. > > >>> Thanks. > > >>> On Feb 24, 11:59 am, Karthik wrote: > Please confirm, if the following is allowed? > > 1. Set rpp=100 and retrieve 15 pages search results by incrementing > the param 'page' > 2. Get the id of the last status on page 15 and set that as the > max_id > for the next query > 3. If we have more results, go to step 1
[twitter-dev] getting replies to user if user is not following the replying user
Hello, Is it possible to track replies sent to a user even though that user is not following that person? If so, how? Jeff
[twitter-dev] Re: What is 140 characters?
DO NOT ENCODE WITH HTML ENTITIES. The only reason that < and > are encoded as < and > is because these values are represented within an XML element. This is invalid XML: This <-- is a test And this is valid XML: This <-- is a test If you use HTML entities, they will only show up correctly in a web browser. SMS and other media will display &crap;. -ch On Mar 10, 10:13 pm, Nicolas Steenhout wrote: > > "All" is such an inclusive term, isn't it? :-) > > > ONE OF US! ONE OF US! > > Hey! I resemble that :) > > But I fear we're somewhat West of the OT's question :) > > And we still don't know what to do about encoding html entities used > for accents in languages such as French, Spanish, etc ;) > > Nic
[twitter-dev] Re: Twitter image
Miguel, We ask that you ensure your efforts do not give users the impression they are on Twitter.com, so please provide clear clues or differences in your design that inform users that they are not on the main site. Otherwise we have no issue with you basing your design on ours. You can refer to the Terms of Service [1] during the design process or reply back if you have specific questions. [1] - http://twitter.com/terms Best, Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Mar 10, 2009 at 9:34 PM, shapper wrote: > > Hello, > > I would like to add a twitter image on my web site saying something > like: > > ThisWebSite.com in Twitter. > > I am using a font similar's to Twitter's logo font. > > I would like to create a design that is familiar to the users ... > using a similar font, blue color and a bird. > > Is this a problem? > > Thanks, > Miguel > > >
[twitter-dev] Re: Using max_id to navigate to pages after 15
Hi Ronnie, Did the output contain any sort of warning message? When the max_id is too old we have to adjust it and the output will contain a warning saying as much. Thanks; — Matt Sanford On Mar 11, 2009, at 02:34 AM, ronin wrote: Hi Doug, I tried the approach that Karthik mentioned but it didn't quite work. So after the first 15 pages worth of tweets were retrieved, I set the max_id to the id of the last tweet and page =1 For example, id of last tweet = 1000 max_id = 1000 page = 1 then the next query (for the next 15 pages) http://search...? max_id=1000&since_id=100&page=1... The results returned basically ignored the max_id and the ids were all greater than the stipulated 1000. Any idea why the max_id was ignored ? Is there a way to retrieve tweets beyond 15 pages? Thanks for the help in advance, Ronnie On Mar 10, 4:45 pm, Doug Williams wrote: Nish, The way I read your question, it sounds like you are trying to use the max_id parameter incorrectly. max_id allows you to specify the maximum status id to return. It is the way to limit the results to statuses before a given status id. It is complementary to the since_id parameter, capping the results of a query at the top of the result list where since_id closes the bottom. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Tue, Mar 10, 2009 at 7:20 PM, nish wrote: Hi, Were you able to get more than 1500 tweets using the max_id method? I somehow cannot get it. I am using the search JSON API and whenever I set the max_id looks like the server resets it to something else. Thanks. On Feb 24, 11:59 am, Karthik wrote: Please confirm, if the following is allowed? 1. Set rpp=100 and retrieve 15 pages search results by incrementing the param 'page' 2. Get the id of the last status on page 15 and set that as the max_id for the next query 3. If we have more results, go to step 1
[twitter-dev] Re: How many accounts is too many?
Twitter is opt-in. If you don't want certain kinds of content in your
friends timeline, you just don't follow a particular account. I don't
think we should get terribly dogmatic about how an account is used
(beyond things that violate TOS). In fact, the flexibility of Twitter
and its API is a big reason why it has such a large dev community, I'd
say.
I subscribe to a couple broadcast-only "news ticker" accounts, because
I like the content and prefer to have it in my friends timeline over
other delivery systems.
--
Ed Finkler
http://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com
On Mar 10, 1:15 pm, TjL wrote:
> On Tue, Mar 10, 2009 at 11:37 AM, Clinton wrote:
>
> >> You're confusing Twitter with RSS.
>
> >> RSS is a way to "push" this type of information out to people.
>
> >> Twitter is the wrong tool.
>
> > Well, is it? Yes, you're right, I AM thinking of using this like RSS,
> > but is that necessarily wrong?
>
> If you ask just about anyone who uses Twitter a lot, they would tell
> you yes, it is wrong.
>
> Google "twitter is not rss" (including the quotes) and read some of the
> results.
>
> RSS is RSS. People who want RSS go to RSS.
>
> What's the advantage of Twitter? That people can get them via SMS? Not
> at the rates you're talking about publishing.
>
> With the exception of "Breaking News" I don't see any sort of purpose
> to duplicate what RSS provides via Twitter.
>
> > To put it in context, there are lots of people who read the day's
> > obituaries (or other family announcements) in their daily newspaper. I
> > could imagine these people being interested in receiving a list of new
> > notices daily.
>
> Sounds like a perfect job for a daily email digest. I'd sign up for
> one of those if my local paper provided it.
>
> I would not, however, sign up for their Twitter feed.
>
> Seriously, I'm not trying to be a PITA or smart-aleck.
>
> There's not enough info in 140 characters to tell me what I need to
> know, so all you can do is post a name, age, and a link to your
> website.
>
> You are probably not going to send any "Breaking News! Maybelle Lewis,
> 90, died" updates. Once a day is plenty.
>
> I'd MUCH rather give you my email address and get the daily digest
> where I can get the full obit (and you can stick some other marketing
> information in the email if you'd like :-)
>
> > My previous number of 3,500 was the number of new notices across a
> > whole site (which consists of many newspapers), but for individual
> > newspapers, we're talking about anything between 0 and 100 per day-
> > usually more like 20-30. That is manageable.
>
> FWIW I believe that 20-30 a day is going to rate you as a "nuclear follow
> cost"
>
> http://www.followcost.com
>
> which I point to as further evidence that this is not how Twitter
> users intend to use Twitter.
>
> >> If you/they are determined to do this, then the best way to do it
> >> ("least-worst") solution is to make it so that you are sending the
> >> fewest number of status updates as possible which are as specific as
> >> possible.
>
> > Sure. In this context, that amounts to a tweet for each new notice
> > that is published - any less and we'd just be sending stats: "20 new
> > obituaries", which is meaningless to everybody.
>
> Yes, but
>
> "Obituaries for John Smith, Kelly Green, Joseph Smith, Al Jones, [and
> so on]http://tr.im/";
>
> would be better than 10 separate posts
>
> > I'd welcome other ideas for how to incorporate twitter into the site,
> > or pointers to useful implementations by other companies.
>
> How other companies are using Twitter might be a good thing to checkout.
>
> Look athttp://twitter.com/zapposfor example.
>
> They aren't link-blasting you with sale information or special promo
> codes. It's an actual person typing in actual messages, making
> connections with actual people.
>
> On the other side, there ishttp://twitter.com/cnnwho has 34,561
> followers, but even they posting less than 20 times a day. And they're
> CNN.
>
> Look at how Rachel Maddow is using ithttp://twitter.com/maddow
> Pointers to her show but not JUST that.
>
> If there is an on-scene reporter who wants to take on an official
> Twitter account, that'd be one thing, but if it's going to be
> automated, I think it's missing the point.
>
> TjL
[twitter-dev] Re: How to change Source name to Client tool Source?
> You probably missed it the same way i missed it. The term Twitter uses > is not what my mind assumed it would be. > > I googled "Custom Twitter Client Name" and "Change Twitter Client > Name" and "Twitter Client Name" and nothing came up... I forget what > finally brought me to this page. And the part in the Twitter docs is > "How do I get _from [MyApp]_ which is like documentation but not human > friendly :) Oh, I don't know, "just fill out this handy form[1]" seems pretty straightforward to me. :-P [1] http://twitter.com/help/request_source -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- FOOLS! I WILL DESTROY YOU ALL! ASK ME HOW! -- "Girl Genius" 8/29/07
[twitter-dev] Re: TinyUrl and Twitter. Should I use it?
Does anyone knows if there is a reliable C# library to generate bit.ly urls? Thanks, Miguel On Mar 11, 4:16 am, Steve Brunton wrote: > [top quoting is the debil] > > Another +1 for bit.ly. I was trying to do a "tweet this" for .com, but > I couldn't work any ju-ju to get it to work the way I wanted. When > OAuth is public (or out of private beta) I'll work on it again and use > bit.ly to shorten the URL's back to the news story. > > -steve
[twitter-dev] Re: How to change Source name to Client tool Source?
You probably missed it the same way i missed it. The term Twitter uses is not what my mind assumed it would be. I googled "Custom Twitter Client Name" and "Change Twitter Client Name" and "Twitter Client Name" and nothing came up... I forget what finally brought me to this page. And the part in the Twitter docs is "How do I get “from [MyApp]” which is like documentation but not human friendly :)
[twitter-dev] Re: Using max_id to navigate to pages after 15
Hi Doug, I tried the approach that Karthik mentioned but it didn't quite work. So after the first 15 pages worth of tweets were retrieved, I set the max_id to the id of the last tweet and page =1 For example, id of last tweet = 1000 max_id = 1000 page = 1 then the next query (for the next 15 pages) http://search...?max_id=1000&since_id=100&page=1... The results returned basically ignored the max_id and the ids were all greater than the stipulated 1000. Any idea why the max_id was ignored ? Is there a way to retrieve tweets beyond 15 pages? Thanks for the help in advance, Ronnie On Mar 10, 4:45 pm, Doug Williams wrote: > Nish, > The way I read your question, it sounds like you are trying to use the > max_id parameter incorrectly. max_id allows you to specify the maximum > status id to return. It is the way to limit the results to statuses before a > given status id. It is complementary to the since_id parameter, capping the > results of a query at the top of the result list where since_id closes the > bottom. > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Tue, Mar 10, 2009 at 7:20 PM, nish wrote: > > > Hi, > > > Were you able to get more than 1500 tweets using the max_id method? > > > I somehow cannot get it. I am using the search JSON API and whenever > > I set the max_id looks like the server resets it to something else. > > > Thanks. > > > On Feb 24, 11:59 am, Karthik wrote: > > > Please confirm, if the following is allowed? > > > > 1. Set rpp=100 and retrieve 15 pages search results by incrementing > > > the param 'page' > > > 2. Get the id of the last status on page 15 and set that as the max_id > > > for the next query > > > 3. If we have more results, go to step 1
[twitter-dev] Re: Using max_id to navigate to pages after 15
Did anyone ever manage to get more than 1500 or past 15 pages worth of tweets by: 1. Set rpp=100 and retrieve 15 pages search results by incrementing the param 'page' 2. Get the id of the last status on page 15 and set that as the max_id for the next query, 3. If we have more results, go to step 1 as mentioned by Karthik? For me, once the first 15 pages are retrieved and the max_id is set to the id of the last tweet of page 15, the results returned are not below that max_id. E.g. after first 15 pages, the last id is 1000 The first query (for the next 15 pages) would be something like http://&max_id=1000&since_id=100&page=1 The ids returned would still be greater than 1000 and it's as though the max_id is ignored Any idea why? Is it because the limit has been reached for max_id ? ** The id quoted are just sample values, the realistic number is way higher. On Mar 10, 4:45 pm, Doug Williams wrote: > Nish, > The way I read your question, it sounds like you are trying to use the > max_id parameter incorrectly. max_id allows you to specify the maximum > status id to return. It is the way to limit the results to statuses before a > given status id. It is complementary to the since_id parameter, capping the > results of a query at the top of the result list where since_id closes the > bottom. > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Tue, Mar 10, 2009 at 7:20 PM, nish wrote: > > > Hi, > > > Were you able to get more than 1500 tweets using the max_id method? > > > I somehow cannot get it. I am using the search JSON API and whenever > > I set the max_id looks like the server resets it to something else. > > > Thanks. > > > On Feb 24, 11:59 am, Karthik wrote: > > > Please confirm, if the following is allowed? > > > > 1. Set rpp=100 and retrieve 15 pages search results by incrementing > > > the param 'page' > > > 2. Get the id of the last status on page 15 and set that as the max_id > > > for the next query > > > 3. If we have more results, go to step 1
[twitter-dev] Re: Bidirectional Twitter-to-email client thoughts
2009/3/11 Kelly Jones
>
> I think I mis-explained my twitter-to-email client idea earlier, so
> here are more details.
>
> % When I receive a friends_timeline message, it comes in from
> {tweet_...@twitter.xyz.com .
>
> % If I reply, I *must* provide twitter auth credentials (perhaps in
> my email headers), and my reply shows up as "@sender " with
> in_reply_to_status_id set to {tweet_id}.
>
> % When I compose an email to {us...@twitter.xyz.com,
> it gets posted
> as "@user ". Again, I *must* supply twitter credentials (no
> spammers allowed!)
>
> % Similar for incoming direct messages, except the message comes from
> {us...@direct.twitter.xyz.com if {user}
> is following me or
> {us...@twitter.xyz.com if the user's not.
>
> % When I email {us...@direct.twitter.xyz.com,
> it gets sent as a
> direct message to {user} *OR* bounces back if {user} isn't following
> me.
>
> % Minor: replies to me (/replies.json) maybe have an extra "X-Reply:
> Yes" header or something, so I can separate them from the general
> friends_timeline.
>
> I could probably hack something like this using Pine's sendmail-path
> setting and a Perl script, but has someone already invented this
> wheel?
So you're intending to have people's Twitter credentials flying around the
internet in plain text? Not the best of plans IMHO.
Why not have them register with your service using OAuth and associate an
email address with their account. You could also get them to enter a
passphrase which they'd have to put in the subject of emails they send you
to provide an extra bit of security.
Personally I think trying to apply an email interface to Twitter is like
trying to control a modern TV with a long stick. While it might be
interesting to develop I don't see any value to it.
Or maybe I've missed something.
-Stuart
--
http://stut.net/projects/twitter/
