Unrren States PATENT AND TRADEMARK OFFICE. ae SMSO ea ‘ora ‘omnor01e OnE 2000 Tor Twitter, Ine anes Aun: Legal = patents, RAVER, CHARLES 1355 Market Street, Suite 900 San Francisco, CA 94103 Ts oe Please find below and/or attached an Office communication concerning this application or proceeding. ‘The time period for reply, if any, is set in the attached communication PIOL-90A (Rev, 08107)UNITED STATEe PATENT AND TRADEMARIC OFFICE, a Trademark ce United State? DO NOT USE IN PALM PRINTER (THROPARTY REQUESTER'S 00» PONDENGE ADE RYAN ALLEY IP | POBOxa7 ALEXANDRIA, VA 22813 EX PARTE REEXAMINATION COMMUNICATION TRANSMITTAL FORM REEXAMINATION CONTROL NO. 90014,072, PATENT NO, 9,088,532. ART UNIT 3992 Enclosed is a copy of the latest communication from the United States Patent and Trademark Office in the above identified ex parte reexamination proceeding (37 CFR 1.550(f)) Where this copy is supplied after the reply by requester, 37 CFR 1.535, or the time for filing a reply has passed, no submission on behalf of the ex parte reexamination requester will be acknowledged or considered (37 CFR 1.550(g)). PTOL-465 (Fiev.07-04)Control No. Patent Under Reexamination 90014,072 9088532, Office Action in Ex Parte Reexamination |-zzaminer Unit | AIA Fat Inventor to CHARLES CRAVER File) Status 992 No. ~ The MAILING DATE of this communication appears on the cover sheet with the correspondence address ~ 2.L] Responsive to the communication(s) filed on, C1 A cecaration(syatdavits) under 37 CFR 1.190(b) was/were fled on .0 This action is made FINAL ©.0 A statement under 37 CFR 1.530 has not been received from the patent owner {A shortened statutory period for response to this action is set to expire Z month(s) from the malig date of this letter. Failure to respond within the period for response wil result In termination ofthe proceeding and Issuance ofan ex parte reexamination certificate in accordance with this action. 37 CFR 1,550(d). EXTENSIONS OF TIME ARE GOVERNED BY 37 CFR 1.550(c). Ifthe period for response spectied above is less than thy (20) days, a response within the statutory minimum of thi (90) days willbe considered timely. Part! THE FOLLOWING ATTACHMENT(S) ARE PART OF THIS ACTION 1. C1 Notice of References Cited by Examiner, PTO-892 2. DD imerview summary, PTO-474 2. [1 Information Disclosure Statement, PTO/SB/08. 40 Part ll SUMMARY OF ACTION ta. BY Claims 1-9.8.9,19-15.17,20 and 21 are subject to reexamination 1p, Di) Claims 4-7.10-12.16.18 and 19 are not subject to reexamination, 2. 1 Claims have been canceled in the present reexamination proceeding 3. O claims __ are patentable andior confirmed 4. Bl Olaims 1.9.9 19-16 172021 are rejected 5. 1 Claims are objected to. 6. [1 Theckawings, led on___ are acceptable. 7. [1 The proposed drawing correction, filed on _has been (7a) [] approved (7b)] disapproved. 8. C1 Acknowledgment is made of the prorty claim under 35 USC. § 119(a}-() or () 2) CAI 5) Cisome" ©)C1None of the cetiied copies have 1 C1 been received 2 C1 not been received 2 [1 been filed in Application No, 4 (1 been fied in reexamination Control No. __ 5 C1 been received by the international Bureau in PCT application No * See the attached detailed Office action for a list ofthe cartiied copies nat received 9. (Since the proceeding appears to be in condition for issuance of an ex parte reexamination certificate except for formal matters, prosecution as fo the merits is closed in accordance with the practice under Ex parte Quayle, 1935 C.D. 11, 483 0.6. 213. 10.) Other: ve (if third party sequester) PTOL-466 (Rev. 08-12) Office Action in Ex Parte Reexamination Part of Paper No. 20180527Application/Control Number: 90/014,072 Page 2 Art Unit: 3992 lL Summary In the instant 90/014,072 ex parte reexamination of US Patent 9,088,532 (hereinafter "the ‘532 Patent’), claims 1-3, 8, 9, 13-15, 17, 20 and 21 are under reexamination in light of the Order Granting Reexamination mailed 3/12/2018 responding to the request for reexamination filed 1/19/2018 by the Third Party Requester. Claims 1-3, 8, 9, 13-15, 17, 20 and 21 stand rejected below. Extensions of Time Extensions of time under 37 CFR 1.136(a) will not be permitted in this reexamination proceedings because the provisions of 37 CFR 1.136 apply only to “an applicant” and not to the patent owner in a reexamination proceeding. Additionally, 35 U.S.C. 305 requires that ex parte reexamination proceedings “will be conducted with special dispatch” (37 CFR 1.550(a)). Extensions of time in ex parte reexamination proceedings are provided for in 37 CFR 1.550(c). Notification of Concurrent Proceedings The Patent Owner is reminded of the continuing responsibility under 37 CFR 1.985 to apprise the Office of any litigation activity, or other prior or concurrent proceeding, involving Patent No. 9,088,532 throughout the course of this reexamination proceeding. The third party requester is also reminded of the ability to similarly apprise the Office of any such activity or proceeding throughout the course of this reexamination proceeding. See MPEP § 2686 and 2686.04.Application/Control Number: 90/014,072 Page 3 Art Unit: 3992 Service of Papers Any paper filed by either the patent owner or the third party requester must be served on the other party in the reexamination proceeding in the manner provided by 37 CFR 1.248. See 37 CFR 1.903 and MPEP 2666.06. Related Proceedings and Matters The '532 Patent under reexamination is not currently under open litigation. The ‘532 Patent is not currently subject to Inter Partes Review before the Patent Trial and Appeal Board ("PTAB”). As the instant ‘532 Patent is still pending, and no final decision has been made in any litigation, the instant claims in this proceeding will be given their "broadest reasonable interpretation" consistent with the Patent specification. Please see In re Swanson, No. 07-1534 (Fed. Cir. 2008) ll, Background and Request Independent claims 1, 13, 20 and 21 as issued are as follows: 1. Amethod of message distribution, comprising: receiving, from a first computing device ofa first user, a selection of a plurality of endpoints for receiving messages, wherein the first user is one of a plurality of users who are followers of a second user; storing the selection of the plurality of endpoints in a storage; receiving, trom a second computing device of the second user, a message for distribution to one or more unspecified recipients; identifying, by a computer processor, the followers of the second user as recipients of the message; identifying, in the storage, the plurality of endpoints selected by the first user; and sending the message to the followers of the second user, including the first user, wherein the sending includes sending the message to each of the plurality of endpoints selected by the first user.Application/Control Number: 90/014,072 Page 4 Art Unit: 3992 13. A message distribution system, comprising: a computer processor; a routing engine executing on the computer processor and configured to: receive, from a first computing device of a first user, a selection of a plurality of endpoints for receiving messages, wherein the first user is one of a plurality of users who are followers of a second user; store the selection of the plurality of endpoints in a data repository; receive, from a second computing device of the second user, a message for distribution to one or more unspecified recipients; identify the followers of the second user as recipients of the message; and identify, in the data repository, the plurality of endpoints selected by the first user; and a transmission engine configured to send the message to the followers of the second user, including the first user, wherein the transmission engine sends the message to each of the plurality of endpoints selected by the first user. 20. A non-transitory computer readable medium comprising a plurality of instructions for message distribution, the plurality of instructions comprising functionality to: receive, from a first computing device of a first user, a selection of a plurality of endpoints for receiving messages, wherein the first user is one of a plurality of users who are followers of a second user; store the selection of the plurality of endpoints in a storage; receive, from a second computing device of the second user, a message for distribution to one or more unspecified recipients; identity the followers of the second user as recipients of the message; identity, in the storage, the plurality of endpoints selected by the first user; and send the message to the followers of the second user, including the first user, wherein the sending includes sending the message to each of the plurality of endpoints selected by first user. 21. A message distribution system for distributing messages, the message distribution system comprising: a computer processor; a routing engine executing on the computer processor and configured to: receive, from a first computing device of a first user, a request for joining a follower group of users following a second user; in response to receiving the request for joining, store information about the first user in a data repository for storing follower group information about the follower group of users: receive, from the first computing device of the first user, a selection of a plurality of endpoints for receiving messages, the plurality of endpoints including two or more of email, short messaging service (SMS) and web; store selection information regarding the selection of the plurality of endpoints in the data repository; receive, from a second computing device of the second user, a message for distribution to one or more unspecified recipients; identify, based on the stored follower group information, the users in the follower group as recipients of the message; and identify, based on the stored selection information, the plurality of endpoints selected by the first user; and a transmission engine configured to send the message to each of the users in the follower group, including the first user, ‘wherein the transmission engine is configured to send the message to each of the plurality of endpoints selected by the first user. The ‘532 Patent teaches towards a system and method for point to multipoint communication of messages. FIG 1 is representative:Application/Control Number: 90/014,072 Page 5 Art Unit: 3992 The system disclosed determines information about destination users including preferred devices and message receiving preferences, and applies rules based on such to determine message destinations. Col. 3 Il. 11-61. In the prosecution history of the '532 Patent, claims 1-21 were allowed after an amendment by Patent Owner in response to a Non-Final Rejection mailed 6/24/2014 rejecting claims over the Abrams, Ghadialy and Galbreath references. In his amendment, the limitations “wherein the first user is one of a plurality of users who are followers of a second user’, “if the message for distribution is for unspecified recipients” and “sending the message to the followers of the second user, including the first user, wherein the sending includes sending the message to each of the plurality of endpoints selected by the first user” were added to issued claim 1, and similar limitations were added to issued claims 13, 20 and 21.Application/Control Number: 90/014,072 Page 6 Art Unit: 3992 IV. References Rathod Rathod discloses a system for sending and receiving messages to subscriber groups among known or unknown user subscribers. Rathod at 453, 304. A messenger interface allows a sender to select endpoints. /d. at FIG 18 and ¢ 270. Hull Hull discloses a system for sending and receiving messages to subscriber groups among known or unknown user subscribers in a social network. FIG 6 is representative:Application/Control Number: 90/014,072 Page 7 Art Unit: 3992 In Hull, indirect relationships exist between a first user and other users. Hull at {4 0018-0019. Tingo Tingo discloses a messaging system including rules for identifying receipt preferences and making determinations for message sending based thereon. Tingo at 90057-0061 V. Rejections Claim Rejections - 35 USC §§ 102 and 103 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AlA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of the appropriate paragraphs of pre-AIA 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless — (a) the invention was known or used by others in this country, or patented or described in a printed publication in this or a foreign country, before the invention thereof by the applicant for a patent. (6) the invention was desoribed in a patent granted on an application for patent by another filed in the United States before the invention thereat by the applicant for patent, or on an Intemational application by another who has fulfilled the requirements of paragraphs (1), (2), and (4) of section 371(c) of this ttle before the invention thereof by the applicant for patent.Application/Control Number: 90/014,072 Page 8 Art Unit: 3992 The following is a quotation of pre-AIA 35 U.S.C. 103(a) which forms the basis for all obviousness rejections set forth in this Office action: (@) Appatent may not be obtained though the invention is not identically disclosed or described {as set forth in section 102, if the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subjact ‘matter pertains. Patentability shall not be negatived by the manner in which the invention was made, Rathod REJ 1) Claims 1-3, 8, 9, 13-15, 17, 20 and 21 are rejected under 35 USC § 102(a) or (e) as anticipated by Rathod. Rathod, being published on May 10, 2007, constitutes prior arl under 35 U.S.C. § 102(a) (Pre-AIA) against the '532 Patent, which has an earliest claimed priority date of July 28, 2007, after the publication date of Rathod. Rathod, being filed as an Intemational Application on July 18, 2006 signating the US and published in English, constitutes prior art under 35 U.S.C. § 102(e) (Pre-AiA) against the ’532 Patent, which has an earliest claimed priority date of July 23, 2007, after the filing date of Rathod. As to claim 1, Rathod discloses a method of message distribution (A Human Services Network (HSN) includes a Messenger with communications interfaces. See Rathod 925, describing HSN of FIG. 8 with “management functions includfing]... Communication"; FIG. 18, Messenger element 18G), comprising receiving, from a first computing device of a first user, a selection of a plurality of endpoints (devices or interfaces where a message is to be delivered) for receiving messages, wherein the first user is one of a plurality of users who are followers (including a member of a group who has registered for another user, such as aApplication/Control Number: 90/014,072 Page 9 Art Unit: 3992 subscriber) of a second user (in Rathod FIG. 6, element 6J, several different ‘first computing devices" (PDS, Laptop, Mobile, etc.) of a first user are connected to the HSN. See Rathod, $248. In an HSN Messenger interface of FIG. 18, the “first user," a subscriber, makes a "selection from a plurality of endpoints” in 18H for message delivery, including IM, E-Mail, Voice, etc. See Rathod, $270 (°FIG. 18 showing [GUI] for Subscriber... 18H... providing for selection of various communication modality including text mfe}ssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, ‘meeting and collaborating’); In Rathod, FIG. 18, the HSN messenger 18G is controlled by an Explorer (HSNE) with tools 181 for the subscriber or “first user* to be a “follower[Jof the second user.” See Rathod, $270 (HSNE “illustrate various tools for ‘match making, various....(78L) parameters selection including taxonomy." *18G...showfs] a mfe}ssfen]ger having a input area and mfe}ssaging contents of each of participant in the communication process with the said subscriber or within the said group." Also in Rathod, FIG. 26, the HSN Explorer (SNE) shows selection and matching of various agents, which is a "second user." See Rathod 9279-280 (describing FIG. 26 as a wizard interface for each channel of the HSN). in the same interface of FIG. 18, the message is sent to the selected “endpoint” in 18H, including IM, E-Mail, Voice, etc. See Rathod, 1270 ("FIG. 18 showing [GUI] for Subscriber... 18H providing for selection of various communication modality including text mfejssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’)Application/Control Number: 90/014,072 Page 10 Art Unit: 3992 storing the selection of the plurality of endpoints in a storage (Selected endpoints must necessarily be stored in a computer system to achieve the sending discussed below. Nonetheless, in Rathod, FIGS. 1 & 2, the HSN network includes an MS SQL Server 1C/2C and Web Database 18/28 that stores all system data with a host 1A/2A. See Rathod, 9243-244 ("FIG. 2 shows a schematic... ilustrating structural connection of developer nodes in the peer to peer environment along with the relationship aspects thereof with the other channel nodes and HSN controller. 24- 2G illustrating preferred components of present web server so as to establish connection with the various HumanServiceNet Channel nodes and interne! framework”); receiving, from a second computing device of the second user, a message for distribution to one or more unspecified recipients (such as a status update to one or more followers; in Rathod FIG. 4, agents, which are followed "second users” as discussed in the first receiving step, access the HSN through their own “second computing device" and interlace. See Rathod $246 ("FIG. 4 shows a schematic block diagram of a [HSN] Human Agent (4SNHA)... with other channel nodes and peer service providers therein the UHSF system... wherein each of operational modes for muttidevice (41) enablement is represented along with multiuser (4F} operation and muttictiont usability in the various smart devices (4J))”. These second users have a same message interface in Rathod FIG. 21 for communicating with subscribers, who use the interface in Rathod FIG. 18. See Rathod 270 ("18J & 21 J showing a subscriber's and human agent's workspace respectively’); in Flathod, the HSN systemApplication/Control Number: 90/014,072 Page 11 Art Unit: 3992 is configured for message “distribution to one or more unspecified recipients.” See Rathod, 953 ("the present invention is to communicate securely with unknown human user or human circle"); 9304 ("HSNE provides for Email. .. with known as weil as unknown users and subscribe for auto contents from selected multi sources’). Especially, in FIG. 21 of Rathod, followed agents Sam Page, LasVegas, efc., “second users" send messages to a group in messenger 21G without any specified recipient - all subscribers receive the messages as “one or more unspecitied recipients." See Rathod, FIGS. 18 and 21 ("! send detail... message 21G of agent in FIG. 21, delivered lo group 18G in FIG. 18 without specifying a distinct user’), 91270 ("18G & 21G showing a mfe[ss[en|ger having a input area and mfe|ssaging contents of each of participant in the communication process with the said subscriber or within the said group") Identifying (must inherently occur for sending), by a computer processor, the followers of the second user as recipients of the message; identifying, in the storage, the plurality of endpoints selected by the first user (Rathod FIGS. 1 and 2 itustrate a web host 1A/2A including the above-discussed HSN Services ID, including “followers of the second user as recipients” and "endpoints selected by the first user" input as discussed in the first “receiving” step. These services are interfaced with Database Server 1C and IB having all other data, including the “followers” and "endpoints" for identification in the sending. See Rathod, 1243; FIGS. 1, 2); andApplication/Control Number: 90/014,072 Page 12 Art Unit: 3992 sending the message to the followers of the second user, including the first user, wherein the sending includes sending the message to each of the plurality of endpoints selected by the first user (in Rathod, the HSN system in FIGS. 18 and 21 ilustrates "sending the message to the followers of the second user" as the message- receiving group in messenger 21G. The message “I send detail...in 21G of agent/second user in FIG. 21 is delivered ("/ send detail... *) fo the group in 18G in FIG. 18, which is the receiving interface for the subscriberiirst user. See Rathod, 1270 (°18G & 21G showing a mfelssfeniger having a input area and mfejssaging contents of each of participant in (he communication process with the said subscriber or within the said group’). In an HSN Messenger interface of FIG. 18, the message is sent to “endpoints selected by the first user,” in this instance the "HSN IM" tab selected in 18H that causes the message to appear in the HSN IM message interlace 18G. See Rathod, 9270 ("FIG. 18 showing [GUI] for Subscriber... 18H... providing for selection of various communication modality including text mfe}ssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’); see also, 1150 ("The present invention provisioned for information and knowledge to anybody, anywhere ... to communicate via any util icluding HSN IM, HSN Email, Phone, Fax, Collaborative tools. File sharing tools, E-Mail etc.) As to claim 2, Rathod discloses further that the second user is one of a plurality of users who are followers of the first user, and wherein the second user receives messages sent to followers of the first user, and wherein the plurality of endpoints comprises e-mail, short messaging service (SMS), and web (/n Rathod, the agents mayApplication/Control Number: 90/014,072 Page 13 Art Unit: 3992 also subscribe to the subscribers through two-way matchmaking, in reverse of claim 1; that is, "the second user is [a] follower] of the first user.” See Rathod, $304 ("Send or advertise Email content to any matched subscribers (two way match making)"). in Rathod FIG. 18, the endpoints 18H include "email, SMS, and web."See Rathod, $270 (18H & 21H... including text mfejssaging.. .. file sharing,. . . emailing’}) As to claim 3, Rathod discloses further: receiving, from the first computing device, an SMS registration message requesting creation of a new account of the first user (in Rathod, @ channel node. a communications link from the user's “computing device’ requests "registration" with the system via "SMS." See Rathod, claim 90 (HSN receives "registration request from plurality of channel nodes via... SMS"); creating the new account in response to receiving the SMS registration message (in Rathod, the SMS “registration message” causes a ‘new account” to be “created.” See Rathod, 115 (subscribers are “made to register at the Human service net controller server"), 19101, 126 (server creates "record in response to a first registration request in the database thereof via information inputted by each of the unregistered user")); and sending, to the first computing device, an acknowledgement message indicating that the new account is created, wherein the plurality of endpoints is associated with the new account in the storage (An “acknowledgement message" could be any communication foliowing registration that would indicate the account is created. In Rathod, a user name or identity of the user is created, which governs where - that is, 10Application/Control Number: 90/014,072 Page 14 Art Unit: 3992 what “endpoint” - the messages are sent. Further, an “acknowledgement” in the form of key and login data is provided following registration. See Rathod, 1126, (server creates database entry including “identity of a said unregistered user and a field representing a role of the said unregistered user in the primary transaction" Then, “after completion of said first registration HSN controller generating a channel identity for such registered channel node further authenticating access via award of product key, package key and fogin data attached therewith"}) As to claim 8, Rathod discloses further: identifying a hyperlink within the message (in Rathod, the HSN Messenger in FIG. 18 displays a hyperlink "HA" and “identities the hyperlink” with underlining. See Rathod, FIG, 18, element 18G with "HA match Link."); and displaying the hyperlink to the first user as an active link, wherein the active link comprises a shortened representation of the hyperlink (in Rathod, the "displayed hyperlink is an active link, a shortened representation of the hyperlink" that, when clicked, takes the user to its destination in the interface of FIG. 18. SeeRathod, 99273- 274 ("matched results (18F & 21F) containing...URL....short information of source “Users... can click hyperlink for more detaits")) As to claim 9, Rathod discloses further: identifying, within the message, a reference to an image (in Rathod, FIGS. 24 and 26 are user search engines (for subscriberfirst or agent/second users) in the HSN, which include image filter options in 24D and 25D, which, when activated, "identifyl] within the message, a reference to an image.” See Rathod, $278Application/Control Number: 90/014,072 Page 15, Art Unit: 3992 Cf 1G. 24 and 28 illustrate example of graphical user interface (GUi) for Subscriber and human agent active composite search engine along with the muitiple search results thereof and multiple searching tools therefor including . . . 240) & 25D various search parameters’); FIG. 24, element 24D "Image" option.); and displaying, to the first user, the message with an indication of the image (in Rathod, when an image is found in the contents, such result is "displayed, to the first user, the message with an indication of the image" by the results of FIGS, 24 and 28. See Rathod, $278 ("246 & 25E showing a typical representation of search results showing namespace of the result and actionable tools supplemented therewith so as lo ‘execute the said search resi ?) As to claim 13, Rathod discloses a message distribution system, comprising} a computer processor; a routing engine executing on the computer processor (In Rathod, FIG. 1 is a schematic of an HSN computer system including Host 1A 2 id Servers ID including functionality, which necessarily include a computer processor and division of tasks among modules or "engines" to achieve the HSN functionality. See Rathod 170) and configured to: receive, from a first computing device of a first user, a selection of a plurality of endpoints (devices or interfaces where a message is to be delivered) for receiving messages, wherein the first user is one of a plurality of users who are followers (including a member of a group who has registered for another user, such as aApplication/Control Number: 90/014,072 Page 16 Art Unit: 3992 subscriber) of a second user (/n Rathod FIG. 6, element 6J, several different “first computing devices" (PDS, Laptop, Mobile, etc.) of a first user are connected to the HSN. See Rathod, $248. In an HSN Messenger interface of FIG. 18, the “first user," a subscriber, makes a "selection from a plurality of endpoints” in 18H for message delivery, including IM, E-Mail, Voice, etc. See Rathod, $270 (°FIG. 18 showing [GUI] for Subscriber... 18H... providing for selection of various communication modality including text mfe}ssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’); in Rathod, FIG. 18, the HSN messenger 18G is controlled by an Explorer (HSNE) with tools 181 for the subscriber or “first user" to be a “foilower[Jof the second user.” See Rathod, $270 (HSNE “illustrate various tools for match making, various...(76L) parameters selection including taxonomy.” "18G...showfs] a mfelssfen]ger having a input area and mfe}ssaging contents of each of participant in the communication process with the said subscriber or within the said group." Also in Rathod, FIG. 26, the HSN Explorer (SNE) shows selection and matching of various agents, which is a "second user." See Rathod 9279-280 (describing FIG. 26 as a wizard interface for each channel of the HSN). in the same interface of FIG. 18, the message is sent to the selected “endpoint” in 18H, including IM, E-Mail, Voice, etc. See Rathod, 1270 ("FIG. 18 showing [GUI] for Subscriber... 18H providing for selection of various communication modality including text mfejssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’Application/Control Number: 90/014,072 Page 17 Art Unit: 3992 store the selection of the plurality of endpoints in a data repository (Selected endpoints must necessarily be stored in a computer system to achieve the sending discussed below. Nonetheless, in Rathod, FIGS. 1 & 2, the HSN network includes an MS SQL Server 1C/2C and Web Database 18/28 that stores all system data with a host 1A/2A. See Rathod, 9243-244 ("FIG. 2 shows a schematic... ilustrating structural connection of developer nodes in the peer to peer environment along with the relationship aspects thereof with the other channel nodes and HSN controller. 24- 2G illustrating preferred components of present web server so as to establish connection with the various HumanServiceNet Channel nodes and interne! framework”); receive, from a second computing device of the second user, a message for distribution to one or more unspecified recipients (such as a status update to one or more followers; in Rathod FIG. 4, agents, which are followed "second users” as discussed in the first receiving step, access the HSN through their own “second computing device" and interlace. See Rathod $246 ("FIG. 4 shows a schematic block diagram of a [HSN] Human Agent (HSNHA)... with other channel nodes and peer service providers therein the UHSF system... wherein each of operational modes for muttidevice (41) enablement is represented along with multiuser (4F} operation and muttictiont usability in the various smart devices (4J))”. These second users have a same message interface in Rathod FIG. 21 for communicating with subscribers, who use the interface in Rathod FIG. 18. See Rathod 270 ("18J & 21 J showing a subscriber's and human agent's workspace respectively’); in Flathod, the HSN systemApplication/Control Number: 90/014,072 Page 18 Art Unit: 3992 is configured for message “distribution to one or more unspecified recipients.” See Rathod, 953 ("the present invention is to communicate securely with unknown human user or human circle"); 9304 ("HSNE provides for Email. .. with known as weil as unknown users and subscribe for auto contents from selected multi sources’). Especialy, in FIG. 21 of Rathod, followed agents Sam Page, LasVegas, etc. “second users" send messages to a group in messenger 21G without any specified recipient - all subscribers receive the messages as “one or more unspecitied recipients." See Rathod, FIGS. 18 and 21 (" send detail...message 21G of agent in FIG. 21, delivered to group 18G in FIG. 18 without specifying a distinct user’) 91270 ("18G & 21G showing a mfe[ss[en|ger having a input area and mfe|ssaging contents of each of participant in the communication process with the said subscriber or within the said group"); identify (must inherently occur for sending) the followers of the second user as recipients of the message; and identity, in the data repository, the plurality of endpoints selected by the first user (Rathod FIGS. 1 and 2 itustrate a web host 1A/2A including the above-discussed HSN Services ID, including “followers of the second user as recipients" and "endpoints selected by the first user" input as discussed in the first “receiving” step. These services are interfaced with Database Server 1C and IB having all other data, including the “followers” and "endpoints" for identification in the sending. See Rathod, 1243; FIGS. 1, 2); andApplication/Control Number: 90/014,072 Page 19 Art Unit: 3992 a transmission engine configured to send the message to the followers of the second user, including the first user, wherein the transmission engine sends the message to each of the plurality of endpoints selected by the first user (in Ftathod, the HSN system in FIGS. 18 and 21 illustrates “sending the message to the followers of the second user" as the message-receiving group in messenger 21G. The message "i send detail...in 21G of agent/second user in FIG. 21 is delivered ("i send detail. ..*) to the group in 18G in FIG. 18, which is the receiving interface for the subscriberfirst user. See Rathod, 1270 ("18G & 21G showing a mejssfenjger having a input area and mfe/ssaging contents of each of participant in the communication process with the said subscriber or within the said group"). In an HSN Messenger interface of FIG. 18, the message is sent to "endpoints selected by the first user,” in this instance the "HSN IM" tab selected in 18H that causes the message to appear in the HSN IM message interlace 18G. See Rathod, 9270 ("FIG, 18 showing [GUI] for Subscriber... 18H... providing for selection of various communication modality including text mlejssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, ‘meeting and collaborating’); see also, 1150 ("The present invention provisioned for information and knowledge to anybody, anywhere ... to communicate via any utilities including HSN IM, HSN Email, Phone, Fax, Collaborative tools. File sharing tools, E- Mail etc."). As to claim 14, Rathod discloses further that the second user is one of a plurality of users who are followers of the first user, and wherein the second user receives messages sent to followers of the first user (in Rathod, the agents may alsoApplication/Control Number: 90/014,072 Page 20 Art Unit: 3992 subscribe to the subscribers through two-way matchmaking, in reverse of claim 4; that is, "the second user is [a] follower] of the first user." See Rathod, $304 ("Send advertise Email content to any matched subscribers (two way match making)’).) As to claim 15, Rathod discloses further that the routing engine is further configured to: receive, from the first computing device, an SMS registration message requesting creation of a new account of the first user (in Feathod FIG. 18, the endpoints 18H in ide "email, SMS, and web" See Rathod, 9270 ("18H & 2IM...inclu ding text mfelssaging.....file sharing, ...emailing’); In Rathod, a channel node, a communications link from the user's “computing device," requests “registration” with the system via "SMS." See Rathod, claim 90 (HSN receives “registration request from plurality of channel nodes v SMS."}); and create the new account in response to receiving the SMS registration message (in Rathod, the SMS “registration message" causes a "new account" to be "create 1.” See Rathod, 915 (subscribers are "made to register at the Human service net controlier server"), $9101, 126 ver creates “record in response to a first registration request in the database thereof via information inputted by each of the unregistered user"), and wherein the transmission engine is further configured to send, to the first computing device, an acknowledgement message indicating that the new account is created, wherein the plurality of endpoints is associated with the new account in the data repository (An “acknowledgement message" could be any communicationApplication/Control Number: 90/014,072 Page 21 Art Unit: 3992 following registration that would indicate the account is created. in Rathod, a user name or identity of the user is created, which governs where - that is, to what “endpoint” - the messages are sent. Further, an “acknowledgement” in the form of key and login data is provided following registration. See Rathod, $126, (server creates database entry including “identity of a said unregistered user and a field representing a role of the said unregistered user in the primary transaction" Then, “after completion of said first registration HSN controller generating a channel identity for such registered channel node further authenticating access via award of product key, package key and login data attached therewith’). As to claim 17, Rathod discloses further that the message distribution system further comprises a rules module configured to: identify, for the first user, a plurality of message receipt preferences comprising a time window for receiving messages (in Rathod, the HSN of FIG. 7 includes a host 1A with web services ID including user preferences and "rules." See Rathod 9121 ("each of supernode having data storage means for maintaining . . . profiles of each of subscribers in the UHSF system network, wherein the said storing meansfurther updating the profiles in accordance with the survey details ... along with real ime HNS preferences", In Rathod FIG. 19, element 191, the subscribing users/“first users” provide "message receipt preferences including a time window for receiving messages" through use of a "schedule" tool.); and make a determination that a current time is within the time window for receiving messages, wherein the sending of the message to the first user is based on theApplication/Control Number: 90/014,072 Page 22 Art Unit: 3992 determination (in Rathod, the sending of requested information is in accordance with the predefined schedule, such that the system must “determine that a current time is within the time window for receiving messages" and send based on that determination, See Rathod cl. 38 ("customizing the... reception by means of auto contents determination according lo preferences . . . wherein each of subscribed providers providing the requested contents at predefined frequency and schedule’). As to claim 20, Rathod discloses a non-transitory computer readable medium comprising a plurality of instructions for message distribution (in Rathod, FIG. 1, the HSN functionality is provided by a host $A executing HSN Services ID, which must be embodied on a "computer-readable medium" in order to function in a host, See also, Rathod, 149 (°he present invention . . . provides software implemented automation facilitating human involvement in the process of knowledge invocation in 2 distributed peer to peer environment’), the plurality of instructions comprising functionality to: receive, from a first computing device of a first user, a selection of a plurality of endpoints (devices or interfaces where a message is to be delivered) for receiving messages, wherein the first user is one of a plurality of users who are followers (including a member of a group who has registered for another user, such as a subscriber) of a second user (in Rathod FIG. 6, element 6J, several different "first computing devices" (PDS, Laptop, Mobile, etc.) of a first user are connected to the HSN, See Rathod, $248. In an HSN Messenger interface of FIG. 18, the “first user," aApplication/Control Number: 90/014,072 Page 23 Art Unit: 3992 subscriber, makes a “selection irom a plurality of endpoints" in 18H for message delivery, including iM, E-Mail, Voice, etc. See Rathod, $270 ("FIG. 18 showing [GUI] for Subscriber... 18H... providing for selection of various communication modality including text mlejssaging. voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’), in Rathod, FIG. 18, the HSN messenger 18G is controlled by an Explorer (HSNE) with tools 181. for the subscriber or "first user" to be a “tollowerljof the second user." See Rathod, 1270 (HSNE “illustrate various tools for match making, various...(16L) parameters selection including taxonomy." "18G...showfs} a mle}ss{en}ger having a inpul area and mfejssaging contents of each of participant in the communication process with the said subscriber or within the said group." Also in Rathoo, FIG. 26, the HSN Explorer (HSNE) shows selection and matching of various agents, which is a "second user." See Rathod 9279-280 (describing FIG. 26 as a wizar interface for each channel of the HSN). In the same interface of FIG. 18, the message is sent to the selected “endpoint” in 18H, including IM, E-Mail, Voice, etc. See Rathod, 1270 ("FIG. 18 showing [GUI] for Subscriber... 18H. providing for selection of various communication modality including text mlelssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating"}}; store the selection of the plurality of endpoints in a storage (Selected endpoints must necessarily be stored in a computer system to achieve the sending discussed below. Nonetheless, in Rathod, FIGS. 1 & 2, the HSN network includes an MS SQL. Server 1C/2C and Web Database 18/2B that stores ali system data with a hostApplication/Control Number: 90/014,072 Page 24 Art Unit: 3992 1A/2A, See Rathod, 9243-244 (FIG. 2 shows a schematic... iustrating structural connection of developer nodes in the peer to peer environment atong with the relationship aspects thereof with the other channel nodes and HSN controller. 2A- 2G illustrating preferred components of present web server so as to establish connection with the various HumanServiceNet Channel nodes and internet framework." receive, from a second computing device of the second user, a message for distribution to one or more unspecified recipients (such as a status update to one or more followers; in Rathod FIG. 4, agents, which are followed "second users" as discussed in the first receiving step, access the HSN through their own “second computing device" and interlace. See Rathod $246 "FIG. 4 shows a schematic biock diagram of a [HSN] Human Agent (HSNHA} with other channel nodes and peer service providers therein the UHSF system... wherein each of operational modes for multidevice (41) enablement is represented along with multiuser (4F) operation and muttictient usability in the various smart devices (4J))". These second users have a same message interface in Rathod FIG. 21 for communicating with subscribers, who use the interlace in Rathod FIG. 18. See Rathod $270 ("18 & 21 J showing a subscriber's and human agent's workspace respectively"); in Rathod, the HSN system is configured for message “distribution to one or more unspecified recipients.” See Rathod, 953 (“the present invention is to communicate seourely with unknown human user or human circle"); 9304 (“HSNE provides for Email. .. with known as well as unknown users and subscribe for auto contents from selected multiApplication/Control Number: 90/014,072 Page 25 Art Unit: 3992 sources"). Especially, in FIG. 21 of Rathod, followed agents Sam Page, LasVegas, etc., "second users” send messages to a group in messenger 21G without any specitied recipient - alt subscribers receive the messages as “one or more unspecitied recipients.” See Rathod, FIGS. 18 and 21 ("I send detail...message 21G of agent in FIG. 21, delivered to group 18G in FIG. 18 without specifying a distinct user’), 9270 ("18G & 2G showing a mfe|ssjenjger having a input area and mfe}ssaging contents of each of participant in the communication process with the said subscriber or within the said group"), identify (must inherently occur for sending) the followers of the second user as recipients of the message; identify, in the storage, the plurality of endpoints selected by the first user (Rathod FIGS. 1 and 2 illustrate a web host 14/24 including the above-discussed HSN: Services 1D, including "followers of the second user as recipients” and "endpoints selected by the first user" input as discussed in the first "receiving" step. These services are interfaced with Database Server 1C and IB hai her data, including the "followers" and "endpoints" for identification in the sending. See Rathod, $243; FIGS. 1, 2); and send the message to the followers of the second user, including the first user, wherein the sending includes sending the message to each of the plurality of endpoints selected by first user (/n Rathod, the HSN system in FIGS. 18 and 27 illustrates "sending the message to the followers of the second user” as the message- receiving group in messenger 21G. The message "I send dotail...in 21G ofApplication/Control Number: 90/014,072 Page 26 Art Unit: 3992 agent/second user in FIG. 21 is delivered ("/ send detail... *) to the group in 18G in FIG. 18, which is the receiving interface for the subscriberfirst user. See Rathod, $270 ("18G & 21G showing a mfe)ssjenjger having a input area and mfe}ssaging contents of each of participant in the communication process with the said subscriber or within the said group"). in an HSN Messenger interface of FIG. 18, the message is sent to “endpoints selected by the first user,” in this instance the "HSN iM" tab selected in 18H that causes the message to appear in the HSN iM message interlace 18G, See Flathod, 91270 ("FIG. 18 showing [GUI) for Subscriber... 18H...providing for selection of various communication modality including text mfe}ssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’); see also, $150 ("The present invention provisioned for information and knowledge to anybody, anywhere ... to communicate via any utilities including HSN IM, HSN Email, Phone, Fax, Collaborative tools. Fite sharing tools, E-Mail etc.’). As to claim 21, Rathod discloses a message distribution system for distributing messages, the message distribution system comprisin a computer processor (in Rathod, FIG, 1 is a schematic of an HSN computer system including Host 1A and Servers 1D including HSN functionality which necessarily include a computer processor and division of tasks among modules or "engines" to achieve the HSN functionality. See Rathod 9170.); a routing engine executing on the computer processor and configured to:Application/Control Number: 90/014,072 Page 27 Art Unit: 3992 receive, from a first computing device of a first user, a request for joining a follower group of users following a second user (in Rathod, FIG. 26, the HSN Explorer (HSNE) shows selection and matching of various agents, which is a "second user" such that selecting and matching the agent is “a request for joining a follower group of... a second user” See Rathod 19279-280 (describing FIG. 26 as a wizard interface for each channel of the HSN). In Rathod, FIG. 18, the HSN messenger 18G is controlled by an Explorer (HSNE) with too!s 181. for the subscriber or “first user” to be a participant in a group, where messages from an agent/second user are received. See Rathod, 1270 (HSNE “iitustrate various tools for match making, various . .. (181) parameters selection including taxonomy." "8G... . showfs] a me|ss[en|ger having a input area and mfejssaging contents of each of participant in the communication process with the said subscriber or within the said group.”); in response to receiving the request for joining, store information about the first user in a data repository for storing follower group information about the follower group of users ( The follower group join request must necessarily be stored in a computer system to achieve the sending discussed. Nonetheless, in Rathod, FIGS. 1 & 2, the HSN network includes an MS SQL. Server 1C/2C and Web Database 18/2B that stores all system data with a host 14/24. See Rathod, 9243-244 ("FIG. 2 shows a schematic .... illustrating structural connection of developer nodes in the peer to peer environment along with the relationship aspects thereof with the other channel nodes and HSN controller. 24-2G illustrating preferred components of present web server soApplication/Control Number: 90/014,072 Page 28 Art Unit: 3992 as {0 establish connection with the various HumanServiceNet Channel nodes and internet framework.")); receive, from the first computing device of the first user, a selection of a plurality of endpoints (devices or interfaces where a message is to be delivered) for receiving messages (in Rathod FIG. 6, element 6J, several different "first computing devices" (PDS, Laptop, Mobile, etc.} of a first user are connected to the HSN, See Rathod, $248. in an HSN Messenger interface of FIG. 18, the “first user,” a subscriber, makes a “selection from a plurality of endpoints" in 18H for message delivery, inoluding IM, E-Mail, Voice, etc. See Fathod, $270 (“FIG. 18 showing [GUI] for Subscriber... 18H... providing for selection of various communication modality incluaing text mfejssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’); in Rathod, FIG. 18, the HSN messenger 18G is controlled by an Explorer (HSNE) with tools 181. for the subscriber or “first user" to be a “follower{jof the second user." See Rathod, $270 (HSNE ‘illustrate various tools for match making, various...(18L) parameters selection including taxonomy." "18G...showfs] a mlelss{en|ger having a input area and mfejssaging contents of each of participant in the communication process with the said subscriber or within the said group." Also in Rathod, FIG. 26, the HSN Explorer (HSNE) shows selection and matching of various agents, which is a "second user." See Rathod 1279-280 (describing FIG. 26 as a wizard interface for each channel of the HSN). in the same interface of FIG. 18, the message is sent to the selected “endpoint” in 18H, including IM, E-Mail, Voice, etc. See Rathod, 270 ("FIG. 18 showing [GUI] for Subscriber... 18HApplication/Control Number: 90/014,072 Page 29 Art Unit: 3992 providing for selection of various communication modality including text mfejssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’), the plurality of endpoints including two or more of email, short messaging service (SMS) and web (In Rathod FIG. 18, the endpoints 18H include “email, SMS, and web" See Rathod, $270 ("18H & 2IH...including text mfessaging,..file sharing,...emaiting’)}; store selection information regarding the selection of the plurality of endpoints in the data repository (Selected endpoints must necessarily be stored in a computer system to achieve the sending discussed below. Nonetheless, in Rathod, FIGS. 1 & 2, the HSN network includes an MS SQL Server 1C/2C and Web Database 18/2B that stores ail system dala with a host 1A/2A, See Rathod, 9243-244 ("FIG. 2 shows a schematic ... illustrating structural connection of developer nodes in the peer to peer environment along with the relationship aspects thereof with the other channel nodes and HSN controller. 2A-2G illustrating preferred components of present web server so as to establish connection with the various HumanServiceNet Channel nodes and internet framework. receive, from a second computing device of the second user, a message for distribution to one or more unspecified recipients (such as a status update to one or more followers; in Rathod FIG. 4, agents, which are followed "second users” as discussed in the first receiving step, access the HSN through their own “second computing device” and interlace. See Rathod 9246 (FIG. 4 shows a schematic block diagram of a HSN] Human Agent (HSNHA)... with other channel nodes and peerApplication/Control Number: 90/014,072 Page 30 Art Unit: 3992 service providers therein the UHSF system... wherein each of operational modes for multidevice (41) enablement is represented along with multiuser (4F} operation and ‘mutticient usability in the various smart devices (4J))”. These second users have a same message interface in Rathod FIG. 21 for communicating with subscribers, who use the interface in Rathod FIG. 18. See Rathod $270 ("184 & 21 J showing a subscriber's and human agent's workspace respectively"); in Rathod, the HSN system is configured for message “distribution to one or more unspecified recipients.” See Rathod, $83 ("the present invention is to communicate securely with unknown human user or human circle"); 1304 ("HSNE provides for Email. .. with known as well as unknown users and subscribe for auto contents from selected multi sources"), Especially, in FIG. 21 of Rathod, followed agents Sam Page, LasVegas, etc., “second users" send messages to a group in messenger 21G without any specified recipient - all subscribers receive the messages as "one or more unspecified recipients.” See Rathod, FIGS. 18 and 21 ("I send detail...message 21G of agent in FIG. 21, delivered to group 18G in FIG. 18 without specifying a aistinet user’), 9270 ("8G & 2IG showing a mfejssfen|ger having a input area and mfelssaging contents of each of participant in the communication process with the said subsoriber or within the said group’ identify (must inherently occur for sending), based on the stored follower group information, the users in the follower group as recipients of the message; and identify, based on the stored selection information, the plurality of endpoints selected by the first user (Rathod FIGS. 1 and 2 illustrate a web host 1A/2A includingApplication/Control Number: 90/014,072 Page 31 Art Unit: 3992 the above-discussed HSN Services ID, including "followers of the second user as recipients" and "endpoints selected by the first user" input as discussed in the first “receiving” step. These services are interfaced with Database Server 1C and IB having all other data, including the “followers” and "endpoints" for identitication in the sending. See Rathod, $243; FIGS. 1, 2); and a transmission engine configured to send the message to each of the users in the follower group, including the first user, wherein the transmission engine is configured to send the message to each of the plurality of endpoints selected by the first user (in Rathod, the HSN system in FIGS. 18 and 21 iflustrates “sending the message to the followers of the second user" as the message-receiving group in messenger 21G. The message ‘I send detail...in 21G of agent/second user in FIG. 21 is delivered ("I send detail... ") to the group in 18G in FIG. 18, which is the receiving interface for the subscriberfirst user. See Rathod, 1270 ("18G & 21G showing a mfejssfenjger having a input area and mfejssaging contents of each of participant in the communication process with the said subscriber or within the said group"). In an HSN Messenger interface of FIG. 18, the message is sent to "endpoints selected by the first user," in this instance the "HSN IM" tab selected in 18H that causes the message to appear in the HSN IM message interlace 18G. See Rathod, $270 ("FIG. 18 show ig [GUI] for Subseriber...18H...providing for selection of various communication modality including text mle}ssaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating’); see also, 150 ("The present invention provisioned for information and knowledge to anybody, anywhere...to communicate via any utilitiesApplication/Control Number: 90/014,072 Page 32 Art Unit: 3992 including HSN iM, HSN Email, Phone, Fax, Collaborative tools. File sharing tools, E- Mail etc.) REJ 2) Claims 1-3, 8, 9, 13-15, 20 and 21 are rejected under 35 USC § 102(e) as anticipated by Hull, US 2011/0289574, which incorporates by reference provisional reference 60/540505. As to claim 1, Hull discloses a method of message distribution, comprising: receiving, from a first computing device of a first user, a selection of a plurality of endpoints for receiving messages (Hull at p. 33 (Table 5. Preferences/Controls), Hull discloses general preferences including notifications settings that allow the user to select delivery media medium including email, IM, and SMS in order to better control what kind of messages they receive from people in the social network. Hull at p. 31 (Table 4. Communication/Publishing) Hull discloses that ‘Establishing Communication preferences: Provide ability for SN users to determine how they prefer to receive alerts from SN (either via email, IM, SMS or none).” Also see Provisional ‘505 at p. 69 (Table 5. Preferences/Controls)), wherein the first user is one of a plurality of users who are followers of a second user (Hull at pp. 22-29 (Table 2. Networks - First Degree Connection Management and Establishing Network Depth for Messaging Purposes) Hull discloses that the user may control information and settings relating to their social networks and that the user may define the depth if his/her network for incoming communications/messages including invitations to join a person's network, email ‘messages, instant messages and testimonial submissions. The users may decide whoApplication/Control Number: 90/014,072 Page 33, Art Unit: 3992 to follow and who may follow them. Hull at p. 31 (Table 4. Communication/Publishing) Hull discloses “Blog Alerts: Provide ability for a SN user to choose to receive a SN message whenever a particular user (target) update's his/her blog.”...” A SN user may track up to 25 SN blogs ata time.” Hull at pp. 47-49 (Table 2. Networks - Establishing Network Depth for Messaging Purposes)) storing the selection of the plurality of endpoints in a storage (Hull at [0036-46] Hull discloses storage of among other things contact, behavior, profile and activity information.); receiving, from a second computing device of the second user, a message for distribution to one or more unspecified recipients (Hull at [0050] discloses that the user's actions are tracking and made available of the social network. Further, Hull at [0039-41] discloses that the user information is stored in the user profile and can be viewed by other members of the social network based on established criteria such as the relationship between the user and the prospective viewer. Further, Hull at [0072-73] and p. 20 discloses that the system can receive messages from the user to include in their profile that will be distributed to unspecified recipients such as a message to let people to know their intent. See also Hull at pp. 47-49 (Table 2. Networks — Establishing Network Depth for Messaging Purposes. See also Hull at p. 16 (Table - Component and feature sets) disclosing “View (public view): Friends path (degrees of separation), add/remove from network, photo, avatar, ASL, quote, interests, URLs, testimonials, blog (journal), poll.” and ‘Preferences: Expose contact information to afferent groups of people, blog (public read/comment), polis (public read/comment),Application/Control Number: 90/014,072 Page 34 Art Unit: 3992 photos (public view/add), alerts delivery mediums (email, IM, SMS), alert types (buddy requests, new posts or testimonials).” Hull at p. 17 (Table - Component and feature sets: Publishing) discloses “Blog: Owner may write basic journal for their profile. ... May integrate RSS feeds.” Hull at p. 31 (Table 4. Communication/Publishing) discloses “Blog Alerts: Provide ability for a SN user to choose to receive a SN message whenever @ particular user (target) update's his/her blog.”...” A SN user may track up to 25 SN blogs at a time.”); identifying, by a computer processor, the followers of the second user as recipients of the message (Hull at [0038, 0075-76, 0101-103] discloses identifying followers of the user based on “a classification of users and/or corresponding relationships within a user's social network, such as family members, friends, co- workers, poker buddies, fishing buddies, and the like.” See also Hull at [0039-43], pp. 47-49 (Table 2. Networks — Establishing Network Depth for Messaging Purposes), and p. 16 (Table - Component and feature sets) disclosing “View (public view): Friends path (degrees of separation), add/remove from network, photo, avatar, ASL, quote, interests, URLs, testimonials, blog (journal), poll.” and “Preferences: Expose contact information to different groups of people, blog (public read/comment), polls (public read/comment), photos (public view/ada), alerts delivery mediums (email, IM, SMS), alert types (buddy requests, new posts or testimonials).”, and p. 17 (Table - Component and feature sets: Publishing) disclosing “Blog: Owner may write basic journal for their profile. ... May integrate RSS feeds.” Also see Hull at p. 31 (Table 4. Communication/Publishing) disclosing “Blog Alerts: Provide ability for a SN user to choose to receive a SN messageApplication/Control Number: 90/014,072 Page 35, Art Unit: 3992 whenever a particular user (target) update's his/her blog.”...” A SN user may track up to 25 SN blogs at a time.”); identifying, in the storage, the plurality of endpoints selected by the first user (Hull at [0075-76, 0106, 0126] and p. 33 (Table 5. Preferences/Controls) disclosing general preferences including notifications settings that allow the user to select delivery media medium including email, IM, and SMS in order to better contro! what kind of messages they receive from people in the social network. Also see Provisional ‘505 at p. 69 table (8. Preferences/Controls).); and sending the message to the followers of the second user, including the first user, wherein the sending includes sending the message to each of the plurality of endpoints selected by the first user (Hull at (0075-76, 0126] and p. 33 (Table 5. Preferences/Controls) aisclosing general preferences including notifications settings that allow the user to select delivery media medium including email, IM, and SMS in order to better control what kind of messages they receive from people in the social network. Hull at p. 30 (Table 4. Communication/Publishing — Category Messages) and Provisional ‘508 at p. 69 (Table 5. Preferences/Controls). Also see Hull at p. 16 (Table (Component and feature sets) disclosing “View (public view): Friends path (degrees of separation), add/remove from network, photo, avatar, ASL, quote, interests, URLs, testimonials, blog (journal), poll.” and ‘Preferences: Expose contact information to different groups of people, blog (public read/comment), polls (public read/comment), photos (public view/add), alerts delivery mediums (email, IM, SMS), alert types (buddy requests, new posts or testimonials).” and Hull at p. 17 (Table - Component and feature