This happening on my application as well. I've tested on other applications
(TweetDeck, Tweetie) - and they all post "from web"

Yep, happens also on our application. Seems like a twitter bug - I verified we send
the correct 'source' parameter

Same here. The tweet shows the <source> element, but it does not appear on the website.

e.g. http://twitter.com/jaschroe/status/1966725471 and 
http://twitter.com/statuses/show/1966725471.xml

Note: TwitterBerry is not using OAuth.

Happening to me too on my old basic auth source parameter, tried using apps like
twhirl and noticed it's affecting them too.

With all the recent increase in Twitter API developers and ease of registering an OAuth application, we're 
seeing a large growth in the source parameter database. The logic that appends source parameters to updates 
caches all of the source names in one large object. This object recently surpassed 1MB which is interesting 
because it is the largest size of an object that fits in memcached. The lack of ability to cache this object was 
causing an enormous hit on the database degrading performance.

The quick solution was to disable source parameters so that engineers didn't need to give up their weekend. 
This will be fixed as soon as possible, likely early in June 1 workday.

Cool, thanks for the update. 

Seeing that issue with my app as well. this effects only Oauth applications. Tweetdeck and tweetie still puts out 
source.

This seems to be failing with OAUTH as well.  Mine was working fine 2 days ago and
now it only says "from web" instead of from my application.

I have two apps and I know one fails for sure, I haven't tested the 2nd one yet but
I'm guessing that will fail too.

My system does not use OAuth, rather the standard 'Basic Auth' and is not functional
here.  I think the issue  igudo1 on comment #5 likely applies to all source
parameters no matter what method of auth is used.

today is june 2,when will this issue be fixed?We are waiting all the time.

> today is june 2,when will this issue be fixed?We are waiting all the time.

I started this thread to question. You earn the right to <i>complain</i> after you
start paying for the service.

Due to problems with other *critical* code we've had to delay deployment of this fix
until tomorrow. Thanks again for your continued patience.

>You earn the right to <i>complain</i> after you start paying for the service.

I sincerely hope that's not the attitude Twitter has for it's users and third-party developers.

When the fix goes live - are all posts that have been submitted not from the Web
going to change the correct Application or will it still say web?

I'm using TweetDeck since a longtime.
Since two days i'm discovering that.
When i'm updating then it's appearing as web.
Albiet i'm using TweetDeck.
Please do it sooner thanks ! 

Honestly,  they will get to it when they can.  Yes it is kinda a pain, but your world
shouldn't come to an end when a Tweet isn't source'd from your app.  Come on people.

stevec317, thanks for that.

Really, it's not like you'll die or a forest will burn down to ashes if you don't see
"from <appname>". Get some perspective, people.

Noticed this is coming back now.

One question: Is the source data for apps from the past couple days always going to
be web? 

I ask because I want to know how much db scrubbing I need to do over at TweetStats.

Many thanks,

dpc (@dacort)

Damon,
Yes, these statuses will forever be "from Web".

(No comment was entered for this change.)

Using a new application with Basic Auth, I'm still seeing "web" as the source.

I'm using the Twitterizer API, and if I send the source as "Twitterizer", the source
shows up on the website as "Twitterizer".  If I send the source as "Quitter" (the
name of my application), the source shows up as "web".

I've reproduced the issue using CURL.

I'm wondering if updates from sources that have not shown up before are having a problem.

Is Quitter registered with Twitter as an application either through the OAuth tokens
or manually via email with HTTP Auth?

I have the same problem with Comment with the Basic Auth, I have registered the 
application name, but when i post the status with the source parament and the app 
name, it do not show my app name and show the "web", Twitterizer is ok.
 how can i do ? must do the OAuth process? what do u mean  about manually via email 
with HTTP Auth?  

I actually have the same question. I am using basic Auth but can't append my app in the 
from source. Anyone care to comment on how this can be done - other than using oAuth?

Twitter disabled source parameter registration for non-OAuth.

Before the OAuth API was available to use Twitter.com developers had a manual email
process whereby developers could email Alex Payne and get a response with the valid
"source" code to put in your API calls.  Alas that process was abandoned when OAuth
beta came out to encourage people to use the OAuth API if starting from scratch. 
Thus if you do not already have a Twitter source id for the HTTP Auth API already,
then you will not be able to do this without moving to the OAuth API.

Please see official announcement sent out by Twitter developers a couple of months back:
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/ce57405a08483877/077165f18da99ff7?lnk=raot

HTH and sorry I couldn't give you better news.
Susan