[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-22 Thread Emrah KAVUN

Hi,

If it can be in any help, I have a kind of private url shortening
service that I could adapt to your needs. www.fwd.li.

I can't really design the page because I am blind (the reason why there
is no logo). However it might come handy to have an url shortening api
service designed individually for your apps.

I currently support plain text and xml output.

Cheers,
Emrah
P.s.: if someone is interested in making a logo, you're welcome. If
someone else would like to carry on the dev, welcome as well. :)

TjL wrote:
 On Tue, May 19, 2009 at 10:48 PM, Cameron Kaiser spec...@floodgap.com wrote:
   
 The best you can do is use the bit.ly API to un-shorten the link and
 grab your URL key from there.

 Have a look at the /expand method in their API:
 http://code.google.com/p/bitly-api/wiki/ApiDocumentation
   
 Or, implement your own URL shortening scheme (either internally, or using
 a specific service that meets your needs), with the assumption that the
 shortening will occur and at least this way you can control the situation
 under how the shortening is handled.
 

 I believe that Twitter will shorten links over 30 characters, but this
 does not *always* seem to be the case.

 Your best bet (IMO) is to determine which service you want to use and
 shorten the links yourself. I started putting together a list of them
 not too long ago and came up with these:

 bit.ly
 xrl.us
 tr.im
 snipr.com
 tinyarro.ws
 tinyurl.com
 icanhaz.com
 budurl.com

 There are, no doubt, others.
   



[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-22 Thread Nancy Miracle
Hi Emrah, I ended up using bitly, but thanks.

On Fri, May 22, 2009 at 3:10 AM, Emrah KAVUN e...@ekanet.net wrote:


 Hi,

 If it can be in any help, I have a kind of private url shortening
 service that I could adapt to your needs. www.fwd.li.

 I can't really design the page because I am blind (the reason why there
 is no logo). However it might come handy to have an url shortening api
 service designed individually for your apps.

 I currently support plain text and xml output.

 Cheers,
 Emrah
 P.s.: if someone is interested in making a logo, you're welcome. If
 someone else would like to carry on the dev, welcome as well. :)

 TjL wrote:
  On Tue, May 19, 2009 at 10:48 PM, Cameron Kaiser spec...@floodgap.com
 wrote:
 
  The best you can do is use the bit.ly API to un-shorten the link and
  grab your URL key from there.
 
  Have a look at the /expand method in their API:
  http://code.google.com/p/bitly-api/wiki/ApiDocumentation
 
  Or, implement your own URL shortening scheme (either internally, or
 using
  a specific service that meets your needs), with the assumption that the
  shortening will occur and at least this way you can control the
 situation
  under how the shortening is handled.
 
 
  I believe that Twitter will shorten links over 30 characters, but this
  does not *always* seem to be the case.
 
  Your best bet (IMO) is to determine which service you want to use and
  shorten the links yourself. I started putting together a list of them
  not too long ago and came up with these:
 
  bit.ly
  xrl.us
  tr.im
  snipr.com
  tinyarro.ws
  tinyurl.com
  icanhaz.com
  budurl.com
 
  There are, no doubt, others.
 




