As more wireless carriers adopt Google Android, many new consumers ask frequently how to do common tasks on their Android phone. This section is dedicated to offering Android Advice to new and experienced Android consumers. There will be more to come, however here are the top 6 frequently asked questions by new Android users:

1. What Android apps should I download?

There are many list all over the web, even many on our website (coming from Blackberry to Android see this list). We'll list a few must have best Android apps to get you started:

• Must Have: Astro File Manager, use this app to browse files on your SD card. Bar Code Scanner, use this app to scan the QR bard codes with all of our reviews to quick link you to apps in the Android Market!
• Task Management: TasKiller
• Battery/Power Management: Power Manager or Screebl
• Email: K9 Mail or Exchange by Touchdown
• Music: Pandora or Meridian Player
• Home Screen Customization: aHome or SlideScreen
• Productivity & Note-Taking: Astrid or Evernote

Keep visiting www.AndroidTapp.com for the best Android app recommendations.

2. How do I setup email accounts?

First gather your POP3 or IMAP protocol access information. Launch Email > type email address and password > Choose either POP3 or IMAP account > enter Incoming POP3 or IMAP protocol information > enter Outgoing information > choose whether email account is default.

3. How do I save battery power?

Try turning off Bluetooth, Wifi and GPS when not needed. Try to minimize update intervals of some apps such as Facebook and Twitter from the settings menu. There are apps to help manage battery power for you such as Power Manager.

4. How do I Customize my phone?

There are many home screen customization apps to give a completely different experience; popular apps include aHome, Open Home and SlideScreen.

5. How do I set Ringtones?

Either purchase them from sources like Amazon MP3 or download free with Mabilo Ringtones.

To place your own MP3 songs as ringtones go to the Android Market to download Rings Extended. Plug your phone to computer via USB cable. An icon will appear in the top left notification bar, slide the bar down (this is called the window shade). Tap USB connected > Mount > on your computer a new drive will appear > drag your own MP3 files to the drive > tap home button > Menu button > Settings > Sound & display > Phone ringtone > choose Rings Extended to browse your MP3 files on the phone.

6. How do I import my Contacts from SIM card?

From home screen tap Menu > Contacts > Menu > Import contacts > Import All (Import allows for single imports)

Have more questions? Feel free to ask in the comments below or Contact Us!

