Re: [twitter-dev] Re: Will requesting DM access now disable xAuth for my app?

Thanks for being my guinea pig! 8D -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Sunday, May 29, 2011 at 12:49 PM, twittelator

[twitter-dev] Will requesting DM access now disable xAuth for my app?

Fellers, For testing as we prep our apps for the switch to PIN-based auth, I'd like to change the default access level to Read, Write, Private Message. However, I'm concerned this will disable xAuth for existing users immediately, rather than once we hit June 30. Can I do this, or should I

[twitter-dev] Re: A new permission level

how to migrate to a solid oAuth flow on desktop and mobile would be very useful to many devs. Good luck. -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API

[twitter-dev] Saved search destroy method not always effective?

not appear to have been deleted. http://friendpaste.com/33zXI3iZCKN23vc1NlhCeJ Anyone else seeing this? -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com

[twitter-dev] Re: Deprecation of following and notification elements

| prettyjson [...] following:0, [...] I believe that following is supposed to indicate of the authenticating user is following the requested user, but even if it's the other way around, it seems wrong. Am I missing something, though? -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ

[twitter-dev] Re: Deprecation of following and notification elements

Or, as I think slightly more clearly, perhaps this is an example of the inconsistency discussed in the OP. Sorry for the noise if that's the case. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On May 27, 11:50 am, Ed Finkler funkat

[twitter-dev] Re: Can Twitter please pick a From: and stick with it?

You do a ton of great things, Matt. We all make mistakes, but you and the rest of the crew there do a bang-up job. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On May 7, 11:24 am, Matt Sanford m...@twitter.com wrote: Hi all

[twitter-dev] Re: Twitter's official comment on our disabling of OAuth

That is, in fact, what Beta typically means: not suitable for production use. Overuse of the term by a few popular web apps notwithstanding. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Apr 23, 9:25 am, mikehar m...@picnik.com

[twitter-dev] Re: first try

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 Finkler http://funkatron.com Twitter

[twitter-dev] Re: The OAuth Conundrum

that pull data down for my data mining experiments. I am afraid that going OAuth-only will effectively kill off these kinds of apps. That would suck, in my opinion. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 26, 1:44 pm, Gavin

[twitter-dev] Re: 4-legged OAuth discussion

to have a one-round OAuth grant to more than one consumer, but *please* make sure that all consumers are broken out and granted access individually. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 25, 8:21 pm, Ivan ivan.kiri

[twitter-dev] Re: The OAuth Conundrum

unsuitable for some. OAuth as the only authentication scheme will create a much higher barrier for simple exploration of the API. That will be disappointing to me if it happens. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 26, 1

[twitter-dev] Re: Proof of identity rather than authorization

with it. Well, Basic Auth still works *now*. I've personally advocated it not go away ever. If you agree, you may want to make this preference known. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com

[twitter-dev] Re: How many accounts is too many?

reason why it has such a large dev community, I'd say. I subscribe to a couple broadcast-only news ticker accounts, because I like the content and prefer to have it in my friends timeline over other delivery systems. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ

[twitter-dev] Re: How to get started?

did the tech editing work on this. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 1, 12:51 pm, Elker elia...@gmail.com wrote: (I'm deeply sorry if I'm not supposed to post here or whatsoever.) Hi! I've got experience in HTML

[twitter-dev] Re: MAKE TWITTER WORK WITH GOOGLE TALK AGAIN ALREADY!

This isn't an API issue. You should address it to http://help.twitter.com/. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 2, 2:03 pm, APintheLP aphillip...@gmail.com wrote: come on guys...this is getting rediculousdo your

[twitter-dev] Re: 500 internal error

Try using a debugging proxy like Charles so you can see the exact request being sent. That aids greatly in sorting out things like this. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Feb 25, 5:48 am, Paul Haenel paul.hae

Re: a simple workaround for lack of OAuth

attack. Whether or not this actually makes you *safer* is something we should very carefully consider. Personally, I'd say it helps, but only a little -- far less than most of our Thought Leaders claim. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron

Re: a simple workaround for lack of OAuth

Shiflett's Essential PHP Security. Rails devs should keep an eye on http://www.rorsecurity.info/. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron

Re: a simple workaround for lack of OAuth

I think Scoble likes to hear himself talk, and loves to stir up drama. It's how he keeps people paying attention to him. I'd find more reputable sources for that argument. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Fri, Jan 2, 2009 at 12:44 AM, Richie

Re: a simple workaround for lack of OAuth

