Hi Jonathan,
This is being investigated by our engineers at the moment. We'll be posting
updates to this ticket on our issue tracker:
http://code.google.com/p/twitter-api/issues/detail?id=1650
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, May 18, 2011 at 5:42 PM, Jonathan Strauss <jonat...@awe.sm> wrote:
> I'm totally with you guys on the value of switching to web intents,
> and we recommend all our customers doing new implementations use them.
> However, there are just too many legacy implementations against the
> "old hack", as Taylor deemed it, for you to expect everyone to switch
> over in such a timeframe. For a very long time the /?status= method
> was the only way to tweet from a website and web intents are only a
> few months old, so I hope you guys don't diminish the priority of
> fixing this bug just because you want to force everyone to the new way
> of doing things.
>
> -jonathan
>
> On May 18, 7:50 am, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
> > Hi Omar,
> >
> > Sorry for the confusion -- we recommend Web Intents as we've developed
> the
> > Tweet Intent specifically for this purpose -- let us know what tweaks you
> > think the display needs to "look good" in a full browser tab. Intents are
> > optimized to load quickly and service the user's intent as efficiently as
> > possible -- the old way requires a more significant load time and invites
> > the user to engage in all kinds of other fun Twitter activity aside from
> > tweeting -- maybe they'll even forget why you sent them there in the
> first
> > place.
> >
> > This is a bug and while I don't have an ETA on when it will be fixed, it
> was
> > not intentional and this old hack has not been deprecated.
> >
> > @episod <http://twitter.com/episod> - Taylor Singletary
> >
> >
> >
> >
> >
> >
> >
> > On Tue, May 17, 2011 at 5:34 PM, omegdadi <omegd...@gmail.com> wrote:
> > > Hey There,
> >
> > > +1. This issue is affecting all of our products at the moment. I can't
> > > find any notification anywhere about this being deprecated today.
> > > Please restore this functionality. And allow us some time to migrate
> > > w/ a date in mind. If it's no longer going to be supported, we need to
> > > know sooner as we have clients waiting for an answer at the moment. We
> > > would like to use intents, but we need a full page to send the user to
> > > since we can't always open a popup window (ie from Flash.) and that
> > > page doesn't look good in a full browser tab.
> >
> > > Thanks,
> > > Omar
> >
> > > On May 17, 3:05 pm, Arnaud Meunier <arn...@twitter.com> wrote:
> > > > Hey Yahel,
> >
> > > > Meet Web Intents:http://dev.twitter.com/pages/intents(takea look on
> the
> > > > "intent/tweet" intent). It really is super easy to implement. For
> > > example:http://twitter.com/intent/tweet?text=foobar
> >
> > > > Arnaud / @rno <http://twitter.com/rno>
> >
> > > > On Tue, May 17, 2011 at 1:18 PM, Yahel Carmon <yah...@gmail.com>
> wrote:
> > > > > Hey,
> >
> > > > > We've just noticed that auto-populating tweets using
> > > > >http://twitter.com/home/?status=foobarnolonger works.
> >
> > > > > Has this feature been totally removed, or is this a temporary
> glitch?
> > > > > (Perversely,http://twitter.com/?status=foobarworks, but that was
> the
> > > > > older method that broke last year and we were told to add /home to
> fix
> > > it.)
> >
> > > > > I know we're supposed to move to the official Tweet button, but we
> have
> > > a
> > > > > very large scale CRM that still relies on the old method.
> >
> > > > > Please let me know ASAP, as we have a lot of broken tweet links in
> the
> > > > > wild.
> >
> > > > > Thanks,
> >
> > > > > Yahel
> >
> > > > > --
> > > > > Yahel Carmon
> > > > > (917) 445-3498
> > > > > Twitter:http://twitter.com/yahelc
> > > > > Facebook:http://facebook.com/yahel
> > > > > LinkedIn:http://www.linkedin.com/in/yahelc
> >
> > > > > --
> > > > > Twitter developer documentation and resources:
> > >https://dev.twitter.com/doc
> > > > > API updates via Twitter:https://twitter.com/twitterapi
> > > > > Issues/Enhancements Tracker:
> > > > >https://code.google.com/p/twitter-api/issues/list
> > > > > Change your membership to this group:
> > > > >https://groups.google.com/forum/#!forum/twitter-development-talk
> >
> > > --
> > > Twitter developer documentation and resources:
> https://dev.twitter.com/doc
> > > API updates via Twitter:https://twitter.com/twitterapi
> > > Issues/Enhancements Tracker:
> > >https://code.google.com/p/twitter-api/issues/list
> > > Change your membership to this group:
> > >https://groups.google.com/forum/#!forum/twitter-development-talk
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
