Letting Us Set the "From" Attribute To Our Program

93 views
Skip to first unread message

railhea...@gmail.com

unread,
Mar 14, 2007, 11:44:11 AM3/14/07
to Twitter Development Talk
I'd like to have the "From" attribute set to my application's name,
rather than "From web."

Any plans on opening this up to us?

RickMeasham

unread,
Mar 15, 2007, 5:28:12 PM3/15/07
to Twitter Development Talk
On Mar 15, 2:44 am, "railheaddes...@gmail.com"

<railheaddes...@gmail.com> wrote:
> I'd like to have the "From" attribute set to my application's name,
> rather than "From web."

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

unread,
Mar 15, 2007, 9:46:37 PM3/15/07
to twitter-deve...@googlegroups.com
We're discussing a solution for this internally, and we'll get back
to you ASAP.

--
Alex Payne
Obvious
http://twitter.com/al3x

bear

unread,
Mar 16, 2007, 1:42:46 AM3/16/07
to Twitter Development Talk
how does twitterific do it then?

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

Alex Payne

unread,
Mar 16, 2007, 11:13:05 AM3/16/07
to twitter-deve...@googlegroups.com
At the moment, Twitterific passes a special parameter to us when
updating, and we simply verify that it's the string we're looking
for. Dead simple, but decidedly manual. We've got something better
in the works.

Ed Finkler

unread,
Mar 16, 2007, 7:28:08 PM3/16/07
to twitter-deve...@googlegroups.com
On 3/16/07, Alex Payne <al...@al3x.net> wrote:
>
> At the moment, Twitterific passes a special parameter to us when
> updating, and we simply verify that it's the string we're looking
> for. Dead simple, but decidedly manual. We've got something better
> in the works.

Awesome. I'm totally jealous of those Twitterriffic folks.

--
- Ed Finkler
http://funkatron.com/

kev...@newsgator.com

unread,
Mar 19, 2007, 2:26:01 PM3/19/07
to Twitter Development Talk
cool... i am looking for this as well!

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:

Ed Finkler

unread,
Mar 19, 2007, 4:09:51 PM3/19/07
to twitter-deve...@googlegroups.com
On 3/19/07, kev...@newsgator.com <kev...@newsgator.com> wrote:
>
> cool... i am looking for this as well!
>
> a user-agent addition could be a simple solt'n: Twitter-App-Name/
> TinyTwitter

Yes, actually, I plan on setting that header in the next version of
Spaz. Being a bit lazy atm with it.

Alex Payne

unread,
Mar 21, 2007, 4:35:39 PM3/21/07
to twitter-deve...@googlegroups.com
Please do start sending headers to us. It'll be most helpful for
planning our capacity.

--
Alex Payne
Obvious
http://twitter.com/al3x

Rick Measham

unread,
Mar 21, 2007, 5:26:41 PM3/21/07
to twitter-deve...@googlegroups.com
Alex Payne wrote:
> Please do start sending headers to us. It'll be most helpful for
> planning our capacity.

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)

Alex Payne

unread,
Mar 21, 2007, 6:00:24 PM3/21/07
to twitter-deve...@googlegroups.com
Rick,

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

Rick Measham

unread,
Mar 21, 2007, 6:40:27 PM3/21/07
to twitter-deve...@googlegroups.com
Alex Payne wrote:
> Those X headers are exactly along the lines of what I was thinking.
> Thanks for setting a sane de-facto standard!

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

Ed Finkler

unread,
Mar 21, 2007, 10:27:22 PM3/21/07
to twitter-deve...@googlegroups.com

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! ;)

kev...@newsgator.com

unread,
Mar 23, 2007, 2:25:39 PM3/23/07
to Twitter Development Talk
nicely done rick - i like!

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 -

Ed Finkler

unread,
Mar 23, 2007, 8:37:17 PM3/23/07
to twitter-deve...@googlegroups.com
BTW, I'm implementing the X-headers and meta.xml file in Spaz as of v 0.2.2.

Ordinal Malaprop

unread,
Mar 24, 2007, 2:58:02 PM3/24/07
to Twitter Development Talk
I have put in the X-headers in the current Twitterbox 0.3, and have
posted about it as well (for anyone who actually reads my nonsense).

railhea...@gmail.com

unread,
Mar 25, 2007, 4:27:35 PM3/25/07
to Twitter Development Talk
I've added them to TwitterPost, but I'm still seeing "from web."

Rick Measham

unread,
Mar 25, 2007, 4:59:39 PM3/25/07
to twitter-deve...@googlegroups.com
railhea...@gmail.com wrote:
> I've added them to TwitterPost, but I'm still seeing "from web."

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

Mario Menti

unread,
Mar 25, 2007, 6:08:43 PM3/25/07
to twitter-deve...@googlegroups.com
On 3/25/07, railhea...@gmail.com <railhea...@gmail.com> wrote:

I've added them to TwitterPost, but I'm still seeing "from web."


I think it will be a while until Twitter actually implement them at their end. At the moment, they're just "a sane de-facto standard", according to Alex..

Mario.

Alex Payne

unread,
Mar 25, 2007, 9:53:54 PM3/25/07
to twitter-deve...@googlegroups.com
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
Obvious
http://twitter.com/al3x

alexkingorg

unread,
Mar 26, 2007, 11:44:41 AM3/26/07
to Twitter Development Talk
Perhaps you could "bless" or modify the format proposed in the docs:

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

http://alexking.org

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:
>

tho...@mewes.org

unread,
Mar 29, 2007, 3:57:09 AM3/29/07
to Twitter Development Talk
Any news on this?

--
Thommy Mewes

Alex Payne

unread,
Mar 29, 2007, 11:31:54 AM3/29/07
to twitter-deve...@googlegroups.com
As per the recently released official API documentation:

"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

Siegfried Hirsch

unread,
Mar 29, 2007, 4:59:32 PM3/29/07
to twitter-deve...@googlegroups.com
2007/3/29, Alex Payne <al...@al3x.net>:

>
> As per the recently released official API documentation:
>
> "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!

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

Reply all
Reply to author
Forward
0 new messages