Hi all,

Just a heads up. Yesterday we deployed some code that inserts
rel="nofollow" into the <a> tag surrounding the source app's name on
the Twitter website.

This seems to have also made it through to the API responses, as you
may now start seeing things like:
&lt;a href=&quot;http:\/\/ubertwitter.com&quot;
rel=&quot;nofollow&quot;&gt;UberTwitter&lt;\/a&gt;
in the source value.

Tweets coming from web do not have this inserted:
&lt;a href=&quot;http:\/\/twitter.com\/&quot;&gt;web&lt;\/a&gt;

I am just informing you in case you have source parsing code which
depended on the format of the previous structure. I am not sure that
this is a permanent change for API responses, but while this is being
decided I wanted to let you know.

Thanks,
-Chad

Reply via email to