To be fair, these two developments are really far apart in their delivery dates. The Gmail status update could come as soon as tomorrow, whereas the the speech-to-text-to-speech translation system is still a ways out. You can definitely see just how much work Google needs to do by trying to read your Google Voice voicemail transcriptions. (Voice search works better on Android 2.1 because you're talking slower and enunciating.) But both these features point in the same direction many of the company's other products have been hinting at. Here's a list of Google's major products, in case you forgot, and which sector of communication they want to dominate.

Google Voice: This is a big one, and it'll be the most natural interface for Google to slot in the voice-translation into. If you're using it the way Google wants you to use it, you're already piping all your voice calls and SMS through Google's tubes. And refining speech to text gives them a good idea of your interests and what you're talking about, allowing them to better serve up the relevant ads to you during calls.

Gmail: Having access to at least one end of everyone's email conversations, outside of business emails, gives Google the ability to be a gateway for most of your written communications. But that's not enough for Google, which is why they developed...

Google Wave: It's email, message boards, chat rooms and collaboration software all in one, except every participant needs a Google account. This closes that "openness" loophole that email has, and forces everyone into Google's biosphere. So this, and Gmail, should make sure that every medium-length communique passes through Google's maw for analysis. But what about shorter and longer forms? Update: Thanks commenters, for reminding me that Google made Wave open, so people can create their own Wave servers to talk to each other with the Wave protocol. The point still remains, that if you were going to use a service, wouldn't you rather use the service from the company that created the protocol, for performance and feature reasons?

Google Docs: For longer documents.

Google Talk: For short blasts of instant messaging, video chats and some audio chatting.

Picasa and YouTube: Communication doesn't have to be all text-based, you putting your photos and videos online count too.

Android and Chrome OS: By getting you down at the operating system level, Google can theoretically know every kind of communication you perform. It knows who you talk to, how you do it and when you do it. It can even shape the how by delivering the experience themselves.

Everything else. There's Checkout, Finance, Maps, Reader, News and other apps, which fill in the other forms of communication or expression that aren't quite covered by the major products above. One major missing piece is social networking, where Google basically failed before with its Orkut service (except for Brazil), so this new Twitter/Gmail hybrid might be their next entrance into the space.

But why do they want these things? Why would Google want to be the middleman between you and the world? To sell you ads, of course. And don't think Google is going to stop at just helping you talk over the internet or over the phone, they're going to reach into meatspace as well. How? One step is making that speech-to-speech translation portable, so you can do a sort of near-field communication with someone else with the same device while at the same time being able to look them in the face. Then, blast you two with the appropriate ads on the billboard next to you.

LittleSis API: LittleSis is a free database tracking the key relationships of politicians, business leaders, lobbyists, financiers, and their affiliated institutions (also described as an involuntary facebook of powerful Americans, collaboratively edited). The LittleSis API exposes the raw data used on the LittleSis website. The data consists of basic information about people and organizations, and the relationships between them. It uses a RESTful interface and responses are formatted in XML and JSON.

Mixpanel API: Mixpanel is a web service that lets companies track how users engage with their websites in real-time. The Mixpanel API allows users to post and access the data that Mixpanel is analyzing. This is a RESTful API and responses are returned in JSON format.

Mood of the Nation API: Mood of the Nation API allows clients to retrieve the raw trending data associated with the free Mood of the Nation iPhone application. The application collects mood information (physical, mental, emotional) from users and trends over day, week, month.

Motime API: The Motime Open Access platform is an affiliate program based on the APIs of the Motime service which allows partners/affiliates to advertise Motime ringtone content on their own web or mobile sites and earn money for each referral given to Motime. The search API offers a REST protocol to allow developers to link their content with Motime's catalog of ringtones.

Muselius API: The Muselius API can be used to display information on up to 99 museums in an area on your own web site. The information about museums can be used to enrich your art related sites, hotels and tourist sites. Muselius is a global directory of museums. Our mission is to facilitate the information you need for visiting museums all over the world. Muselius is created and maintained with the help of many users who update and complete the data we have about each museum.

OpenSRS API: OpenSRS API is intended for resellers who offer domains and supporting services to their customers. Resellers can provide functionality to their customers by integrating data from the RESTful API functions (includes SSL support). Developers can use the API to run queries or automate tasks that would otherwise be performed manually using the Domain Name Control Panel.

Fring is an Israel based startup that has been offering its signature VoIP application for mobile devices is now available for Android phones in the Android Market. Fring is an app that allows users to connect via popular chast and VoIP tools like Skype and Google Talk.

It was first introduced a little over three years ago in beta for handsets that were running Symbian OS. Since that time it has spread across the other popular platforms to gain a foothold in the instant messaging space on mobiles. Not to mention cornering VoIP though API development with some of the most popular internet based messaging software.

Fring allows users to aggregate their connections across networks and easily send text, photos, files and now video. And yes, like anything else being released today, Fring will allow you to tweet. Happy?

The two most robust platforms for using Fring are on Symbian 9 or higher and Windows Mobile phones. The newest, Android, has a few features for now like text chat, mobile calling and personalization settings.

Using the application is fairly straight forward as you need to download and install for your phone, register and then wait for Fring to connect the together your networks and contacts. Once this step is done you can begin getting in touch with your posse(s) via your mobile.

I've had good luck with Fring when I needed to get in touch with a contact that I didn't have handy in my phone contacts and for Skype text based chats. Now that it is ready for the new kid, Android, I would suspect that more features like those for the iPhone will make their way into the app.

DISCLOSURE OF MATERIAL CONNECTION: http://cmp.ly/0

Android Market VoIP by Fring is a post from: TechStartups.com

The gadgets are flowing and they've got both publishers and subscribers in a tizzy over their options. Are they 3g? Can I put my content on it? Just wifi? What services do they deliver? Do I need to build an app? Am I locked in?

All great questions but not the one that is at the front of my mind. That question being where is the personal media hub for all of this content? Each type of media that we consume has a disparative quality of some sort that requires another gadget or format transcoder to allow usage which means, users need a hub.

I just want to know where that hub will be. I'm not sure if it belongs in the cloud or can even exist there due to limitations placed on that content by rights holders. Which is a legitimate reason not to use the cloud since publishers need to eat.

A couple reasons to use the cloud would be transfer speeds, remote accessibility and backups. With increased gadget connectivity it would make sense to do this. An example of a gadget that needs to be fed from an outside source like the cloud is the PSPgo. It relies on connectivity to fetch games, video and browse the web.

The games on PSPgo arrive from a Sony controlled hub behind a firewall. If the cloud is too limiting due to rights management the other other solution would be to offer a private hub. Another gadget, but one that resides in the dwelling of an individual. Using the Sony model for control and privacy a device like this could be the next evolution of an inclusive hub. It seems to me to be the missing link.

Media management across multiples platforms and for varying devices would require some version of a standard protocol. The protocol probably already exists and could be as simple as HTTP with SSL. The device itself a web server that connects to cars, phones, tablets, computers, televisions, etc.

A device like this could also create new opportunities for rights holders to create new models for selling content. I'm thinking in the range of micropayments for ongoing usage or payments for amount of time used. An example would be a movie that instead of a 24 hour limit would allow the consumer to view it 2 times on any device before being crippled or offered for purchase for an additional few dollars.

My personal interest would be to have a media hub that I had control over and could add content to from any device like the PSPgo, Kindle, iPhone or computer. The ability for these devices to speak a common language for file storage and retrieval would increase consumption and sales as all of a users purchases become portable, even if lockedin to a device.

There are plenty of media hubs that exist today for personal use that can be net connected, but this device would find its niche in storing and delivering content without limitation.

DISCLOSURE OF MATERIAL CONNECTION: http://cmp.ly/0

Where is the personal media hub for ebooks, music and videos? is a post from: TechStartups.com

I was asked to review a scenario for a friend this morning that deals with competition for mind share in an ongoing row between disparate entities. Ahem, feuding like Hatfields and McCoys as Waylon Jennings would say, and they're doing it primarily online.

Most of us choose to go about our business online without causing confrontation. You might not choose to be involved in a situation like this.

However, if you are put in this position tactics for a remedy are below:

1. Make sure all of your sites where dynamic content is being created on have RSS feeds
2. Make sure the sites are being indexed by Google . . . and recently cached by going to Google and typing in site:blogdomain.com blogdomain.com being the site URL
3. Most of the sites below (I was furnished with list including Topix and Blog Catalog to mention a couple) require registration and some code editing to claim the sites. Register with them and follow their protocol for submission into their directories for partner programs and additional synidcation
4. Create a press release(s) that contains links, not just copy, but links to the RSS feeds from clients site(s). Example, For more information on this ongoing issue subscribe to: http://www.blogdomain.com/rssfeed. The popular outlets have wide syndication
5. Use this tool from Google http://www.google.com/sktool/# and enter your sites and the sites of the competitor into it. Disregard the pricing listed on the page for AdWords and focus on the keywords. Compare the the keywords of your competitor with those of your sites and adjust accordingly in all digital communications. Organic search is king.
6. Next use this too from Google https://adwords.google.com/select/KeywordToolExternal once your keywords are set to see how you are doing
7. Depending on the blog or site platform you should have the ability to create keyword RSS feeds. Do this. Robots like structured data and favor feeds. Most, if not all, Google real-time alerts come from RSS feed links back to the source site.
8. Commenting on local (this is a regional battle for mind share) blogs with links to client site(s) and feeds is another way to increase chances of indexing and more favorable search results

If I were fighting this battle or one like it these are exact steps that I would take. So dear reader, if we ever lock horns, we may duel to a draw since you have my playbook.

DISCLOSURE OF MATERIAL CONNECTION: http://cmp.ly/4

How to Win Mind Share in Online Battles is a post from: TechStartups.com

Database normalization is a technique for designing relational database schemas that ensures that the data is optimal for ad-hoc querying and that modifications such as deletion or insertion of data does not lead to data inconsistency. Database denormalization is the process of optimizing your database for reads by creating redundant data. A consequence of denormalization is that insertions or deletions could cause data inconsistency if not uniformly applied to all redundant copies of the data within the database.

Why Denormalize Your Database?

Today, lots of Web applications have "social" features. A consequence of this is that whenever I look at content or a user in that service, there is always additional content from other users that also needs to be pulled in to page. When you visit the typical profile on a social network like Facebook or MySpace, data for all the people that are friends with that user needs to be pulled in. Or when you visit a shared bookmark on del.icio.us you need data for all the users who have tagged and bookmarked that URL as well. Performing a query across the entire user base for "all the users who are friends with Robert Scoble" or "all the users who have bookmarked this blog link" is expensive even with caching. It is orders of magnitude faster to return the data if it is precalculated and all written to the same place.

This is optimizes your reads at the cost of incurring more writes to the system. It also means that you'll end up with redundant data because there will be multiple copies of some amount of user data as we try to ensure the locality of data.

A good example of a Web application deciding to make this trade off is the recent post on the Digg Blog entitled Looking to the Future with Cassandra which contains the following excerpt

The Problem

In both models, we're computing the intersection of two sets:

1. Users who dugg an item.
2. Users that have befriended the digger.

The Relational Model

The schema for this information in MySQL is:

CREATE TABLE `Diggs` ( `id` INT(11), `itemid` INT(11), `userid` INT(11),
`digdate` DATETIME, PRIMARY KEY (`id`), KEY `user` (`userid`), KEY `item` (`itemid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;   CREATE TABLE `Friends` ( `id` INT(10)
AUTO_INCREMENT, `userid` INT(10), `username` VARCHAR(15), `friendid` INT(10), `friendname`
VARCHAR(15), `mutual` TINYINT(1), `date_created` DATETIME, PRIMARY KEY (`id`), UNIQUE
KEY `Friend_unique` (`userid`,`friendid`), KEY `Friend_friend` (`friendid`) ) ENGINE=InnoDB
DEFAULT CHARSET=utf8;

The Friends table contains many million rows, while Diggs holds hundreds of millions. Computing the intersection with a JOIN is much too slow in MySQL, so we have to do it in PHP. The steps are:

1. Query Friends for all my friends. With a cold cache, this takes around 1.5 seconds to complete.
2. Query Diggs for any diggs of a specific item by a user in the set of friend user IDs. This query is enormous, and looks something like:

   SELECT
   `digdate`, `id` FROM `Diggs` WHERE `userid` IN (59, 9006, 15989, 16045, 29183, 30220,
   62511, 75212, 79006) AND itemid = 13084479 ORDER BY `digdate` DESC, `id` DESC LIMIT
   4;

   The real query is actually much worse than this, since the IN clause contains every friend of the user, and this can balloon to hundreds of user IDs. A full query can actually clock in at 1.5kb, which is many times larger than the actual data we want. With a cold cache, this query can take 14 seconds to execute.

Of course, both queries are cached, but due to the user-specific nature of this data, it doesn't help much.

The solution the Digg development team went with was to denormalize the data. They also went an additional step and decided that since the data was no longer being kept in a relational manner there was no point in using a traditional relational database (i.e. MySQL) and instead they migrated to a non-RDBMS technology to solve this problem.

How Denormalization Changes Your Application

There are a number of things to keep in mind once you choose to denormalize your data including

1. Denormalization means data redundancy which translates to significantly increased storage costs. The fully denormalized data set from the Digg exampled ended up being 3 terabytes of information. It is typical for developers to underestimate the data bloat that occurs once data is denormalized.

2. Fixing data inconsistency is now the job of the application. Let's say each user has a list of the user names of all of their friends. What happens when one of these users changes their user name? In a normalized database that is a simple UPDATE query to change a single piece of data and then it will be current everywhere it is shown on the site. In a denormalized database, there now has to be a mechanism for fixing up this name in all of the dozens, hundreds or thousands of places it appears. Most services that create denormalized databases have "fixup" jobs that are constantly running on the database to fix such inconsistencies.

The No-SQL Movement vs. Abusing Relational Databases for Fun & Profit

If you're a web developer interested in building large scale applications, it doesn't take long in reading the various best practices on getting Web applications to scale such as practicing database sharding or eschewing transactions before it begins to sound like all the advice you are getting is about ignoring or abusing the key features that define a modern relational database system. Taken to its logical extreme all you really need is a key<->value or tuple store that supports some level of query functionality and has decent persistence semantics. Thus the NoSQL movement was borne.

The No-SQL movement is a used to describe the increasing usage of non-relational databases among Web developers. This approach has initially pioneered by large scale Web companies like Facebook (Cassandra), Amazon (Dynamo) & Google (BigTable) but now is finding its way down to smaller sites like Digg. Unlike relational databases, there is a yet to be a solid technical definition of what it means for a product to be a "NoSQL" database aside from the fact that it isn't a relational database. Commonalities include lack of fixed schemas {TODO}. Below is a list of some of the more popular NoSQL databases that you can try today along with a brief description of their key qualities

1. CouchDB: A document-oriented database where documents can be thought of as JSON/JavaScript objects. Creation, retrieval, update and deletion (CRUD) operations are performed via a RESTful API and support ACID properties. Rich querying is handled by creating Javascript functions called "Views" which can operate on the documents in the database via Map/Reduce style queries. Usage: Although popular among the geek set most users seem to be dabblers as opposed to large scale web companies.

2. Cassandra: A key-value store where each key-value pair comes with a timestamp and can be grouped together into a column family (i.e. a table). There is also a notion of super columns which are columns that contain whose values are a list of other key-value pairs. Cassandra is optimized to be always writable and uses eventual consistency to deal with the conflicts that inevitably occur when a distributed system aims to be always writable yet node failure is a fact of life. Querying is available via the Cassandra Thrift API and supports fairly basic data retrieval operations based on key values and column names. Usage: Originally developed and still used at Facebook today. Digg and Rackspace are the most recent big name adopters.

3. Voldemort: Very similar to Cassandra which is unsurprising since they are both inspired by Amazon's Dynamo. Voldemort is a key-value store where each key value pair comes with a timestamp and eventual consistency is used to address write anomalies. Values can contain a list of further key value pairs. Data access involves creation, retrieval and deletion of serialized objects whose format can be one of JSON, strings, binary BLOBs, serialized Java objects and Google Protocol Buffers. Rich querying is non-existent, simple get and put operations are all that exist. Usage: Originally developed and still used at LinkedIn.

There are a number of other interesting NoSQL databases such as HBase, MongoDB and Dynomite but the three above seem to be the most mature from my initial analysis. In general, most of them seem to be a clone of BigTable, Dynamo or some amalgam of ideas from both papers. The most original so far has been CouchDB.

An alternative to betting on a speculative database technologies at varying levels of maturity is to misuse an existing mature relational database product. As mentioned earlier, many large scale sites use relational databases but eschew relational features such as transactions and joins to achieve scalability. Some developers have even taken that practice to an extreme and built schema-less data models on top of traditional relational database. A great example of this How FriendFeed uses MySQL to store schema-less data which is a blog post excerpted below

Lots of projects exist designed to tackle the problem storing data with flexible schemas and building new indexes on the fly (e.g., CouchDB). However, none of them seemed widely-used enough by large sites to inspire confidence. In the tests we read about and ran ourselves, none of the projects were stable or battle-tested enough for our needs (see this somewhat outdated article on CouchDB, for example). MySQL works. It doesn't corrupt data. Replication works. We understand its limitations already. We like MySQL for storage, just not RDBMS usage patterns.

After some deliberation, we decided to implement a "schema-less" storage system on top of MySQL rather than use a completely new storage system.

Our datastore stores schema-less bags of properties (e.g., JSON objects or Python dictionaries). The only required property of stored entities is id, a 16-byte UUID. The rest of the entity is opaque as far as the datastore is concerned. We can change the "schema" simply by storing new properties.

In MySQL, our entities are stored in a table that looks like this:

CREATE TABLE entities ( added_id INT NOT NULL AUTO_INCREMENT PRIMARY
KEY, id BINARY(16) NOT NULL, updated TIMESTAMP NOT NULL, body MEDIUMBLOB, UNIQUE KEY
(id), KEY (updated) ) ENGINE=InnoDB; 

The added_id column is present because InnoDB stores data rows physically in primary key order. The AUTO_INCREMENT primary key ensures new entities are written sequentially on disk after old entities, which helps for both read and write locality (new entities tend to be read more frequently than old entities since FriendFeed pages are ordered reverse-chronologically). Entity bodies are stored as zlib-compressed, pickled Python dictionaries.

Now that the FriendFeed team works at Facebook I suspect they'll end up deciding that a NoSQL database that has solved a good story around replication and fault tolerance is more amenable to solving the problem of building a schema-less database than storing key<->value pairs in a SQL database where the value is a serialized Python object.

As a Web developer it's always a good idea to know what the current practices are in the industry even if they seem a bit too crazy to adoptyet.

Further Reading

• How FriendFeed Uses MySQL to Store Schema-less Data by Bret Taylor
• Looking to the future with Cassandra Digg Blog

Now Playing: Jay-Z - Run This Town (feat. Rihanna & Kanye West)

Steve Gillmor is going to love this, of course, since he proclaimed that RSS was dead and Twitter was the new messaging protocol bus, or something to that effect. Rest In Peace, RSS, he wrote, saying It's time to get completely off RSS and switch to TwitterAll my RSS feeds are in Google Reader. I don't go there any more. Since all my feeds are in Google Reader and I don't go there, I don't use RSS anymore.

Santosh Jayaram, Twitter's existing head of operations (and also from Google), will presumably remain with the company and report to Costolo.

Costolo, who is also an early Twitter investor, is someone who has actual experience building scalable infrastructures, which Twitter sorely needs. The company hasn't launched any new features in recent memory, and continues to have regular downtime. In fact, Twitter's inability to build features and keep the service live is a serious competitive disadvantage. Costolo can presumably fix all that.

Twitter is actively hiring more senior people, we've heard. In July they hired Alexander Macgillivray, Google's associate general counsel for Product and IP, as their new General Counsel.

Crunch Network: CrunchBoard because it's time for you to find a new Job2.0

Shared by Schlomo
Word. Chesspark/Collecta has known this for a long time.

Web surfers nowadays use many browsers on different machines, even on small devices like smartphones. They obviously need a way to gather together all these sparse data (like bookmarks, passwords, history, etc.) and make them available from any browser at any time.

Two of the largest internet players today provide two different approaches, both at the same experimental state:

• Mozilla with Weave, a product from its labs, providing a Firefox extension, a opensource server implementation, and a documented protocol
• Google will offer a Chrome feature, Google Talk server, Google account, and maybe a documented protocol, since the code is opensource

It is possible to provide browser data sync client as a cross-browser extension or plugin, a server component which would rely on an existing XMPP server and account of your choice, and a protocol which could well be Bookmarks, Message Archiving, or Persistent Storage of Public and Private Data via PubSub.

This shows the ongoing effort of Google to use XMPP: Talk and Jingle, GMail notifications, Wave, and now data sync.

With Google and Apple using XMPP for its notifications service, XMPP shows itself as a strong infrastructure for a wide array of applications beyond the simple chat.

Background

The most interesting area of new development on the web is the innovation happening around realtime messaging, the ability to deliver updates to a website or application in one or two seconds. While various systems like Yahoo News Alerts or feed readers like Google Reader have offered some simple ways of delivering fairly fast notifications, they are still built on an infrastructure that relies upon requesting a web page repeatedly. These systems do the equivalent of hitting the "reload" button in your web browser over and over.

While those systems have been using these inefficient methods to deliver updates, newer platforms like Twitter, Facebook and FriendFeed have focused on building the infrastructure for efficient large-scale delivery of updates using their own proprietary networks. A lot of attention has been paid to Twitter's 140-character limit, or Facebook's News Feed, but the compelling technology that enables the user experience on these platforms is the immediacy with which updates are delivered. Earlier systems like instant messaging or chat allowed realtime messaging on a one-to-one or small group basis, but it's been harder to deliver those realtime messages to anyone in the world who wanted to receive them unless you had a lot of money, expertise and infrastructure.

Another barrier is that, while there are many different programs and clients that let you connect to Twitter or Facebook with your own applications, there haven't been any free and open options for delivering realtime messages to a large audience if you couldn't, or didn't want to, rely on those companies.

But recently, a few key pieces have fallen into place that make it inexpensive and relatively easy to add realtime messaging as an incremental upgrade to existing websites and web applications. This set of related technologies, which I'm calling the Pushbutton platform, will yield a broad new set of capabilities for users, publishers and developers on the web. Best of all, Pushbutton technologies are free, open and decentralized, meaning that the arrival of realtime on the web will not be owned or controlled by any single company.

Defining Pushbutton

The concept and potential of Pushbutton is a lot like Ajax it's not a single technology or invention, it's a whole family of technologies, some of which have been in development or deployment for nearly a decade, that together enable this new realtime web. Pushbutton's foundation is built on these systems:

• Atom and RSS: The most common feed formats, for syndication on the web
• PubSubHubBub and RSSCloud: Powerful new "hubs" for distributing messages
• Web Hooks: Simple web services for receiving messages, rather than sending them

Pushbutton systems rely on the web's fundamental HTTP protocol for communication between these component parts. The architecture of Pushbutton message delivery is also simple to understand. Before Pushbutton, in today's systems, when you create a message (a blog post, tweet or other update) that's published in your RSS or Atom feed, every application or site that wants updates from you has to repeatedly request your feed to know when it's updated. You can optionally notify ("ping") some applications to tell them it's time to come collect your new updates, but this is time-consuming and resource-intensive on both sides, especially if you want to notify a lot of people.

In the best case, the system we have now is analogous to a person coming by your house and saying "Hey, there's a new edition of your favorite newspaper today. You should go get it." And then you have to go to the newspaper's printing plant to pick it up. In a Pushbutton web, that person is delivering each story to your house the moment it's complete.

That's because Pushbutton-enabled applications will improve upon the current state of affairs by proactively delivering not just the notification that there's a new message, but the content of the message itself. And instead of requiring all those applications to come to your site to read the update, it uses a hub server in the cloud to pass along the message directly to all the receivers that are interested in it.

1. You, the Sender, create a message to be delivered via RSS or Atom
2. Your application gives the messsage to one or more PubSubHubBub or RSSCloud hubs, which reside in the Cloud
3. The PubSubHubBub or RSSCloud hubs deliver the message to any Receivers, the applications or sites that have requested updates from you

In this way, each time you create a new message, a large number of Receivers can consume that message in near realtime (usually less than a second) without a lot of complexity. This kind of messaging has been possible with custom-built or more obscure technologies in the past, but the Pushbutton ecosystem is a breakthrough for a few reasons:

• Sending messages just requires a minor change to an RSS or Atom feed, and a simple, well-defined update notification, instead of major changes to the application where you create your messages.
• Receiving messages is also very simple, only requiring a developer to handle incoming notifications of updates.
• Most of the system's complexity is handled in the hub servers, which are well-documented, implementable in a variety of programming languages, and built around open code that will likely attract a large developer community.
• Most of the scaling effort and expense happens at the hub level, and all current hubs are designed to run on inexpensive cloud systems like Google App Engine or Amazon's EC2.
• The software for Sending, Receiving or running a hub is free, open source and available on almost any platform.
• Messages sent on Pushbutton platforms are delivered via HTTP, which is familiar to any web developer and runs well on any hosting environment. All requests between the different layers of a Pushbutton system can be made as simple REST calls.
• Pushbutton technologies can be adopted incrementally, so that features can be added piecemeal on either the sender or receiver side, without requiring a wholesale upgrade to infrastructure or application architecture.

Who's Behind Pushbutton?

Pushbutton technologies have been created and advocated by some of the most credible and experienced developers of social web technologies. Here's a brief overview of the impressive pedigree of these components:

• PubSubHubBub was co-created by Brad Fitzpatrick and Brett Slatkin of Google. Brad was founder of LiveJournal, and created or co-created fundamental social web technologies like Memcached, OpenID and more.
• XML-RPC update pings, RSS and the RSS Cloud ideas were pioneered by Dave Winer, who has been actively developing open implementations of each of these technologies.
• Web Hooks have been evangelized by Jeff Lindsay, and have been deployed by a variety of different companies and platforms which all independently developed the technique.

In addition, Google has supported Brad and Brett's development of PubSubHubBub, and enabled it on the Google FeedBurner service. A number of smaller companies are deploying large parts of this infrastructure as well. In short, some of the best reputations in developing open web systems have made Pushbutton possible, from the biggest tech companies to the most steadfastly independent developers on the web.

Related Ideas and Prior Art

There are a lot of existing technologies that have influenced the creation and evolution of Pushbutton technologies; If you're familiar with any of these systems, you're probably already ahead of the curve in understanding part of what Pushbutton is trying to enable.

• Twitter Firehose, FriendFeed SUP, TypePad Update Stream: These realtime delivery systems offer up the content of their respective platforms as an unending stream that developers can consume and use in their applications. At the present time, they all have varying licenses and degrees of openness, and slightly different formats for delivering updates, but have proven the utility of the "sending" part of Pushbutton's realtime functionality.
• XMPP (Jabber), NNTP (Usenet), IRC: These older internet protocols all delivered various degrees of realtime messaging and distributed messaging capabilities, and can form a very useful base of experience for Pushbutton developers to learn from. In some cases, fundamental architectural choices about security, authentication or architecture were made when the Internet was less populated and less complex, making them inappropriate for today's applications. In all cases, these protocols are less-known by most contemporary web developers, and thus lack familiar toolkits and development resources, which make them quite challenging to deploy in common, inexpensive environments.
• TrackBack and Pingback: These systems for delivering updates between blogging systems were very effective in enabling rich distributed conversations in the early days of the blogosphere. These have declined in usefulness due to poor or missing implementations of authentication, which led to spam problems, and a general lack of understanding of their utility by a lot of newer bloggers. Pushbutton may offer an opportunity to restore some of the value of the idea behind these systems.
• Reverse HTTP may end up being a useful component of some Pushbutton deployments, as a complement or companion to Comet and related techniques.

What should we worry about?

• A format war? If you're familiar with the communities around technologies like feeds, you may know they have a deserved reputation for being contentious and even breaking into heated disputes over arcane details. I don't think that's likely to happen this time, because there are only one or two viable formats for each layer of the platform, and the creators of each part have shown some consistent good-faith efforts to promote interoperability where possible and peaceful coexistence where necessary. In the Ajax community, for example, the "X" in Ajax often stands for JSON instead of XML, but this hasn't hindered its broad adoption at all. I'm also willing to personally commit to try to prevent any kind of interpersonal conflict that would inhibit the adoption of Pushbutton technologies. Worry? No.
• Scaling issues? There will inevitably be some learning to do about how to scale the resource-intensive hub layer of a Pushbutton system. But because the hubs live on cloud systems that make enormous amounts of computing resources easily available, because the coders creating the reference implementations of the hub software have great experience making web-scale systems, and because it's relatively simple to introduce new hubs as needed, this will likely not be a gating factor for adoption of Pushbutton. Worry? No.
• Intellectual Property Concerns? I'm not a lawyer, and this isn't legal advice. But there has already been a great deal of interest in these systems, and it's likely that any bad actors who were interested in throwing their patent lawyers at this sort of system would probably already be suing people left and right. And the main players who are already involved have shown a consistent desire to make truly open systems that don't have IP encumbrances. Put simply, I think anybody smart enough to invent these kinds of technologies is smart enough to not want to look like jerks by suing somebody for using them. Worry? Probably not.
• Competition from centralized systems? Pushbutton technologies are not just free and open, they're decentralized, which is a serious threat to the "lobster trap" model of social software. We can expect serious competition from the centralized networks that are currently building these sorts of systems. If a threat arises to Pushbutton's adoption, this is the most likely source. Worry? Definitely.
• Bad user experience? One of the worst things we can do in making use of new technologies is to ignore the social, personal or even political implications of their use. Messages that are immediately delivered can't, by their nature, be erased from all the places they appear. The idea of permanently archiving these types of messages is unfamiliar to a lot of less technically-savvy users. And whenever we see something shiny and new, we have the temptation to use technology for technology's sake, whether or not we're solving a real problem or providing a real value. If Pushbutton gets a bad rap early on despite having tremendous potential, this will be why. Worry? Hell, yes.

Conclusion

I have tremendous excitement about the new realtime era of web applications. While I'm fundamentally an optimistic person, I have great skepticism when it comes to mindless hype about new technologies, so it's with a bit of reluctance that I indulge in some hype myself. But I think the Pushbutton web has the opportunity to give individuals and organizations with distinct and passionate voices the ability to be even more immediate and expressive on the web, and after ten years of publishing on the web, that's the part I love the most.

I have no doubt that some skeptics will say "Pushbutton is just PubSubHubBub by another name", just like they said "Ajax is XMLHttpRequest by another name", and if that's what the super-geeky guys want to believe, I'm fine with that. And I'm sure there will still be some significant technical details to resolve. But I think by giving the overall concept an approachable, understandable name and (hopefully!) an explanation that can be understood by anyone with an interest, it can catalyze interest in a whole new area of innovation on the web. And to be honest, when I see folks like Brad Fitzpatrick and Dave Winer hacking on the same set of problems, I can't help but think something interesting will come of it.

Over the next few days, I'll be outlining some of the opportunties around Pushbutton, espousing more of the philosophy that has the potential to imbue Pushbutton with a bit more meaning than most new web tech, and providing some simple explanations of how you can get started both learning about and taking advantage of these technologies. Most of all, I hope you'll offer your pointed criticisms, thoughtful critiques, detailed corrections and even better ideas. I'll be following the conversation here in the comments, across the blogosphere, and on Twitter using the tag #pshb.

Google makes its money mostly from targeted advertising on product searches and other narrow, directed searches. The advertising on news-related searches is not nearly as valuable. Google could remove all newspapers and journalism content from its Web search catalog tomorrow and lose very little of its revenue. The links to news it provides are valuable to its users but not terribly valuable to its advertisers.

Most galling was that The Huffington Post's use of an Associated Press version of SI's report was initially tops on Google, which meant that it, and not SI.com, tended to be the place readers clicking through to get the gist of the breaking scandal would land.... Why did The Huffington Post come up ahead of SI.com? Because, even Google insiders concede, Huffington is effective at implementing search optimization techniques, which means that its manipulation of keywords, search terms, and the dynamics of Web protocol give it an advantage over others scrambling to be the place readers are sent by search engines. What angered the people at Sports Illustrated and Time Inc. is that Google, acting as traffic conductor, seemed unmoved by their grievance over what had happened to their ownership of the story. An SI editor quoted to me Time Inc's editor-in-chief, John Huey, noting crisply that, "talking to Google is like trying to talk to a television."

This was my first meeting with the Web's creator, whose work and philosophy was a direct inspiration for me when I launched ReadWriteWeb back in 2003.¹

Sponsor

After shaking hands, I told Tim Berners-Lee that this blog's name was in part inspired by the first browser, which he developed, called "WorldWideWeb". That was a read/write browser; meaning you could not only browse and read content, but create and edit content too. It was a shame then when Mosaic, a read-only browser, became the first mainstream web browser in the mid-90s. It wasn't until the rise of Web 2.0 that the read/write philosophy gained widespread acceptance.² On that note, we launched into the interview...

Note: the interview will be published in two parts, with Part 1 today on the topic of Linked Data. Part 2 will explore other topics and will run tomorrow.

How Linked Data Relates to The Semantic Web

RWW: Earlier this year you gave an inspiring talk at TED about Linked Data. You described Linked Data as a sea change akin to the invention of the WWW itself - i.e. we've gone from a Web of documents to a Web of data. Can you please explain though how Linked Data relates to the Semantic Web, is it a subset of it?

TBL: They fit in completely, in that the linked data actually uses a small slice of all the various technologies that people have put together and standardized for the Semantic Web.

We started off with the Semantic Web roadmap, which had lots of languages that we wanted to create. [However] the community as a whole got a bit distracted from the idea that actually the most important piece is the interoperability of the data. The fact that things are identified with URIs is the key thing.

The Semantic Web and Linked Data connect because when we've got this web of linked data, there are already lots of technologies which exist to do fancy things with it. But it's time now to concentrate on getting the web of linked data out there.

Web inventor Tim Berners-Lee and ReadWriteWeb founder Richard MacManus

How Linked Data Has Evolved via Grassroots

RWW: Linked Data has had a lot of grassroots support, which you mentioned in your TED speech. This is something Semantic Web technologies, such as RDF, have struggled to get over the years. Has the W3C been pushing the more bottom-up Linked Data world, because of the frustration over lack of take-up of top-down Semantic Web?

TBL: A lot of the initial RDF and OWL projects came out of the academic world; and some of them were projects to show what you could do in a closed world. And the files were zipped up and left on a disc. While they were interesting projects, and while the systems were useful systems, the semantic web community maybe missed the point of the 'web' bit and focused too much on the 'semantic'. However the work that's been done in the Semantic Web, the standards, was really valuable. It's relatively recently for example that SPARQL [an RDF query language] has been developed.

Somebody drew an analogy the other day: can you imagine trying to promote a world of databases without SQL? Even though it's not an interoperable protocol, it's just a query language. So similarly, all that's been put into RDF, rdfs and OWL is very valuable to the linked data community.

The Linked Data community tend to use a subset of that [Semantic Web technologies], of OWL for example. But they certainly use SPARQL. So you could argue that really it wasn't ready to be deployed widely.

Linked Data started as a very informal Design Issues note that I put in; it was a grassroots movement from very early on. So yes W3C has been emphasizing the importance of Linked Data. It's been the Semantic Web Interest Group of course, and various [other Semantic Web] activities, which has been pushing it. But also Linked Data has been seized on - a group of people for example put together DBpedia.³ That wasn't commissioned, that was that they just thought it would be a really cool idea.

Graph of Linked Data sets on the Web, as at March 2009

Linked Data and Governments

RWW: In a recent Design Issues note, you urge governments to put their data online as Linked Data (although you'd also be happy for governments to just make available the raw data - presumably so that others can then structure it). What do you realistically expect, for example, the U.S. or U.K. governments to do over the next year? And in the near future, do you foresee different governments interconnecting their Linked Data sets?

TBL: One can't generalize, governments are (like most big organizations) fascinatingly diverse inside them. So you'll find that there are places inside governments where you get a champion who gets linked data and who's just written a script and produced some linked data. So in the UK government for example, you'll find there's RDFa [in the code of its website] for civil service jobs. So if somebody wants to make a database of all the jobs, they can do that very easily.

There are other cases where the easiest thing for somebody to do is to just put data up in whatever form it's available. Comma separated values (CSV) files are remarkably popular. They're exported sometimes from spreadsheets. It's remarkable how much information is in spreadsheets. Or sometimes pulled out of a database and then put up on the web. It's not as good, not as useful to the community, as if Linked Data had been put up there and linked. But the first step of actually putting the data out there is the one that nobody else can do.

Data.gov, a catalog of public data, was launched in May by the U.S. government

The way to go is for government departments to go the extra step and convert [their data] into Linked Data. One of the nice things about Linked Data, when they have a pile of it, is that they could run a SPARQL server on it. SPARQL servers are a commodity product, a solution for all of the people who say 'but actually I wanted to have XML.' A SPARQL server will generate an XML file [and] allow somebody to write out, effectively, a URL for the XML file.

In fact, I don't see why SPARQL servers shouldn't provide CSV files, something which as far as I know isn't in the standards. But I'd recommend it, certainly in government context, because CSV files are what people have and what people want.

So the message [for government] is to use RDF. Linked Data is the backplane, it's the thing that you connect to in both directions. As a [web] producer your job is to make sure that you produce Linked Data one way or another. And as a consumer, there are lots of ways to consume that data once it's out there as Linked Data.

Part 2 of ReadWriteWeb's interview with Tim Berners-Lee will be published tomorrow...

Footnotes:

1. The very first sentence written on this blog, on 20 April, 2003, was: "The World Wide Web in 2003 is beginning to fulfill the hopes that Tim Berners-Lee had for it over 10 years ago when he created it."

2. For more on read/write browsers, you can read another early RWW post entitled What became of the Browser/Editor.

3. DBpedia is a community project to extract structured information from Wikipedia; see ReadWriteWeb's profile of this and similar resources.

Ah, lawyers. It's a love-hate relationship.

Just this week alone, I'm working with a literary attorney (publishing), an entertainment attorney (TV), and a corporate financing attorney (angel investments). All three are great.

Yesterday, though, I received the threatening letter below from Protocol Integrated Direct Marketing, whose call centers I recommend in the 4HWW. WTF?

Click to enlarge

But what did I say about Protocol specifically? Here it is, after an group intro where I indicate providers can also be compensated per-minute:

Protocol Marketing: One of classic sales-oriented call centers. I've used them for years.

I used them as a start-up CEO and felt the recommendation was valuable to readers. Blasphemer! Even if a correction were needed somewhere, the legal bitch slap isn't needed.

My response was simple: I called the lawyer and told him I would both have the mention removed and also announce the correction to readers (that's this blog post).

I suspect the CEO, Don Norsworthy, is not aware of this letter, as he would have no doubt approached it differently after recognizing a few things:

1. How you say something IS what you say.

Ever heard it's not just what you say, it's how you say it? I would go further: how you say something is what you say. A simple call or e-mail to Random House with we're getting too many calls for the wrong services; would you mind changing it to the following? would have sufficed. Have a normal human conversation and don't come off sounding like Robocop (video above).

But what if you need to be forceful? If someone's motives are clearly bad? I've dealt with this as well. First of all, if their actions are done with obvious malevolent-intent or law-breaking, you can be more forceful. Second, for those cases that fall in the middle, it's possible to be forceful and clear without being rude. For example:

It's come to our attention that [action your want them to cease in neutral terms]. I'm sure you are unaware, but this causes [negative consequences for you], which results in [other problems]. We thank you in advance for removing/stopping/correcting X as soon as possible [notice how less abrasive this is than 'immediately', but it achieves the same effect] and confirming when this has been done. Legal action is always a last resort, but if we do not receive confirmation within one business week, we'll be compelled to take appropriate next steps. Your fastest correction and confirmation is both important and appreciated.

2. It's counterproductive to threaten someone until you determine their incentives to refuse compliance.

In other words, what do I gain by refusing to remove them? Nothing. In fact, it's in my readers' best interest to make it accurate or remove it. Threatening me with Darth Vader-speak like compel compliance with [our] demand just pisses people off, and I could have still been a strong proponent of theirs. Too bad, so sad.

3. It's better to steer the golden goose rather than kill it.

If I'm sending them enough calls to inundate their phone lines (ironic in itself, since they're offering call center services), it would be in their best interest to just make the description more accurate, no? It's free advertising in a #1 NY Times bestseller to be published in 33 languages. How much advertising cost or cost-per-acquisition (CPA) does that save them if it's accurate? Knowing the revenue model and having worked with call centers, I'd guess hundreds of thousands of dollars at a minimum. To save what? A few thousand dollars in filtering out mom-and-pop callers at $.90 per minute? That's just penny-wise and pound-foolish.

4. Don't mistake symptoms with root problems, or confuse correlation with causation.

There are no income investment requirements that I can find listed anywhere on their call center site. It strikes me that their main problem relates to a system-wide issue with pre-qualification. The blurb in the 4HWW is just a symptom any successful PR or marketing that brings people to them will produce the same filtering bottleneck. Fixing the root cause instead of threatening the person who makes the root cause come to the surface.

If they have a problem with closer, Protocol might also consider removing the following from the second paragraph of their main call center page:

Whether you need a salesperson to close deals or specialized technical support services, Protocol's contact center services can help.

Confused? Me too.

5. If you threaten someone in a digital world, it might become what your prospective customers see first.

Principle one: Better not to threaten people whenever possible. Principle two: Google someone before you threaten them. If their PageRank and SEO beats yours, recognize that the public will see what they say first and foremost. Principle three: if someone is sending you business, and you threaten them because of a positive description (even containing inaccuracies), you are disincentivizing all partners, journalists, and customers from evangelizing for you if it becomes public. Given the new dynamics of personal branding in a digital age, being nice should be company policy, if not for cheap Google insurance.

Oh, and being rude sucks.

Be firm when necessary, but be nice whenever possible. Long-term, it doesn't pay to do otherwise.

In conclusion: Protocol, I'm sorry for endorsing you and reflecting my experience in a positive description. I was wrong and you are right. Readers, please pull out your Sharpie and strike Protocol from pg. 201.

Ah, lawyers. Use them wisely or the problem you create could be bigger than the one you solve.

Anyone have suggestions for good call centers that won't threaten me for recommending them?


To lighten the mood, a photo from the American Apparel factory, which I visited last Saturday. More pics here.

A company called Celiocorp has launched a completely different take on the netbook phenomenon. Instead of offering a lightweight computer running either Linux or XP like today's netbooks do, this notebook PC is entirely powered by a device you already own: your smartphone. Dubbed a mobile companion, the Redfly device has an 8-inch screen, a full-sized keyboard and touch pad, and is connected to your smartphone via a USB cable or Bluetooth.

To use the Redfly notebook, all you need to do is install the Redfly driver on your phone (see supported phones here). You can then use the netbook like any computer. Its bigger screen makes it easier to read documents, write emails, or surf the web. Redfly supports remote desktop, virtualization and other cloud-based environments like Citrix, GoToMyPC, LogMeIn, Microsoft's Remote Desktop protocol, stoneware, inc., and others. The netbook also features a VGA connector so you can connect your Redfly netbook to a projector for presentations.

As you use the Redfly device, you can be charging your smartphone too, assuming it's plugged in via the USB cable. The Redfly battery works for up to 8 hours, according to the company.

Because Redfly has no OS, no CPU, no hard drive, and requires no software licenses, its cost is lower than a laptop PC (an Amazon search shows that price to be around $199). That's also slightly more affordable than today's crop of OS-powered netbooks, but not by much.

The benefit to using a mobile companion instead of a PC is that the device can get lost or stolen without any threat of losing important data. Of course, a lot of companies have already started doing this now via the use of virtualized business apps running on top of the OS installed on regular company laptops all the important data is in the cloud so laptop loss or theft isn't as big a concern as before. However, given the price ($199) of Redfly vs. that of a laptop, the replacement cost would be minimal.

in reply to Redfly: A Netbook Entirely Powered By Your Windows Mobile Phone

A company called Celiocorp has launched a completely different take on the netbook phenomenon. Instead of offering a lightweight computer running either Linux or XP like today's netbooks do, this notebook PC is entirely powered by a device you already own: your smartphone. Dubbed a mobile companion, the Redfly device has an 8-inch screen, a full-sized keyboard and touch pad, and is connected to your smartphone via a USB cable or Bluetooth.

To use the Redfly notebook, all you need to do is install the Redfly driver on your phone (see supported phones here). You can then use the netbook like any computer. Its bigger screen makes it easier to read documents, write emails, or surf the web. Redfly supports remote desktop, virtualization and other cloud-based environments like Citrix, GoToMyPC, LogMeIn, Microsoft's Remote Desktop protocol, stoneware, inc., and others. The netbook also features a VGA connector so you can connect your Redfly netbook to a projector for presentations.

As you use the Redfly device, you can be charging your smartphone too, assuming it's plugged in via the USB cable. The Redfly battery works for up to 8 hours, according to the company.

Because Redfly has no OS, no CPU, no hard drive, and requires no software licenses, its cost is lower than a laptop PC (an Amazon search shows that price to be around $199). That's also slightly more affordable than today's crop of OS-powered netbooks, but not by much.

The benefit to using a mobile companion instead of a PC is that the device can get lost or stolen without any threat of losing important data. Of course, a lot of companies have already started doing this now via the use of virtualized business apps running on top of the OS installed on regular company laptops all the important data is in the cloud so laptop loss or theft isn't as big a concern as before. However, given the price ($199) of Redfly vs. that of a laptop, the replacement cost would be minimal.

Read More...

Low and behold, there are a ton of Power User Preferences that can be done through the command line for version 3.1 (I'm running 3.1b3 -> direct download link)

Power User Preferences

The following list shows preferences that can be set with the command line. These preferences can be used to configure Twitterrific for special uses.

To set one of these power user preferences, quit Twitterrific and issue the following from a command line:

% defaults write com.iconfactory.Twitterrific [preference] [type] [value]

where [preference] is the name of the preference, [type] is the data type and [value] is the data value to use (shown in the table below.) After restarting Twitterrific, you should see the new preference setting.

To delete the preference and return to a default setting, use:

% defaults delete com.iconfactory.Twitterrific [preference]

Make sure that you match case when typing the [preference] keybaseurl is not the the same as baseUrl. Use man defaults for more information about setting defaults with the command line.

Preference	Type	Default Value	Description
connectionLogging	-bool	NO	When this preference is set to YES, Twitterrific will log connection information to the Console. This is helpful for debugging Twitter problems.
processTweetScriptPath	-string	None	A path to an AppleScript that will be used to process each new tweet that arrives. The script parameters are described below.
protocol	-string	http://	Allows Twitterrific to be configured for other protocols, such as https://.
baseUrl	-string	twitter.com	Allows Twitterrific to be configured for other servers supporting the Twitter API.
filterOwnTweets	-bool	NO	If this preference is set to YES, Twitterrific will not display your own tweets. It will only display the tweets of your friends.
tweetScreenNameFilter	-string	None	Defines an ICU regular expression that will be used to filter incoming tweets based on the screen name of the tweet. If you want to block everything from @crackheadjoe and @chattypatty, you would set this preference to (crackheadjoe|chattypatty).
tweetTextFilter	-string	None	Defines an ICU regular expression that will be used to filter incoming tweets based on the text of the tweet. Setting this preference to [cC][aA][nN] [hH][aA][sSzZ] will let you avoid LOLCAT inanity.
maximumStatusCount	-integer	200	This preference specifies how many tweets from your timeline to hold in memory.
maximumMessagesCount	-integer	20	This preference specifies how many direct messages to hold in memory.
sonicTwooshTechnology	-bool	NO	The vocal stylings of Jonathan Wolf' Rentzsch inform you when a posted tweet is exactly 140 characters long.
growlMaximumShown	-integer	5	This value sets the maximum number of Growl notifications that will be displayed after a refresh. If there are more than the maximum, a summary is displayed.
displayScreenName	-bool	NO	When this preference is set to YES, chockenberry will be displayed instead of Craig Hockenberry.
pinScrollingEdges	-bool	NO	This preference changes how the view is scrolled when keep same view is selected. If your view is at the very top of the list, that position is maintained.

Eastern and Western Districts of Arkansas
Local Rule 26.1 Outline for Fed. R. Civ. P. 26(f) Report

District of Alaska
Local Form 26(f): Scheduling and Planning Conference Report (see item 4(B))
Local Rule 16.1 Pre-Trial Procedures (requiring use of Local Form 26(f) or one substantially similar)

District of Arizona
Order Setting Rule 16 Case Management Conference (Magistrate Judge Michelle H. Burns)
Order Setting Rule 16 Case Management Conference (District Judge David G. Campbell)
Order Setting Rule 16 Case Management Conference (Magistrate Judge David K. Duncan)
Order Setting Rule 16 Case Management Conference (District Judge Mary H. Murguia)

Northern District of California
Standing Order For All Judges Of The Northern District Of California: Contents Of Joint Case Management Statement (see item 6)
Local Rule 16-9 Case Management Statement and Proposed Order (requiring parties' Joint Case Management Statement to include all topics listed in Standing Order)

District of Colorado
Appendix F: Scheduling Order
Instructions for Preparation of Scheduling Order

District of Connecticut
Local Rules 16(b), 26, 37 and Form 26(F)

District of Delaware
Default Standards for Discovery of Electronic Documents

Middle District of Florida
Civil Discovery Practice Handbook (see Part VII Technology)

Southern District of Florida
Rule 16.1 Pretrial Procedure in Civil Actions
Rule 26.1 Discovery and Discovery Material (Civil)
Appendix A: Discovery Practices Handbook (see Part III, in particular)

Southern District of Georgia
Rule 26(f) Report

Central District of Illinois
Magistrate Judge Byron G. Cudmore's Rule 16 Scheduling Order
Magistrate Judge David G. Bernthal's Suggested Form for Proposed Discovery Plan (Urbana Division)

Northern District of Indiana
Report of Parties' Planning Meeting

Southern District of Indiana
Uniform Case Management Plan (see Part III(K))
Rule 16.1 Pretrial Procedures (requiring use of Uniform Case Management Plan)

Northern and Southern Districts of Iowa
Scheduling Order and Discovery Plan
Instructions and Worksheet for Preparation of Scheduling Order and Discovery Plan and Order Requiring Submission of Same
Local Rule 16.1 Scheduling Order and Discovery Plan (requiring use of form)
Local Rule 26.1 Pretrial Discovery and Disclosures (requirement to submit discovery plan satisfied by submission of form Scheduling Order and Discovery Plan)

District of Kansas
Guidelines for Discovery of Electronically Stored Information
Initial Order Regarding Planning and Scheduling

District of Maryland
Suggested Protocol for Discovery of Electronically Stored Information

Eastern District of Missouri
Local Rule 3.01. Federal Rule of Civil Procedure 26

District of New Hampshire
Local Rule 26.1 Discovery Plan
Civil Form 2: Sample Discovery Plan

District of New Jersey
Local Rule 26.1 Discovery (see subpart (d))

Southern District of New York
Individual Practices of District Judge Harold Baer, Jr. (see Item 3)
Proposed Pretrial Scheduling Order (District Judge Harold Baer, Jr.)
District Judge Colleen McMahon's Rules Governing Electronic Discovery
Civil Case Management Plan (District Judge Colleen McMahon)

Northern District of Ohio
Local Rules, Appendix K: Default Standards for Discovery of Electronically Stored Information (E-Discovery)
Rule 16.3 Track Assignment and Case Management Conference
Case Management Conference Scheduling Order (District Judge Dan Aaron Polster)
Case Management Conference Notice (District Judge Jack Zouhary)
Case Management Conference Order (District Judge Jack Zouhary)

Southern District of Ohio
Rule 26(f) Report of Parties (Western Division at Dayton)
Joint Discovery Plan (Western Division) (District Judge Susan J. Dlott)
Rule 26(f) Report of the Parties (Eastern Division)

Eastern District of Pennsylvania
Report of Rule 26(f) Meeting
Pretrial Scheduling/Status Conference Report (Senior District Judge Norma L. Shapiro)
Standard Management Track; Order (Senior District Judge Norma L. Shapiro)
Order Governing Electronic Discovery (District Judge Timothy J. Savage)
District Judge Timothy J. Savage's Scheduling and Motion Policies and Procedures

Middle District of Pennsylvania
Local Rule 26.1 Duty to Investigate and Disclose

Western District of Pennsylvania
Local Rule 16.1.1 Scheduling and Pretrial Conferences - Generally (see item (B), requiring use of Appendix B form)
Appendix B: Fed. R. Civ. P. 26(f) Report of the Parties (see item 11)

Eastern District of Tennessee
Form Scheduling Order (Knoxville) (Senior District Judge Leon Jordan) (see Item 4(d))
Form Scheduling Order (Knoxville) (District Judge Thomas A. Varlan) (see Item 4(d))
Form Scheduling Order (Chattanooga) (Magistrate Judge Susan K. Lee) (see Item 5(a))

Middle District of Tennessee
Administrative Order No. 74: Default Standard for Discovery of Electronically Stored Information (E-Discovery)
Sample Initial Case Management Order (District Judge Aleta A. Trauger) (see Item L)

Western District of Tennessee
Form Scheduling Order (Western Division) (Magistrate Judge Diane K. Vescovo)

Eastern District of Texas
Notice of Scheduling Conference, Proposed Discovery Order, and Proposed Dates for Docket Control Order (Magistrate Judge John D. Love) (see item 2(A))

Northern District of Texas
Miscellaneous Order No. 62 (Dallas Division, Patent Cases) (see item 2.1(a)(2))

Southern District of Texas
Local Rules of Practice for Patent Cases (Corpus Christi Division) (see Rule 2-1(a)(2))
Court Procedures of District Judge Nancy F. Atlas (see Item 6(C)(5) and Joint Discovery/Case Management Plan)
Court Procedures of District Judge Lee H. Rosenthal (see Joint Discovery/Case Management Plan)

District of Utah
Attorneys' Planning Meeting Report

District of Vermont
Local Rule 26.1 Discovery
Local Form Rule 26.1(b): Stipulated Discovery Schedule/Order

Southern District of West Virginia
Report of Parties' Planning Meeting
Local Rule 16.1 Scheduling Conferences (requiring use of court's form)

District of Wyoming
Local Rule 26.1 Discovery and Appendix D: Rule 26 Conference Checklist (see subpart (e) of local rule)

For more information on the local rules of United States District Courts, click here to see a page with links to all the District Courts' web pages.

Verizon seeks unspecified monetary damages and wants Cox blocked from using the patents in the future.

Below is a list of the specific patents and links to the actual patent. Four of the eight patents are ones that Verizon alleged Vonage had infringed. A federal appeals court affirmed Vonage infringed two of Verizon's patents. In October of last year, Vonage agreed to pay Verizon up to US$120 million.

This case against Cox is significant because rather than seeking the same win it got from Vonage from other similarly situated companies, Verizon is now seeking to expand the breadth of its winning patent portfolio to fixed VoIP. To the extent that Verizon wins here, this could have broad implications for other fixed services using Docsys (as Cox and the rest of the cable industry generally use), presumably other fixed VoIP that doesn't use Docsys, and depending on which if any patents are upheld to VoIP billing systems, routing systems, network management, and other technologies. So while this is the first major suit against a fixed VoIP services, my quick read of the patents suggests that only in a few cases (like the 930 patent) are the patents limited to fixed functionality. Among analysts, there is still speculation as to why Verizon chose to go after Cox cable instead of a cable company like Comcast who presumably uses the same technology, shares a greater competition footprint, and has a larger number of customers.

The patents Verizon says Cox is infringing upon:

U.S. Patent No. 6,970,930 available here (not in Vonage case) Method and system of providing differentiated services

U.S. Patent No. 6,104,711 available here (Vonage was found to have infringed) Enhanced Internet domain name server to translate information from a public, packet-based network

U.S. Patent No. 6,430,275 available here (Vonage found not to have infringed) Enhanced signaling for terminating resource

U.S. Patent No. 6,137,869 available here (Vonage found not to have infringed) Network session management

U.S. Patent No. 6,282,574 available here (Vonage was found to have infringed) Method, server and telecommunications system for name translation on a conditional basis and/or to a telephone number

U.S. Patent No. 6,335,927 available here (not in Vonage case) Multi-protocol telecommunications routing optimization

U.S. Patent No. 6,292,481 available here (not in Vonage case) Inter-carrier signaling and usage accounting architecture for internet telephony

U.S. Patent No. 6,636,597 available here (not in Vonage case) Method of and system for providing services in a communications network

It's no secret that consumers are quickly turning to Internet voice services because they are exciting, innovative and often do things never before possible with traditional PSTN phones. It's just disappointing that rather than trying to win over consumers, companies have tried to win over judges. As TeleGeography notes as Vonage's growth has slowed, "US VoIP subscriber growth is falling well behind the blistering pace set by European VoIP service providers." It means that "by 2011, VoIP penetration in Europe will be approximately twice as great as in the US." One of the key differences as TeleGeography points out is that in Europe, incumbent service providers have had to compete against VoIP providers and now themselves account for 26% of VoIP subscribers, while in the US incumbents have remained largely on the sidelines in terms of VoIP.

At the dawn of a new era, we should be trying to lead the world in broadband based communication technologies and putting new ideas into action for consumers. It would be a shame if because of policy and patents, that America lost its leadership in a key enabling technology because we argued more over who invented which aspect rather than how we advance it.

We can and should do better.

-----

Readers of my blog are invited to join me on both twitter and Facebook.

Tags: Vonage, Patent, Cox, Verizon, VoIP, Jeff Pulver

Google ber Allies

A Sliced Apple

Dance of the Elephants

Sun Sets on Palm?

Facing the Music

Success and Motivation, Part 1

Apr 23rd 2004 9:37AM

Success and Motivation

I did it too. I drove by big houses and would wonder who lived there. What did they do for a living? How did they make their money? Someday, I would tell myself, I would live in a house like that. Every weekend I would do it.

I read books about successful people. In fact, I read every book or magazine I could get my hands on. I would tell myself 1 good idea would pay for the book and could make the difference between me making it or not.

I worked jobs I didn't like. I worked jobs I loved, but had no chance of being a career. I worked jobs that barely paid the rent. I had so many jobs my parents wondered if I would be stable. Most of them aren't on my resume anymore because I was there so short a time or they were so stupid I was embarrassed. You don't want to write about selling powdered milk or selling franchises for TV repair shops. In every job, I would justify it in my mind whether I loved it or hated it that I was getting paid to learn and every experience would be of value when I figured out what I wanted to do when I grew up.

If I ever grew up, I hoped to run my own business some day. It's exactly what I told myself every day. In reality, I had as much doubt as confidence. I was just hoping the confidence would win over the doubt and it would all work out for the best.

I remember being 24 years old, living in Dallas in a 3-bedroom apartment with 5 other friends. This wasn't a really nice place we all kicked in to move up for. This place has since been torn down. Probably condemned. I didn't have my own bedroom. I slept on the couch or floor depending on what time I got home. I had no closet. Instead I had a pile that everyone knew was mine. My car had the usual hole in the floorboard, a '77 FIAT X19 that burned a quart of oil that I couldn't afford every week.

To make matters worse, because I was living on happy hour food, and the 2 beers cover charge, I was gaining weight like a pig. My confidence wasn't at an all time high. I was having fun. Don't get me wrong. I truly was having a blast. Great friends, great city, great energy, pretty girls. Ok, the pretty girls had no interest in my fat and growing ass at the time, but that's another story....

I was motivated to do something I loved. I just wasn't sure what it was. I made a list of all the different jobs I would love to do. (I still have it.) The problem was that I wasn't qualified for any of them. But I needed to pay the bills.

I finally got a job working as a bartender at a club. A start, but it wasn't a career. I had to keep on looking during the day.

About a week later I answered a want ad out of the newspaper for someone to sell PC Software at the first software retail store in Dallas. The ad was actually placed by an employment agency. The fee was to be paid by the company, so I gave it a shot.

I put on my interview face, and of course my interview suit, which just happened to be one of my 2 polyester suits that I had bought for the grand total of 99 dollars. Thank god for 2-fer, 2-fer, 2-fer madness at the local mens clothing store. Grey Pinstripe. Blue Pinstripe. Didn't matter if it rained, those drops just rolled down the back of those suits. I could crumple them. They bounced right back. Polyester, the miracle fabric.

I wish I could say the blue suit and my interview skills impressed the employment agency enough to set up the interview with the software store. In reality, not many had applied for the job and the agency wanted the fee so they would have sent anyone over to interview. I didn't care.

I pulled out the grey for my interview at Your Business Software. I was fired up. It was my shot to get into the computer business, one of the industries I had put on my list!

I remember the interview well. Michael Humecki the Prez, and Doug (don't remember his last name), his partner double-teamed me. Michael did most of the talking to start. He asked me if I had used PC software before. My total PC experience at the time was on the long forgotten TI/99A that had cost me 79 dollars. I used it to try to teach myself Basic while recovering from hangovers and sleeping on the floor while my roommates were at work. They weren't impressed.

I was trying to pull out every interview trick I knew. I went through the spiel about how I was a good salesperson, you know the part of the interview where you are basically begging for a job, using code phrases like "I care about the customer", "I promise to work really, really hard" and "I will do whatever it takes to be successful". Unfortunately, I was getting that "well if no one else applies for the job, maybe" look from Michael.

Finally, Doug spoke up. He asked me. "What do you do if a customer has a question about a software package and you don't know the answer?" All of the possible answers raced through my mind. I had to ask myself if this was the "honesty test question" you know where they want to see if you will admit to things you don't know. Is this some trick technology question and there is an answer everyone but me knows? After who knows how long, I blurted out that "I would look it up in the manual and find the answer for them." Ding, ding, ding...Doug just loved this answer.

Michael wasn't as convinced, but he then asked me the question I was dying to hear: "Would you not go back to the employment agency at all, so when we hire you we don't have to pay the fee?" I was in.

What does all this mean? Nothing yet. It was just fun to tell. You have to wait till part 2, if you care, and if there is a part two. Right now, it's much more important that I go play with my daughter.

Success and Motivation, Part 2

Apr 25th 2004 3:41AM

So my career in Dallas begins. I'm a software salesperson with Your Business Software in Dallas. $18k per year. The first retail software store in Dallas.

I have to sweep the floor and be there to open the store, but that's not a bad thing. When I tell my future ex-girlfriends that I sell software and am in the computer biz, I'm not going to mention the sweeping the floor part. Plus, I had to wear a suit to work, and the 2-fer madness specials looked good at happy hour after work. Better yet, the store didn't open till 9:30am, which meant if I had a fun night, I had at least a little time to sleep.

I bet right about now you are questioning where my focus was? Where was my commitment to being the future owner of the Dallas Mavericks? Please. I was stoked I had a good job. I was stoked it was in an industry that could turn into a career. At 24, I was just as stoked that the office was close to where the best happy hours were and that I might finally have more than 20 bucks to spend for a night on the town.

Since I'm talking about partying, I do have to say that my friends and I were very efficient in that area. Beyond living off bar food and happy hours, we literally would agree that none of us would bring more than 20 bucks for a weekend night out. This way we all could pace each other. At least that was the way it was supposed to work, and it did until we figured out the key to having a great night out on the cheap. They key was buying a bottle of cheap, cheap champagne. I can't even spell the name, but it was a full bottle, and it cost 12 bucks. Tear the label off and as far as anyone knew it was Dom. Each of us would grab one, and sip on it all night. It was far cheaper than buying beers or mixed drinks all night, and we never had to buy a drink for a girl, we just gave them some champagne! Of course the next day was hell, but since when was I responsible enough to care about a hangover...

But I digress. Back to business. As fired up as I was about the job, I was scared. Why? Because I have never worked with an IBM PC in my life. Not a single time, and I'm going to be selling software for it. So what do I do? I do what everyone does: I rationalize. I tell myself that the people walking in the door know as little as I do, so if I just started doing what I told my boss I would do, read the manuals, I would be ahead of the curve. That's what I did. Every night I would take home a different software manual, and I would read them. Of course the reading was captivating. Peachtree, PFS, DBase, Lotus, Accpac... I couldn't put them down. Every night I would read some after getting home, no matter how late.

Of course it was easy on the weekends. After drinking that cheap champagne, I wasn't getting out of bed till about 9pm, so I had tons of time to lie on the floor and read. It worked. Turns out not a lot of people ever bothered to RTFM (read the frickin' manual), so people started really thinking I knew my stuff. As more people came in, because I knew all the different software packages we offered, I could offer honest comparisons and customers respected that.

Within about 6 months, I was building a clientele and because I had also spent time on the store's computers learning how to install, configure and run the software, I started having customers ask me to install the software at their offices. That meant I got to charge for consulting help: 25 bucks an hour that I split with the store. That turned into a couple hundred extra bucks per month and growing. I was raking it in, enough that I could move from the Hotel (that was what we called our apartment) where the 6 of us lived, into a 3 bedroom apartment across the street, where instead of 6 of us, there were only 3. Finally, my own bedroom!

I was earning consulting fees. I was getting referrals. I was on the phone cold calling companies to get new business. I even worked out a deal with a local consultant who paid me referral fees, which lead to getting a $1500 check. It was the first time in my adult life that I was able to have more than 1k dollars in the bank.

That was a special moment believe or not, and what did I do to celebrate? Nope...I didn't buy better champagne. I had these old ratty towels that had holes in them and could stand on their own in the corner, they were so nasty I needed a shower from drying off after a shower...I went out and bought 6 of the fluffiest, plushest towels I could find. I was moving on up in the world. I had the towels. Life was good. Business was good and getting better for me. I was building my customer base, really starting to understand all the technology, and really establishing myself as someone who understood the software. More importantly no, most importantly I realized that I loved working with PCs. I had never done it before. I didn't know if this was going to be a job that worked for me, or that I would even like and it turns out I was lucky. I loved what I was doing. I was rolling so well, I was even partying less... during the week.

Then one day, about 9 months into my career as a salesperson/consultant, I had a prospect ask if I could come to his office to close a deal. 9am. No problem to me. Problem to my boss, Michael Humecki. Michael didn't want me to go. I had to open the store. That was my job. We were a retail store, not an outbound sales company. It sounded stupid to me back then too, particularly since I had gone on outbound calls during the day before. I guess he thought I was at lunch.

Decision time. It's always the little decisions that have the biggest impact. We all have to make that "make or break" call to follow orders or do what you know is right. I followed my first instinct: close the sale. I guess I could have rescheduled the appointment, but I rationalized that you never turn your back on a closed deal. So I called one of my coworkers to come in and open up, and closed the deal. Next day I came in check in hand from a new customer and Michael fired me.

Success and Motivation, Part 3

May 7th 2004 1:48AM

Read | Permalink | Email this | Comments

Office Depot Featured Gadget: Xbox 360 Platinum System Packs the power to bring games to life!

<Lawrence />

Introduction

Maybe you're lucky enough to work for a company that has standardized on SharePoint portals and ASP.NET applications across the board. In that case, you do not need to integrate different types of portals and web applications. For most large corporations, though, there will be many portals and different technologies behind those portals. I am currently working with one of those large enterprises that use non-Microsoft portals (from Linux/Apache/PHP sites all to the way to WebSphere) that need to integrate with Microsoft Office SharePoint Server (MOSS) 2007.

The question on how to integrate those with SharePoint is asked quite often. Sometimes there is a need to leverage content stored in SharePoint sites. In some cases SharePoint must consume data hosted in the other portals. There are many options to integrate SharePoint in those cases, so I compiled a list of different technologies you can leverage. Please note that I do not include in the list any of the WSS/MOSS SDK facilities to integrate with other ASP.NET applications, focusing on options applicable when working with a portal not hosted in a Microsoft-centric environment. I included ideas on how to integrate by producing and consuming links, e-mails, RSS feeds, IFrames, WSRP portlets, Web Services and Search.

1. Links

One simple way to integrate two web applications is simply providing links from one to the other. If you maintain a similar User Interface in both, users might not even notice the transitions.

1a. Links Producer

SharePoint is fundamentally an ASP.NET application and you can link to any WSS or MOSS site, list, library or item directly. There are also ways to link directly to specific views or actions associated with items. It would be possible, for instance, to have a URL pointing directly to the page that adds an item to a list.

1b. Links Consumer

SharePoint also provides rich support for hosting external links. You can use the built-in navigation facilities to link to items hosted outside MOSS. For instance, you can add a top navigation link or a quick launch link directly to a URL outside MOSS. You also have the choice to open the link in a new window or not. You also have a specific list type to store links and you can add external sites in other areas like the Site Directory. There are also many other out-of-the-box web parts where you can link to something living outside SharePoint.

Reference: How to customize navigation: http://office.microsoft.com/en-us/sharepointtechnology/HA101191001033.aspx

2. E-mail

E-mail via the SMTP protocol is something that we have used reliably for a long time. You can get data in and out of SharePoint using it and you'll likely find some level of support in many other portals.

2a. E-mail Producer

You can get e-mail alerts from any SharePoint list and it should not be hard to use that information to populate information in another portal. You can also associate a custom workflow to any list to send an e-mail to an external address every time a list item is added or updated, with the ability to format the body of the e-mail with properties of the item. Although those alerts and workflow-generated e-mails are typically sent to humans, they could be useful in an integration scenario, especially if your target can parse the mail message to isolate the individual properties.

2b. E-mail Consumer

You can configure any SharePoint list to be mail-enabled. With that, you can send e-mails directly to a SharePoint discussion list, add a blog entry or post a document attached to a message to a document library. A workflow or event handler could be use to further process items received that way to perform specific actions as these items are added.

Reference: How to add content to sites using e-mails: http://office.microsoft.com/en-us/sharepointtechnology/HA100867301033.aspx

3. RSS

RSS stands for Really Simple Syndication and it's a simple format to describe digital content. RSS is increasingly used on the Internet to provide information about frequently updated information like news feeds and blog posts.

3a. RSS Producer

You can enable any SharePoint list (including document libraries, calendars, task lists, blogs and wiki libraries) to provide an RSS feed. You have options to select which columns are provided in the feed (like title, date and author) and you can set a limit for the number of items and how old the items can be. Each RSS feed for a specific list has a URL and it comes to the client as an XML document.

References: How to manage RSS feeds: http://office.microsoft.com/en-us/sharepointtechnology/HA100214251033.aspx

3b. RSS Consumer

SharePoint provides an out-of-the-box web part called RSS Viewer, which allows you to place an RSS feed in any WSS page. You have a number of configuration options including obviously the URL where the feed comes from, how many items should be displayed and multiple options on how each one is shown.

4. IFrame

IFrames are HTML elements that let you display an HTML page inside another one. Most modern browsers will let you place this <iframe> HTML markup within a page, specifying the URL to the other page and the dimensions of the frame, among other options.

Reference: IFrame: http://www.w3.org/TR/html4/present/frames.html

4a. IFrame Producer

You obviously can include any SharePoint page into a page in another portal using an IFrame. The main issue there is the fact that you will get the MOSS navigation in that IFrame, which typically is not desired. To overcome that, you can create a special MOSS page that hides all those elements and show just the element you want to expose. To accomplish that, you can create a minimal master page and a simple layout with a single web part zone.

Reference: How to create a minimal master page: http://msdn2.microsoft.com/en-us/library/aa660698.aspx

4b. IFrame Consumer

SharePoint provides an out-of-the-box web part called Page Viewer, which allows you to display any other page as an IFrame.

5. WSRP

Web Services for Remote Portlets (WSRP) aims to standardize interactions between portals using a special set of markups to make it easy to consume a portion of the overall user portal without having to write unique code.

Reference: WSRP 1.0 specification from OASIS: http://www.oasis-open.org/committees/download.php/3343/oasis-200304-wsrp-specification-1.0.pdf

5a. WSRP Producer

Microsoft does not provide an out-of-the-box WSRP producer. However, you can leverage a third party solution like NetUnity Software to provide that functionality.

Reference: Blog about WSRP in SharePoint: http://blogs.msdn.com/mikefitz/archive/2006/02/06/525536.aspx
Reference: NetUnity Software web site: http://www.netunitysoftware.com

5b. WSRP Consumer

SharePoint provides an out-of-the-box web part called WSRP Consumer Web Part, which allows you to display a WSRP portlet in a MOSS page.

Reference: How to use the WSRP Consumer Web Part: http://www.wssdemo.com/blog/Lists/Posts/Post.aspx?List=d5813c18%2D934f%2D4fd6%2D9068%2D5cdd59ce56ba&ID=234

6. Web Services

Web Services (as defined by the W3C) are a series of standards to allow computers to communicate using XML messages and SOAP, describing their operations via WSDL. If a system exposes their functionality that way, any client supporting those standards can interact with it.

Reference: http://www.w3.org/2002/ws

6a. Web Services Producer

SharePoint exposes a lot of its functionality using Web Services over HTTP. This can be used, for instance, to get a list of libraries on a site, to add an item to a list, to get information about users, etc. SharePoint web services are implemented using the .NET Framework and they use SOAP, XML and HTTP, also providing a WSDL. The SharePoint SDK includes a complete reference of all the web services available and the list includes: Administration, Alerts, Authentication, Copy, Document Workspace, Forms, Imaging, List Data Retrieval, Lists, Meetings, People, Permissions, SharePoint Directory Management, Site Data, Sites, Search, Users and Groups, Versions, Views, Web Part Pages, and Webs.

Reference: List of Web Services in WSS/MOSS: http://msdn2.microsoft.com/en-us/library/ms445760.aspx

6b. Web Services Consumer

SharePoint can leverage web services exposed by other applications using the Business Data Catalog (BDC). This is done using an XML-based definition of what is exposed by that application and usually involves describing entities, properties and actions that are exposed by that application. Once the BDC definition is in place, you can expose those via the BDC-related web parts. You can also integrate the BDC data as a content source for Search. Another option is to write a custom web part that consumes the external web service and provides a user interface to interact with it.

Reference: Business Data Catalog Overview: http://msdn2.microsoft.com/en-us/library/ms551230.aspx

P.S.: Also, as suggested by Ian Morrish, the Data Form Web Part (known as Data View Web Part in the previous version) can render Web Services and XML using XSL. For details around this, check http://www.sharepointblogs.com/ssa/archive/2007/02/24/showing-web-service-data-in-a-data-view-web-part.aspx

7. Search

Search is usually a main component of a portal. When two portals are interacting, they will typically need to search or be searched by each other.

7a. Search Producer

SharePoint exposes all its data via HTTP and you can configure any search engine to crawl it. The search engine would start with a site directory and for each site it will use the View All Site Content link on the quick launch to discover all lists and libraries on the site. SharePoint also has a crawl web service that could be leveraged to enumerate all site collections even if you don't have a site directory.

Reference: How the MOSS crawl works: http://blogs.technet.com/josebda/archive/2007/03/19/crawling-sharepoint-sites-using-the-sps3-protocol-handler.aspx

7b. Search Consumer

SharePoint can index several types of content sources beyond SharePoint sites. That includes any HTTP-based web site, file shares using SMB and anything you are consuming via the BDC. You basically need to define a content source in the Search SSP to describe how and when your crawl should run. You can also develop your own protocol handler to address custom scenarios.

Reference: How SharePoint crawls content: http://technet2.microsoft.com/Office/en-us/library/f32cb02e-e396-46c5-a65a-e1b045152b6b1033.mspx

8. WebDav

Although not really an integration technology, WebDAV provides a way to download and upload files hosted in SharePoint. This is what clients leverage for the explorer view and there are many clients that can interact that way.

9. AJAX

AJAX is not a specific technology but a set of technologies, mostly related to using client-side javascript to asynchronously do post backs and partial page refreshes. If you are using AJAX, you can leverage some of the other technologies mentioned here to interact with SharePoint. There is no out-of-the-box web part to host AJAX code, but there's already many discussions detailing how to support this scenario and leverage it inside a web part.

Reference: Information about ASP.NET-based AJAX: http://ajax.asp.net
Reference: Building a web part that uses AJAX: http://www.capdes.com/2007/02/microsoft_office_sharepoint_se.html
Reference: Building a web part that uses AJAX: http://sharethispoint.com/archive/2007/02/28/Using-a-SPGridView-inside-an-ASP.net-Ajax-UpdatePanel.aspx

Conclusion

I hope that helps you sort out the multiple different integration points and will allow you to choose the best technology for your specific case. There are certainly a lot of details to account for, like whether you are planning to write custom code to help with the integration (and if you are, on what side you will be hosting that code) and how the authentication between the two systems will work (Kerberos is your friend and so is MOSS 2007 SSO).

I find the RSS feeds option quite interesting, since it is easy to implement, provides much more functionality than simple links, allows for some level of customization and could even work well with an AJAX-type solution. If you can get away with that one, you will certainly have a lot less to worry about.