CALL FOR PRIOR ART: (Twitter) “Device independent message distribution platform” (8401009)

Question

This is a recently issued patent from Twitter

"Device independent message distribution platform"

This recently issued patent describes the basic mechanics and functionality of Twitter.

BASIC PATENT DATA:

• Patent Number: 8,401,009
• Priority Number: US2008177589
• Issue Date: March 19, 2013
• Priority Date: July 22, 2008 (provisional filed July 23, 2007)
• Assignee: Twitter, Inc.
• Inventor: Jack Dorsey, San Francisco and Christopher Isaac Stone

PATENT OVERVIEW: This is the patent that describes the basic mechanics and functionality of Twitter, summarized roughly as:

• A method of communicating among users
• One user (the "first" user) can "follow" another user (the "second" user).
• The "second" user can post a message. The message is not posted "to" anyone, it is just posted.
• All followers of the second user receive the posted message.
• The first user can choose from a set of possible methods for receiving messages.

The first claim contains more steps such as, if the first user tells the system whom they wish to follow, the system records that fact. And when the second user posts a message, the system looks up the list of all users previously recorded as following that user so it knows who to send copies of the message to. And so on.

Claim 1 requires, specifically:

1. A method for device-independent point to multipoint communication, the method comprising:

   Receiving from a first computing device of a first user a selection of one or more endpoints for receiving update messages;

   Receiving, from the first computing device, a request to follow a second user;

   Designating, by a computer processor, the first user as a follower of the second user in response to the request, wherein designating the first user comprises configuring an account of the first user to reference update messages broadcasted by the second user;

   Receiving, from a computing device of the second user, a broadcast request to broadcast an update message in a first format, wherein the update message lacks identification of the first user as an intended recipient, and wherein the update message includes an identification of the second user as a sender of the update message;

   Identifying, by the computer processor, a plurality of followers of the second user in response to the broadcast request, wherein the first user is among the plurality of followers;

   Determining addressing information of each of the plurality of followers, wherein the addressing information of the first user identifies the endpoints for receiving messages;

   Applying, for each of the plurality of followers, rules to the update message based on the addressing information;

   Translating the update message into an appropriate format for each of the endpoints; and

   Broadcasting the update message to each of the endpoints in the appropriate format.

Other claims are for the computer system that does this.

WHY IT MATTERS: This patent covers the basic functionality of a Twitter-like service.

Are you familiar with technology similar to that described in this patent application?

If so, please submit evidence of that prior art as an answer below. Please submit only one piece of prior art per answer below. We welcome multiple prior art proposals from the same individual; please create separate answers for each one. This is so the community can vet each individual piece of prior art independently.

For details about what makes good prior art, please see our FAQ. If you'd like to contribute in another way, please vote or comment on submissions made below. And we welcome you to post your own request for prior art if you know of another questionable patent or patent application. Thanks for participating!

Answer 1

Interesting reference, but I think one main difference is that Miski is based on users subscribing to arbitrary subjects, whereas the Twitter patent is (partly) based on users subscribing to other users. Now this might seem like an obvious variation ("let subject = user id"), but:

