[twitter-dev] Re: Twitter user picture sizes
We'd really like to see a fix for this too. Having a few hundred unexpectedly large images floating around is playing havoc with our memory usage. Regards, Andrew Maizels PeopleBrowsr On Mar 26, 2:53 pm, Jason Schroeder jasch...@gmail.com wrote: Here is a 480x480 _normal image:http://s3.amazonaws.com/twitter_production/profile_images/108666778/I... Any progress on working with the UX team to resize these? TwitterBerry is expecting a 48x48-pixel image. Cheers, Jason TwitterBerry On Mar 24, 7:49 am, Shannon Whitley shannon.whit...@gmail.com wrote: Don't forget the _mini. :) This is my list: (original) _mini _normal _bigger On Feb 25, 12:15 am, Dave Briccetti da...@davebsoft.com wrote: Hi. I’ve searched around for 1/2 hour or so, and haven’t found an authoritative explanation of the sizes of pictures, and how to retrieve them. It seems that profile_image_url leads to a tiny picture: http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... But there is also a slighter bigger version: http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... And then a proper full-sizeone: http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... Am I correct in this? That the big version URL can be derived from that in profile_image_url by dropping the _normal from the name? Is this part of the API spec? Safe to use? Thanks.
[twitter-dev] Re: How can I automatically retweet from a list of followed accounts?
Also be aware that auto Retweeting may not work as well as you expect because of 140 char limits. adding RT @username may trim off some chars at the end of tweet. It's pretty hard to implement a program to condense long tweets to fit 140 chars On Mar 27, 4:33 pm, Jim mccoy@gmail.com wrote: I'm a complete newbie, so apologies if this isn't an appropriate forum for my question. I would like to set up a Twitter account that automatically retweets the tweets from a list of followed accounts. (I hope that makes sense.) The idea is that a group of people chimes in on a specific topic, and their tweets will be rebroadcast to any and all that are following the main account, but there's administrative control to stop following anyone who behaves badly. This presupposes that the followed accounts would be dedicated, i.e. set up solely for the purpose of twittering to the main account about the topic. Is this sort of thing allowed on Twitter? Are there tools to help, or is there a straightforward solution without tools? Thanks for anything you've got... Jim
[twitter-dev] Re: social graph methods with a bit more info
On Sun, Mar 29, 2009 at 11:41 PM, Damon Clinkscales sca...@pobox.comwrote: How often does this cache update? I'm curious how accurate and reliable this would be, since people are constantly modifying their social graph. In the case of the id/screen_name thing, the data wouldn't change much. Ideally, there'd be a way of forcing an update from Twitter in the case of known/suspected stale data. As to keeping up with the social graph, I think the current social graph methods are sufficient/wonderful for that. Ah, okay - so it's not necessarily a grab of the social graph then, but rather a user cache. If that's what it is I have a similar-sized cache, assuming Twitter were to start allowing this, I could make available as well. I'd be really surprised if they started to allow this though. Although there is still the problem of keeping the data up-to-date. People change their images, location, description, Tweets, number of followers/friends, etc. quite often. I think Twitter could provide a cache of this data a lot faster than they could provide a way to easily force updates on stale data. It sure would be nice though - I wouldn't have to make as many calls out to Twitter if they had a better way to get just the user updates. Jesse
[twitter-dev] Re: Using max_id to navigate to pages after 15
Hi I am Alos facing the same problem. If any one knows the solution please tell me. i too tried max_id with since_id. when i try with max_id only i got tweets correctly as karthik said. but when i tried max_id with since_id , the response seems that the api is ignoring max_id when given with since_id. On Mar 11, 7:10 pm, Ronnie ronniel...@gmail.com wrote: Hi Matt, The bug has been logged over at:http://code.google.com/p/twitter-api/issues/detail?id=342colspec=ID%... Thanks for replying and looking into it. On Mar 11, 9:29 am, Matt Sanford m...@twitter.com 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=allrpp=100since_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 nish.par...@gmail.com 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 m...@twitter.com 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=1000since_id=100page=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 d...@twitter.com 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 nish.par...@gmail.com 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 fermis...@gmail.com 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 nish.par...@gmail.com 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
[twitter-dev] Re: first try
Hi. Thanks. Well I tried it from a shared server. I got some success
but then I added
httpRequest('twitter.com');
echo pResponse:br /hr /pre$response/prehr //pn;
httpRequest('twitter.com', '/statuses/update.xml?status=I am testing
the Twitter API', 'POST');
echo pResponse:br /hr /pre$response/prehr //pn;
httpRequest('twitter.com', '/statuses/update.xml?status=Test+Test
+1+2+3!', 'POST');
echo pResponse:br /hr /pre$response/prehr //pn;
just underneath the line: //!-- Replace the following code for later
examples from the article --
but it does not seem to write to my account.
Also, the webpage takes a long time to load (about 90 secs) and then
shows
Contacting Twitter...
n
Response:
n
Response:
n
Response:
n
with three sets of two horizontal lines.
Any idea why it is not writing to my account?
Thanks!
On Mar 30, 12:11 pm, Ed Finkler funkat...@gmail.com wrote:
Okay, first off, the Fatal error is happening because PHP on your
install is set-up to time-out scripts after 60 seconds (this is to
avoid runaway processes on the server).
I'm not sure exactly why your socket connection is timing out. One
possibility is that a local firewall is blocking outgoing connections
until you explicitly allow them.
I'd recommend installing a Windows binary of curl for testing on the
command line, and also grabbing a copy of the Charles debugging proxy
to see what's actually being sent and received (if anything!).
--
Ed Finklerhttp://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com
On Mar 29, 10:37 pm, Bill william...@gmail.com wrote:
Hi, I tried to access the twitter API with the following code but I
get the error:
Contacting Twitter...
n
Fatal error: Maximum execution time of 60 seconds exceeded in C:\xampp
\htdocs\twitter.php on line 26
I am running this from an apache server on my home computer
at:http://127.0.0.1/twitter.php
I have not applied for any special account with twitter, just my
regular twitter id and password were entered. Can anyone tell me why
this is not working?
Thanks!
?php
$twitter_username = '';
$twitter_password = '';
$errno = 0;
$errstr = '';
$response = '';
function httpRequest($host, $path = '/', $method = 'GET') {
global $errno, $errstr, $response;
global $twitter_username, $twitter_password;
$header = $method $path HTTP/1.1rn;
$header .= Host: $hostrn;
$header .= Accept-Encoding: nonern;
$header .= Authorization: Basic . base64_encode
({$twitter_username}:{$twitter_password}) . rn;
$header .= Connection: Closernrn;
$sock = fsockopen($host, 80, $errno, $errstr, 30);
if (!$sock) {
die(pstrongfsockopen() error:/strongbr /$errstr ($errno)
/p);
} else {
fwrite($sock, $header);
while (!feof($sock)) {
$response .= fgets($sock, 128);
}
fclose($sock);
$response = trim(str_replace(array('', ''), array('lt;',
'gt;'), $response));
return true;
}
}
echo pContacting Twitter.../pn;
//!-- Replace the following code for later examples from the article
--
httpRequest('twitter.com');
echo pResponse:br /hr /pre$response/prehr //pn;
?
[twitter-dev] Re: social graph methods with a bit more info
You can always provide your own cache. It doesn't take that much to get a complete name-ID cache locally. What does take a lot of calls is keeping it up-to-date. Since you can change names on ID's it's not always accurate (though the ID never changes). It's a huge task to get that initial scrape, takes about 2 months depending on your access, but it's doable. If we could make more calls per hour you could significantly cut that time, or if twitter made just that information available in a fire- hose format where you could suck down the entire list at once. It'll be a big file, there's almost 30 million user IDs now. On Mar 29, 4:38 pm, Jesse Stay jesses...@gmail.com wrote: If Twitter's going to allow this, why don't they just do it themselves and provide more accurate and up-to-date info? How often does this cache update? I'm curious how accurate and reliable this would be, since people are constantly modifying their social graph. Alex and crew have already said they might be able to provide more info once they fully convert over to their new architecture. My hope is that once they're able to do that I can just pull subsets of each social graph down, such as number of new followers since x date, or other criteria. A FQL-type language (similar to Facebook's) would be ideal for something like that. Jesse On Sun, Mar 29, 2009 at 1:03 PM, softprops d.tang...@gmail.com wrote: Wow! What a great idea. Offloading the burden on twitter's servers/dbs to a simple id-name cache hosted via another service on someone elses. I will have to check that out. On Mar 29, 2:52 pm, Damon Clinkscales sca...@pobox.com wrote: On Sat, Mar 28, 2009 at 11:47 PM, Damon Clinkscales sca...@pobox.com wrote: see On Sat, Mar 28, 2009 at 9:16 PM, softprops d.tang...@gmail.com wrote: It would be nice if thehttp:// twitter.com/[friends|followers]/ids.format uri's could return a bit more useful info like the screen_name. [ snip ] ... ?xml version=1.0 encoding=UTF-8? ids id screen_name=foo1/id id screen_name=bar2/id /ids They aren't going to do this for performance reasons, even though yes, it would be useful. seehttp://is.gd/ptJ9 -damon An alternative solution may be possible though. I've recently been reminded that @infochimps has a massive scrape of the Twitter social graph and is willing to make that available, in whole or in part. However, they are currently awaiting Twitter's permission on precisely what can be released. You can read more about this here - http://blog.infochimps.org/2008/12/29/massive-scrape-of-twitters-frie... Assuming that the data is released, even in a limited form, there is potential there for an id--screen_name mapping table which could serve as a cache primer for apps that need that. This could potentially save a bajillion calls against Twitter's API, which in turn would have other good effects. One of the most notable places where this is obviously needed is tying Twitter Search results to Twitter users. For historical reasons, the user id in the search result is not the Twitter user_id, so you have to use the screen name. -damon --http://twitter.com/damon
[twitter-dev] Generate random Twitter poems
This script generates random Twitter poems: http://intrinsitivity.com/tweets/poems.php It grabs the public timeline in JSON format and uses JavaScript, mostly jQuery, to filter (3 tweets, 42 chars max) and append #poem to the end. Results range from pretty funny to outright incomprehensible. Just wanted to share :o)
[twitter-dev] Re: social graph methods with a bit more info
On Mar 30, 3:32 am, Jesse Stay jesses...@gmail.com wrote: On Sun, Mar 29, 2009 at 11:41 PM, Damon Clinkscales sca...@pobox.comwrote: How often does this cache update? I'm curious how accurate and reliable this would be, since people are constantly modifying their social graph. In the case of the id/screen_name thing, the data wouldn't change much. Ideally, there'd be a way of forcing an update from Twitter in the case of known/suspected stale data. As to keeping up with the social graph, I think the current social graph methods are sufficient/wonderful for that. Ah, okay - so it's not necessarily a grab of the social graph then, but rather a user cache. If that's what it is I have a similar-sized cache, assuming Twitter were to start allowing this, I could make available as well. I'd be really surprised if they started to allow this though. Although there is still the problem of keeping the data up-to-date. People change their images, location, description, Tweets, number of followers/friends, etc. quite often. I think Twitter could provide a cache of this data a lot faster than they could provide a way to easily force updates on stale data. It sure would be nice though - I wouldn't have to make as many calls out to Twitter if they had a better way to get just the user updates. I think that is the point/trade off. What is the real cost to twitter of developers making more calls for small chunks of data vs. less calls for a bit more custom set of data? It's less http traffic but a bigger payload. I guess it also depends on how the data is cached. As Alex mentioned in the link above As they are, we fetch data from a single data store in our architecture to return the lists of IDs. In order to provide usernames, we'd have to bog down this request by joining together multiple sources of data. It would require a bit or rearchitecting on their part before I think we see a compromise being made. The major difficulty again maintaining the freshness of data with users changing their screen names among other things. Probably easier said than done. It would be great if twitter did start opening up the caching of user data to other services and perhaps provide web hooks that get fired when that external services cache should be updated. Jesse
[twitter-dev] Some profile images are PNG, but reported as JPGs
A number of profile images (http://twitter.com/wootshirt is a good example. I'd give the exact URL, but it keeps changing...) have a URL that indicates it's a JPG (ends in .jpg) and a returned Content-type of image/jpeg, but are in fact PNGs. This is fine for browsers, as they work around this sort of brokenness, but then my client gets confused when trying to load what it thinks is a JPG and thinks it's invalid, when it's in fact just badly named. Now, I'm going through the process of fixing said client, but if Twitter could do this properly on their end, it would be most helpful Tom Parker
[twitter-dev] Re: OAuth authorization page formatted for iPhone/Pod?
Hi all, I think I mentioned it the end of last week, but perhaps not. I'm working on the mobile pages since it was one of the beta-isms surrounding OAuth. There is no ETA yet but it's being worked on. Thanks; — Matt Sanford On Mar 30, 2009, at 04:51 AM, dean.j.robinson wrote: Thumbs up :) I was thinking about the same thing, just hadn't gotten around to ticketing, given the number of iphone//mobile related apps, it would be appreciated by many I think. On Mar 30, 5:50 am, Chad Etzel jazzyc...@gmail.com wrote: Hi Guys, I have opened a code issue here:http://code.google.com/p/twitter-api/issues/detail?id=395 It would be very handy if the Twitter OAuth Authorization page was formatted in an iPhone/Pod friendly manner so users don't have to zoom way in to read the text and enter their information. This will enhance the usability and flow of apps authenticating on iPhone/Pod. I tried to search for similar issues, but found none... so please forgive me if this is in the works or I missed something. Thanks, -Chad
[twitter-dev] Re: Can we make this a private list?
On Mon, Mar 30, 2009 at 8:58 AM, Clint Shryock cts...@gmail.com wrote: How then would you propose acceptance to this group is determined? I don't know, that's why I'm asking. I've never admin'd a google group before. I think it's in Twitter's best interest to allow information on their API for new developers as accessible as possible to build their platform. This list is a great resource in accomplishing that. In my opinion you should have contacted people from this list you've had interactions with privately and shown them in that manner. Otherwise, I would have solicited people interested in screening an app. That, of course, is an option, but getting responses to anything posted here is a total crapshoot, and sending a message to a subset of those people makes chances for a response even worse. I'd rather send a message to the group since that's what it is for, without fear of having it be spread all over the place. Maybe that's not possible, and I can deal with that. Anyway, it was just a suggestion/question. Maybe it's not feasible. If not, then nevermind :) -chad
[twitter-dev] Twitter API with WCF
I am working on a wpf twitter client that talks to the twitter api with wcf. My experience had been pretty good so far and had not run into a lot of issues. However, I just realized that the status/update method in the twitter api does not support the source parameter. I've looked at a number of other open source twitter client and found out they construct the post requests manually with a source parameter and uses the HttpWebRequest class to make the request. Is there any way to specify the source parameter for status/update in wcf?
[twitter-dev] Re: Twitter API with WCF
Hi Leo, The update method should take a source parameter, but you have to register one first. Check out http://apiwiki.twitter.com/FAQ#INeedSomething Thanks; — Matt Sanford / @mzsanford On Mar 30, 2009, at 08:04 AM, leo wrote: I am working on a wpf twitter client that talks to the twitter api with wcf. My experience had been pretty good so far and had not run into a lot of issues. However, I just realized that the status/update method in the twitter api does not support the source parameter. I've looked at a number of other open source twitter client and found out they construct the post requests manually with a source parameter and uses the HttpWebRequest class to make the request. Is there any way to specify the source parameter for status/update in wcf?
[twitter-dev] Re: Some profile images are PNG, but reported as JPGs
Tom, There is a feature that has been requested that will provide permanent URLs for profile images [1]. However, your issue sounds different. If you don't feel that the issue linked below meets your needs, can you please create a new issue so we can track this? 1. http://code.google.com/p/twitter-api/issues/detail?id=242 Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 2:29 AM, Tom Parker palf...@gmail.com wrote: A number of profile images (http://twitter.com/wootshirt is a good example. I'd give the exact URL, but it keeps changing...) have a URL that indicates it's a JPG (ends in .jpg) and a returned Content-type of image/jpeg, but are in fact PNGs. This is fine for browsers, as they work around this sort of brokenness, but then my client gets confused when trying to load what it thinks is a JPG and thinks it's invalid, when it's in fact just badly named. Now, I'm going through the process of fixing said client, but if Twitter could do this properly on their end, it would be most helpful Tom Parker
[twitter-dev] Re: Can we make this a private list?
Chad: what you state IS quite desirable, but is, unfortunately, equally not feasible. You can moderate join requests, you can moderate members' posts, but the distinction you seem to be looking for in your original email is near-impossible to establish. Perhaps membership to the list should be predicated on assignment of a source parameter, and detection of that parameter being in-use? (This would cut off a lot of casual or tangential looky-loos ... not unlike myself, who either haven't had need to apply, or have applied and simply haven't used. It could be a decent yardstick ... but then you have people doing widgets and other integrations, who may never need a source param ...) On Mon, Mar 30, 2009 at 11:42 AM, Chad Etzel jazzyc...@gmail.com wrote: On Mon, Mar 30, 2009 at 8:58 AM, Clint Shryock cts...@gmail.com wrote: How then would you propose acceptance to this group is determined? I don't know, that's why I'm asking. I've never admin'd a google group before. I think it's in Twitter's best interest to allow information on their API for new developers as accessible as possible to build their platform. This list is a great resource in accomplishing that. In my opinion you should have contacted people from this list you've had interactions with privately and shown them in that manner. Otherwise, I would have solicited people interested in screening an app. That, of course, is an option, but getting responses to anything posted here is a total crapshoot, and sending a message to a subset of those people makes chances for a response even worse. I'd rather send a message to the group since that's what it is for, without fear of having it be spread all over the place. Maybe that's not possible, and I can deal with that. Anyway, it was just a suggestion/question. Maybe it's not feasible. If not, then nevermind :) -chad
[twitter-dev] Re: Can we make this a private list?
Chad, A number of people have asked on- and off- list where they should display their app and ask for feedback. Do you think that a separate group for feedback and suggestions for workable apps would be beneficial? Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 10:02 AM, Andrew Badera and...@badera.us wrote: Chad: what you state IS quite desirable, but is, unfortunately, equally not feasible. You can moderate join requests, you can moderate members' posts, but the distinction you seem to be looking for in your original email is near-impossible to establish. Perhaps membership to the list should be predicated on assignment of a source parameter, and detection of that parameter being in-use? (This would cut off a lot of casual or tangential looky-loos ... not unlike myself, who either haven't had need to apply, or have applied and simply haven't used. It could be a decent yardstick ... but then you have people doing widgets and other integrations, who may never need a source param ...) On Mon, Mar 30, 2009 at 11:42 AM, Chad Etzel jazzyc...@gmail.com wrote: On Mon, Mar 30, 2009 at 8:58 AM, Clint Shryock cts...@gmail.com wrote: How then would you propose acceptance to this group is determined? I don't know, that's why I'm asking. I've never admin'd a google group before. I think it's in Twitter's best interest to allow information on their API for new developers as accessible as possible to build their platform. This list is a great resource in accomplishing that. In my opinion you should have contacted people from this list you've had interactions with privately and shown them in that manner. Otherwise, I would have solicited people interested in screening an app. That, of course, is an option, but getting responses to anything posted here is a total crapshoot, and sending a message to a subset of those people makes chances for a response even worse. I'd rather send a message to the group since that's what it is for, without fear of having it be spread all over the place. Maybe that's not possible, and I can deal with that. Anyway, it was just a suggestion/question. Maybe it's not feasible. If not, then nevermind :) -chad
[twitter-dev] Re: help me out, por favor
Peter, I'm a little confused as to what you are looking for from a support point of view here. What exactly is your question regarding the TOS and how can I help? Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Sun, Mar 29, 2009 at 3:43 PM, Peter Denton petermden...@gmail.comwrote: Hello, Doing a research report - information wont be sold - no names will be used - just for edification.* I'm being serious*, I just some honest answers to help me with something. If this is a TOS violation, I searched and didnt see anything, so not trying to make lex, doug, and matt upset. Please take one second to just answer inline if you don't mind. I have cc'd myself or so you can replay out of the group, or if it doesnt come through, my email is petermden...@gmail.com *Have you developed a twitter application? *yes [ ] no [ ]* How many apps have you developed? **Have you developed a iPhone application? *yes [ ] no [ ]* * [ ] yes, its the same app* * *What is your development platform? ** Is it your business/hobby? Is your goal to make it a business? **How do you communicate with other twitter developers? *this list [ ] email [ ]* * chat [ ] i dont [ ]* **have you had any frustrations along the way?* * * * * * *
[twitter-dev] Re: direct_messages since_id parameter doesn't work
Ben, I can see the same problem. There is now an open issue for this problem [1]. 1. http://code.google.com/p/twitter-api/issues/detail?id=399 Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson ben.burle...@gmail.comwrote: I use this URL: http://twitter.com/direct_messages.xml?since_id=82528092 The result includes the message with that ID (when it should only include messages AFTER that ID) AND previous messages. This is very broken. Should I abandon it and just use the since parameter (as date)? If so, fix the API doc!!!1 Cheers, Ben
[twitter-dev] Re: direct_messages since_id parameter doesn't work
Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time. -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams d...@twitter.com wrote: Ben, I can see the same problem. There is now an open issue for this problem [1]. 1.http://code.google.com/p/twitter-api/issues/detail?id=399 Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson ben.burle...@gmail.comwrote: I use this URL: http://twitter.com/direct_messages.xml?since_id=82528092 The result includes the message with that ID (when it should only include messages AFTER that ID) AND previous messages. This is very broken. Should I abandon it and just use the since parameter (as date)? If so, fix the API doc!!!1 Cheers, Ben
[twitter-dev] Re: Twitter user picture sizes
It's one of our top issues right now. On Sun, Mar 29, 2009 at 23:05, Andrew Maizels andrew.maiz...@gmail.com wrote: We'd really like to see a fix for this too. Having a few hundred unexpectedly large images floating around is playing havoc with our memory usage. Regards, Andrew Maizels PeopleBrowsr On Mar 26, 2:53 pm, Jason Schroeder jasch...@gmail.com wrote: Here is a 480x480 _normal image:http://s3.amazonaws.com/twitter_production/profile_images/108666778/I... Any progress on working with the UX team to resize these? TwitterBerry is expecting a 48x48-pixel image. Cheers, Jason TwitterBerry On Mar 24, 7:49 am, Shannon Whitley shannon.whit...@gmail.com wrote: Don't forget the _mini. :) This is my list: (original) _mini _normal _bigger On Feb 25, 12:15 am, Dave Briccetti da...@davebsoft.com wrote: Hi. I’ve searched around for 1/2 hour or so, and haven’t found an authoritative explanation of the sizes of pictures, and how to retrieve them. It seems that profile_image_url leads to a tiny picture: http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... But there is also a slighter bigger version: http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... And then a proper full-sizeone: http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... Am I correct in this? That the big version URL can be derived from that in profile_image_url by dropping the _normal from the name? Is this part of the API spec? Safe to use? Thanks. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Can we make this a private list?
On Mon, Mar 30, 2009 at 1:02 PM, Andrew Badera and...@badera.us wrote: Chad: what you state IS quite desirable, but is, unfortunately, equally not feasible. You can moderate join requests, you can moderate members' posts, but the distinction you seem to be looking for in your original email is near-impossible to establish. Perhaps membership to the list should be predicated on assignment of a source parameter, and detection of that parameter being in-use? (This would cut off a lot of casual or tangential looky-loos ... not unlike myself, who either haven't had need to apply, or have applied and simply haven't used. It could be a decent yardstick ... but then you have people doing widgets and other integrations, who may never need a source param ...) In my case, I just started developing using twitters api. I came here to ask you guys questions for help. I have no app in production so I can't refer anyone to a particular project. I came here so seek info. I'd feel put off if I couldn't learn anything just because I haven't built anything with twitters api before. Thats kind of a catch22. On Mon, Mar 30, 2009 at 11:42 AM, Chad Etzel jazzyc...@gmail.com wrote: On Mon, Mar 30, 2009 at 8:58 AM, Clint Shryock cts...@gmail.com wrote: How then would you propose acceptance to this group is determined? I don't know, that's why I'm asking. I've never admin'd a google group before. I think it's in Twitter's best interest to allow information on their API for new developers as accessible as possible to build their platform. This list is a great resource in accomplishing that. In my opinion you should have contacted people from this list you've had interactions with privately and shown them in that manner. Otherwise, I would have solicited people interested in screening an app. That, of course, is an option, but getting responses to anything posted here is a total crapshoot, and sending a message to a subset of those people makes chances for a response even worse. I'd rather send a message to the group since that's what it is for, without fear of having it be spread all over the place. Maybe that's not possible, and I can deal with that. Anyway, it was just a suggestion/question. Maybe it's not feasible. If not, then nevermind :) -chad
[twitter-dev] Re: Can we make this a private list?
Doug, This forum is the appropriate place to bring up questions about the API, regardless if you have an application in development. Therefore, please don't feel like you cannot speak up just because you don't have code you can show off. Chances are if you have a question, so do other developers. All we ask is that you check the FAQ and search the archives of this group before posting a new topic. Cheers, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 12:28 PM, Doug Tangren d.tang...@gmail.com wrote: On Mon, Mar 30, 2009 at 1:02 PM, Andrew Badera and...@badera.us wrote: Chad: what you state IS quite desirable, but is, unfortunately, equally not feasible. You can moderate join requests, you can moderate members' posts, but the distinction you seem to be looking for in your original email is near-impossible to establish. Perhaps membership to the list should be predicated on assignment of a source parameter, and detection of that parameter being in-use? (This would cut off a lot of casual or tangential looky-loos ... not unlike myself, who either haven't had need to apply, or have applied and simply haven't used. It could be a decent yardstick ... but then you have people doing widgets and other integrations, who may never need a source param ...) In my case, I just started developing using twitters api. I came here to ask you guys questions for help. I have no app in production so I can't refer anyone to a particular project. I came here so seek info. I'd feel put off if I couldn't learn anything just because I haven't built anything with twitters api before. Thats kind of a catch22. On Mon, Mar 30, 2009 at 11:42 AM, Chad Etzel jazzyc...@gmail.com wrote: On Mon, Mar 30, 2009 at 8:58 AM, Clint Shryock cts...@gmail.com wrote: How then would you propose acceptance to this group is determined? I don't know, that's why I'm asking. I've never admin'd a google group before. I think it's in Twitter's best interest to allow information on their API for new developers as accessible as possible to build their platform. This list is a great resource in accomplishing that. In my opinion you should have contacted people from this list you've had interactions with privately and shown them in that manner. Otherwise, I would have solicited people interested in screening an app. That, of course, is an option, but getting responses to anything posted here is a total crapshoot, and sending a message to a subset of those people makes chances for a response even worse. I'd rather send a message to the group since that's what it is for, without fear of having it be spread all over the place. Maybe that's not possible, and I can deal with that. Anyway, it was just a suggestion/question. Maybe it's not feasible. If not, then nevermind :) -chad
[twitter-dev] Re: Coldfusion Twitter status posting help
Fair enough. I did see the basic authentication mention in the wiki guide. I can parse together the username:password and put it into base64...I just don't know how to pass that to Twitter. Do you know where I can find an example online? I've looked and found examples like I posted above that seem to work for others...just not working for me it seems. I wonder if there's an issue with odd characters being in the password? I have a single character that's not alphanumeric...I wonder if that could be it? On Mar 30, 10:41 am, Matt Sanford m...@twitter.com wrote: Hi there, I don't know CF, but it looks like you're passing username and password as form fields. You need to use HTTP Basic authentication and only pass in status as a parameter. Thanks; — Matt Sanford / @mzsanford On Mar 29, 2009, at 11:32 AM, Craig328 wrote: I've been banging my head on this issue for the past 3-4 days to the point that my skull has attained a soggy, squishy quality...so any help would be most appreciated. I have a Twitter account that I want to post simple periodic updates to from a website I own. I can successfully do this: cfhttp url=http://twitter.com/account/verify_credentials.xml; method=get username=#variables.Tusername# password=#variables.Tpassword# That works everytime. However, this does not work: cfhttp url=http://twitter.com/statuses/update.xml; method=POST username=#variables.Tusername# password=#variables.Tpassword# charset=UTF-8 cfhttpparam type=FORMFIELD name=user value=#variables.Tusername# cfhttpparam type=FORMFIELD name=password value=#variables.Tpassword# cfhttpparam type=FORMFIELD name=status value=#variables.Tstatus# /cfhttp Not just that but any variation of the post to update.xml fails and the fail reason is: Could not authenticate you. I've tried it in just about every combination I can think of. I've scoured Twitter's API docs, Google and everywhere in between and can't get this to go. I'm hoping someone can point me in the right direction. This seems a really simply thing but it's driving me to distraction. I don't believe there's a setting in Twitter itself that is causing the issue...but perhaps I'm wrong. Any help/assistance would be most welcome and appreciated. Thanks in advance.
[twitter-dev] Re: Using max_id to navigate to pages after 15
Maybe I'm not getting it, but from Search API documentation page, I don't see max_id as an available parameter. was it added recently? On Mar 11, 2:34 am, ronin ronniel...@gmail.com 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=1000since_id=100page=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 d...@twitter.com 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 nish.par...@gmail.com 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 fermis...@gmail.com 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: TweetGrid for iPhone - please test
You might consider letting people using desktop Safari/WebKit use it anyway. I can imagine people using it as a Fluid app. On Sun, Mar 29, 2009 at 14:04, Chad Etzel jazzyc...@gmail.com wrote: Hi All, I have created a TweetGrid native webapp for iPhone/Pod. The native is in quotes because it's not truly a native app (as in, you can't get it from the app store), but it was developed with the iWebKit.net framework and is pretty convincing in its look and feel. If you haven't seen iWebKit.net before, go check it out (or goto http://iwebkit.mobi on your iphone). Anyone with an iPhone/Pod can test this out. Just point iPhone Safari to http://tweetgrid.com/iphone/ (sorry, not going to work in other browsers) Here's the native part: If you use the + sign and hit Add to Home Screen it will create a launcher for the site/app that puts Safari in stand-alone fullscreen mode. When launching it from the homescreen, you won't see the safari address bar or the navigation/bookmark buttons at the bottom. Current Features of TweetGrid for iPhone: - Real-time auto-updates of Twitter Search results - Multiple account authorization through OAuth - authorize as many accounts as you want under the main screen Settings arrow - this is the only clunky part b/c Twitter's OAuth page is not optimized for mobile (yet). - Tweet from the results page - Click the Tweet button in the top right title bar - Choose any of your authorized accounts to send the tweet - Save your searches for quick access from the home screen - See and search current Trending Topics - Sticky Settings for: - Auto update - on/off - Refresh Interval - 10 to 60 seconds - Show Avatars - on/off (handy for EDGE/slow connection) - Show TwitPic thumbnails - on/off (just for fun...) - These settings persist for each new search Please try it out and let me know what you think. I haven't announced this publicly to anyone yet, so if you are inclined to tell other people about it, please hold off for now. I would like to get some feedback from other devs first. Thanks! -Chad -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: public_timeline, invalid profile_image?
We're on this. Thanks for the reports. On Sun, Mar 29, 2009 at 18:27, Gary Zhao garyz...@gmail.com wrote: I'm seeing it too. 2009/3/29 Günter Grodotzki guen...@grodotzki.ph since some days I am always getting: http://static.twitter.com/images/default_profile_normal.png as profile-image from the user via public-timeline (Data-mining-feed). I checked the announcement-google-group + twitter.com/twitterapi (subscribed to feed anyway ;) ) but could not see any change. The site affected: www.geoheartbeat.com -- Gary http://twitter.com/garyzhao -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Can we make this a private list?
On Mon, Mar 30, 2009 at 1:38 PM, Doug Williams d...@twitter.com wrote: Chad, A number of people have asked on- and off- list where they should display their app and ask for feedback. Do you think that a separate group for feedback and suggestions for workable apps would be beneficial? If there was a group of people that would be willing to actively participate in such a group, then I think it would be a valuable thing. imho, the value of a group/list is in the amount of response or discussion that is generated by the posts. Right now asking for feedback on apps (for example) is extremely hit-or-miss. As an example: my post yesterday asking for testers/feedback on my iphone webapp did generate some traffic (from my analytics I saw that at least 20 people went to try it out), but only 1 person sent a reply to that thread (publicly or privately). This is just a personal example as a data-point, I'm not whining or having a self-pity party... so turn off your flamethrowers. If there were a separate list where people were willing and able to test apps and give feedback to people before publicly launching something, that could be really helpful. However, I know the perception of creating a separate private list will probably be negative and seen as creating a clique or something, but for the people that are always hanging around these boards I think they would appreciate it. How would you decide who to give membership to? I dunno... again, I know there's not an easy answer. The way I see it now (or at least in the recent past), this board has been mainly used for asking how to get a source parameter, basic how-to-get-started type questions, and reporting twitter service outages or glitches that the twitter team are probably already painfully aware of. I know there are others that feel the same way, and I'm not alone. I'm not saying these are bad or unworthy topics, I think I have been helpful in answering a fair share of getting started questions b/c it's important to grow the community. I just think it would be nice to have a placed for deeper, more focused discussion for the active 3rd party developers out there. Maybe that's pie in the sky, who knows... I'm not trying to start factions here... maybe I didn't phrase my initial question correctly carry on, -Chad
[twitter-dev] DM since_id does not work!
request messages with since_id attribute returns old messages: request new messages since 82395201 Get new message: 73801853 Get new message: 74232720 Account: http://twitter.com/t411
[twitter-dev] Re: Coldfusion Twitter status posting help
check out this JSP taglib: http://www.servletsuite.com/servlets/twittertag.htm you can use it in CF as well On Mar 29, 10:32 pm, Craig328 craig...@gmail.com wrote: I've been banging my head on this issue for the past 3-4 days to the point that my skull has attained a soggy, squishy quality...so any help would be most appreciated. I have a Twitter account that I want to post simple periodic updates to from a website I own. I can successfully do this: cfhttp url=http://twitter.com/account/verify_credentials.xml; method=get username=#variables.Tusername# password=#variables.Tpassword# That works everytime. However, this does not work: cfhttp url=http://twitter.com/statuses/update.xml; method=POST username=#variables.Tusername# password=#variables.Tpassword# charset=UTF-8 cfhttpparam type=FORMFIELD name=user value=#variables.Tusername# cfhttpparam type=FORMFIELD name=password value=#variables.Tpassword# cfhttpparam type=FORMFIELD name=status value=#variables.Tstatus# /cfhttp Not just that but any variation of the post to update.xml fails and the fail reason is: Could not authenticate you. I've tried it in just about every combination I can think of. I've scoured Twitter's API docs, Google and everywhere in between and can't get this to go. I'm hoping someone can point me in the right direction. This seems a really simply thing but it's driving me to distraction. I don't believe there's a setting in Twitter itself that is causing the issue...but perhaps I'm wrong. Any help/assistance would be most welcome and appreciated. Thanks in advance.
[twitter-dev] Re: DM since_id does not work
This is a known issue [1] and we're working on it right now. Thanks; — Matt Sanford [1] - http://code.google.com/p/twitter-api/issues/detail?id=399 On Mar 30, 2009, at 01:02 PM, Abava wrote: request messages with since_id attribute returns old messages: request new messages since 82395201 Get new message: 73801853 Get new message: 74232720 Account: http://twitter.com/t411
[twitter-dev] Re: direct_messages since_id parameter doesn't work
Wondering if you possibly broke some sort of ActiveResource (Rails) compatibility here? My call, which worked just fine this morning and the past 12 months, now fails with a 400 Bad Request. DirectMessage.find(:all) Thanks, -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:13 pm, Doug Williams d...@twitter.com wrote: All, This is being looked into as I type. Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 12:09 PM, bjhess bjh...@gmail.com wrote: Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time. -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams d...@twitter.com wrote: Ben, I can see the same problem. There is now an open issue for this problem [1]. 1.http://code.google.com/p/twitter-api/issues/detail?id=399 Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson ben.burle...@gmail.com wrote: I use this URL: http://twitter.com/direct_messages.xml?since_id=82528092 The result includes the message with that ID (when it should only include messages AFTER that ID) AND previous messages. This is very broken. Should I abandon it and just use the since parameter (as date)? If so, fix the API doc!!!1 Cheers, Ben
[twitter-dev] Re: DM since_id does not work!
Please search the groups and the Current Issues... they are working on this now. On Mon, Mar 30, 2009 at 4:02 PM, Abava dnam...@gmail.com wrote: request messages with since_id attribute returns old messages: request new messages since 82395201 Get new message: 73801853 Get new message: 74232720 Account: http://twitter.com/t411
[twitter-dev] Re: DM since_id does not work!
This is a dupe of the same topic that is currently on the front page [1]. Please remember to search before posting. 1. http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e0b6e371409b00b Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 1:02 PM, Abava dnam...@gmail.com wrote: request messages with since_id attribute returns old messages: request new messages since 82395201 Get new message: 73801853 Get new message: 74232720 Account: http://twitter.com/t411
[twitter-dev] Re: How do I acquire the twitter data mining feeds
Richard,
Can you please contact me off list as this seems like an individual issue
rather than a group problem: doug {at} twitter [dot] com
Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Mon, Mar 30, 2009 at 1:00 PM, Richard richard.rui@gmail.com wrote:
I read the FAQ part in Twitter API site, and filled the form. But it
seems it doesn't work. I still get 20 results per request. Can anyone
tell me how to get the data mining feeds?
[twitter-dev] Re: direct_messages since_id parameter doesn't work
Nevermind … rate limit. ~Barry On Mar 30, 3:06 pm, bjhess bjh...@gmail.com wrote: Wondering if you possibly broke some sort of ActiveResource (Rails) compatibility here? My call, which worked just fine this morning and the past 12 months, now fails with a 400 Bad Request. DirectMessage.find(:all) Thanks, -- Barryhttp://iridesco.comhttp://bjhess.com On Mar 30, 2:13 pm, Doug Williams d...@twitter.com wrote: All, This is being looked into as I type. Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 12:09 PM, bjhess bjh...@gmail.com wrote: Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time. -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams d...@twitter.com wrote: Ben, I can see the same problem. There is now an open issue for this problem [1]. 1.http://code.google.com/p/twitter-api/issues/detail?id=399 Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson ben.burle...@gmail.com wrote: I use this URL: http://twitter.com/direct_messages.xml?since_id=82528092 The result includes the message with that ID (when it should only include messages AFTER that ID) AND previous messages. This is very broken. Should I abandon it and just use the since parameter (as date)? If so, fix the API doc!!!1 Cheers, Ben
[twitter-dev] Re: TweetGrid for iPhone - please test
That's a good idea. I'm not a regular mac user, so I hadn't thought of that use-case. I'll try to relax the iphone-only magic later today. Thanks for the suggestion! -Chad On Mon, Mar 30, 2009 at 3:49 PM, Alex Payne a...@twitter.com wrote: You might consider letting people using desktop Safari/WebKit use it anyway. I can imagine people using it as a Fluid app. On Sun, Mar 29, 2009 at 14:04, Chad Etzel jazzyc...@gmail.com wrote: Hi All, I have created a TweetGrid native webapp for iPhone/Pod. The native is in quotes because it's not truly a native app (as in, you can't get it from the app store), but it was developed with the iWebKit.net framework and is pretty convincing in its look and feel. If you haven't seen iWebKit.net before, go check it out (or goto http://iwebkit.mobi on your iphone). Anyone with an iPhone/Pod can test this out. Just point iPhone Safari to http://tweetgrid.com/iphone/ (sorry, not going to work in other browsers) Here's the native part: If you use the + sign and hit Add to Home Screen it will create a launcher for the site/app that puts Safari in stand-alone fullscreen mode. When launching it from the homescreen, you won't see the safari address bar or the navigation/bookmark buttons at the bottom. Current Features of TweetGrid for iPhone: - Real-time auto-updates of Twitter Search results - Multiple account authorization through OAuth - authorize as many accounts as you want under the main screen Settings arrow - this is the only clunky part b/c Twitter's OAuth page is not optimized for mobile (yet). - Tweet from the results page - Click the Tweet button in the top right title bar - Choose any of your authorized accounts to send the tweet - Save your searches for quick access from the home screen - See and search current Trending Topics - Sticky Settings for: - Auto update - on/off - Refresh Interval - 10 to 60 seconds - Show Avatars - on/off (handy for EDGE/slow connection) - Show TwitPic thumbnails - on/off (just for fun...) - These settings persist for each new search Please try it out and let me know what you think. I haven't announced this publicly to anyone yet, so if you are inclined to tell other people about it, please hold off for now. I would like to get some feedback from other devs first. Thanks! -Chad -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: twitter in iframes
Not until the clickjacking problem is solved by the browser vendors. End of story. On Mon, Mar 30, 2009 at 14:31, Ryan ryan10...@gmail.com wrote: I can see that twitter recently has inserted a (graceful) iframe buster which clears out the html. Why is twitter in iframe such a bad thing when the content is public anyways - the rss feed of the content is available for consumption? I know about the clickjacking attack, but that unnecessarily penalizes the good applications. Any thoughts on allowing twitter pages in iframes through registered usage? -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: twitter in iframes
clickjacking does not really affect pages like http://twitter.com/britneyspears. whatever... I understand you got to protect yourself from misuse. On Mar 30, 5:38 pm, Alex Payne a...@twitter.com wrote: Not until the clickjacking problem is solved by the browser vendors. End of story. On Mon, Mar 30, 2009 at 14:31, Ryan ryan10...@gmail.com wrote: I can see that twitter recently has inserted a (graceful) iframe buster which clears out the html. Why is twitter in iframe such a bad thing when the content is public anyways - the rss feed of the content is available for consumption? I know about the clickjacking attack, but that unnecessarily penalizes the good applications. Any thoughts on allowing twitter pages in iframes through registered usage? -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Can we make this a private list?
What I would like to do is make the basic information much more accessible, which would ensure that the more fundamental questions are answered implicitly while the conversation can cultivate around more productive topics. The link to the FAQ doesn't curb the thrice weekly request for source parameter help, and there are a lot of requests that redundant. Do you guys have any suggestions to provide community newcomers a checklist of information they need to get started? Do you have any good examples of other communities that do it better? Well, maybe I just gave myself an idea there... Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 12:58 PM, Chad Etzel jazzyc...@gmail.com wrote: On Mon, Mar 30, 2009 at 1:38 PM, Doug Williams d...@twitter.com wrote: Chad, A number of people have asked on- and off- list where they should display their app and ask for feedback. Do you think that a separate group for feedback and suggestions for workable apps would be beneficial? If there was a group of people that would be willing to actively participate in such a group, then I think it would be a valuable thing. imho, the value of a group/list is in the amount of response or discussion that is generated by the posts. Right now asking for feedback on apps (for example) is extremely hit-or-miss. As an example: my post yesterday asking for testers/feedback on my iphone webapp did generate some traffic (from my analytics I saw that at least 20 people went to try it out), but only 1 person sent a reply to that thread (publicly or privately). This is just a personal example as a data-point, I'm not whining or having a self-pity party... so turn off your flamethrowers. If there were a separate list where people were willing and able to test apps and give feedback to people before publicly launching something, that could be really helpful. However, I know the perception of creating a separate private list will probably be negative and seen as creating a clique or something, but for the people that are always hanging around these boards I think they would appreciate it. How would you decide who to give membership to? I dunno... again, I know there's not an easy answer. The way I see it now (or at least in the recent past), this board has been mainly used for asking how to get a source parameter, basic how-to-get-started type questions, and reporting twitter service outages or glitches that the twitter team are probably already painfully aware of. I know there are others that feel the same way, and I'm not alone. I'm not saying these are bad or unworthy topics, I think I have been helpful in answering a fair share of getting started questions b/c it's important to grow the community. I just think it would be nice to have a placed for deeper, more focused discussion for the active 3rd party developers out there. Maybe that's pie in the sky, who knows... I'm not trying to start factions here... maybe I didn't phrase my initial question correctly carry on, -Chad
[twitter-dev] Re: twitter in iframes
Actually, that 'follow' button it a great clickjacking target, unless you already follow @britneyspears … which is cool. I'm not here to judge. :) — Matt On Mar 30, 2009, at 02:52 PM, Ryan wrote: clickjacking does not really affect pages like http://twitter.com/britneyspears . whatever... I understand you got to protect yourself from misuse. On Mar 30, 5:38 pm, Alex Payne a...@twitter.com wrote: Not until the clickjacking problem is solved by the browser vendors. End of story. On Mon, Mar 30, 2009 at 14:31, Ryan ryan10...@gmail.com wrote: I can see that twitter recently has inserted a (graceful) iframe buster which clears out the html. Why is twitter in iframe such a bad thing when the content is public anyways - the rss feed of the content is available for consumption? I know about the clickjacking attack, but that unnecessarily penalizes the good applications. Any thoughts on allowing twitter pages in iframes through registered usage? -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Social Graph followers/ids returns nothing
I'm getting this sporadically and randomly, but I was wondering if anyone else is seeing it. Occasionally I'm seeing /followers/ids return just blank results. I seem to be getting a 200 response, but nothing returned. Is anyone else seeing this? Jesse
[twitter-dev] Re: twitter in iframes
Wow. That would be one evil clickjacking attack concept if it could work. Are pages on m.twitter.com protected from clickjacking as well? Zac Bowling On Mon, Mar 30, 2009 at 3:23 PM, Matt Sanford m...@twitter.com wrote: Actually, that 'follow' button it a great clickjacking target, unless you already follow @britneyspears … which is cool. I'm not here to judge. :) — Matt On Mar 30, 2009, at 02:52 PM, Ryan wrote: clickjacking does not really affect pages like http://twitter.com/britneyspears. whatever... I understand you got to protect yourself from misuse. On Mar 30, 5:38 pm, Alex Payne a...@twitter.com wrote: Not until the clickjacking problem is solved by the browser vendors. End of story. On Mon, Mar 30, 2009 at 14:31, Ryan ryan10...@gmail.com wrote: I can see that twitter recently has inserted a (graceful) iframe buster which clears out the html. Why is twitter in iframe such a bad thing when the content is public anyways - the rss feed of the content is available for consumption? I know about the clickjacking attack, but that unnecessarily penalizes the good applications. Any thoughts on allowing twitter pages in iframes through registered usage? -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Some profile images are PNG, but reported as JPGs
2009/3/30 Doug Williams d...@twitter.com: There is a feature that has been requested that will provide permanent URLs for profile images [1]. However, your issue sounds different. If you don't feel that the issue linked below meets your needs, can you please create a new issue so we can track this? It's a different issue - I can work with either the current temporary URLs or permenant ones, provided they've got the right Content-type and/or file extension, and so I've opened http://code.google.com/p/twitter-api/issues/detail?id=401 Thanks. Wasn't sure whether to consider this an API bug earlier, as it's also an issue with the web front end, not just the API. Tom
[twitter-dev] Wrong Friends Count
I'm running friends/ids for the user CoffeeCupNews, and while the Twitter UI says he has 17,336 friends, friends/ids is returning 14,872 friends. Is something stuck in cache right now? Jesse
[twitter-dev] Re: Coldfusion Twitter status posting help
Abava, thanks. Unfortunately, the CFML engine I'm using runs on .NET so I can't use the JSP stuff without a lot of wrappers and such. On Mar 30, 4:04 pm, Abava dnam...@gmail.com wrote: check out this JSP taglib:http://www.servletsuite.com/servlets/twittertag.htm you can use it in CF as well On Mar 29, 10:32 pm, Craig328 craig...@gmail.com wrote: I've been banging my head on this issue for the past 3-4 days to the point that my skull has attained a soggy, squishy quality...so any help would be most appreciated. I have a Twitter account that I want to post simple periodic updates to from a website I own. I can successfully do this: cfhttp url=http://twitter.com/account/verify_credentials.xml; method=get username=#variables.Tusername# password=#variables.Tpassword# That works everytime. However, this does not work: cfhttp url=http://twitter.com/statuses/update.xml; method=POST username=#variables.Tusername# password=#variables.Tpassword# charset=UTF-8 cfhttpparam type=FORMFIELD name=user value=#variables.Tusername# cfhttpparam type=FORMFIELD name=password value=#variables.Tpassword# cfhttpparam type=FORMFIELD name=status value=#variables.Tstatus# /cfhttp Not just that but any variation of the post to update.xml fails and the fail reason is: Could not authenticate you. I've tried it in just about every combination I can think of. I've scoured Twitter's API docs, Google and everywhere in between and can't get this to go. I'm hoping someone can point me in the right direction. This seems a really simply thing but it's driving me to distraction. I don't believe there's a setting in Twitter itself that is causing the issue...but perhaps I'm wrong. Any help/assistance would be most welcome and appreciated. Thanks in advance.
[twitter-dev] since_id returning older messages
I am trying to retrieve direct messages using the since_id to fetch only the new ones. The documentations says Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. However, the API is giving me messages with an ID lower than the since_id that I pass. Is this a known issue? Here is what I ask for: http://twitter.com/direct_messages.xml?since_id=80627918 Here is what I get back (I snipped out the irrelevant stuff) direct-messages type=array direct_message id80627918/id ... /direct_message direct_message id80615056/id ... /direct_message You can see that the second message is lower than my since_id parameter. Am I doing something wrong?
[twitter-dev] Re: Can we make this a private list?
Let's please keep this list focused on developers working with/on the twitter api... other uses, like the promotion of application or looking for help with alpha testing of applications is not appropriate (though we can sympathize with the problem). RE: doug's question about making 'basic information more accessible... it's pretty accessible, and simple, and I think nicely summarized on one page (albeit a _large_ page) ... and sometime RTFM is the right response ... careful of bloating the help so that it becomes unreadably large... cheers! jeffrey http://www.jeffrey-greenberg.com
[twitter-dev] Re: since_id returning older messages
On Mon, Mar 30, 2009 at 6:11 PM, Jake off...@gmail.com wrote: I am trying to retrieve direct messages using the since_id to fetch only the new ones. The documentations says Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. However, the API is giving me messages with an ID lower than the since_id that I pass. Is this a known issue? yes. see the list from today. many posts. -damon
[twitter-dev] statuses/replies now include mentions
Devs, Before today calls to statuses/replies [1] would return only tweets that were prefixed with a @username. As clients began to recognize the value in mentions of a @username anywhere in the tweet, they opted to perform a search for @username to get the superset. Twitter agrees [2] that the definition of a reply has changed, and as such, calls to statuses/replies contain any tweets that include a mention of the authenticating user. If your client has been using the Search API to retrieve @replies, you should begin to migrate to statuses/replies method as it now best practice. 1. http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies 2. http://blog.twitter.com/2009/03/replies-are-now-mentions.html Code on, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: statuses/replies now include mentions
...and there was much rejoicing! Hooray / -chad On Mon, Mar 30, 2009 at 8:44 PM, atebits loren.brich...@gmail.com wrote: Fantastic change - thanks! On Mar 30, 5:39 pm, Doug Williams d...@twitter.com wrote: Devs, Before today calls to statuses/replies [1] would return only tweets that were prefixed with a @username. As clients began to recognize the value in mentions of a @username anywhere in the tweet, they opted to perform a search for @username to get the superset. Twitter agrees [2] that the definition of a reply has changed, and as such, calls to statuses/replies contain any tweets that include a mention of the authenticating user. If your client has been using the Search API to retrieve @replies, you should begin to migrate to statuses/replies method as it now best practice. 1.http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies 2.http://blog.twitter.com/2009/03/replies-are-now-mentions.html Code on, Doug Williams Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] Re: statuses/replies now include mentions
Something to keep in mind: our UX team has decided to represent this feature as @$username on the web. If you don't have room for that label in your Twitter app's GUI, consider an @ symbol. If you don't like that representation, at least considering renaming Replies to Mentions in your GUI to stay consistent with what new users will see when they sign in to twitter.com. That said, the new behavior is intuitive even with the label of Replies, so don't panic if it takes a few days (or weeks) to push out a new version of your app with a new label in the GUI. You shouldn't need to change any of the logic (though you may get to remove some if you were doing vanity searches via the Search API). If your users don't like the new behavior, it's trivial to give them the option to filter out anything but tweets starting with @$username. We figured we'd err on the side of giving you more data to work with. Enjoy! On Mon, Mar 30, 2009 at 17:39, Doug Williams d...@twitter.com wrote: Devs, Before today calls to statuses/replies [1] would return only tweets that were prefixed with a @username. As clients began to recognize the value in mentions of a @username anywhere in the tweet, they opted to perform a search for @username to get the superset. Twitter agrees [2] that the definition of a reply has changed, and as such, calls to statuses/replies contain any tweets that include a mention of the authenticating user. If your client has been using the Search API to retrieve @replies, you should begin to migrate to statuses/replies method as it now best practice. 1. http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies 2. http://blog.twitter.com/2009/03/replies-are-now-mentions.html Code on, Doug Williams Twitter API Support http://twitter.com/dougw -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: statuses/replies now include mentions
Are replies created by setting the in_reply_to_status_id with the statuses/update method affected by this change? There are some clients that set the id when doing things like retweeting -- and these may or may not have a reference to a user's screen name in them. Will these tweets continue to show up in the statuses/replies feed? -ch On Mar 30, 5:39 pm, Doug Williams d...@twitter.com wrote: Devs, Before today calls to statuses/replies [1] would return only tweets that were prefixed with a @username. As clients began to recognize the value in mentions of a @username anywhere in the tweet, they opted to perform a search for @username to get the superset. Twitter agrees [2] that the definition of a reply has changed, and as such, calls to statuses/replies contain any tweets that include a mention of the authenticating user. If your client has been using the Search API to retrieve @replies, you should begin to migrate to statuses/replies method as it now best practice. 1.http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies 2.http://blog.twitter.com/2009/03/replies-are-now-mentions.html Code on, Doug Williams Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] Re: Social Graph followers/ids returns nothing
We've had reports of this for users with many followers/following. On Mon, Mar 30, 2009 at 15:48, Jesse Stay jesses...@gmail.com wrote: I'm getting this sporadically and randomly, but I was wondering if anyone else is seeing it. Occasionally I'm seeing /followers/ids return just blank results. I seem to be getting a 200 response, but nothing returned. Is anyone else seeing this? Jesse -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: statuses/replies now include mentions
Craig, Great questions. The in_reply_to_status_id will be honored only if the value is a status_id that was authored by a user that is also mentioned in the tweet. Therefore, if you include a status_id for this parameter and that is either 1) invalid or 2) does not belong to a user mentioned in the tweet, the field will be discarded. Your second question then becomes pretty intuitive when coupled with our recent change to the in_reply_to_status_id field. If this field is valid by the rules above, it will produce a in reply to user in the Web GUI. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Mar 30, 2009 at 6:26 PM, Jakk specto...@gmail.com wrote: I've been waiting for this for so long, thank you! On Mar 30, 8:39 pm, Doug Williams d...@twitter.com wrote: Devs, Before today calls to statuses/replies [1] would return only tweets that were prefixed with a @username. As clients began to recognize the value in mentions of a @username anywhere in the tweet, they opted to perform a search for @username to get the superset. Twitter agrees [2] that the definition of a reply has changed, and as such, calls to statuses/replies contain any tweets that include a mention of the authenticating user. If your client has been using the Search API to retrieve @replies, you should begin to migrate to statuses/replies method as it now best practice. 1.http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies 2.http://blog.twitter.com/2009/03/replies-are-now-mentions.html Code on, Doug Williams Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] Re: statuses/replies now include mentions
What would be a nice addition would be the ability to have a mentions meta tag with the Tweet stating those mentioned in the Tweet. Those in the mentions meta tag don't necessarily have to be in the Tweet. Consider this similar to Facebook's tagging for photos and videos, and UIs could build tagging around that without the user ever having to mention anyone in the Tweet itself. My thought on this is that by using that method, users wouldn't necessarily have to pollute their Tweets with a user's name while trying to get their attention. It also wouldn't take away from the 140 characters and the Tweet could focus more on content. I'd love to see the same types of meta-tagging for hashtags and keywords describing the Tweet. Jesse On Mon, Mar 30, 2009 at 7:04 PM, Alex Payne a...@twitter.com wrote: Something to keep in mind: our UX team has decided to represent this feature as @$username on the web. If you don't have room for that label in your Twitter app's GUI, consider an @ symbol. If you don't like that representation, at least considering renaming Replies to Mentions in your GUI to stay consistent with what new users will see when they sign in to twitter.com. That said, the new behavior is intuitive even with the label of Replies, so don't panic if it takes a few days (or weeks) to push out a new version of your app with a new label in the GUI. You shouldn't need to change any of the logic (though you may get to remove some if you were doing vanity searches via the Search API). If your users don't like the new behavior, it's trivial to give them the option to filter out anything but tweets starting with @$username. We figured we'd err on the side of giving you more data to work with. Enjoy! On Mon, Mar 30, 2009 at 17:39, Doug Williams d...@twitter.com wrote: Devs, Before today calls to statuses/replies [1] would return only tweets that were prefixed with a @username. As clients began to recognize the value in mentions of a @username anywhere in the tweet, they opted to perform a search for @username to get the superset. Twitter agrees [2] that the definition of a reply has changed, and as such, calls to statuses/replies contain any tweets that include a mention of the authenticating user. If your client has been using the Search API to retrieve @replies, you should begin to migrate to statuses/replies method as it now best practice. 1. http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies 2. http://blog.twitter.com/2009/03/replies-are-now-mentions.html Code on, Doug Williams Twitter API Support http://twitter.com/dougw -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: statuses/replies now include mentions
I can also see there being a need to filter out some of your mentions: if you're one of those users who gets a lot of retweets, seeing RT @chockenberry SAID SOMETHING FUNNY is going to get pretty annoying as thousands of people echo what you say. Is there going to be an option so that only replies get put into your mentions feed (statuses/ replies)? I think this is a stellar idea. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- How are you gentlemen? All your base are belong to us! -
[twitter-dev] Re: statuses/replies now include mentions
Great, this will be a helpful change. Any discussion of codifying Retweets in a similar way in the search API? It seems like they are also a subset of Mentions where 1) starts with RT 2) includes a @mention 3) rest of the content (fuzzy) matches a previous tweet by the @mention tweeter. Yes, but it seems TMTOWTDI with RTs because I've also seen xyzpdq (via @omglol), retweet @omglol: xyzpdq, etc. There's too much variation in syntax. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- You've got to have a gimmick if your band sucks. -- Gary Giddens ---
[twitter-dev] Re: changing source URL
I got this email: Thanks for requesting a source parameter link for your application, QuickSilver Unfortunately, we've rejected your request. Here's why: quicksilver as a source parameter is taken. Please provide something unique 'quicksilver_launcher' for instance. Please address the issues above and submit another request if appropriate. Thanks for your interest and good luck! I know its taken. But i must be able to use it. QuickSilver is open- source. No one can limit its use. And i have seen QuickSilver being used with two different URLs http://dyve.net/2009/03/04/improved-twitter-for-quicksilver-tweetscp/ points to coda.blog and other used by the user (http://twitter.com/colinharman/statuses/1337750035), points to blacktree.com I should have access to the one pointing to blacktree.com.
[twitter-dev] Re: statuses/replies now include mentions
Great, this will be a helpful change. Any discussion of codifying Retweets in a similar way in the search API? It seems like they are also a subset of Mentions where 1) starts with RT 2) includes a @mention 3) rest of the content (fuzzy) matches a previous tweet by the @mention tweeter. -mike On Mar 30, 10:28 pm, tweetip twee...@mac.com wrote: In changing our code, we've decided: Show my replies becomes Show my mentions but Reply to is not becoming Mention to - it stays Reply to otoh having both my replies and my mentions is something users will ask for... hth :)
[twitter-dev] Re: changing source URL
On Tue, Mar 31, 2009 at 12:37 PM, Chris Cairns nochan...@gmail.com wrote: I know its taken. But i must be able to use it. QuickSilver is open-source. It means that some other client took the quicksilver id already. Both clients you mention could use the same name but different ids. -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
[twitter-dev] Re: changing source URL
You can use existing sources in your application. It will just link to already associated URL. Examples: https://twitter.com/home?status=testsource=quicksilver https://twitter.com/home?status=testsource=twhirl On Mon, Mar 30, 2009 at 20:37, Chris Cairns nochan...@gmail.com wrote: I got this email: Thanks for requesting a source parameter link for your application, QuickSilver Unfortunately, we've rejected your request. Here's why: quicksilver as a source parameter is taken. Please provide something unique 'quicksilver_launcher' for instance. Please address the issues above and submit another request if appropriate. Thanks for your interest and good luck! I know its taken. But i must be able to use it. QuickSilver is open-source. No one can limit its use. And i have seen QuickSilver being used with two different URLs http://dyve.net/2009/03/04/improved-twitter-for-quicksilver-tweetscp/ points to coda.blog and other used by the user (http://twitter.com/colinharman/statuses/1337750035), points to blacktree.com I should have access to the one pointing to blacktree.com. -- Abraham Williams | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from: Madison WI United States.
[twitter-dev] Re: statuses/replies now include mentions
Thanks for the clarification, Doug. Overall, I think this is a very positive change. Just a little spooked that it came out of the blue like it did - maybe next time it would be wise to give us a bit of a heads up before deploying... More questions: On http://twitter.com/account/notifications, will there be new options to control how your @replies are handled? Currently, the user can choose: All @replies @replies to the people I'm following No @replies Does this now mean: All mentions Mentions to the people I'm following No mentions ? I can also see there being a need to filter out some of your mentions: if you're one of those users who gets a lot of retweets, seeing RT @chockenberry SAID SOMETHING FUNNY is going to get pretty annoying as thousands of people echo what you say. Is there going to be an option so that only replies get put into your mentions feed (statuses/ replies)? -ch On Mar 30, 6:38 pm, Doug Williams d...@twitter.com wrote: Craig, Great questions. The in_reply_to_status_id will be honored only if the value is a status_id that was authored by a user that is also mentioned in the tweet. Therefore, if you include a status_id for this parameter and that is either 1) invalid or 2) does not belong to a user mentioned in the tweet, the field will be discarded. Your second question then becomes pretty intuitive when coupled with our recent change to the in_reply_to_status_id field. If this field is valid by the rules above, it will produce a in reply to user in the Web GUI. Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 6:26 PM, Jakk specto...@gmail.com wrote: I've been waiting for this for so long, thank you! On Mar 30, 8:39 pm, Doug Williams d...@twitter.com wrote: Devs, Before today calls to statuses/replies [1] would return only tweets that were prefixed with a @username. As clients began to recognize the value in mentions of a @username anywhere in the tweet, they opted to perform a search for @username to get the superset. Twitter agrees [2] that the definition of a reply has changed, and as such, calls to statuses/replies contain any tweets that include a mention of the authenticating user. If your client has been using the Search API to retrieve @replies, you should begin to migrate to statuses/replies method as it now best practice. 1.http://apiwiki.twitter.com/REST-API-Documentation#statuses/replies 2.http://blog.twitter.com/2009/03/replies-are-now-mentions.html Code on, Doug Williams Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] Re: statuses/replies now include mentions
On Tue, Mar 31, 2009 at 12:33 AM, Cameron Kaiser spec...@floodgap.com wrote: Yes, but it seems TMTOWTDI with RTs because I've also seen xyzpdq (via @omglol), retweet @omglol: xyzpdq, etc. There's too much variation in syntax. TMTOWTDI ?? There's More Than One Way To Do It ... I imagine there's not a big Perl crowd on this list. *le sigh* Ah, of course... I had never seen it in acronym form before, and I was le tired. AH MOTHERLAND! -chad
[twitter-dev] Re: statuses/replies now include mentions
On Mon, Mar 30, 2009 at 10:33 PM, Cameron Kaiser spec...@floodgap.comwrote: Yes, but it seems TMTOWTDI with RTs because I've also seen xyzpdq (via @omglol), retweet @omglol: xyzpdq, etc. There's too much variation in syntax. TMTOWTDI ?? There's More Than One Way To Do It ... I imagine there's not a big Perl crowd on this list. *le sigh* I got it - how young is this list? I'm only 31, but I guess that's old these days. Perl's much more widely used than people think, I think. Anyone noticed the YAML::Syck messages in SMS from Twitter lately? Jesse
[twitter-dev] Re: statuses/replies now include mentions
Also, I see Alex is talking about @$username - is that documented somewhere? I didn't find it when I went looking in the REST API doc (or the search doc either, for that matter). Alex means it as a pattern, i.e., @doctorlinguist, @al3x, etc. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- He who Laughs, Lasts. --
