Any plans on opening this up to us?
This would be great .. I see it as only possible once they create some
sort of third party authentication system so that the API know which
application sent the status.
--
Alex Payne
Obvious
http://twitter.com/al3x
On Mar 15, 9:46 pm, Alex Payne <a...@al3x.net> wrote:
> We're discussing a solution for this internally, and we'll get back
> to you ASAP.
>
> --
> Alex Payne
> Obvioushttp://twitter.com/al3x
Awesome. I'm totally jealous of those Twitterriffic folks.
--
- Ed Finkler
http://funkatron.com/
a user-agent addition could be a simple solt'n: Twitter-App-Name/
TinyTwitter
just a thought... and keep up the awesome work!!!
-kevin
On Mar 16, 5:28 pm, "Ed Finkler" <funkat...@gmail.com> wrote:
Yes, actually, I plan on setting that header in the next version of
Spaz. Being a bit lazy atm with it.
--
Alex Payne
Obvious
http://twitter.com/al3x
I'd imagine we should be sending an X-Twitter-Client header rather than
a User-Agent, as the actual User-Agent is good for monitoring (claimed)
browsers and/or WWW libraries.
If User-Agent, then it should be *appended* to the existing one. Eg:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070309
Firefox/2.0.0.3 Twitter/GoogleGadget/1.01
I really want to push for X headers though. Even if twitter.com doesn't
use them immediately, they may be of interest in the future (esp the URL
for advertising a library of clients)
X-Twitter-Client: GoogleGadget
X-Twitter-Client-URL: http://twitter.isite.net.au/meta.xml
X-Twitter-Client-Version: 1.01
(The meta.xml would be something like the following:)
<client>
<name>GoogleGadget</name>
<version>2.01</version> <!-- so we need to update! There's a new
one! -->
<author>
<name>Rick Measham</name>
<email>goo...@twitter.isite.net.au</email>
<twitter>RickMeasham</twitter>
</author>
<url>http://twitter.isite.net.au</url>
<twitter>GoogleGadget</twitter>
<description><[CDATA[
The Twitter Google Gadget brings all the fun of twitter to your Google
personalised homepage.
<a
href="http://fusion.google.com/add?feedurl=http%3A//twitter.isite.net.au/twitter.xml"><img
src="http://buttons.googlesyndication.com/fusion/add.gif" width="104"
height="17" border="0" alt="Add to Google"></a>
]]>
</client>
Just my $0.02 .. I'll set the above X-Headers until I get word otherwise :-D
Cheers!
Rick Measham
(RickMeasham)
Those X headers are exactly along the lines of what I was thinking.
Thanks for setting a sane de-facto standard!
--
Alex Payne
Obvious
http://twitter.com/al3x
Woowoo! You should already have a pile of requests using them .. I'm
also setting the X-Forwarded-For header as my Google Gadget needs a
gateway to turn request parameters into basic auth (though I may be able
to get it to do login-auth and avoid that .. Mmmm)
I've put the header information on the API Docs wiki
(http://twitter.pbwiki.com/API-Docs) but noted that they're only in
their infancy :)
Anyone else, feel free to comment .. especially on the meta XML.
Cheers!
Rick Measham
Oh, that's rather good, Rick. I was going to have a more standard
User-Agent string, but now you've upped the bar. On second thought,
now you've given me more work -- dammit! ;)
On Mar 21, 8:27 pm, "Ed Finkler" <funkat...@gmail.com> wrote:
> > href="http://fusion.google.com/add?feedurl=http%3A//twitter.isite.net.au/tw..."><img
> > src="http://buttons.googlesyndication.com/fusion/add.gif" width="104"
> > height="17" border="0" alt="Add to Google"></a>
> > ]]>
> > </client>
>
> > Just my $0.02 .. I'll set the above X-Headers until I get word otherwise :-D
>
> > Cheers!
> > Rick Measham
>
> > (RickMeasham)
>
> Oh, that's rather good, Rick. I was going to have a more standard
> User-Agent string, but now you've upped the bar. On second thought,
> now you've given me more work -- dammit! ;)
>
> --
> - Ed Finklerhttp://funkatron.com/- Hide quoted text -
>
> - Show quoted text -
The inclusion of the headers was in readiness for including it in the
site and feeds .. it's not there yet :)
BTW: Alex .. Just occurred to me that this 'source' isn't in the JSON or
XML yet.
Cheers!
Rick Measham
I've added them to TwitterPost, but I'm still seeing "from web."
--
Alex Payne
Obvious
http://twitter.com/al3x
http://twitter.pbwiki.com/API-Docs
in the near future?
I'm holding off on a "real" release of my WordPress integration plugin
because I want to include the proper headers. If I know they will
begin working automagically in the future, I would go ahead and
release it now.
Thanks,
--Alex King
On Mar 25, 7:53 pm, Alex Payne <a...@al3x.net> wrote:
> You got it, Mario. We'll let people know when we start approving
> third-party applications to show up as the source on the web site.
> It should be tied into the release of our AuthSub/Flickr-auth system
> that Blaine has made mention of on this list.
>
> --
> Alex Payne
> Obvioushttp://twitter.com/al3x
>
> On Mar 25, 2007, at 6:08 PM, Mario Menti wrote:
>
--
Thommy Mewes
"the Twitter engineers are working an authentication scheme similar
to Google’s AuthSub or Flickr’s API Authentication. This will have
added benefit of registering third-party applications to better
promote them on the site. The Development Talk group will be
notified when this authentication scheme is ready for testing."
We're not quite there yet. Thanks!
--
Alex Payne
Obvious
http://twitter.com/al3x
I'm doing the triQQr tool for windows and extending it to use the new
api functions.
That sounds good - do you have a time frame for this? Cause I had
inserted a like to my tools homepage and I am justing dropping this
behavior for the next version.
and keep the servers running ;)
--
Siegfried // http://triQQr.de