I trust that Twitter will close down that loophole pretty quickly, so
that we have an equal playing field for all apps, especially those who
choose not to exploit the loophole.


On Jul 3, 4:17 am, Harrison <peppe...@gmail.com> wrote:
> Just a heads up. I don't think this is officially supported by any
> means, but if you pass "source=web" in your REST call, the source will
> return to the old "web".
>
> i.e.
> $ curl -u username:password -d "status=This is a 
> test."http://twitter.com/statuses/update.xml
>
> "This is a test.
> 2 minutes ago from API"
>
> $ curl -u username:password -d "source=web&status=This is a not a
> test."http://twitter.com/statuses/update.xml
>
> "This is a not a test.
> 2 minutes ago from web"
>
> On Jul 3, 4:22 am, Dewald Pretorius <dpr...@gmail.com> wrote:
>
> > Okay. Thanks for the clarification.
>
> > It's not a big issue. Just needed to know what to tell my users.

Reply via email to