[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-20 Thread TjL

On Tue, May 19, 2009 at 10:48 PM, Cameron Kaiser spec...@floodgap.com wrote:

 The best you can do is use the bit.ly API to un-shorten the link and
 grab your URL key from there.

 Have a look at the /expand method in their API:
 http://code.google.com/p/bitly-api/wiki/ApiDocumentation

 Or, implement your own URL shortening scheme (either internally, or using
 a specific service that meets your needs), with the assumption that the
 shortening will occur and at least this way you can control the situation
 under how the shortening is handled.

I believe that Twitter will shorten links over 30 characters, but this
does not *always* seem to be the case.

Your best bet (IMO) is to determine which service you want to use and
shorten the links yourself. I started putting together a list of them
not too long ago and came up with these:

bit.ly
xrl.us
tr.im
snipr.com
tinyarro.ws
tinyurl.com
icanhaz.com
budurl.com

There are, no doubt, others.


[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-20 Thread Nancy M

They were not doing this (at least to my URLS) on Monday and they were
on Tuesday...

Best,
Nancy



On May 19, 9:59 pm, Chad Etzel jazzyc...@gmail.com wrote:
 On Tue, May 19, 2009 at 10:47 PM, Abraham Williams 4bra...@gmail.com wrote:

  When did Twitter switch to usingbit.lyanyways?

 Sometime last week, if I recall.  Looking at the stats for spammy
 links is incredible... people will click anything (tho I can't tell
 how many of the clicks are actually other twitter link tracking
 services like twitturly, etc).
 -Chad


[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-20 Thread Nancy M

Thanks very much for the advice!

I've done as you suggested and added a call to the bit.ly API to
shorten our URL and that seems to be working.

If this is a feature, it is a very irritating one,  I must say, but
oh well.

Best,
Nancy




On May 20, 9:04 am, Howard Siegel hsie...@gmail.com wrote:
 On Wed, May 20, 2009 at 06:59, TjL luo...@gmail.com wrote:

  Your best bet (IMO) is to determine which service you want to use and
  shorten the links yourself. I started putting together a list of them
  not too long ago and came up with these:

 bit.ly
  xrl.us
  tr.im
  snipr.com
  tinyarro.ws
  tinyurl.com
  icanhaz.com
  budurl.com

  There are, no doubt, others.

 is.gd


[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-19 Thread Chad Etzel

You are correct, Twitter is doing the bit.ly conversion on their end.
They automatically shorten URLs based on some set of metrics (I think
character length and formatting have something to do with it), and
there's no (current) way to suppress this behavior when posting.

The best you can do is use the bit.ly API to un-shorten the link and
grab your URL key from there.

Have a look at the /expand method in their API:
http://code.google.com/p/bitly-api/wiki/ApiDocumentation

-Chad

On Tue, May 19, 2009 at 6:04 PM, Nancy M nmira...@gmail.com wrote:

 I'm using perl (NET::Twitter) to submit a status update.  The update
 consists of a text string and a URL of our tracker module.  The
 purpose of this is to allow us to track any sales that arise as a
 result of the clickthrough and associate them with the source.

 It appears that the URL is being changed:

 The source reads (for instance)
 Added Item: 5.25 carats princess diamond pave engagement ring new
 http://tias.com/cgi-bin/tw.fcgi/itemKey=3923612043

 where http://tias.com/cgi-bin/tw.fcgi/itemKey=3923612043 is the key to
 our tracker and the page that is eventually served is
 http://www.earthling.com/13527/PictPage/3923612043.html  (that latter
 was determined from http://www.earthling.com/13527/PictPage/3923612043.html)
 which is a very very handy tool, I must say.

 However, when I interrogate the text from twitter, it turns out that
 our URL has been changed to a bit.ly one:

 p $result-{text}
 Added Item: 5.25 carats princess diamond pave engagement ring new
 http://bit.ly/11qkU1

 I've dug down through the LWP::userAgent level and it seriously
 appears that this change is happening at Twitter

 Firstly, it isn't on our bit.ly account (and I really don't want to
 use bit.ly for this) and second why is this happening?

 Any advice?

 Am I missing something critical in the documentation someplace?



[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-19 Thread Abraham Williams
If you don't want to use bit.ly shorten the urls with the shortener of your
choice first.



When did Twitter switch to using bit.ly anyways?

On Tue, May 19, 2009 at 17:24, Chad Etzel jazzyc...@gmail.com wrote:


 You are correct, Twitter is doing the bit.ly conversion on their end.
 They automatically shorten URLs based on some set of metrics (I think
 character length and formatting have something to do with it), and
 there's no (current) way to suppress this behavior when posting.

 The best you can do is use the bit.ly API to un-shorten the link and
 grab your URL key from there.

 Have a look at the /expand method in their API:
 http://code.google.com/p/bitly-api/wiki/ApiDocumentation

 -Chad

 On Tue, May 19, 2009 at 6:04 PM, Nancy M nmira...@gmail.com wrote:
 
  I'm using perl (NET::Twitter) to submit a status update.  The update
  consists of a text string and a URL of our tracker module.  The
  purpose of this is to allow us to track any sales that arise as a
  result of the clickthrough and associate them with the source.
 
  It appears that the URL is being changed:
 
  The source reads (for instance)
  Added Item: 5.25 carats princess diamond pave engagement ring new
  http://tias.com/cgi-bin/tw.fcgi/itemKey=3923612043
 
  where http://tias.com/cgi-bin/tw.fcgi/itemKey=3923612043 is the key to
  our tracker and the page that is eventually served is
  http://www.earthling.com/13527/PictPage/3923612043.html  (that latter
  was determined from
 http://www.earthling.com/13527/PictPage/3923612043.html)
  which is a very very handy tool, I must say.
 
  However, when I interrogate the text from twitter, it turns out that
  our URL has been changed to a bit.ly one:
 
  p $result-{text}
  Added Item: 5.25 carats princess diamond pave engagement ring new
  http://bit.ly/11qkU1
 
  I've dug down through the LWP::userAgent level and it seriously
  appears that this change is happening at Twitter
 
  Firstly, it isn't on our bit.ly account (and I really don't want to
  use bit.ly for this) and second why is this happening?
 
  Any advice?
 
  Am I missing something critical in the documentation someplace?
 




-- 
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.


[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-19 Thread Cameron Kaiser

 The best you can do is use the bit.ly API to un-shorten the link and
 grab your URL key from there.
 
 Have a look at the /expand method in their API:
 http://code.google.com/p/bitly-api/wiki/ApiDocumentation

Or, implement your own URL shortening scheme (either internally, or using
a specific service that meets your needs), with the assumption that the
shortening will occur and at least this way you can control the situation
under how the shortening is handled.

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- MOVIE IDEA: The E-mail Signature Who Loved Me --


[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL

2009-05-19 Thread Chad Etzel

On Tue, May 19, 2009 at 10:47 PM, Abraham Williams 4bra...@gmail.com wrote:

 When did Twitter switch to using bit.ly anyways?

Sometime last week, if I recall.  Looking at the stats for spammy
links is incredible... people will click anything (tho I can't tell
how many of the clicks are actually other twitter link tracking
services like twitturly, etc).
-Chad