1. it changes the functionality in subtle but significant ways (for instance, only one user can make posts on a "subject", and a user can only make posts on one "subject"); and
2. the claims have many other elements in addition to followed/follower mechanics, and this is related to only one of those (and even that one it doesn't directly address).

When it comes to subject-based publish/subscribe systems, there are many, many other systems that may predate even Miski, such as mailing lists, group chatrooms, and message-oriented middleware such as MQSeries/MQ, Tibco, and so on. A quick glance at the cited references found quite a few about forwarding messages to relevant subscribers (although I didn't find any where the subscription is for a user).

Additionally, it's important to realize that the claim has many requirements other than following posts. The first claim is as follows:

A method for device-independent point to multipoint communication, the method comprising:

receiving from a first computing device of a first user a selection of one or more endpoints for receiving update messages;

receiving, from the first computing device, a request to follow a second user;

designating, by a computer processor, the first user as a follower of the second user in response to the request, wherein designating the first user comprises configuring an account of the first user to reference update messages broadcasted by the second user;

receiving, from a computing device of the second user, a broadcast request to broadcast an update message in a first format, wherein the update message lacks identification of the first user as an intended recipient, and wherein the update message includes an identification of the second user as a sender of the update message;

identifying, by the computer processor, a plurality of followers of the second user in response to the broadcast request, wherein the first user is among the plurality of followers;

determining addressing information of each of the plurality of followers, wherein the addressing information of the first user identifies the endpoints for receiving messages;

applying, for each of the plurality of followers, rules to the update message based on the addressing information;

translating the update message into an appropriate format for each of the endpoints; and

broadcasting the update message to each of the endpoints in the appropriate format.

As such, the claim is not only about following users and broadcasting posts to followers, but also about "applying rules" based on "addressing information" to those posts and "translating" them to "appropriate formats" based on the devices associated with the followers. (Plenty of prior art around for those aspects as well, including in the cited references, but the combination of all these aspects is what made the claim novel and non-obvious. Conversely, one must perform all the elements in the claim to infringe.)

Answer 2

Miski: A White Paper

This document, which originally existed as a documentation web page for an unimplemented project on SourceForge, now only exists as a series of snapshots on Wayback.

The document describes a messaging system with follower/following mechanics, very similar to that described in the independent claims of the patent. Note that Feb 2001 is not only earlier than the application date for 8401009, it is also earlier than all but two of the patents in the "Referenced" list, and those two don't have anything to do with "follower/following". The reason I assert priority over the other references is to point out that one can determine the relevance of Miski as prior art without reading all the other references dated later.

To match Miski with the Twitter-like system defined in the patent's first claim, one must translate or relate concepts as follows:

• The patent's "first user" is the subscribing user in the Miski document (which I also referred to as the "second user" at one point).
• The patent's "second user" is the posting user in the Miski document (which I also referred to as the "first user" in some places).
• There are no "subjects" in the patent. Miski would be equivalent in functionality to Twitter if everyone had a default subject called "Everything" (this scenario is not considered in the Miski document, but the users of an actual implementation of Miski would always be able to choose to define such a subject within their own subject hierarchy).
• In the Miski document, I suggested that a message always consists of a URL which points to the content. As with the patent, actual delivery of the message is by whatever means is agreed between the subscriber and the system.
• Within the 9 steps detailed in the patent's first claim, the Miski document does not explicitly list steps 5 to 9 as separate steps, but it does clearly state that a message is delivered from poster to poster's server to subscriber's server to subscriber, as a consequence of the subscriber subscribing to the poster and the poster then posting a message. At the time of writing, I would have regarded the detailed computation steps required as fairly "obvious" (but I could discuss this in further detail if desired).
• In the Miski document I described a system of unique IDs, where each ID consists of a unique name within a given domain plus a domain name, with a similar structure to that of email addresses. The patent claims do not seem to mention assignment of IDs at all, although it is hard to imagine how a Twitter-like system could be implemented without explicit IDs.
• "Reposting" is like "retweeting" (but there is no "retweeting" in the patent anyway, so that concept is not relevant to the prior art issue).

To assist with reading the Miski document, so that anyone can skip those parts not relevant to the issue of prior art, I have identified three selections within the document that contain all the prior art for this patent:

• From "A brief summary of the features that define the Miski system is as follows -" to "The headers include a web URL pointing to message bodies for those messages for which the receiving users decide they want to receive the full contents."
• From "The following scenario demonstrates the basic features of the system- " to "Her web browser retrieves the message contents from Fred's server. "
• The section under the heading "Delivery Methods" (which ends "as a moderated chat system.")

Answer 3

How about US Patent No. 6,389,455 (1998 filing)?

Col. 8:4 references corporate accounts where the regional manager can be on the receiving end of sale rep communications. All contacts go through a dotbounce hub so the message is not sent to anyone. Rules of the forward impact formatting.

---

EDIT

For those that did not read the '009 patent -

"Disclosed is a system (and/or method) that includes, for example, a routing engine that receives a message from any of various entry points, including e-mail, .... The routing engine determines the identities of the destination users to receive the message, possibly by expanding destination groups. The routing engine determines the endpoints on which the destination users wish to receive the message, the endpoints can be one or more of e-mail,.... The destination endpoints are independent of the source entry points, and the message sender does not need to have knowledge of the endpoints, or endpoint-specific user addresses."

The '009 is premised on the belief that as of its filing -

"Additionally, there is no general method of sending a message to multiple users who may be receiving the same message using different devices or interfaces. For example, a user may want to send a message to three SMS recipients (all using different cell phone service providers), two e-mail recipients, and a web interface recipient."

Hate to tell you but that is what the '455 patent is. The big question is who is Meyer Cordless LLC?

__ Edit - answered my own question - Looks like it is affiliated somehow with IV.

http://webcache.googleusercontent.com/search?q=cache:kJPfdZL-WgQJ:www.plainsite.org/flashlight/index.html%3Fid%3D3245967+&cd=4&hl=en&ct=clnk&gl=us&client=firefox-a

__ EDIT - We've overcome the "'009 isn't directed to email" and are now on the "receiver choosing" is different, well to the extent you think "receiver choosing" is in the '009 claim -

'455 discloses the receiver controlling the flow of the email - Non-sender notifies and controls routing of the incoming message.

'455 - "For example, a user who is a frequent flier on a particular airline may wish to receive airborne e-mails care of the airborne e-mail service provider. Such airborne e-mail service provider notifies the bounce system of the presence of a particular User and inform the bounce system of the applicable routing address and duration of the validity of such routing address."

Is there is a particular element in the '009 claim that is lacking, point it out. Please reference the claim.