[twitter-dev] Re: Mobile OAuth fix is LIVE
Ryan, Don't know if it will fit in with your architecture, but maybe this service could be of use to you: http://wapple.net/ On Feb 6, 12:39 am, Ryan Sarver rsar...@twitter.com wrote: Ill talk with the team and figure out if it's better to roll it back or just limit it to the known, working user agents On Fri, Feb 5, 2010 at 3:42 PM, CharlesW cwilt...@gmail.com wrote: That's an amazingly great recommendation, Michael. -- Charles On Feb 5, 9:22 am, Michael Steuer mste...@gmail.com wrote: In fact, I'd recommend that you only show the new version for devices you have actually tested against... Mobile browser support is a crap shoot and you really can't assume that something that works on one device, works on another... You need to test each and every one of them (or at least each family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen, iPhone OS, Motorola V3 series, etc.) I've been in mobile development for 15 years... Let me know if you need some pointers off list... Happy to assist. On 2/5/10 8:40 AM, CharlesW cwilt...@gmail.com wrote: Ryan, Thanks for both the attempted fix and the announcement. Unfortunately, where the previous version was kind of a crapshoot for mobile users because the buttons appeared black (see my screenshot in the bug report athttp:// code.google.com/p/twitter-api/issues/detail?id=395), this new version doesn't work at all on many mobile browsers. Because this breaks mobile Twitter support completely for many (most? all?) phones using older browsers, can you please revert to the previous version, and then stage a new version somewhere else that we can help you test? -- Charles On Feb 3, 3:16 pm, Ryan Sarver rsar...@twitter.com wrote: FINALLY! An update has just gone live that fixes rendering of the OAuth screens for most mobile devices. We also fixed a few small nagging things like the default action is now allow instead of deny if you just hit go on an iPhone. I've attached two screenshots so you can see the updated screens. Please test it out with your various mobile web apps and let us know if you run into any problems or edge cases. Ryan IMG_0739.png 93KViewDownload IMG_0738.png 75KViewDownload
Re: [twitter-dev] Re: Mobile OAuth fix is LIVE
And for QA, if you're not able to procure each commercially available handset, check out www.deviceanywhere.com. Or if you prefer to outsource, hit me up off list, I can give you a list of reputable mobile QA houses. On Feb 6, 2010, at 7:40 AM, Dewald Pretorius dpr...@gmail.com wrote: Ryan, Don't know if it will fit in with your architecture, but maybe this service could be of use to you: http://wapple.net/ On Feb 6, 12:39 am, Ryan Sarver rsar...@twitter.com wrote: Ill talk with the team and figure out if it's better to roll it back or just limit it to the known, working user agents On Fri, Feb 5, 2010 at 3:42 PM, CharlesW cwilt...@gmail.com wrote: That's an amazingly great recommendation, Michael. -- Charles On Feb 5, 9:22 am, Michael Steuer mste...@gmail.com wrote: In fact, I'd recommend that you only show the new version for devices you have actually tested against... Mobile browser support is a crap shoot and you really can't assume that something that works on one device, works on another... You need to test each and every one of them (or at least each family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen, iPhone OS, Motorola V3 series, etc.) I've been in mobile development for 15 years... Let me know if you need some pointers off list... Happy to assist. On 2/5/10 8:40 AM, CharlesW cwilt...@gmail.com wrote: Ryan, Thanks for both the attempted fix and the announcement. Unfortunately, where the previous version was kind of a crapshoot for mobile users because the buttons appeared black (see my screenshot in the bug report athttp:// code.google.com/p/twitter-api/issues/detail?id=395), this new version doesn't work at all on many mobile browsers. Because this breaks mobile Twitter support completely for many (most? all?) phones using older browsers, can you please revert to the previous version, and then stage a new version somewhere else that we can help you test? -- Charles On Feb 3, 3:16 pm, Ryan Sarver rsar...@twitter.com wrote: FINALLY! An update has just gone live that fixes rendering of the OAuth screens for most mobile devices. We also fixed a few small nagging things like the default action is now allow instead of deny if you just hit go on an iPhone. I've attached two screenshots so you can see the updated screens. Please test it out with your various mobile web apps and let us know if you run into any problems or edge cases. Ryan IMG_0739.png 93KViewDownload IMG_0738.png 75KViewDownload
[twitter-dev] Twitter Widget - Website
There may be a bug on the Customized Twitter Widget (used to be integrated into website). While options enable a user to choose the height and how many tweets appearing (rpp), the interface automatically resizes itself in result of the tweet lengths. For example, if 4 tweets are submitted (all one line each), the widget will reduce in size height dramatically. On the other hand, if each tweet uses all 140 characters, the size of the widget will greatly increase. Is there a way to lock the height of the widget?? Thank you ;-) Andrew Marks andrewgma...@gmail.com
[twitter-dev] Loading list of friends from twitter api
Hey guys, I'm using the twitter ruby gem to get the usernames of someone's followers after they signs in to my app. What happens if that person has thousands (even millions) of followers? How does twitter return this information? Is it ordered by the users with the most recent updates? I suppose it will be paginated..? Thanks. Peter
[twitter-dev] a1.twimg.com access denied image error
i haven't noticed this error lately, but today i am. anyone else noticing it on the a1 server when trying to access images?
[twitter-dev] direct message whitelisting?
Hey twitter-development-talk, I've searched Google and the list's archives for an answer to the following question but have yet to find it: do whitelisted user accounts that have been whitelisted for 20k API calls/day have higher direct message limits, as well? If so, what are they? If not, is there a process for getting an account whitelisted for higher direct message limits? Thanks! trevor
[twitter-dev] Re: Mobile OAuth fix is LIVE
Can you let us know the current supported User Agents? That way I can direct our users to it if I am certain their phones are supported. Thanks T On Feb 6, 4:39 am, Ryan Sarver rsar...@twitter.com wrote: Ill talk with the team and figure out if it's better to roll it back or just limit it to the known, working user agents
Re: [twitter-dev] direct message whitelisting?
I'd like a public answer for this, we have whitelisted systems and some of our customers are starting to use their accounts as 'command centers', our software permits them to mass message members of certain lists. Right now the biggest list is a dozen and it's used infrequently, but we have proposals to two organizations with a million plus members and this feature is something they very specifically want ... On Sat, Feb 6, 2010 at 1:13 AM, Trevor Sehrer trevor.seh...@gmail.comwrote: Hey twitter-development-talk, I've searched Google and the list's archives for an answer to the following question but have yet to find it: do whitelisted user accounts that have been whitelisted for 20k API calls/day have higher direct message limits, as well? If so, what are they? If not, is there a process for getting an account whitelisted for higher direct message limits? Thanks! trevor -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717
Re: [twitter-dev] direct message whitelisting?
whitelisting for direct messages is different than whiltelisting for API calls. i tend to believe we are a lot more restrictive in giving out whitelisting for DMs - but e-mail a...@twitter.com with your intentions to request it. On Sat, Feb 6, 2010 at 1:52 PM, neal rauhauser nrauhau...@gmail.com wrote: I'd like a public answer for this, we have whitelisted systems and some of our customers are starting to use their accounts as 'command centers', our software permits them to mass message members of certain lists. Right now the biggest list is a dozen and it's used infrequently, but we have proposals to two organizations with a million plus members and this feature is something they very specifically want ... On Sat, Feb 6, 2010 at 1:13 AM, Trevor Sehrer trevor.seh...@gmail.comwrote: Hey twitter-development-talk, I've searched Google and the list's archives for an answer to the following question but have yet to find it: do whitelisted user accounts that have been whitelisted for 20k API calls/day have higher direct message limits, as well? If so, what are they? If not, is there a process for getting an account whitelisted for higher direct message limits? Thanks! trevor -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Any iPhone Twitter apps with OAuth login ?
On Fri, Jan 29, 2010 at 4:20 PM, Ryan Sarver rsar...@twitter.com wrote: Good news. A mobile-friendly version of the OAuth page is due to be deployed next week (finally!:). We look forward to your feedback on the new screens when they are ready. Looks much better now, thanks !
[twitter-dev] http://search.twitter.com/operators/ not loading in UIWebView on iPhone
Not sure whose bug is it, but I am having trouble loading http://search.twitter.com/operators/ in UIWebView on iPhone. The problem is not specific to my app—you can see this bug also with the official UICatalog example. The problem is specific to search.twitter.com/operators/ and UIWebView. The link loads fine in iPhone Safari, and http://search.twitter.com/ and other Twitter links load fine in UIWebView. But, to provide inline help for search, it would be handy to load this in UIWebView too. I didn't have time to investigate if the bug is on server or client side. My hunch is that Twitter may not handle the user-agent of UIWebView correctly, but this is just a random guess, would need to investigate more. rgds, Jaanus
[twitter-dev] from app identification
Hello! I don't know what to do. I'm trying to develop a Twitter client based on MGTwitterEngine, which use this code to define the client: #define DEFAULT_CLIENT_NAME @tweetero #define DEFAULT_CLIENT_VERSION @1.7 #define DEFAULT_CLIENT_URL @http://yfrog.com; #define DEFAULT_CLIENT_TOKEN@tweetero And, It works for yfrog. I know that I need to include OAuth in my app, but in the iPhone is very difficult to implement. Twitter can do an special exception and register my client's name, like the old times? All another clients for the iPhone are pre-Oauth, and uses the old way. Examples are Tweetie, echofon and Twitterrific. When I try to register my name... #define DEFAULT_CLIENT_NAME @Plumifero #define DEFAULT_CLIENT_VERSION @1.0 #define DEFAULT_CLIENT_URL @http://matmartinez.net/; #define DEFAULT_CLIENT_TOKEN@Plumifero Obviously doesn't works. Thanks and «sorry for my english».
Re: [twitter-dev] Twitter Widget - Website
In the script code you can specify the height.
script src=http://widgets.twimg.com/j/2/widget.js;/script
script
new TWTR.Widget({
version: 2,
type: 'profile',
rpp: 4,
interval: 6000,
width: 250,
* height: 400,*
...
Abraham
On Fri, Feb 5, 2010 at 14:56, Andrew Marks andrewgma...@gmail.com wrote:
There may be a bug on the Customized Twitter Widget (used to be
integrated into website). While options enable a user to choose the
height and how many tweets appearing (rpp), the interface
automatically resizes itself in result of the tweet lengths.
For example, if 4 tweets are submitted (all one line each), the widget
will reduce in size height dramatically. On the other hand, if each
tweet uses all 140 characters, the size of the widget will greatly
increase. Is there a way to lock the height of the widget?? Thank
you ;-)
Andrew Marks
andrewgma...@gmail.com
--
Abraham Williams | Community Advocate | http://abrah.am
Project | Out Loud | http://outloud.labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
Re: [twitter-dev] Incoming User-Objects are blank ?
The Search API does not contain the standard user object that is returned
from the rest of the API methods. Have a look at the response section on:
http://apiwiki.twitter.com/Twitter-Search-API-Method:-search
Abraham
On Fri, Feb 5, 2010 at 05:05, nico n...@second-dimension.de wrote:
Hi guys,
i am using the Twitterscript Libary for as3-Developing...I want to
search twitter (exp: Apple) and show the results in a List. There i
wanna display the image/name of each author...
My problem ist, that the twitterUser object of the twitterStatus
object is totally empty / all vars are empty..
this.twitt = new Twitter();
this.tSearch= new TwitterSearch();
this.twitt.addEventListener(TwitterEvent.ON_SEARCH, onSearch);
//this.tSearch.lang = de;
this.tSearch.addKeyword(Apple);
//this.tSearch.addKeyword(Unfall, false,
true);
this.twitt.search(this.tSearch);
}
protected function onSearch(event:TwitterEvent):void
{
trace(event.data );
_tweetArray = event.data as Array;
var twitterStatus:TwitterStatus;
for (var i : int = 0; i event.data.length;
i++)
{
twitterStatus = event.data[i];
trace( twitterStatus.user.id) // = Empty
}
Any idea? I think that Twitterscript is a great lib, so i really
regret it, if i can't use it. :/
greetings, nico
--
Abraham Williams | Community Advocate | http://abrah.am
Project | Out Loud | http://outloud.labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
Re: [twitter-dev] Retweets and location problems in search API
A work around would be to pull the original tweet information from the REST API and see if you still want to keep/use it. Did you check the issue tracker for an existing bug request? If none you could create one so Twitter can keep track of it. http://code.google.com/p/twitter-api/issues/list Abraham On Fri, Feb 5, 2010 at 00:00, Matt L mlev...@gmail.com wrote: In the search API, if you query for RT in the San Francisco area using the geocode parameter it returns both official retweets (ones created by hitting the retweet button) and unofficial retweets (retweets where either the user or the client has simply inserted the text RT). Official retweets keep the location field of the original tweet. Unofficial retweets take on the location of the user who retweeted the message. The problem I'm having is that this makes geolocation searches for retweets from a certain area very confusing. It's impossible to search for what/who people in a certain city, say San Francisco are rtweeting the most. Users in San Francisco who use the official retweet feature and retweet something from NY don't show up in a query for San Francisco Retweets. Likewise, if one was interested in who from San Francisco was being retweeted the most, they would also be stymied b/c the results are polluted with unofficial RT's that look text-wise like an official RT (same message text format). So they would get a lot of results of San Franciscans retweeting people from New York. The only way to check against that would be to do a show/user lookup on the from_user, and the rate limit on that API would be eaten up very quickly for any persistant search. Is there any plan to address these issues? Has anyone in the development community found a work around? Thanks, Matt -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Query About Direct Messages
My understanding is a single Twitter account can send up to 250 DMs per day. Abraham On Fri, Feb 5, 2010 at 04:09, kiran kumar kiran.nets...@gmail.com wrote: In Twitter,showing 250 per day limit.i want know to that,250 means message or 250 users.I want to develop a tool to send direct messages to my friends at a time.So,any body help me to solve my problem. Thank u. Kiran -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Re: It's been three months since the truncation change.... can't the docs be updated?
I fully blame Twitter. They got us all hooked by being agreeable and easy going then we go and get all huffy over little things. :-P Abraham On Thu, Feb 4, 2010 at 16:03, Dewald Pretorius dpr...@gmail.com wrote: You don't have to have respect for third-party developers -- it's your site and you can do as you like -- but common sense should tell you that it behooves you to at least *try* to hide your contempt. I think I'm known for now and then directing a flame thrower in the direction of the Twitter folks, sometimes out of frustration and sometimes because wearing a diplomat's pants give me a serious wedgie. Despite that, I have never felt that Twitter has contempt for the developers. -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
RE: [twitter-dev] Query About Direct Messages
Correct, only 250 dm's per account per day. So 50 messages per day to 5 people OR 1 message to 250 people..of course if you have multiple accounts Cheers, Dean From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Abraham Williams Sent: Sunday, February 07, 2010 1:02 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Query About Direct Messages My understanding is a single Twitter account can send up to 250 DMs per day. Abraham On Fri, Feb 5, 2010 at 04:09, kiran kumar kiran.nets...@gmail.com wrote: In Twitter,showing 250 per day limit.i want know to that,250 means message or 250 users.I want to develop a tool to send direct messages to my friends at a time.So,any body help me to solve my problem. Thank u. Kiran -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
