> Your definition of "time to adjust" may not be ours. Twitter has, to > be honest, a fairly crappy reputation for changing API behavior. While > some of that was surely driven by performance concerns, I don't see > how this could be. This doesn't help the rep. > > Please, do not enable this by default, *ever*. Don't change behavior > unless it is necessary. Add a new API method, or make recent results > the default and keep it that way. > > If you're advocating for developers, advocate for making us do less > work to maintain current functionality, please.
This is spot on. It's not that I think the idea itself is bad -- I'm all for more relevant search results *when relevance is what's requested*. Right now, every app that queries the Search API expects time-oriented results because that's what we got before. Making this the new default is needless dev chaos, *and* I haven't heard if there is even a way to opt back to the old behaviour if this becomes the ill-advised default anyway. I'd love to support this feature, in the appropriate context, when it makes sense to do so. I don't want to have to code around it as the new, unsolicited default when it doesn't. -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- FORTUNE: Good day for romance, but try a single person this time. ---------- To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
