Because sources are displayed on a number of platforms, we'd like to keep them as simple and static as possible. That way they remain easily formatted and cached.
On Fri, Oct 24, 2008 at 6:18 AM, Phil <[EMAIL PROTECTED]> wrote: > > I'm not sure I follow. Forgive me, I'm relatively new at this sort of > thing. > > I realize that Twitter has lots of irons in the fire...no doubt of > that. Would there be any interest in working on a more involved source > parameter? The result may lead to enhancing any monetization goals for > Twitter...I'm just sayin'. Thanks. > > On Oct 23, 10:51 am, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> Well, you could always examine the referrers that you get and see if >> they're coming from a tweet's permalink URL. >> >> >> >> On Thu, Oct 23, 2008 at 6:24 AM, Phil <[EMAIL PROTECTED]> wrote: >> >> > That's it? Can you suggest some alternatives? For the sake of >> > 'development' isn't there more that can be discussed? >> >> > On Oct 22, 12:39 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> >> Apologies, but we want to keep the source parameter links as simply >> >> static URLs to sites and products. >> >> >> On Wed, Oct 22, 2008 at 9:42 AM, Phil <[EMAIL PROTECTED]> wrote: >> >> >> > Can get more from the source feature on a tweet for my API. Can that >> >> > text be altered to perform a different function? >> >> >> > Specifically, the source function currently allows a click through to >> >> > the website. A function that is the same for any and all tweets >> >> > originating from the API. >> >> >> > Can the text/function be modified so that a click will take the user >> >> > to a function on the website specifically related to that individual >> >> > tweet, re: a rating function? >> >> >> -- >> >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
