> Change breaks both expectations and code. It is inevitable.
I agree with this statement. However, there seems to be some confusion
over whether retweets will still be prefixed with RT. If retweets are
no longer prefixed with RT, then I do not understand why that change
is being made. You could do everything you are doing with the retweet
API; however, still ensure that retweets are prefixed with RT.

My concern is that there is nothing to force users to upgrade their
twitter applications, there is nothing to force applications to use
the retweet API (although, I agree most probably will) and for an
indeterminate amount of time users will still "retweet" by prefixing
their tweets with RT. If the retweet API would simply still prefix
retweets with RT, at least retweets messages would "look" consistent
and searches that relied upon the de-factor starndard of RT
@<username> would still work as expected.

I am personally excited about the retweet api, and the ability to
unambiguously tie a retweet back to the original tweet message;
however, as mentioned above I'm concerned that retweets will no longer
be prefixed with 'RT'.

- Chris

On Nov 12, 8:29 am, John Kalucki <jkalu...@gmail.com> wrote:
> The Retweet feature has many possible realizations. We've tried nearly
> every possible combination of all the functional dimensions as the
> feature evolved over many months. It's possible that what you saw was
> based on a snapshot of the current state of the feature, and the
> feature subsequently changed.
>
> In any case, what was in production earlier this week is the best
> indicator of what the feature will be moving forward. I'd also expect
> the feature to continue to evolve and new features to sprout up.
>
> Change breaks both expectations and code. It is inevitable. The
> Platform team prioritizes mitigation efforts for third-party apps, but
> a full mitigation isn't always possible. We can't gate all forward
> progress on perfect mitigation, or we'd pretty much never be able to
> ship a new feature. A bigger and better Twitter is ultimately better
> for the ecosystem, despite the knocks along the way.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Services, Twitter Inc.
>
> On Nov 12, 2:50 am, Walter Smulders <walter.smuld...@gmail.com> wrote:
>
> > In the examples that are shown in the developers preview for the RT
> > api these where prefixed with RT, was this done on purpose or did this
> > change after the examples where made public?
>
> > On Nov 11, 6:48 pm, John Kalucki <jkalu...@gmail.com> wrote:
>
> > > Search is aware of the need for a retweet operator, but the feature is
> > > unscheduled and completely speculative.
>
> > > In any case, Search will become less useful for this sort of
> > > repetitive complete corpus search. If you need all of something, or a
> > > sample of something, you should be moving to the Streaming API
> > > wherever possible.
>
> > > -John Kaluckihttp://twitter.com/jkalucki
> > > Services, Twitter Inc.
>
> > > On Nov 11, 9:39 am, Yaniv Golan <stu...@yanivgolan.com> wrote:
>
> > > > Thanks John,
> > > > this means that my app won't work anymore!
> > > > streaming api makes my life very hard
> > > > hence i need to search for links and then extract them, this is very
> > > > resource demanding to do on the fly
> > > > while with search API i can search then extract and then search again
> > > > i could use queue system but then again i will lose all the real time
> > > > fun
> > > > will there be a filter in the search api for retweets like there is
> > > > for links?
> > > > that could solve all my problems
>
> > > > On Nov 11, 7:22 pm, John Kalucki <jkalu...@gmail.com> wrote:
>
> > > > > Retweets do not modify the original text in any way. There is no RT to
> > > > > search upon.
>
> > > > > There is a feed of all public retweets on the Streaming API, but it is
> > > > > not generally available. Instead, you can request a sample of all
> > > > > statuses and filter for those that are retweets.
>
> > > > > -John Kaluckihttp://twitter.com/jkalucki
> > > > > Services, Twitter Inc.
>
> > > > > On Nov 11, 8:58 am, Yaniv Golan <stu...@yanivgolan.com> wrote:
>
> > > > > > oh...
> > > > > > that's cool :)
> > > > > > Thanks i really got wםrried for a sec
>
> > > > > > On Nov 11, 5:08 pm, Walter Smulders <walter.smuld...@gmail.com> 
> > > > > > wrote:
>
> > > > > > > With the retweet function the status text will still be prefixed 
> > > > > > > with
> > > > > > > RT
>
> > > > > > > On Nov 11, 11:59 am, Yaniv Golan <yango2...@walla.co.il> wrote:
>
> > > > > > > > Hi
> > > > > > > > I'm using twitter search API to search statuses with retweet
> > > > > > > > expressions (e.g RT VIA) with the link filter
> > > > > > > > i search the documentation over and over but i can't find any 
> > > > > > > > solution
> > > > > > > > to what will happen after the retweet will rollout completely 
> > > > > > > > (the
> > > > > > > > retweet expressions as we knew them will disappear and there is 
> > > > > > > > no
> > > > > > > > other API method to much my search criteria)
> > > > > > > > what should i do to get all the retweets that contains links?
> > > > > > > > thanks

Reply via email to