If you take a step back and think about popular Web services, be they RSS feed readers, communications tools, social networks, link aggregators or lifestreams, their core deliverable is data. The way they are differentiating is through enabling that data to be accessed by more people, and manipulated in new ways. But as their popularity grows, with more users, more features, and richer media, be it photographs, music, or video, the data can spiral out of control, demanding larger databases, more servers, faster networks, better caching... you name it. And if they don't deal with it? Death. The services can slow down or crash, and users will move on.Not every Web service has had the structure, the planning or the money of Google, so not every site can keep going with all features, saving all data, forever and ever.
Twitter's recent struggles keeping up with user growth and resulting issues have been extremely visible. To cope with the load, the microblogging service started whacking features one by one. At various points, Twitter turned off the @Replies tab, removed pagination, reduced the number of times that external services could access its API, and eliminated the use of instant messaging services. Limping along, Twitter has slowly returned to speed, as one by one, most of the pieces have been turned back on, but not everybody is happy about it.
But don't think Twitter's alone. Just yesterday, I logged into SocialThing, a lifestreaming service thought by many to have a better GUI for FriendFeed, and found that it had been forced to scale back its offering as users grew.
Rather than supporting many different services, SocialThing only lets me include Twitter, Flickr and Facebook, with LiveJournal, Pownce and Vimeo also being options. But the many other sites I use? Blocked. They write, "We have had to temporarily disable a few of our services, due to user growth. We hope to have them back up soon!"

At a time when FriendFeed is gaining notoriety for supporting rapid access to the streaming of 35 different services without slowdown, that kind of scaling down can't be good.
For Shyftr, a new RSS reader I've covered quite a bit here, they too are seeing the challenge of user growth. As we saw with Mergelab's closure, the act of tracking thousands of feeds and storing their data for an infinite amount of time can be very challenging. I've already seen Toluu upgrade their server farm, and Shyftr has done the same recently. But more changes are coming to handle the rising user base.
As founder Dave Stanley wrote in a blog post, Notice: System Changes and New Implementations, Shyftr will be removing "a substantial portion of backdated data" which should reduce recent issues with database performance, and let them turn on services that had been disabled thanks to site slow-downs, including search. As he said, "It's time we trim some fat while making the system leaner, more efficient, and better prepared for future growth."
If you have a Shyftr login, see the full post:
Notice: System Changes and New Implementations
I expect that the rules for small companies are different than the rules for big companies. Twitter has gotten such a bad response for its issues in part due to its popularity, and in part due to its criticality for some communications. For smaller sites like Shyftr and SocialThing, users are more likely to be accepting of temporary scale-backs or data removal. But if the big guys like Yahoo!, Google, Apple or Microsoft, took the route of deleting data and reducing features, it'd be likely that we'd see an uproar.
So how should they handle it? Do you, as a user, have an absolute right to all your archives, ever? Do you have the right to demand that once features are added, they never be removed? And do services have an obligation to scale up their hardware and infrastructure to keep you happy? Would you help fund their upgrades? Handling growth is critical, in my opinion, and those best prepared for scaling will leapfrog those who are forced to "lay off" their data. We're wishing Twitter luck, but there are a lot of smaller services struggling with similar issues.
More and more often, I'm running into items I want to share, but might not be detailed enough to generate a full post. So here are a few things that caught my eye over the last few days. If it makes sense, maybe I'll make this a recurring feature.
Considering almost ninety percent of the FriendFeed team has a Google pedigree, it's no surprise they made aspects most associated with Google, such as scalability and simplicity a priority. Also a big thing at Google? Search. FriendFeed's search function indexes in real-time, and can be diced every which way, including by service.









When
TweetSmart is essentially an extension of Twitter's direct message service, or DMs, with some interesting wrinkles thrown in. TweetSmart users are encouraged to send links to the TweetSmart Twitter account, and to use one of 11 categories provided by the site, ranging from mortgage and real estate to Web, technology and social media. Depending on the category you choose, your link will be properly tagged, featuring the icon of the category you selected.
Today's news on
This morning,
It's only Wednesday, but it's already been a very big week for Yuvi Panda of TheStatBot. After 

Not eager to sit still, 

Not too long ago, 
When Gabe Rivera
Blog widgets are seemingly a dime a dozen these days, but offering a strong search function on your Web site is a must, regardless of how cleanly you've laid out your archive pages, or how well you've implemented tags or labels. A little over a week ago, after seeing 
Acting as a front-end for 

Meanwhile, as Lijit is watching my site traffic for search activity, it's also monitoring standard blog tracking tools, including page views, how many visitors are coming, and where they are coming from. Combining the two facets of the service, from search to statistics, Lijit can tell me which countries search for what most frequently, what is the city that offers me the most visits (Mountain View, CA), and from what country did my most recent search terms originate. I can also see which pages proved most popular after search terms were entered.



One of the cooler things about the Bookmarklet is the ability to select pictures from the shared story, and add them as well. Once you have hit the "Share on FriendFeed" Bookmarklet, hover your mouse over any image on the page, and you will see a little rectangle pop up, saying "Share image on FriendFeed". Click once to get the picture added to your Bookmarklet in progress. Adding an image, or multiple images, if you choose, does not change the title or the comments being shared.




As the FriendFeed interface is spartan, so is FF To Go. But for most mobile phone users, this is expected. FF To Go shows three main tabs upon login, including "Friends", "Me" and "Everyone", and each option mirrors the same tabs on FriendFeed. Users can even navigate between each tabs by hitting 0, 1 or 2 on their cell phone after having logged in.