Patent Publication Number: US-2017353410-A1

Title: Messaging Sharing System and Method of Use

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims benefit to U.S. Patent Application No. 62/157,950 filed on May 6, 2015 and Ser. No. 15/149,065 filed on May 6, 2016. 
    
    
     STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT (IF APPLICABLE) 
     Not applicable. 
     REFERENCE TO SEQUENCE LISTING, A TABLE, OR A COMPUTER PROGRAM LISTING COMPACT DISC APPENDIX (IF APPLICABLE) 
     Not applicable. 
     BACKGROUND OF THE INVENTION 
     Prior art known to the Applicant to be relevant but not, in the Applicant&#39;s opinion, preventing patent eligibility for the current claims follow: US 2014/0006525, U.S. Pat. No. 6,721,784, US 2013/0055144, US default Setting Selection 0161851, and U.S. Pat. No. 8,782,144. 
     None of the known inventions and patents, taken either singularly or in combination, is seen to describe the instant disclosure as claimed. 
     BRIEF SUMMARY OF THE INVENTION 
     A composite message sharing method for sending and sharing of a composite message between a plurality of computers over a network by packaging up a portion of a plurality of messages into said composite message and managing access to said composite message. Providing a device application, comprising a messaging application, on said plurality of computers belonging to a plurality of users, wherein, each among said plurality of computers comprise at least a processor, a memory and a communication hardware, said device application is executed in said processor of said plurality of computers, and a portion of said plurality of messages and/or said composite message are transmitted with said communication hardware. providing a server application on said server. configuring said plurality of computers and said server to communicate with each other over said network. 
     BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING 
       FIG. 1  illustrates a flow chart view of a first network configuration  101 . 
       FIG. 2A  illustrates a perspective overview view of a mobile phone  201   a.    
       FIG. 2B  illustrates a perspective overview view of a personal computer  201   b.    
       FIG. 2C  illustrates a perspective overview view of a tablet  201   c.    
       FIG. 2D  illustrates a perspective overview view of a smartphone  201   d.    
       FIG. 3A  illustrates view of an address space  302  block diagram. 
       FIG. 3B  illustrates view of an address space  302   a.    
       FIG. 3C  illustrates view of an address space  302   d.    
       FIG. 4A  illustrates view of a data storage  110 . 
       FIG. 4B  illustrates view of a first computer  102   a.    
       FIG. 5A  illustrates view of a memory  306   a.    
       FIG. 5B  illustrates view of a memory  306   a.    
       FIG. 6A  illustrates view of a first use diagram  600 . 
       FIG. 6B  illustrates view of a first mobile device  610   a.    
       FIG. 6C  illustrates view of a plurality of users  650 . 
       FIG. 7A  illustrates a perspective overview view of a first user  601   a.    
       FIG. 7B  illustrates an elevated overview view of a messaging dialog app  620 . 
       FIG. 7C  illustrates an elevated overview view of a composite message  706   a.    
       FIG. 8  illustrates an elevated overview view of a messaging application  820 . 
       FIG. 9A  illustrates a flow chart view of a plurality of system database tables  900 . 
       FIG. 9B  illustrates a flow chart view of a field relationships diagram  950 . 
       FIG. 10  illustrates view of an user Table  902 . 
       FIG. 11  illustrates view of a messages Table  904 . 
       FIG. 12  illustrates view of a share Events  906 . 
       FIG. 13  illustrates view of a share Conditions  908 . 
       FIG. 14  illustrates view of a share query tables  1400 . 
       FIG. 15  illustrates view of a composite message data  1500 . 
       FIG. 16A  illustrates a flow chart view of a first mobile device  610   a.    
       FIG. 16B  illustrates view of a long press  1622 . 
       FIG. 16C  illustrates view of a messages  1603 . 
       FIG. 16D  illustrates view of a message selection interface  1600 . 
       FIG. 17  illustrates view of a hidden icon  1702 . 
       FIG. 18A  illustrates view of a selection bar  1602 . 
       FIG. 18B  illustrates view of a composite message box  1830 . 
       FIG. 18C  illustrates view of a composite message box  1830 . 
       FIG. 18D  illustrates view of a composite message box  1830 . 
       FIG. 19A  illustrates view of a recipients interface  1900 . 
       FIG. 19B  illustrates view of a recipient fields  1950  in a table relationship diagram. 
       FIG. 20  illustrates view of an expiration interface  2000 . 
       FIG. 21A  illustrates view of a third mobile device  610   c.    
       FIG. 21B  illustrates view of a composite message box  1830 . 
       FIG. 22  illustrates a flow chart view of a composite message sharing method  2200 . 
       FIG. 23  illustrates view of a news feed screen  2300 . 
       FIG. 24  illustrates view of a friend request screen  2400 . 
       FIG. 25  illustrates view of a messenger screen  2500 . 
       FIG. 26  illustrates view of a notifications screen  2600 . 
       FIG. 27  illustrates view of a profile screen  2700 . 
       FIG. 28  illustrates a flow chart view of a composite message sharing method  2800 . 
       FIG. 29  illustrates view of a data object  2900 . 
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     The following description is presented to enable any person skilled in the art to make and use the invention as claimed and is provided in the context of the particular examples discussed below, variations of which will be readily apparent to those skilled in the art. In the interest of clarity, not all features of an actual implementation are described in this specification. It will be appreciated that in the development of any such actual implementation (as in any development project), design decisions must be made to achieve the designers&#39; specific goals (e.g., compliance with system- and business-related constraints), and that these goals will vary from one implementation to another. It will also be appreciated that such development effort might be complex and time-consuming, but would nevertheless be a routine undertaking for those of ordinary skill in the field of the appropriate art having the benefit of this disclosure. Accordingly, the claims appended hereto are not intended to be limited by the disclosed embodiments, but are to be accorded their widest scope consistent with the principles and features disclosed herein. 
     These parts are illustrated in the figures and discussed below: an improved messaging system  100 , a first network configuration  101 , a plurality of computers  102 , a first computer  102   a , a second computer  102   b,  a third computer  102   c,  a plurality of locations  103 , a first location  103   a , a second location  103   b,  a third location  103   c,  a printer  104 , a network  106 , a server  108 , a data storage  110 , a computer types  201 , a mobile phone  201   a,  a personal computer  201   b,  a tablet  201   c , a smartphone  201   d,  a screen  202 , a keyboard  204   a,  a trackball  204   b,  a cameras  204   c,  a camera  204   c,  a track pad  204   d,  a data  206 , a home button  220 , an address space  302 , an address space  302   a,  an address space  302   d,  a processor  304 , a processor  304   a,  a processor  304   d,  a memory  306 , a memory  306   a,  a memory  306   d,  a communication hardware  308 , a communication hardware  308   a,  a communication hardware  308   d,  a device application  502 , a data records  504 , a server application  506 , a first use diagram  600 , a first user  601   a,  a second user  601   b,  a third user  601   c,  a plurality of messages  602 , a first message  602   a,  a second message  602   b,  a one or more responses  604 , a first response  604   a,  a second response  604   b,  a first mobile device  610   a,  a second mobile device  610   b,  a third mobile device  610   c,  a messaging dialog app  620 , a text entry area  622 , a plurality of users  650 , a composite message  706   a,  a composite message  802 , a first CM  802   a,  a second CM  802   b,  a messaging application  820 , a data object  822 , a plurality of system database tables  900 , an user Table  902 , a messages Table  904 , a share Events  906 , a share Conditions  908 , a field relationships diagram  950 , an user ID  1002 , an user Name  1004 , a contact Info  1006 , a phone  1008 , an email  1010 , a first Name  1012 , a last Name  1014 , a message ID  1102 , a message Text  1104 , a date Sent  1106 , a date Received  1108 , an attachment  1110 , a sender  1112 , a recipient  1114 , a share Event  1116 , a message metadata  1120 , a share ID  1202 , a date Created  1204 , a date Expiring  1206 , a resharing  1208 , an id  1302 , an event Ref  1304 , a message Ref  1306 , a condition  1308 , a share query tables  1400 , a composite message data  1500 , a submessages  1502 , a message selection interface  1600 , a selection bar  1602 , a messages  1603 , a first selection option  1604   a,  a second selection option  1604   b,  a third selection option  1604   c,  a fourth selection option  1604   d,  a motion  1620 , a long press  1622 , a time selection option  1630 , a hidden icon  1702 , a show icon  1704 , an omit icon  1706 , a message sharing interface  1800 , a select recipients button  1802 , a set expiration button  1804 , an attach file button  1806 , a limit re-sharing button  1808 , an intro message  1810 , a send button  1820 , a composite message box  1830 , a share message entry box  1832 , a one or more buttons  1850 , a sharing limitations  1852 , a retract button  1854 , a recipients interface  1900 , a recipients menu  1902 , a return to send page button  1904 , a data  1910 , an icons  1912 , a recipient fields  1950 , an expiration interface  2000 , an expiration options page  2002 , a countdown dialog  2004 , a duration picker  2005 , a default Setting Selection  2006 , an expiration date time selection dialog  2008 , a month selection input  2010 , a time selection input  2012 , an expiration button  2020 , a message placeholder  2102 , a composite message sharing method  2200 , a plurality of steps  2202 , a first step  2202   a,  a second step  2202   b,  a third step  2202   c,  a fourth step  2202   d,  a fifth step  2202   e , a sixth step  2202   f,  a seventh step  2202   g,  an eighth step  2202   h,  a news feed screen  2300 , a newsfeed posts  2301 , a first newsfeed post  2301   a,  a second newsfeed post  2301   b,  a third newsfeed post  2301   c,  a navigation buttons  2302 , a newsfeed button  2302   a,  a requests button  2302   b,  a messenger button  2302   c,  a notifications button  2302   d,  a profile button  2302   e,  a first ICM discussion zone  2304   a,  a like count  2306 , a comment count  2308 , a share button  2310   a,  a like button  2310   b,  a tag button  2310   c,  a flag button  2310   d,  a first comment  2312   a,  a first response  2314   a,  a current user label  2320 , a friend request screen  2400 , a new friend request zones  2402 , a first new friend request zone  2402   a,  a second new friend request zone  2402   b,  a profile picture  2404   a,  a name  2406 , a location  2408 , a connections  2410 , a friend button  2412   a,  a button  2412   b,  a report button  2412   c , a find friends zone  2420 , a name  2422 , a names found  2424 , a messenger screen  2500 , a conversations  2502 , a first user message summary zone  2502   a,  a second user message summary zone  2502   b,  a last message text  2504   a,  a last message text  2504   b,  a last message time  2506   a,  a last message time  2506   b,  a profile image  2508   a,  a profile image  2508   b,  a search box  2520 , a new conversation button  2522 , a notifications screen  2600 , a notifications zone  2602 , a first notification  2602   a,  a second notification  2602   b,  a profile screen  2700 , a button  2702   a,  a photos button  2702   b , a friends button  2702   c,  a post  2702   d,  a share photo  2702   e,  a content zones  2704 , an user header zone  2704   a,  an user action zone  2704   b,  a friend action zone  2704   c,  an info button  2706   a,  an activity log button  2706   b,  a button  2706   c,  a composite message sharing method  2800 , a first step  2802   a,  a second step  2802   b,  a third step  2802   c,  a fourth step  2802   d,  a fifth step  2802   e,  a sixth step  2802   f,  a seventh stem  2802   g,  a data object  2900 , a share event document  2902 , and a messages document  2904 . 
       FIG. 1  illustrates a flow chart view of a first network configuration  101 . 
     In one embodiment, said improved messaging system  100  can comprise said first network configuration  101 , said plurality of computers  102 , said printer  104 , said network  106 , said server  108  and said data storage  110 . 
     In one embodiment, said first location  103   a  can comprise said first computer  102   a.    
     In one embodiment, said second location  103   b  can comprise said second computer  102   b , said third computer  102   c  and said printer  104 . 
     In one embodiment, said third location  103   c  can comprise said server  108  and said data storage  110 . 
     In one embodiment, said network  106  can comprise said first network configuration  101 . 
     In one embodiment, said plurality of computers  102  can comprise said first computer  102   a,  said second computer  102   b  and said third computer  102   c.    
     In one embodiment, said plurality of locations  103  can comprise said first location  103   a , said second location  103   b  and said third location  103   c.    
     Said network  106  can be a local area network (LAN), a wide area network (WAN), a piconet, or a combination of LANs, WANs, or piconets. One illustrative LAN is a network within a single business. One illustrative WAN is the Internet. 
     In one embodiment, said server  108  represents at least one, but can be many servers, each connected to said network  106 . Said server  108  can connect to a data storage  110 . Said data storage  110  can connect directly to said server  108 , as shown in  FIG. 1 , or may exist remotely on said network  106 . In one embodiment, said data storage  110  can comprise any suitable long-term or persistent storage device and, further, may be separate devices or the same device and may be collocated or distributed (interconnected via any suitable communications network). 
       FIG. 2A  illustrates a perspective overview view of a mobile phone  201   a.    
       FIG. 2B  illustrates a perspective overview view of a personal computer  201   b.    
       FIG. 2C  illustrates a perspective overview view of a tablet  201   c.    
       FIG. 2D  illustrates a perspective overview view of a smartphone  201   d.    
     In one embodiment, said computer types  201  can comprise said mobile phone  201   a,  said personal computer  201   b,  said tablet  201   c,  said smartphone  201   d,  said screen  202 , said keyboard  204   a,  said trackball  204   b,  said camera  204   c,  said cameras  204   c,  said track pad  204   d,  said data  206  and said home button  220 . 
     In one embodiment, said plurality of computers  102  can comprise said computer types  201 , said mobile phone  201   a,  said personal computer  201   b,  said tablet  201   c  and said smartphone  201   d.    
     In the last several years, the useful definition of a computer has become more broadly understood to include mobile phones, tablet computers, laptops, desktops, and similar. For example, Microsoft®, have attempted to merge devices such as a tablet computer and a laptop computer with the release of “Windows® 8”. In one embodiment, said one or more computers each can include, but is not limited to, a laptop (such as said personal computer  201   b ), desktop, workstation, server, mainframe, terminal, a tablet (such as said tablet  201   c ), a phone (such as said mobile phone  201   a ), and/or similar. Despite different form-factors, said one or more computers can have similar basic hardware, such as a screen  202  and a one or more input devices (such as a keyboard  204   a,  a trackball  204   b,  a one or more cameras  204   c,  a wireless—such as RFID—reader, a track pad  204   d,  and/or a home button  220 ). In one embodiment, said screen  202  can comprise a touch screen. In one embodiment, said track pad  204   d  can function similarly to a computer mouse as is known in the art. In one embodiment, said tablet  201   c  and/or said personal computer  201   b  can comprise a Microsoft® Windows® branded device, an Apple® branded device, or similar. In one embodiment, said tablet  201   c  can be an X86 type processor or an ARM type processor, as is known in the art. 
     Said improved messaging system  100  can comprise a data  206 . In one embodiment, said data  206  can comprise data related to financial transactions. 
     In one embodiment, said one or more computers can be used to input and view said data  206 . In one embodiment, said data  206  can be input into said one or more computers by taking pictures with one of said one or more cameras  204   c,  by typing in information with said keyboard  204   a,  or by using gestures on said screen  202  (where said screen  202  is a touch screen). Many other data entry means for devices similar to said one or more computers are well known and herein also possible with data  206 . In one embodiment, said first computer  102   a  can comprise an iPhone®, a BlackBerry®, a smartphone, or similar. In one embodiment, one or more computers can comprise a laptop computer, a desktop computer, or similar. 
       FIG. 3A  illustrates view of an address space  302  block diagram. 
       FIG. 3B  illustrates view of an address space  302   a.    
       FIG. 3C  illustrates view of an address space  302   d.    
     In one embodiment, said address space  302   a  can comprise said processor  304   a,  said memory  306   a  and said communication hardware  308   a.    
     In one embodiment, said address space  302   d  can comprise said processor  304   d,  said memory  306   d  and said communication hardware  308   d.    
     In one embodiment, said address space  302  can comprise said processor  304 , said memory  306  and said communication hardware  308 . 
     In one embodiment, said first computer  102   a  can comprise said address space  302   a.    
     In one embodiment, said server  108  can comprise said address space  302   d.    
     Each among said one or more computers and said server  108  can comprise an embodiment of address space  302 . In one embodiment, said address space  302  can comprise a processor  304 , a memory  306 , and a communication hardware  308 . In one embodiment, said processor  304  can comprise a plurality of processors, said memory  306  can comprise a plurality of memory modules, and said communication hardware  308  can comprise a plurality of communication hardware components. In one embodiment, said data  206  can be sent to said processor  304 ; wherein, said processor  304  can perform processes on said data  206  according to an application stored in said memory  306 , as discussed further below. Said processes can include storing said data  206  into said memory  306 , verifying said data  206  conforms to a one or more preset standards, or ensuring a required set among said required data  206  has been gathered for said data management system and method. In one embodiment, said data  206  can include data which said one or more computers can populate automatically, such as a date and a time, as well as data entered manually. Once a portion of gathering data has been performed said data  206  can be sent to said communication hardware  308  for communication over said network  106 . Said communication hardware  308  can include a network transport processor for packetizing data, communication ports for wired communication, or an antenna for wireless communication. In one embodiment, said data  206  can be collected in one or more computers and delivered to said server  108  through said network  106 . 
     In one embodiment, said first computer  102   a  can comprise said address space  302   a,  a processor  304   a,  a memory  306   a,  and a communication hardware  308   a.  Likewise, in one embodiment, said server  108  can comprise said address space  302   d,  a processor  304   d,  a memory  306   d,  and a communication hardware  308   d.    
       FIG. 4A  illustrates view of a data storage  110 . 
       FIG. 4B  illustrates view of a first computer  102   a.    
     In the first embodiment, said communication hardware  308   a  and said communication hardware  308   d  can send and receive data to and from one another and or can communicate with said data storage  110  across said network  106 . Likewise, in the second embodiment, data storage  110  can be embedded inside of said one or more computers, which may speed up data communications by said improved messaging system  100 . In another embodiment, said data can be stored temporarily on said data storage  110  and later moved to said data storage  110  for backup and sharing purposes. 
     As illustrated in  FIG. 4A , in one embodiment, said server  108  can comprise a third party data storage and hosting provider or privately managed as well. 
     As illustrated in  FIG. 4B , said data storage  110  can be located on said first computer  102   a,  here labeled as said data storage  110 . Thus, said first computer  102   a  can operate without a data connection out to said server  108  while performing said system and method for field capture of data. 
       FIG. 5A  illustrates view of a memory  306   a.    
       FIG. 5B  illustrates view of a memory  306   a.    
     As illustrated in  FIG. 5A , in one embodiment, said improved messaging system  100  can process said data  206  on said first computer  102   a  and/or said server  108 . For example, in one embodiment, said memory  306   a  can comprise a device application  502  capable of generating a data records  504  from user inputs or, otherwise, processing said data records  504  delivered to said device application  502  from said data storage  110 . In one embodiment, said data records  504  can be transferred between said device application  502  on said memory  306   a  of said first computer  102   a  and a server application  506  in said memory  306   d  of said server  108 . In one embodiment, said server  108  can be useful for processing said data  206 , as is known in the art. As illustrated in  FIG. 5B , in another embodiment, said server  108  can be removed from the flow diagram entirely as said memory  306   a  is capable of processing said data records  504  and/or said data  206  without the assistance of said server  108 . 
       FIG. 6A  illustrates view of a first use diagram  600 . 
       FIG. 6B  illustrates view of a first mobile device  610   a.    
       FIG. 6C  illustrates view of a plurality of users  650 . 
     In one embodiment, said first use diagram  600  can comprise said first user  601   a,  said second user  601   b,  said first mobile device  610   a  and said second mobile device  610   b.    
     In one embodiment, said messaging dialog app  620  can comprise said plurality of messages  602  and said one or more responses  604 . 
     In one embodiment, said plurality of users  650  can comprise said first user  601   a,  said second user  601   b  and said third user  601   c.    
     In one embodiment, said plurality of messages  602  can comprise said first message  602   a  and said second message  602   b.    
     In one embodiment, said one or more responses  604  can comprise said first response  604   a  and said second response  604   b.    
     In one embodiment, said smartphone  201   d  can comprise said first mobile device  610   a , said second mobile device  610   b  and said third mobile device  610   c.    
     In one embodiment, said device application  502  can comprise said messaging dialog app  620  and said text entry area  622 . 
     In one embodiment, a first user  601   a  having a first mobile device  610   a  can communicate with a second user  601   b  having a second mobile device  610   b.  In one embodiment, said first mobile device  610   a  and said second mobile device  610   b  can comprise one of said smartphone  201   d.  As is known in the art, messages can be passed back and forth between said plurality of users  650  between devices. In one embodiment, said first use diagram  600  can describe a round trip communication between said first user  601   a  and said second user  601   b.    
     In one embodiment, said messaging dialog app  620  can comprise a plurality of messages (such as a first message  602   a,  a first response  604   a,  a second message  602   b,  and a second response  604   b ). In one embodiment, writing messages from one user to another can be done in a text entry area  622 . 
     Here, as illustrated and known in the art, said first user  601   a  has sent said first message  602   a  and said second message  602   b  and said second user  601   b  has responded with said first response  604   a  and said second response  604   b.    
     In one embodiment, said plurality of users  650  can comprise said first user  601   a,  said second user  601   b,  and said third user  601   c.    
     Said improved messaging system  100  can comprise a social network feature wherein, said plurality of users  650  store profiles and information related to one another and have preset sharing settings relative to one another, as is known in the art. For example, in one embodiment, said first user  601   a  can comprise a list of favorite friends such as said third user  601   c  and one or more among said plurality of users  650 . 
       FIG. 7A  illustrates a perspective overview view of a first user  601   a.    
       FIG. 7B  illustrates an elevated overview view of a messaging dialog app  620 . 
       FIG. 7C  illustrates an elevated overview view of a composite message  706   a.    
     In one embodiment, said messaging dialog app  620  can comprise said composite message  706   a.    
     In one embodiment, where said first user  601   a  wishes to share a string of messages to a third party (that is separate from said second user  601   b ), he can select a range of messages and forward them to another user (such as said third user  601   c ) as one or more combined messages. In one embodiment, said messaging dialog app  620  is not configured to maintain formatting and Meta data. Instead, a range of messages are combined into a composite message  706   a  and sent as a larger single message. 
       FIG. 8  illustrates an elevated overview view of a messaging application  820 . 
     In one embodiment, said composite message  802  can comprise said first CM  802   a,  said second CM  802   b  and said data object  822 . 
     In one embodiment, said device application  502  can comprise said composite message  802  and said messaging application  820 . 
     In one embodiment, said plurality of messages  602  can comprise said data object  822 . 
     In one embodiment, said messaging application  820  can capture a one or more among said messaging dialog app  620  into a composite message  802 , as illustrated and discussed below. In one embodiment, said messaging application  820  can be expressed as a first CM  802   a,  a second CM  802   b,  etc., not illustrated here. 
       FIG. 9A  illustrates a flow chart view of a plurality of system database tables  900 . 
       FIG. 9B  illustrates a flow chart view of a field relationships diagram  950 . 
     In one embodiment, said plurality of system database tables  900  can comprise said user Table  902 , said messages Table  904 , said share Events  906  and said share Conditions  908 . 
     In one embodiment, said field relationships diagram  950  can comprise said user Table  902 , said messages Table  904 , said share Events  906  and said share Conditions  908 . 
     In one embodiment, said data storage  110  can comprise said user Table  902 , said messages Table  904 , said share Events  906  and said share Conditions  908 . 
     In one embodiment, said plurality of system database tables  900  can comprise subparts of said data storage  110 , which can comprise a user Table  902 , a messages Table  904 , a share Events  906 , and a share Conditions  908 . 
     In one embodiment, said field relationships diagram  950  can comprise a relationship between said subparts of said data storage  110 , as illustrated and described. 
       FIG. 10  illustrates view of an user Table  902 . 
     In one embodiment, said user Table  902  can comprise said user ID  1002 , said user Name  1004 , said contact Info  1006 , said phone  1008 , said email  1010 , said first Name  1012  and said last Name  1014 . 
     In one embodiment, said user Table  902 , a database table, can comprise a plurality of fields such as an user ID  1002 , an user Name  1004 , a contact Info  1006 , a phone  1008 , an email  1010 , a first Name  1012 , and a last Name  1014 . In one embodiment, said user ID  1002  can comprise a unique identifier for each record in said user Table  902 . In one embodiment, said user Name  1004  can comprise a unique alias of each user in said messaging application  820 . In one embodiment, several fields (such as said contact Info  1006 , said phone  1008 , said email  1010 , said first Name  1012 , and said last Name  1014 ) can comprise user information fields which can be used for user identification and communication as known in the art. 
       FIG. 11  illustrates view of a messages Table  904 . 
     In one embodiment, said messages Table  904  can comprise said message ID  1102 , said message Text  1104 , said date Sent  1106 , said date Received  1108 , said attachment  1110 , said sender  1112 , said recipient  1114  and said share Event  1116 . 
     In one embodiment, said plurality of messages  602  can comprise said message metadata  1120 . 
     In one embodiment, said messages Table  904 , a database table, can comprise a plurality of fields such as a message ID  1102 , a message Text  1104 , a date Sent  1106 , a date Received  1108 , an attachment  1110 , a sender  1112 , a recipient  1114 , and a share Event  1116 . In one embodiment, said message ID  1102  can comprise a unique identifier of each field in said messages Table  904 . In one embodiment, said message Text  1104  can comprise a message to be delivered from said sender  1112  to said recipient  1114 . In one embodiment, said date Sent  1106  and said date Received  1108  can track a time a message is sent and received between said plurality of users  650 . In one embodiment, said attachment  1110  can comprise a binary file (such as a picture, video, or similar) attached to a message between said plurality of users  650 . In one embodiment, said attachment  1110  can comprise no attachments or a one or more of binary file attachments. In one embodiment, said sender  1112  and said recipient  1114  can each comprise a reference to one among the fields in said user Table  902 ; where, said sender  1112  is a sender of a message and said recipient  1114  comprises a recipient of a message. In one embodiment, said share Event  1116  can comprise a cross reference to a record in share Events  906 , and the presence of a record in said share Event  1116  means that said sender  1112  has sent one of said composite message  802  to said recipient  1114 . 
       FIG. 12  illustrates view of a share Events  906 . 
     In one embodiment, said share Events  906  can comprise said share ID  1202 , said date Created  1204 , said date Expiring  1206  and said resharing  1208 . 
     In one embodiment, said share Events  906 , a database table, can comprise a plurality of fields such as a share ID  1202 , a date Created  1204 , a date Expiring  1206 , and a Limit resharing  1208 . In one embodiment, said share ID  1202  can comprise a unique identifier for records in said share Events  906 . In one embodiment, said date Created  1204  and said date Expiring  1206  can comprise date and time stamps of the time a record is created and a date where it will be deleted from said messaging application  820 . In one embodiment, said Limit resharing  1208  can comprise a flag (yes/no, true/false or similar flag) which is used to determine whether said third mobile device  610   c  can share said composite message  802  with another user. 
       FIG. 13  illustrates view of a share Conditions  908 . 
     In one embodiment, said share Conditions  908  can comprise said id  1302 , said event Ref  1304 , said message Ref  1306  and said condition  1308 . 
     In one embodiment, said share Conditions  908 , a database table, can comprise a plurality of fields such as an id  1302 , an event Ref  1304 , a message Ref  1306  and a condition  1308 . In one embodiment, said id  1302  can comprise a unique identifier for records in said share Conditions  908 . In one embodiment, said event Ref  1304  can comprise a cross reference to said share ID  1202  in said share Events  906 . In one embodiment, said message Ref  1306  can comprise a cross reference to said message ID  1102  in said messages Table  904 . In one embodiment, said condition  1308  can comprise a flag to indicate a nature of and amount of information being shared, as will be described further to come. 
       FIG. 14  illustrates view of a share query tables  1400 . 
     As illustrated here, there is a one to many relationship between the tables while moving from left to right. This may be configured without this one to many relationship between said messages Table  904  and said share Events  906  in different systems. 
     In one embodiment, said share query tables  1400  can comprise a query being run on said data storage  110 . In one embodiment, user (such as said messages Table  904 ) can share a one or more messages in said messages Table  904  with said recipient  1114 ; wherein, a record can be created in said share Events  906  and a cross reference to said share ID  1202  can be stored in said share Event  1116 . In one embodiment, said date Created  1204  and said date Expiring  1206  can be updated at the time of creating a share Events  906 . In one embodiment, where said date Expiring  1206  is empty, a record associated with said share Events  906  does not expire. Otherwise, that record should expire according to the date stamp stored in said date Expiring  1206 . 
     In one embodiment, said share Conditions  908  can comprise a cross reference table linking a shared record from said share Events  906  with a one or more records in said messages Table  904 . Here, said messages Table  904  is represented twice in this query with a second copy of the table shown as “messages Table  904 _ 1 ”. Accordingly, said share Conditions  908  has two references including said event Ref  1304  related to said share Events  906  and said message Ref  1306  associated with said message ID  1102  of said messages Table  904 . In one embodiment, said condition  1308  can dictate a condition of sharing a record in said messages Table  904 . 
       FIG. 15  illustrates view of a composite message data  1500 . 
     In one embodiment, said composite message data  1500  can comprise said submessages  1502 . 
     In one embodiment, said composite message data  1500  can comprise a data from said data storage  110 , including all or a portion of said user Table  902 , said messages Table  904 , said share Events  906  and said share Conditions  908 . Said composite message data  1500  can represent a portion of data from said share query tables  1400  and in said messaging application  820 . In one embodiment, said composite message data  1500  represents data that can be shared between said plurality of users  650 . 
     In one embodiment, said composite message data  1500  can comprise all the data in said messages Table  904 , said date Created  1204 , said date Expiring  1206 , said Limit resharing  1208 , and a submessages  1502 . In one embodiment, said submessages  1502  can comprise data which has been collected from said share query tables  1400 . 
     Said composite message data  1500  can comprise data sent from said sender  1112  to said recipient  1114  when said messaging application  820  is engaged to share a message thread. In one embodiment, said sender  1112  may choose to send four messages to said recipient  1114 ; wherein, said share Conditions  908  comprises four records to said message ID  1102  in said messages Table  904 ; therefore, said submessages  1502  shows four messages where said message ID  1102  equals to the values in the set {1,2,3, and 4}. 
       FIG. 16A  illustrates a flow chart view of a first mobile device  610   a.    
       FIG. 16B  illustrates view of a long press  1622 . 
       FIG. 16C  illustrates view of a messages  1603 . 
       FIG. 16D  illustrates view of a message selection interface  1600 . 
     In one embodiment, said message selection interface  1600  can comprise said selection bar  1602 , said messages  1603 , said first selection option  1604   a,  said second selection option  1604   b,  said third selection option  1604   c,  said fourth selection option  1604   d,  said motion  1620 , said long press  1622  and said time selection option  1630 . 
     In one embodiment, said selection bar  1602  can comprise said first selection option  1604   a,  said second selection option  1604   b,  said third selection option  1604   c  and said fourth selection option  1604   d.    
     In one embodiment, said message selection interface  1600  can be engaged by swiping a portion of said screen  202 . For example, in one embodiment, said one or more messages  1603  (which can comprise message boxes including said first message  602   a,  et. al.) can be exposed using a swiping motion  1620  to expose a selection bar  1602 , as illustrated in  FIGS. 16B-16C . In another embodiment, said selection bar  1602  can be exposed by using a long press  1622  on a one or more of said one or more messages  1603 . 
     In one embodiment, said message selection interface  1600  can comprise a portion of said messaging application  820 . In one embodiment, said selection bar  1602  can comprise a plurality of selection options including a first selection option  1604   a,  a second selection option  1604   b,  a third selection option  1604   c,  and a fourth selection option  1604   d.  In one embodiment, said plurality of selection options can be altered and encoded as illustrated and described below. 
     In one embodiment, said selection bar  1602  can comprise a time selection option  1630 . In one embodiment, said time selection option  1630  can comprise an option to select all messages between a start time and an end time, rather than selecting each and every message between those times. 
       FIG. 17  illustrates view of a hidden icon  1702 . 
     In one embodiment, said first selection option  1604   a  can comprise said hidden icon  1702 . 
     In one embodiment, said second selection option  1604   b  can comprise said show icon  1704 . 
     In one embodiment, said third selection option  1604   c  can comprise said show icon  1704 . 
     In one embodiment, said fourth selection option  1604   d  can comprise said omit icon  1706 . 
     In one embodiment, said plurality of selection options can be altered to correspond to options in said condition  1308  of said share Conditions  908 . For example, in one embodiment, said plurality of selection options can be changed between “show” (illustrated as a show icon  1704 ), “hide” (illustrated as a hidden icon  1702 ) or “omit” (illustrated as a omit icon  1706 ). Accordingly, here, said first user  601   a  has swiped said messaging application  820  to expose said selection bar  1602 , altered said selection bar  1602  to have said first message  602   a  hidden (with said hidden icon  1702 ), said first response  604   a  and said second message  602   b  shown (with said show icon  1704 ), and said second response  604   b  as omitted (with said omit icon  1706 . In one embodiment, said omit icon  1706  can comprise a default condition of each message when exposing said selection bar  1602 . In one embodiment, said plurality of selection options can be altered by tapping said plurality of selection options, as is known in the art. 
     In this sense, said messaging application  820  can be used to redact information which may not be suitable for a target audience. For example, said first selection option  1604   a  can be kept hidden and said fourth selection option  1604   d  can be omitted entirely. 
       FIG. 18A  illustrates view of a selection bar  1602 . 
       FIG. 18B  illustrates view of a composite message box  1830 . 
       FIG. 18C  illustrates view of a composite message box  1830 . 
       FIG. 18D  illustrates view of a composite message box  1830 . 
     In one embodiment, said message sharing interface  1800  can comprise said select recipients button  1802 , said set expiration button  1804 , said attach file button  1806 , said limit re-sharing button  1808 , said intro message  1810 , said send button  1820 , said composite message box  1830 , said share message entry box  1832 , said one or more buttons  1850 , said sharing limitations  1852  and said retract button  1854 . 
     In one embodiment, said one or more buttons  1850  can comprise said select recipients button  1802 , said set expiration button  1804 , said attach file button  1806  and said limit re-sharing button  1808 . 
     In one embodiment, said messaging application  820  can comprise said message sharing interface  1800 . 
     In one embodiment, said selection bar  1602  can comprise said composite message box  1830 . 
     In one embodiment, swiping a portion of said screen  202  after finishing with said message selection interface  1600  can cause said messaging application  820  to transition into said message sharing interface  1800 . For example, in one embodiment, swiping left on said screen  202  can: cause said plurality of selection options to disappear; said one or more messages  1603  to be shown, hidden or omitted; said selection bar  1602  to transform into a composite message box  1830 ; and a one or more buttons  1850  to appear to the right of said composite message box  1830 . In one embodiment, those among said one or more messages  1603  which are marked to be hidden can be replaced with a hidden message  1832  and those marked as omitted can disappear. 
     In one embodiment, said message sharing interface  1800  can comprise a composite message box  1830  comprising a portion of said one or more messages  1603  having been filtered according to said selection bar  1602 . 
     In one embodiment, said one or more buttons  1850  can comprise a select recipients  1802 , a set expiration  1804 , an attach file  1806  and a limit re-sharing  1808 . Further, said select recipients  1802  can comprise an add intro message  1810  and a send button  1820 , as is known in the art. 
     In one embodiment, said select recipients  1802  can comprise a button which opens a dialog for selecting one or more among said plurality of users  650  with whom to share said composite message box  1830 . 
     In one embodiment, said set expiration  1804  can opens a dialog for selecting an expiration date of a shared message. 
     In one embodiment, said attach file  1806  can allow a user to attach a binary file, such as a picture or video, as discussed above. 
     In one embodiment, said limit re-sharing  1808  can limit the redistribution of said composite message box  1830 . Where said limit re-sharing  1808  is selected, said composite message box  1830  can be restricted for sharing to those users selected in said select recipients  1802  and to no other users. Further, where said limit re-sharing  1808  is selected, said messaging application  820  on other devices can have the screen share, screen shot or other screen data capturing devices disabled for that dialog. This feature is intended to protect users and build confidence when sharing information. 
     In one embodiment, said messaging application  820  can be used for sending a portion of an email thread forward as a complete or redacted thread in the same manner as said composite message  802 . Similar collection, redacting, omitting and summarizing of thread information may be conducted prior to sending such said composite message  802  in this context. 
     Said composite message includes a hidden message comprising a placeholder within a composite message box. the hidden message comprises a portion of the composite message which the first user wished to omit but to include a placeholder. the composite message box is displayed on a computer belonging to the second user with the contents of the composite message. 
       FIG. 19A  illustrates view of a recipients interface  1900 . 
       FIG. 19B  illustrates view of a recipient fields  1950  in a table relationship diagram. 
     In one embodiment, said recipients interface  1900  can comprise said recipients menu  1902 , said data  1910  and said icons  1912 . 
     In one embodiment, the select recipients interface  1900  can comprise a well-known user interface for selecting one or more records from a database table. For example, in one embodiment, the select recipients interface  1900  can comprise a Select recipients menu  1902  comprising a list of the plurality of users  650  along with data  1910  and icons  1912 , as illustrated. Here, as illustrated, the third user  601   c  is selected and none other. However, in one embodiment, the sender  1112  can select a plurality of the plurality of users  650 . In one embodiment, the select recipients interface  1900  can comprise a Return to Send return to send page button  1904  button which returns a user to the message sharing interface  1800  after selecting one or more among the plurality of users  650  to share a message with. 
     In one embodiment, as illustrated in  FIG. 19B , the recipient  1114  record can comprise a one to many relationship with the user ID  1002  of the user Table  902 . 
       FIG. 20  illustrates view of an expiration interface  2000 . 
     In one embodiment, said expiration interface  2000  can comprise said expiration options page  2002 , said countdown dialog  2004 , said expiration date time selection dialog  2008  and said expiration button  2020 . 
     In one embodiment, said countdown dialog  2004  can comprise said duration picker  2005  and said default Setting Selection  2006 . 
     In one embodiment, said expiration date time selection dialog  2008  can comprise said month selection input  2010  and said time selection input  2012 . 
     In one embodiment, the select expiration interface  2000  can comprise a set expiration options page  2002  having a countdown dialog  2004  and an expiration date time selection dialog  2008 . In one embodiment, the countdown dialog  2004  can comprise a duration picker  2005  for selecting a countdown length in a chosen unit, as is known in the art. In one embodiment, the countdown dialog  2004  can also comprise a default Setting Selection  2006 ; wherein a user can select a the default Setting Selection  2006  where the inputs of the duration picker  2005  should be the default share time for the messaging application  820 . This data can be stored in the user Table  902 , although it is not illustrated here. In one embodiment, the inputs of the duration picker  2005  can be calculated as added to the current time to set the date Expiring  1206  of the share Events  906 . 
     In one embodiment, the expiration date time selection dialog  2008  can comprise a month selection input  2010  and a time selection input  2012  for setting the date Expiring  1206  directly. 
     In one embodiment, the set expiration options page  2002  can comprise a no expiration button  2020  which can comprise a label such as “N/A”, “None” or similar. Wherein, use of the no expiration button  2020  can indicate that information shared will not expire. 
       FIG. 21A  illustrates view of a third mobile device  610   c.    
       FIG. 21B  illustrates view of a composite message box  1830 . 
     In one embodiment, said composite message  802  can comprise said message placeholder  2102 . 
     In one embodiment, the third user  601   c  can receive the composite message box  1830  as formatted by the first user  601   a.  In one embodiment, the composite message box  1830  can be displayed on the third mobile device  610   c  as illustrated. 
     The one or more messages, a user profile information, the composite messages, and historical transactions are stored on the server. 
       FIG. 22  illustrates a flow chart view of a composite message sharing method  2200 . 
     In one embodiment, said composite message sharing method  2200  can comprise said plurality of steps  2202 . 
     In one embodiment, said plurality of steps  2202  can comprise said first step  2202   a,  said second step  2202   b,  said third step  2202   c,  said fourth step  2202   d,  said fifth step  2202   e,  said sixth step  2202   f,  said seventh step  2202   g  and said eighth step  2202   h.    
     In one embodiment, the composite message sharing method  2200  can comprise a plurality of steps which can comprise a method of using the messaging application  820  and/or the improved messaging system  100 . 
     The first step  2202   a  can comprise: selecting one or more of the one or more messages  1603  by a sender. The second step  2202   b  can comprise: creating a condition for a portion among the one or more messages  1603 . The third step  2202   c  can comprise: creating the composite message box  1830  with the one or more of the one or more messages  1603 . The fourth step  2202   d  can comprise: setting an expiration date or the no expiration button  2020  for the composite message box  1830 . The fifth step  2202   e  can comprise: setting a flag called the limit re-sharing  1808  to disallow sharing and/or copying of the composite message box  1830  by recipients of the composite message box  1830 . The sixth step  2202   f  can comprise: selecting a one or more among the plurality of users  650  to receive the composite message box  1830 . The seventh step  2202   g  can comprise: sharing the composite message box  1830 . The eighth step  2202   h  can comprise: deleting the composite message box  1830  from the messaging application  820  when the date Expiring  1206  is reached. 
       FIG. 23  illustrates view of a news feed screen  2300 . 
     In one embodiment, said news feed screen  2300  can comprise said newsfeed posts  2301 , said first newsfeed post  2301   a,  said second newsfeed post  2301   b,  said third newsfeed post  2301   c , said navigation buttons  2302 , said newsfeed button  2302   a,  said requests button  2302   b,  said messenger button  2302   c,  said notifications button  2302   d,  said profile button  2302   e,  said first ICM discussion zone  2304   a,  said like count  2306 , said comment count  2308 , said share button  2310   a , said like button  2310   b,  said tag button  2310   c,  said flag button  2310   d,  said first comment  2312   a , said first response  2314   a  and said current user label  2320 . 
     In one embodiment, said first newsfeed post  2301   a  can comprise said first ICM discussion zone  2304   a,  said like count  2306 , said comment count  2308 , said share button  2310   a , said like button  2310   b,  said tag button  2310   c,  said flag button  2310   d,  said first comment  2312   a  and said first response  2314   a.    
     In one embodiment, said newsfeed posts  2301  can comprise said first newsfeed post  2301   a,  said second newsfeed post  2301   b  and said third newsfeed post  2301   c.    
     In one embodiment, said navigation buttons  2302  can comprise said newsfeed button  2302   a,  said requests button  2302   b,  said messenger button  2302   c,  said notifications button  2302   d  and said profile button  2302   e.    
     The messaging application  820  can comprise a navigation buttons  2302  which can comprise a newsfeed button  2302   a,  a requests button  2302   b,  a messenger button  2302   c,  a notifications button  2302   d  and a profile button  2302   e.  In one embodiment, the news feed screen  2300  can open in the messaging application  820  upon clicking the newsfeed button  2302   a.    
     In one embodiment, the news feed screen  2300  can comprise a current user label  2320  to indicate which user is currently signed in; for example, the first user  601   a  is signed in in  FIG. 23 . The news feed screen  2300  can further comprise a one or more newsfeed posts  2301  which can comprise a first newsfeed post  2301   a,  a second newsfeed post  2301   b,  and a second newsfeed post  2301   b.  In one embodiment, the one or more newsfeed posts  2301  can comprise information from one or more users among the plurality of users  650 , as is known in the art. Here, the second newsfeed post  2301   b  and the third newsfeed post  2301   c  are empty so as to focus the discussion on the first newsfeed post  2301   a.    
     In one embodiment, the one or more newsfeed posts  2301  can each comprise a discussion and posting of one among the composite message  802 . For example, the first newsfeed post  2301   a  can comprise the first CM  802   a,  a first ICM discussion zone  2304   a,  a like count  2306 , comment count  2308 , a share button  2310   a,  a  2310   b,  a tag button  2310   c,  and a flag button  2310   d.  In one embodiment, the first ICM discussion zone  2304   a  can comprise a first comment  2312   a  and a first response  2314   a.    
     The news feed screen  2300  can comprise some well-known features form other social networks such as: the like count  2306  adapted to track a number of times that the first newsfeed post  2301   a  has received a click on the like button  2310   b;  the comment count  2308  can comprise a number of comments left in the first ICM discussion zone  2304   a;  the share button  2310   a  allowing users to share the first newsfeed post  2301   a;  the tag button  2310   c  to tag someone or something associated with the first newsfeed post  2301   a;  and the flag button  2310   d  to indicate that an objectionable content is contained in the first newsfeed post  2301   a.    
     Accordingly, the messaging application  820  can provided a news feed screen  2300  for the summary of activities by the plurality of users  650  and for a quick overview of activity on the platform. 
     In one embodiment, the messaging application  820  can be displayed in a web browser, the mobile phone  201   a,  the personal computer  201   b,  the tablet  201   c  and/or the smartphone  201   d . indeed, the messaging application  820  can be accessed in traditional locations with access to the network  106 . 
     In one embodiment, said messaging application  820  can comprise a social network software allowing said plurality of users  650  to connect and share information with one another. the messaging application allows users to post the composite messages to a newsfeed within the social network software. 
       FIG. 24  illustrates view of a friend request screen  2400 . 
     In one embodiment, said friend request screen  2400  can comprise said new friend request zones  2402 , said second new friend request zone  2402   b,  said name  2406 , said location  2408 , said find friends zone  2420 , said name  2422  and said names found  2424 . 
     In one embodiment, said first new friend request zone  2402   a  can comprise said name  2406 , said location  2408  and said connections  2410 . 
     In one embodiment, said new friend request zones  2402  can comprise said first new friend request zone  2402   a  and said second new friend request zone  2402   b.    
     As is known in field, users among the plurality of users  650  can connect to one another through the friend request screen  2400 . In one embodiment, the news feed screen  2300  can comprise a new friend request zones  2402  (which can comprise a first new friend request zone  2402   a  and a second new friend request zone  2402   b ) and a find friends zone  2420 . 
     In one embodiment, the friend request screen  2400  can come up when a user clicks on the requests button  2302   b.  In one embodiment, each among the new friend request zones  2402  can comprise a profile picture  2404   a,  a name  2406 , a location  2408 , a connections  2410 , a friend button  2412   a,  an ignore button  2412   b,  and a report button  2412   c.    
     The friend request screen  2400  can comprise a name  2422  and a names found  2424 . In one embodiment, the name  2422  can receive a query for searching a list of the plurality of users  650 , wherein a portion of the results can be shown in the names found  2424 /. 
       FIG. 25  illustrates view of a messenger screen  2500 . 
     In one embodiment, said messenger screen  2500  can comprise said conversations  2502 , said first user message summary zone  2502   a,  said search box  2520  and said new conversation button  2522 . 
     In one embodiment, said conversations  2502  can comprise said first user message summary zone  2502   a,  said second user message summary zone  2502   b,  said last message text  2504   a,  said last message text  2504   b,  said last message time  2506   a  and said last message time  2506   b.    
     In one embodiment, the messaging application  820  can be adapted for displaying a  2502  (which can comprise a first user message summary zone  2502   a  and a second user message summary zone  2502   b ). In one embodiment, the first user message summary zone  2502   a  can comprise a last message text  2504   a,  a last message time  2506   a,  a profile image  2508   a,  and the user Name  1004  (shown as “first user  601   a ”). Likewise, the second user message summary zone  2502   b  can comprise a last message text  2504   b,  a last message time  2506   b,  a profile image  2508   b,  and the user Name  1004  (shown as “second user  601   b ”). 
     In one embodiment, clicking on one of the one or more conversations  2502  can load a messaging history between two users. In one embodiment, the search box  2520  can be used to search a messaging history. In one embodiment, a new conversation button  2522  can be used to start a new conversation. 
       FIG. 26  illustrates view of a notifications screen  2600 . 
     In one embodiment, said notifications screen  2600  can comprise said notifications zone  2602 , said first notification  2602   a  and said second notification  2602   b.    
     In one embodiment, said notifications zone  2602  can comprise said first notification  2602   a  and said second notification  2602   b.    
       FIG. 27  illustrates view of a profile screen  2700 . 
     The profile screen  2700  can be used, as is known in the art, to post a summary of a user and/or connect with a particular user. 
     The profile screen  2700  can comprise a content zones  2704 . The content zones  2704  can comprise a user header zone  2704   a,  a user action zone  2704   b,  and a friend action zone  2704   c.  In one embodiment, the user header zone  2704   a  can comprise the profile CMge  2508   a,  and the user Name  1004  (here “first user  601   a ”); the user action zone  2704   b  can comprise an update info button  2706   a,  an activity log button  2706   b,  and a more button  2706   c;  and the friend action zone  2704   c  can comprise an about button  2702   a,  a photos button  2702   b,  a friends button  2702   c,  a write post  2702   d,  and a share photo  2702   e.    
     As is known in the art, the update info button  2706   a  can allow a user to update his information such as biographical information; the activity log button  2706   b  can link to a list of activities; the more button  2706   c  can allow a user to see more options; the about button  2702   a  can allow another user to see more information about a user; the photos button  2702   b  can comprise photos of a user; the friends button  2702   c  can comprise a list of friends; the write post  2702   d  can comprise a link to write a new post; and the share photo  2702   e  can comprise a menu to share photos. 
       FIG. 28  illustrates a flow chart view of a composite message sharing method  2800 . 
     In one embodiment, said composite message sharing method  2800  can comprise said first step  2802   a,  said second step  2802   b,  said third step  2802   c,  said fourth step  2802   d,  said fifth step  2802   e,  said sixth step  2802   f  and said seventh stem  2802   g.    
     The composite message sharing method  2800  can describe a procedure for implementing and sharing the composite message  802 . First, the system can receive a selection of two or more messages in a conversation; then, ask whether the user wants to set an expiration; then receive a list of recipients; then, ask if the user wants to add an introduction; then, ask if the user wants to limit resharing; and finally to delete the message when the expiration condition is reached. 
     In one embodiment, the fourth step  2802   d  can comprise either receiving a list of recipients or a post instruction. That is, that the messaging application  820  can receive an instruction to send the composite message  802  to individual users and/or to the news feed screen  2300  for general consideration by all users. 
     In one embodiment, composite message sharing method  2800  comprises one embodiment of sharing said composite message  802  but other methods are disclosed herein. 
       FIG. 29  illustrates view of a data object  2900 . 
     In one embodiment, said data object  2900  can comprise said share event document  2902  and said messages document  2904 . 
     In one embodiment, said improved messaging system  100  can comprise said data object  2900 . 
     In one embodiment, improved messaging system  100  can create and manage data object  2900  for selectively sharing portions of plurality of messages  602  between plurality of users  650 . 
     In one embodiment, said first user  601   a  can create composite message  802  with first mobile device  610   a,  send said composite message  802  to said server  108 . Said server  108  can process said composite message  802 , and send a portion of said plurality of messages  602  to said second user  601   b  on said second mobile device  610   b  according to sharing limitations  1852  established by first user  601   a  on said first mobile device  610   a.    
     In one embodiment, said second user  601   b  can receive a first portion of composite message  802  (such as share event document  2902 ) and retrieve a second portion of composite message  802  (such as messages document  2904 ) at the time said messages document  2904  is to be read on second mobile device  610   b.  Accordingly, content being shared under limitation is only delivered to said second mobile device  610   b  provide said sharing limitations  1852  are not engaged. 
     As illustrated, share event document  2902  can comprise references to messages 2 and 3, and messages document  2904  can comprise the contents of messages 2 and 3. Here, we refer to the unique identifiers (message ID  1102 ) for messages 2 and 3. Further, said share event document  2902  when delivered to second mobile device  610   b  can remove any portions which are marked as “Omit” in condition  1308 . Accordingly, server  108  manage portions of share event document  2902  seen by one or more among said plurality of users  650  and portions subject to sharing limitations  1852  such as messages document  2904   
     The following sentences are included for completeness of this disclosure with reference to the claims. A composite message sharing method for sending and sharing of a composite message between a plurality of computers over a network by packaging up a portion of a plurality of messages into said composite message and managing access to said composite messag   d ¥    d±    1/9 providing a device application, comprising a messaging application, on said plurality of computers belonging to a plurality of users, wherein, each among said plurality of computers comprise at least a processor, a memory and a communication hardware, said device application is executed in said processor of said plurality of computers, and a portion of said plurality of messages and/or said composite message are transmitted with said communication hardware. providing a server application on said server. configuring said plurality of computers and said server to communicate with each other over said network. sending and receiving a portion of said plurality of messages between said plurality of computers, comprising a first computer comprising said device application and a second computer comprising said device application, by sending said portion of said plurality of messages from said device application of said first computer to said server application through said network, and sending a portion of said plurality of messages from said server application to said device application of said second computer through said network. creating said composite message from a portion of said plurality of messages with said device application on said first computer by creating a data object from said portion of said plurality of messages, wherein said data object comprises a portion of said plurality of messages selected, filtered and/or omitted on said first computer, said data object comprises references to said portion of said plurality of messages, said plurality of messages are stored on said server and selectively shared with said second computer according to a sharing limitations associated with said composite message, and said second computer retrieves said portion of said plurality of messages if or when reading said composite message. including a portion of a message metadata belonging to said plurality of messages in said composite message. processing said composite message on a processor on said server with said server application, said server comprising said processor, a memory and a communication hardware, and said plurality of messages are transmitted with said communication hardware of said server. wherein said plurality of computers and said server create said composite message by packaging up a portion of said plurality of messages into said composite message and managing access by said sharing limitations at said server. providing a plurality of system database tables for managing data related to said composite message sharing method comprising at least a user Table for managing data related to said plurality of users, a messages Table for storing said plurality of messages, a share Conditions for cross referencing said composite message holding said plurality of messages in said data object. compiling a data object from a portion of a plurality of system database tables according to inputs on a first computer including a sharing limitations. providing for privacy and confidence for a plurality of users by allowing a composite message to be retracted by opening said composite message in a device application on a first computer, retracting access to said composite message with a retract button, sending retraction signal to a server. limiting access to said composite message and corresponding a plurality of messages after said retract button has been selected. verifying the veracity of a plurality of messages being shared in a composite message as between a plurality of users by including a message placeholder for messages marked as omitted in a sharing limitations. verifying the veracity of a plurality of messages being shared in a composite message as between a plurality of users by restricting editing of said plurality of messages within said composite message. filtering a portion of said plurality of messages according to 1152/ comprises setting a data field comprising a resharing related to said composite message with said first computer, sending said composite message to said server along with a date Expiring, and selectively providing portions of said plurality of messages associated with said composite message to said second computer according to said date Expiring. preventing sharing of a composite message with a third computer when a resharing is set to true. filtering a portion of a plurality of messages according to 1152/ comprises setting a data field comprising a date Expiring related to a composite message with a first computer, sending said composite message to a server along with said date Expiring, and selectively providing portions of said plurality of messages associated with said composite message to a second computer according to said date Expiring. storing said message metadata from a portion of said plurality of messages in said composite message. A message metadata comprises data fields selected among a date Sent, a date Received, a attachment, a sender, and a recipient. processing a composite message into a data object with  108 , wherein said data object is further broken down into a share event document and a messages document. structuring said share event document and said messages document to be read as the entire contents of said composite message. moving portions of said composite message subject to a sharing limitations into said messages document. storing references to said messages document in said share event document. serving a portion said share event document to a second computer as an indication of the contents of said composite message. requesting said messages document by said second computer from a server at the time of reading said composite message with said second computer. selectively serving said messages document to said second computer according to said sharing limitations. A composite message sharing method being computer-implemented for sending and sharing of a composite message between a plurality of computers over a network by packaging up a portion of a plurality of messages into said composite message and managing acce   d     d:     1/9  d     displaying a device application, comprising a messaging application, on said plurality of computers, wherein, each among said plurality of computers comprise at least  304   a,  a memory and  308   a,  said device application is executed in a processor of  102 , and a portion of said plurality of messages and/or said composite message are transmitted with a communication hardware. providing a server application on said server, wherein said server application is configured to manage access to portions of said composite message between said plurality of computers. communicating said plurality of messages and said composite message between said plurality of computers and said server over said network. sending and receiving a portion of said plurality of messages between  102 , comprising a first computer comprising said device application and a second computer comprising  502 , by sending said portion of said plurality of messages from said device application of said first computer to said server application through  106 , and sending a portion of said plurality of messages from said server application to said device application of said second computer through said network. creating said composite message from a portion of said plurality of messages with said device application on said first computer by creating a data object from said portion of  602 , wherein said data object comprises a portion of said plurality of messages selected, filtered and/or omitted on  102   a,  said data object comprises references to said portion of  602 , said plurality of messages are stored on said server and selectively shared with said second computer according to a sharing limitations associated with  802 , and said second computer retrieves said portion of said plurality of messages if or when reading said composite message. including a portion of a message metadata belonging to said plurality of messages in said composite message. Automatically processing said composite message on a processor on said server with  506 , said server comprising  304   d,  a memory and  308   d,  and said plurality of messages are transmitted with a communication hardware of said server. wherein said plurality of computers and said server create said composite message by packaging up a portion of said plurality of messages into said composite message and managing access by said sharing limitations at  108 . providing a plurality of system database tables for managing data related to said composite message sharing method comprising at least a user Table for managing data related to a plurality of users, a messages Table for storing a plurality of messages, a share Conditions for cross referencing a composite message holding said plurality of messages in a data object. A non-transitory computer readable medium with computer executable instructions stored thereon executed by a processor to perform a composite message sharing method for managing a composite message. providing  502 , comprising  820 , on a plurality of computers belonging to  650 , wherein, each among said plurality of computers comprise at least  304   a,  a memory and  308   a,  a device application is executed in a processor of  102 , and a portion of a plurality of messages and/or said composite message are transmitted with a communication hardware. providing a server application on a server. configuring said plurality of computers and said server to communicate with each other over a network. sending and receiving a portion of said plurality of messages between  102 , comprising a first computer comprising said device application and a second computer comprising  502 , by sending said portion of said plurality of messages from said device application of said first computer to said server application through  106 , and sending a portion of said plurality of messages from said server application to said device application of said second computer through said network. creating said composite message from a portion of said plurality of messages with said device application on said first computer by creating a data object from said portion of  602 , wherein said data object comprises a portion of said plurality of messages selected, filtered and/or omitted on  102   a,  said data object comprises references to said portion of  602 , said plurality of messages are stored on said server and selectively shared with said second computer according to a sharing limitations associated with  802 , and said second computer retrieves said portion of said plurality of messages if or when reading said composite message. including a portion of a message metadata belonging to said plurality of messages in said composite message. processing said composite message on a processor on said server with  506 , said server comprising  304   d,  a memory and  308   d,  and said plurality of messages are transmitted with a communication hardware of said server. wherein said plurality of computers and said server create said composite message by packaging up a portion of said plurality of messages into said composite message and managing access by said sharing limitations at said server. 
     Various changes in the details of the illustrated operational methods are possible without departing from the scope of the following claims. Some embodiments may combine the activities described herein as being separate steps. Similarly, one or more of the described steps may be omitted, depending upon the specific operational environment the method is being implemented in. It is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the above-described embodiments may be used in combination with each other. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.”