Perhaps, but I think it's a mistake to shut supertweet down.  It's
solving a real-world problem, doing them a favor by doing something
for twitter so they don't have to.  It pushes all these "corner cases"
off of their API front-end. It doesn't expose the user's Twitter
passwords and users never expose their passwords to supertweet.

Supertweet isn't so people can be lazy - people should still supprot
oAuth and nobody should be using to make API calls on behalf of others
(as in a normal Twitter user client). But it will really help PHP
scripts and the like "bridge" over until their hosting service or
whatever supports tools for OAuth.

So again, I'd say is doing Twitter a favor.

On May 21, 6:14 am, Tammy Fennell <> wrote:
> Hey, I'm pretty sure that Twitter isn't going to like that very much.
> The whole point is that everyone uses it not tries to get around
> it...  I can't imagine supertweet will maintain it's own oauth for
> very long...
> On May 20, 12:02 pm, Jef Poskanzer <> wrote:
> > Thanks to @mrblog and SuperTweet I now have a backup plan in case I
> > don't get OAuth implemented by the time Basic Auth goes away.  It's a
> > Twitter proxy - you use Basic Auth to talk to the proxy, and it uses
> > OAuth to talk to Twitter.  Easy peasy.
> >

Reply via email to