not a criticism of you in particular, but of folks who apparently don't search the archives before posting something along the lines of Scoble said this is a big deal, so you'd better do it! It doesn't help in any way. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron

Re: a simple workaround for lack of OAuth

On Fri, Jan 2, 2009 at 1:41 PM, Cameron Kaiser spec...@floodgap.com wrote: So let's say Scoble is right. How, in fact, does OAuth prevent a bad actor from using credentials to act badly? OAuth solves many problems; it doesn't solve this one. And this.

Re: Sometimes tweets are not made

If you're testing your app locally, use Charles to examine the data: http://www.charlesproxy.com/ -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Tue, Dec 23, 2008 at 9:02 PM, Stecki ma...@stecki.de wrote: I still haven't seen a Charles trace on what

Re: rate_limit_status

The web site does not affect API limits. Your account may have another issue if it's been blocked for this long. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Thu, Dec 18, 2008 at 11:01 AM, Mike shotzomb...@gmail.com wrote: On Dec 18, 10:53 am

Re: rate_limit_status

Oh, I see now. So it changes each time you *check*, not just each time you hit 100. Yes, that doesn't sound right. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Thu, Dec 18, 2008 at 12:32 PM, rhysmeister therhysmeis...@hotmail.com wrote: Definitely

Re: Following limits - again.

This is definitely something you'd have to work with Twitter Support on -- this list is just for discussion of application development. Sorry to hear of your troubles tho. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Wed, Dec 17, 2008 at 9:06 AM, Lianne

Re: direct_messages new NOT working

Try grabbing the HTTP request and response with a debugging proxy like Charles. That will let us know what's really being sent and received. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Thu, Dec 11, 2008 at 1:14 AM, sMan [EMAIL PROTECTED] wrote: Oops

Re: Follow / Unfollow Error?

Try using a debugging proxy like Charles. It should capture data coming from your app, whether it's in the browser or an AIR app. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Wed, Dec 10, 2008 at 3:27 PM, Ninjamonk [EMAIL PROTECTED] wrote: thanks Alex

Re: Using CAPTCHAs to get more followers on twitter.

And so I think there's a real need for a service that helps you increase followers, especially ones who might actually find your tweets interesting. Need seems like a strong word. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron

Re: favorited value is null in JSON

Indeed, I basically can't use TwitterFon until this gets sorted out. (I'm aware of the workaround script online, but don't want to de-fav items in my timeline). -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Sun, Dec 7, 2008 at 10:50 PM, Kazuho Okui [EMAIL

Re: Helpful PHP Optimizations

commit at the end. This should speed up the time spent inserting data considerably. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Sat, Nov 15, 2008 at 11:47 AM, fastest963 [EMAIL PROTECTED] wrote: PHP Optimizations PDO (http://www.php.net/pdo) is a must

Re: No OAuth Support just made Techmeme

I think we know this already, and allowing a flavor of the day story to influence things unduly would be overreaction. I trust Alex, Matt and co. to make the proper decisions in regards to what takes precedence. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron

Re: Search UI and API suggestions

and man is he tall. A vanity mode :-) I guess you could kinda get these now, but you'd have to do client-side filtering to dump the stuff you don't want. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron

Re: Create Twitter Account using the API?

This has been discussed before. The concern is that it would allow for mass creation of accounts, ripe for abuse by spammers. I can't speak for Twitter, but I suspect that it will be a while before we see something like this, if at all. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ

Re: Create Twitter Account using the API?

that argument pretty much mute. I could see that as useful, yeah. Did you file a feature request in the issue tracker yet? -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron

Re: Twitter status source!!

Read the wiki, plz: http://apiwiki.twitter.com/FrontPage On Tue, Nov 4, 2008 at 6:20 PM, charlesmex [EMAIL PROTECTED] wrote: Hi. I am deploying a twitter application. I use the API for update status and put the ApplicationName in source post param, but ever show from web. How display my

Re: is the rate limit what it says it is?

100 req/hr per IP for non-authenticated requests. 100 req/hr per account for authenticated requests. POST requests (like updating status) are not limited. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Tue, Oct 14, 2008 at 6:26 PM, X10 [EMAIL PROTECTED

Re: Problem with replying to messages

Yes, it's because I approved them. 8) On Tue, Oct 14, 2008 at 8:25 PM, jim.renkel [EMAIL PROTECTED] wrote: OK, the replies and this new post are now visible some 15 minutes later. I guess I just wasn't patient enough. :-) Thanks, Jim Renkel On Oct 14, 7:09 pm, Ed Finkler [EMAIL