Ahmed, This is a confirmed bug. The good news is Matt and Alex tag-teamed it and have the fix readied for deploy.
Cheers, Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 1, 2009 at 3:23 PM, AhmedF <inde...@gmail.com> wrote: > > I guess just for future reference - Matt looked into it, identified it > as a bug, and said it should be fixed soon. > > Thanks. > > > On Apr 1, 5:40 pm, Chad Etzel <jazzyc...@gmail.com> wrote: > > In my experience. If you are posting from an OAuth enabled app, the > > "From" value (should) be the value you put into the OAuth app name > > form when creating the app. All "source" parameters passed will be > > ignored. I would imagine this is a pretty good security measure to > > help track down malapps (yes, you heard it hear first, folks... > > malapps will be the biggest new InfoSec term this century!). > > > > If you are posting from a Basic Auth app, it will use the "source" > parameter. > > > > That being said, however, this behavior sounds like a bug. > > -Chad > > > > On Wed, Apr 1, 2009 at 5:29 PM, AhmedF <inde...@gmail.com> wrote: > > > > > I've left it empty and tried 'source' or even 'from' - always comes up > > > with something random. > > > > > On Apr 1, 5:23 pm, Doug Williams <d...@twitter.com> wrote: > > >> Ahmed, > > >> Are you currently passing in anything with your requests as a source > > >> parameter? > > > > >> Doug Williams > > >> Twitter API Supporthttp://twitter.com/dougw > > > > >> On Wed, Apr 1, 2009 at 2:21 PM, AhmedF <inde...@gmail.com> wrote: > > > > >> > And a little follow up - so I updated that status 30 minutes ago, > > >> > where it claimed the from was 'TVTweets'. Just tried again, and now > > >> > both of the messages are from 'Testery' > > > > >> > I guess something is definitely buggy. > > > > >> > On Apr 1, 5:17 pm, AhmedF <inde...@gmail.com> wrote: > > >> > > As it is - I am using your code as the base for the OAuth > transaction > > >> > > - and all attempts to set source/from have failed. > > > > >> > > I'm waiting on getting approved as a legit 'from' field and then > > >> > > seeing what happens. > > > > >> > > On Apr 1, 5:10 pm, Abraham Williams <4bra...@gmail.com> wrote: > > > > >> > > > OAuth apps automatically get their source info added. The app > ids must > > >> > be > > >> > > > getting jumbled somewhere. A work around might be to manually > set > > >> > source=web > > >> > > > or whatever source you want. > > > > >> > > > Try creating an bug report: > > >> >http://code.google.com/p/twitter-api/issues/list > > > > >> > > > On Wed, Apr 1, 2009 at 15:46, AhmedF <inde...@gmail.com> wrote: > > > > >> > > > > I'm testing out a pretty simple OAuth app - the user verifies, > and I > > >> > > > > then push an update to their status. > > > > >> > > > > The confounding part is I am getting absolutely random values > in the > > >> > > > > 'From' field. It was originally Coolspotters, now TVtweets, > and I can > > >> > > > > only be curious as to what it chooses next. > > > > >> > > > > The API says I can only set 'status' and optionally > > >> > > > > 'in_reply_to_status_id' - anyone know why I am getting these > random > > >> > > > > values? (the status message itself is posting just fine). > > > > >> > > > -- > > >> > > > Abraham Williams | Hacker |http://abrah.am > > >> > > > @poseurtech |http://the.hackerconundrum.com > > >> > > > Web608 | Community Evangelist |http://web608.org > > >> > > > This email is: [ ] blogable [x] ask first [ ] private. > > >> > > > Sent from Madison, Wisconsin, United States >
