source name has switch to web

3 views
Skip to first unread message

Adrian

unread,
May 31, 2009, 4:19:10 AM5/31/09
to Twitter Development Talk
Hi, all preexisting and newly added tweets with source Twitya have
changed to Web.

Tweets are added using 'source=twitya' in the post querystring as per
usual.

JakeS

unread,
May 31, 2009, 2:29:35 PM5/31/09
to Twitter Development Talk
This appears to be an issue for almost all clients. My client's
(PockeTwit) source parameter is no longer working either.

JB

unread,
May 31, 2009, 2:19:10 PM5/31/09
to Twitter Development Talk
Both of my OAuth applications are also showing as being "from web"
today...
not using source parameter.

Brooks Bennett

unread,
May 31, 2009, 5:37:38 PM5/31/09
to Twitter Development Talk
Chiming in that this is an issue for me as well...

Chad Etzel

unread,
May 31, 2009, 6:27:48 PM5/31/09
to twitter-deve...@googlegroups.com
Ditto.
http://jazzychad.com/meteor/sources.php is much less interesting now :)
Chad

Peter Denton

unread,
May 31, 2009, 6:28:41 PM5/31/09
to twitter-deve...@googlegroups.com
you're funny
--
Peter M. Denton
www.twibs.com
in...@twibs.com

Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c


Jesse Stay

unread,
May 31, 2009, 7:51:17 PM5/31/09
to twitter-deve...@googlegroups.com

Cameron Kaiser

unread,
May 31, 2009, 8:06:18 PM5/31/09
to twitter-deve...@googlegroups.com
> http://staynalive.com/articles/2009/05/31/where-is-twitters-emergency-response-system/

This isn't exactly an emergency.

It's annoying as hell, it sucks not having tracking and I hope they fix it
quickly. But this is different than, say, someone swiping passwords.

--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * cka...@floodgap.com
-- Statistics means never having to say you're certain. -----------------------

Jesse Stay

unread,
May 31, 2009, 8:12:53 PM5/31/09
to twitter-deve...@googlegroups.com
On Sun, May 31, 2009 at 6:06 PM, Cameron Kaiser <spe...@floodgap.com> wrote:
This isn't exactly an emergency.

It's annoying as hell, it sucks not having tracking and I hope they fix it
quickly. But this is different than, say, someone swiping passwords.

I know it's an emergency for Damon, or anyone else whose app relies on those sources.

Jesse 

Cameron Kaiser

unread,
May 31, 2009, 8:17:25 PM5/31/09
to twitter-deve...@googlegroups.com
> > http://staynalive.com/articles/2009/05/31/where-is-twitters-emergency-response-system/
> >
> > This isn't exactly an emergency.
> >
> > It's annoying as hell, it sucks not having tracking and I hope they fix it
> > quickly. But this is different than, say, someone swiping passwords.
>
>
> I know it's an emergency for Damon, or anyone else whose app relies on those
> sources.

That's exactly my point -- it's not an emergency to Twitter, it's not part
of their core functionality and they've never made it as such. It's a nice
add-on they put in for developers to get props. I like it, and I take
advantage of it, and I'm bummed it doesn't work right now, but I can't see
where proportionately this falls on the same scope as, say, users unable to
fetch timelines. If that were going on and no one were fixing it, I'd be
right there with you. That's core.

--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * cka...@floodgap.com

-- You can't have everything. Where would you put it? -- Steven Wright --------

Peter Denton

unread,
May 31, 2009, 8:19:06 PM5/31/09
to twitter-deve...@googlegroups.com
I think it would be hard to develop a model where people pay for uptime support. 1) if I dont pay, and you and Ian at tweetDeck do, is twitter going to break the feature for non-payers (me?) 2) If this were a big time emergency and they couldnt fix it right away, are paying devs going to sue because they were guaranteed uptime. I understand its annoying, just calling out Ev or Alex for going to Maui just seems a little rude.

Jesse Stay

unread,
May 31, 2009, 8:42:01 PM5/31/09
to twitter-deve...@googlegroups.com
On Sun, May 31, 2009 at 6:17 PM, Cameron Kaiser <spe...@floodgap.com> wrote:
> I know it's an emergency for Damon, or anyone else whose app relies on those
> sources.

That's exactly my point -- it's not an emergency to Twitter, it's not part
of their core functionality and they've never made it as such. It's a nice
add-on they put in for developers to get props. I like it, and I take
advantage of it, and I'm bummed it doesn't work right now, but I can't see
where proportionately this falls on the same scope as, say, users unable to
fetch timelines. If that were going on and no one were fixing it, I'd be
right there with you. That's core.

My point was that developers should be able to pay to get response in situations like this.  If Damon wanted to get support and at least get an answer that they were aware of the situation, he could.  Right now those developers reliant on this are stuck in limbo and there's nothing they can do about it.  There is no way to get prioritized support in situations like this. 

@Jesse

Jesse Stay

unread,
May 31, 2009, 8:45:25 PM5/31/09
to twitter-deve...@googlegroups.com
On Sun, May 31, 2009 at 6:19 PM, Peter Denton <peterm...@gmail.com> wrote:
I think it would be hard to develop a model where people pay for uptime support. 1) if I dont pay, and you and Ian at tweetDeck do, is twitter going to break the feature for non-payers (me?) 2) If this were a big time emergency and they couldnt fix it right away, are paying devs going to sue because they were guaranteed uptime. I understand its annoying, just calling out Ev or Alex for going to Maui just seems a little rude.

I'm not asking for paid uptime - I'm asking for paid support - there's a difference.  I should be able to at least guarantee a response from either a support rep or developer at Twitter that something is being done.  I'd pay for that, and it would give me a lot more confidence in Twitter.

I wasn't calling out Ev or Alex for going to Maui - I even congratulated them for getting some deserved time-off.  I'm glad they're there.  I'm simply asking what do we do in situations like these?  When this affects my app next time, how can I get in touch with Twitter?

@Jesse 

John Kalucki

unread,
May 31, 2009, 10:54:35 PM5/31/09
to Twitter Development Talk
We're aware of this. Twitter developers and operations have been
working quite a bit this weekend on problems related to this issue and
others mentioned on the Twitter Status blog. Rough plans have been
made to fully address the status source tag on Monday, after people
have had some rest, but it's not yet clear when the issue will be
fixed.

-John Kalucki
Services, Twitter, Inc.

Doug Williams

unread,
Jun 1, 2009, 12:17:55 AM6/1/09
to twitter-deve...@googlegroups.com
Please watch this thread for updates: http://code.google.com/p/twitter-api/issues/detail?id=634

Thanks,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages